Organizational Design
The stakeholder map: who decides, who advises, who's told
Sort every project into three circles: a core team that decides, experts consulted on request, and everyone else informed. Then publish the map.
A stakeholder map organizes everyone touching a project into three circles by level of involvement and authority. The inner circle does the work and owns the outcome, the middle ring advises on request, and everyone else is informed. It is the cheapest governance fix available for CX programs that stall because nobody knows who decides.
A stakeholder map sorts everyone touching a project into three circles. The inner circle is the core team: the CX lead, product owner, and lead engineer who do the daily work and own the outcome. The middle ring is consulted for expertise on request: contact-center agents who hear unvarnished customer complaints, accessibility specialists before the first wireframe exists, legal counsel on data. Everyone else is informed through updates and results. That is the whole tool, and it cures a familiar disease: projects where nobody can say who decides, where open-invite workshops replace research with group guessing, and where overlapping responsibilities grind morale and delivery to a halt.
Why it matters to the business
Blurred accountability is the quiet killer of CX programs. Forrester finds fewer than one-third of companies create shared accountability for journey performance, and Gartner's 2021 survey found 83% of organizations struggle to use journey maps to identify and prioritize CX efforts. Those are governance failures, not method failures: artifacts get produced, but no named circle of people owns the follow-through. A published stakeholder map fixes that before the first meeting.
The map also protects delivery by surfacing resistance early. Sales worries about commissions. Engineering worries about velocity. Left unnamed, those detractors stall projects mid-flight, when delay is most expensive.
How to use it
- Draw the three circles for your top CX initiative this week, with named people, not departments.
- Restrict the inner circle to the people accountable for the outcome: CX lead, product owner, lead engineer.
- Book the middle ring deliberately: frontline agents for customer intelligence, accessibility before wireframes, legal on data governance.
- List likely detractors and meet each one before kickoff, not after they object.
- Publish the map so every team knows which circle it occupies and why.
- Re-check the map at every phase gate, because roles drift as projects grow.
Where teams get it wrong
They democratize the inner circle. Wanting to seem inclusive, they invite everyone into research and design decisions, and expertise gets outvoted by opinion. CX decisions belong to people qualified to hold a professional CX role, the same way you would not crowdsource your legal strategy. Inclusion belongs in the informed ring, through honest and frequent communication, not in the decision room.
Ask your team
- For our top CX initiative, can everyone in this room name the same accountable owner?
- Which decisions last quarter were made by workshop vote rather than evidence?
- Who are our likely detractors, and who has spoken with them this month?
Do not democratize the inner circle.
Apply this
Reading about the stakeholder map: who decides, who advises, who's told is one thing. Seeing where it applies in your journey is the useful part.