Stakeholder mapping
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
identify everyone who can shape or block the Larkspur solution and rank them by influence and interest.
Planned topics
- A stakeholder is anyone who decides, pays, builds, operates, secures, or lives with the result: business, engineering, security, operations, vendors, and store staff.
- Map each on two axes: influence (can they stop or change this?) and interest (how much does it affect them?).
- High influence and high interest: manage closely. High influence, low interest: keep satisfied. Low influence, high interest: keep informed.
- The sponsor is one stakeholder, not the map. Quiet, high-influence people (the ERP owner, the security lead) are the ones that surprise projects.
- A map is a working document: it changes when people change roles.
Draft outline details
Demonstration
a grid for Larkspur: CFO (sponsor), head of e-commerce, head of store operations, CISO, ERP team lead, payment vendor account manager, store managers; each placed in a quadrant with one line on what they want.
Check your understanding
Which quadrant holds a security lead who rarely attends meetings but can block go-live?
Show answer
High influence, lower interest: keep satisfied, and move toward closely managed.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.