
Industry
Part of Stakeholder influence: who can stop your work and who hears it first
Stakeholder influence signs, from subtle to obvious
Stakeholder influence signs that your map has a hole in it, read from calendars, threads and documents rather than from how anyone seems to feel.
A map with a missing name looks exactly like a complete one. Nobody announces that they were left off, because until the decision lands they do not know a decision is being made. So the warning has to be read somewhere other than people's reactions. It leaves marks in the ordinary artifacts of the work.
Eleven of those marks are below. None requires you to interpret a mood.
What to take away
- Every sign here is a fact you can check in a calendar, a thread, a document history or a queue. If a sign needs you to read a face, it is not on the list.
- Two signs are worth acting on immediatelyan approval that keeps being described as a formality, and a question that arrives from three unconnected people in a week.
- A sign tells you to ask one question, not to redraw the whole map. The question is nearly always some version of who else this lands on.
The eleven
1. The same question arrives from unconnected people. Three people in different parts of the organization ask you roughly the same thing in a fortnight. They are not coordinating. They are each downstream of something you changed and none of them has been told.
2. An approval keeps being called a formality. Anyone describing a sign-off as a rubber stamp is telling you they have not spoken to the person who signs. A formality that has never been tested is an untested veto.
3. A name appears in a document that is not on your list. Someone has been added to a distribution, a review, or a comment thread by a person closer to the work than you are. They put that name there for a reason. Ask what it was.
4. You cannot say what one person on the list stands to lose. If the sentence "this costs them..." will not finish, either they do not belong on the map or you have not found their stake yet. Both matter and the second is dangerous.
5. The meeting that keeps being rescheduled is always the same one. A conversation that will not happen is usually a conversation somebody is not ready to have. It is the one to hold one to one, this week, in a smaller room.
6. A team keeps being represented rather than present. Their manager speaks for them each time. That works until the point where the cost lands on the people who were never in the room, and the manager is not the one who will absorb it.
7. Somebody answers questions about a system nobody credited them with owning. The person who actually knows how the thing runs is often two levels below the person listed as owning it. That gap in who knows what is where late objections come from, and it is invisible on any chart.
8. The external side of the work has no name against it. Customers, suppliers, regulators and partner teams are the stakes most often left off, because the map was drawn from an internal structure. If nobody is listed, nobody has asked whether anyone outside has been told.
9. Your list is drawn from a distribution group. A group address is a communications artifact. It has no relationship to who is exposed, and building a map from it guarantees you have both extra names and missing ones.
10. Nobody has asked you what it costs them. Real stakeholders ask about the cost early, because the cost is what they are exposed to. A round of consultation in which nobody raised a cost is a round in which nobody who had one was present.
11. The list has not changed in two months. Roles move, budgets shift, a gatekeeper becomes a decider. A map that has been stable through a reorganization is stale rather than settled.
Where each sign points
| Sign | The artifact it lives in | The question it earns |
|---|---|---|
| Repeated question from strangers | Your inbox | Who consumes what this produces? |
| Approval called a formality | The plan | Has anyone spoken to the signer? |
| Unexpected name on a thread | Document history | Who added them, and why? |
| Unfinished cost sentence | Your own notes | What changes for this person? |
| The meeting nobody holds | The calendar | What is being avoided? |
| Represented, never present | Attendee lists | Who absorbs this in practice? |
| Unlisted system owner | Support queues | Who actually operates it? |
| No external name | The map itself | Has anyone outside been told? |
| List built from a group address | The distribution list | Which of these has exposure? |
| No cost questions raised | Meeting notes | Was anyone exposed in the room? |
| A map that never changes | Version history | What has moved since? |
The pattern in the middle column matters more than any individual row. Every one of these is checkable without asking a person how they feel about anything, which is what makes them usable on a bad week.
Signs and their artifacts
Sign
- Repeated question
- Inbox
- Called a formality
- The plan
- Unexpected name
- Document history
- Unfinished cost
- Your notes
- Meeting nobody holds
- Calendar
- Represented, never present
- Attendee lists
Artifact
- Repeated question
- Who consumes output?
- Called a formality
- Spoken to signer?
- Unexpected name
- Who added them?
- Unfinished cost
- What changes for them?
- Meeting nobody holds
- What is avoided?
- Represented, never present
- Who absorbs it?
Question
- Repeated question
- Called a formality
- Unexpected name
- Unfinished cost
- Meeting nobody holds
- Represented, never present
Why the artifacts are more honest than the people
The work leaves records because people route around problems, and those routes appear in systems.
A quiet handoff through a third person, a document with a comment from someone uninvited, and a queue that always holds one team's tickets are facts, not opinions. They show where the organization's real dependencies sit, often not where the chart says.
Conway's law is the same observation pointed at software: what gets built mirrors who actually talks to whom.
That difference is why reading signs matters. A map drawn from reporting lines maps permission, while a map drawn from artifacts maps exposure, and exposure makes someone a stakeholder.
The method for turning either into an ordered set of conversations is in stakeholder influence, and what a stake is, as against an interest, is in stakeholder influence meaning.
Two signs show how your position distorts what reaches you. If people call a sign-off a formality in front of you, or answer for a team instead of bringing it, position does that. See leadership influence.
Once you find a missed person, the conversation is a request to someone who owes you nothing. See influence without authority.
Common questions
How many signs before I stop and redraw the map?
One is enough to ask a question. Three in the same fortnight is enough to stop and redraw, and in practice they cluster, because a map with a hole tends to produce several of these at once rather than one in isolation.
Sign 3 says to chase names other people add. Is that not paranoid?
It is the cheapest source of information available to you. Whoever added the name knows something about the work that you did not, and asking them why takes one message. The paranoid version would be assuming a motive; the useful version is assuming knowledge.
Nobody has asked what it costs them and I think that is because it costs nothing.
Possible, and rare. Test it by naming a cost out loud to one person and watching whether they correct you. If a change genuinely costs nobody anything, either it changes very little or the cost has landed somewhere you have not looked, usually on whoever handles the exceptions.
What do I do when the person who really owns a system is junior and their manager objects to being bypassed?
Do not bypass. Ask the manager to bring them, and say why: you need the operating detail and you would rather have it from the person who has it. Framed as a request for accuracy rather than as a route around anyone, this is almost never refused, and the manager stays in the conversation where they belong.
Is a stale map actually a problem if nothing has gone wrong?
Nothing going wrong is not evidence. The failures caused by a stale map arrive at the end, when a person whose role changed finds out late. The check is five minutes: read the names, ask whether any of them have moved, ask whether anyone new has appeared.







