Stakeholder+ Mapping
Stakeholder+ Mapping is a stakeholder map in which each box carries two bubbles. Above the box, a speech bubble records what the stakeholder says about the team. Below it, a thought bubble records what the team believes the stakeholder has in mind: their worries and their expectations. One to ten people draw the map in 30 to 120 minutes. They read it through with questions about the attention each stakeholder needs, then review it about once a month. George W. Anderson describes the technique in Design Thinking for Tech (2023).
Goal
Stakeholder+ Mapping shows the state of each relationship between a team and its stakeholders: what each stakeholder says about the team and what the team assumes that stakeholder thinks.
The classic map shows who surrounds the team and how these people relate to one another. The bubbles add the state of each relationship. The team sees who criticises it, who supports it and whom it barely knows. Anderson expects the map to produce a decision: where the team spends its attention.
The deliverable is the map: the boxes, their bubbles, a colour code and labelled arrows between roles. The team reviews it about once a month. Two successive versions show who arrived, who left and which relationships changed.
Usage
When to use it
- New team or wider scope: locate the departments, partners and suppliers that surround the team.
- Complaints or escalations from a department: set what it says against what the team assumes about its reasons.
- Preparing a change: find the managers, sponsors and champions who will carry the change to the users.
- Programme with several projects: track the relationships between the teams and their stakeholders from month to month.
- Small team without tooling: one to ten people work on a sheet of paper with a pen.
- Remote team: an online whiteboard replaces the sheet.
- A team that talks openly about its relationships: the team writes in a bubble what a director holds against it.
- Direct contact with the stakeholders: the speech bubbles carry sentences heard in a meeting or read in an email.
When not to use it
- Large or anonymous population: nobody hears what thousands of customers say. Build personas or an empathy map per segment.
- Ranking by power and interest: the map points to priorities without a scale. Place each stakeholder on the stakeholder matrix.
Description
The base map and what the "+" adds
Anderson starts from the stakeholder map that teams have drawn for a long time under various names. It places the people and groups tied to the project and shows their hierarchy. Stakeholder+ Mapping keeps this map and adds two bubbles to each box.
Anderson compares the resulting map to an empathy map. It takes over that map's Says and Thinks zones. An empathy map describes one person or one segment from several angles. Stakeholder+ Mapping places all the stakeholders around one team and keeps two angles for each.
The team can colour each box. In his presentation of the technique, Anderson codes each person's satisfaction in red, amber or green. Elsewhere Anderson describes this code as a separate technique that applies to any map of people: Stakeholder Sentiment Mapping.
What each bubble carries
At step 5, the team writes in the speech bubble what it knows the stakeholder says. At step 6, it writes in the thought bubble what it believes the stakeholder thinks. The first is an observation: someone heard or read the sentence. The second is a hypothesis.
A useful speech bubble quotes a short sentence word for word and carries its date and its source: "Your requests arrive without notice" (email of 6 March). A team summary such as "he is against the project" is an assumption. It goes in the thought bubble.
The team records the source of each speech bubble: the meeting and its date, the email or the colleague who reports the sentence. A reported sentence stays in the speech bubble and names who passed it on: "reported by customer service". It counts as confirmed only when a team member hears it first-hand. Each thought bubble becomes a question for the next interview with the person. When the interview confirms the assumption, the sentence moves to the speech bubble with its source.
The gap between the two bubbles of one box is the most useful information on the map. A head of department says in committee that he supports the project. The team believes he is worried about his headcount. This gap marks the conversation the team needs to have with him.
Participants, duration and materials
Anderson plans for one to ten people and 30 to 120 minutes depending on how complete the map should be. One person alone can draw the map. The materials are a sheet of paper and a pen. Anderson advises starting from an existing stakeholder map and from personas or empathy maps when the team has them.
In a group, one person holds the sheet or the whiteboard. Each participant writes on sticky notes the bubbles of the stakeholders they deal with. The group discusses each thought bubble before sticking it on. Whoever works with a stakeholder every day knows what that stakeholder says. The others know the stakeholder's reputation.
The steps
The steps are Anderson's. The guidance that goes with them is our reading.
- Place the team. The team draws a box in the middle of the sheet and writes its name in it: the project team or the product team.
- Add the neighbouring teams. Around this box, it adds a box for each team or outside department it works with.
- Add the partners. It adds the business partners, external contractors and suppliers.
- Organise the map. It gives each box a relationship or a role: sponsor, internal client, supplier, approval authority.
- Write the speech bubbles. Above each box, the team writes in a bubble what it knows the stakeholder says about it. It notes the source beside each sentence.
- Write the thought bubbles. Below each box, the team writes in a bubble what it believes the stakeholder has on their mind: a worry, a hope, a concern. A box the team knows nothing about keeps its bubbles empty. An empty bubble signals that nobody on the team talks to this stakeholder.
- Colour-code. If colour helps and does not harm accessibility, the team colours the sets of stakeholders or distinguishes positive bubbles from negative ones.
- Make a clean copy. The team redraws the map once it has become messy. It circles the groups that matter most to its success. It gives similar roles the same colour, for example managers in red, business stakeholders in blue and key partners in green. It sorts the problems and difficulties it has noted. A list in the margin with one problem per line is enough.
- Link the roles. The team draws coloured arrows between similar roles in different groups. It labels the relationship on each arrow. For example, the team's architect and the operations architect share an arrow labelled "approves the hosting".
Reading the map
The team reads the finished map with Anderson's questions:
- Who matters most? Who has the most influence? Who is missing?
- Who does the team need to give more attention to?
- Who must the team handle with care?
- Who does it need to communicate with more or less?
- Who matters for its day-to-day work?
- Who matters for its future?
Anderson works through some of these questions with the power-interest grid. This grid is the stakeholder matrix. An answer changes the relationship when it becomes a dated action with an owner. The action can be an interview to schedule, a recipient to add to the monthly report or a box to create for the missing person.
Reviewing the map every month
- 1Software vendor: the role changes from supplier to maintenance provider. The thought becomes "Hopes for a maintenance contract".
- 2Customer service: joins the map as the go-between for the fiduciary firms.
- 3Cantonal IT department: satisfaction moves from low − to medium =.
- 4Contributions department: the thought "Fears double data entry during the transition" becomes the speech "We do not want to enter data twice." (interview on 2 April).
- 5Data protection advisor: speech "Send me the impact assessment." (interview on 28 March). Satisfaction moves to medium =.
Anderson asks the team to revisit the map about once a month. A stakeholder map changes with arrivals, departures, promotions, new projects and shifting interests. The review takes about thirty minutes. The team that drew the map lays the previous version beside the updated one and compares it with the situation: who arrived or left, who changed role. It then decides what it must do differently. Anderson adds reflection questions:
- What problems is the team still trying to solve?
- Has its strategy for solving them changed?
- How does the team define success and how does it measure it?
- How will the team be different tomorrow and why does that difference matter?
- Which stakeholders should the team add to the map? Which should it remove?
- Can the team strengthen the shared sense of belonging with its stakeholders?
The team keeps each dated version. Two versions side by side show what a single map hides: a stakeholder who moved from dissatisfied to neutral, a confirmed assumption that leaves the thought bubble for the speech bubble.
The neighbouring techniques
| Technique | What it produces | Link with Stakeholder+ Mapping |
|---|---|---|
| Stakeholder list | The register of who is concerned, in what capacity and with what authority | Supplies the boxes for steps 2 and 3. |
| Stakeholder matrix | Each stakeholder placed by power and interest | Ranks the stakeholders. Anderson uses it to answer the questions asked when reading the map. |
| Empathy map | What a person says, thinks, does and feels | Lends its Says and Thinks zones to the bubbles. |
| Stakeholder Sentiment Mapping | Each stakeholder's satisfaction shown in colour or by an icon | Is the same red, amber and green satisfaction code. Anderson also applies it to the Stakeholder+ map. |
| Verbatim Mapping | Statements recorded word for word and grouped by theme | Feeds its clusters of verbatims into the speech bubbles. |
Pitfalls
The difficult stakeholder the team avoids. Anderson reports the case of a global insurer. Almost every team avoided a manager who treated others with contempt. Major use cases surfaced after delivery. The team had to fit them into a solution that was already live. The pitfall shows on the map as a dissatisfied box with empty or old bubbles. The question "who must the team handle with care?" calls for a contact plan, never a workaround.
The assumption read as a fact. A thought bubble written with confidence reads as information. Two months later nobody remembers that it rested on an impression from a corridor conversation. The team marks each thought bubble as a hypothesis.
Two colour codes on one map. Step 7 colours sets of stakeholders or the negative and positive bubbles. Step 8 colours the roles: managers in red in Anderson's example. His presentation of the technique colours satisfaction in red, amber and green. A red box becomes ambiguous: it can mean a manager or a dissatisfied stakeholder. The team keeps colour for one meaning and carries the other with a shape or a word. Colour alone also shuts out colour-blind readers. Anderson acknowledges this and proposes emojis instead.
The map that circulates. The thought bubbles attribute worries to named people. A person who discovers on the map what the team thinks of them takes it as a judgement on them. The team keeps the map in its own workspace. When it needs to share something, it shares the stakeholder list or a copy of the map without the bubbles.
The one-day map. A map that nobody revisits describes the organisation on the day of the workshop. Anderson points out that any stakeholder map changes over time. The team sets the date of the next review at the end of the session.
AI considerations
A language model prepares the base map. From the organisation chart, the project charter and the list of contracts, it proposes the boxes for steps 2 and 3 and their roles. The team adds what no document names: the informal go-betweens and the department the team consults once a year.
The model also feeds the speech bubbles. It extracts each sentence a stakeholder has said about the team from minutes, emails and tickets and records its date and source. It groups the sentences by theme. The team rereads each sentence in its context. A truncated quotation changes meaning.
The thought bubbles stay with the team. A model infers a mood from the tone of an email and states it with the confidence of a fact. It knows nothing of the history of the relationship, the tensions between departments or what is said outside the documents. The team treats a thought bubble that the model proposes like any other: as a hypothesis to check.
The map holds personal data: names, quotations and assumptions about the state of mind of identifiable people. In a small organisation, a role points to one person. A team that replaces names with roles therefore does not anonymise the map. It submits the map only to an AI service that the organisation has approved.
Examples
The map shows the state of a team's relationships on the day of the workshop. The employer portal team of a cantonal OASI compensation office drew it on 13 March.
When the team reads the map, it turns the contrast in the contributions department's box into an action. The project manager shows the head of the department the data migration plan before the end of March.
Visualisations
The diagram of one box shows where the two bubbles sit and what each one receives. The example map shows a complete deliverable. The two monthly versions show what a review changes. The table of neighbouring techniques places Stakeholder+ Mapping among the stakeholder maps.
Cost
| Dimension | Level | Justification |
|---|---|---|
| Preparation | Low | A sheet of paper, a pen and the existing stakeholder list. |
| Execution | Medium | 0.5 to 20 person-hours per session depending on the group and how complete the map should be, then 30 minutes of team time per monthly review. |
| Documentation | Medium | One dated version per month and the source of each speech bubble to keep up to date. |
Tooling
Anderson calls for a sheet of paper and a pen for one person working alone. A whiteboard with sticky notes serves a group in a room: each bubble moves without the team redrawing the map. An online whiteboard (Miro, Mural) serves a remote team and keeps the successive versions. A diagramming tool (draw.io, Visio, Lucidchart) produces the clean copy of step 8. The stakeholder register supplies the starting boxes.
Sources
- George W. Anderson, Design Thinking for Tech: Solving Problems and Realizing Value in 24 Hours, Addison-Wesley, 2023. Hour 7 "Connecting with the Right People", section "Design Thinking in Action: Stakeholder+ Mapping", pp. 91-93: the definition, the participants and the duration, the nine steps, the questions for reading the map and the monthly review. Same chapter: the note "Keep It Alive!", the section "Design Thinking in Action: Stakeholder Sentiment Mapping" (p. 100) and the section "What Not to Do: Stick to the Happy Path". Hour 3 "Design Thinking for Small Audiences", section "Learning More Quickly": the prerequisites and the red, amber and green satisfaction code. Hour 9 "Identifying the Right Problem": the verbatims fed into the speech bubbles. Hour 23 "Making Change Sticky": the map as a tool for change awareness.
According to the caption of Anderson's Figure 7.3, the technique adds speech and thought bubbles to a classic stakeholder map. Anderson pairs it with a colour code and a monthly review. Everything not attributed to Anderson is our reading: the compensation office case, the rule on sources and go-betweens in the speech bubbles, the facilitation guidance, the format of the monthly review and four of the five pitfalls.

