A practical map of who really shapes decisions in your company
Org charts show who has authority. This framework shows who holds influence, where it sits, and which individuals your plans quietly depend on.
Every organisation has two charts. The first shows who reports to whom. The second, which almost nobody draws, shows who gets asked before a decision is made, whose objection stops a plan, and which person everyone phones when the system fails on a Friday afternoon. This framework is for the second chart. It gives you a way to sketch it, check it against what actually happens, and use it to plan change without walking into a dependence you did not know existed.
The framework is for the leader who suspects that the formal structure is no longer where decisions get made, and for the change team that has been surprised by an objection it never saw coming. It does not need special software or a survey firm. It needs a notebook, a few conversations, and the willingness to write down what you hear, including the parts you would rather not hear.
Chapter one: Pillar one: Who is consulted before a decision
Start with a recent decision that mattered: a price change, a senior hire, a supplier switch. Ask the person who made it to list everyone they spoke to before they committed, in the order they spoke to them. Then ask those people who they spoke to. The result is rarely the chart on the wall. A sensible test is to compare the consultation list with the formal approval route. Where a name appears in the consultation but not in the approval, you have found an influence point. Where a formal approver appears nowhere in the consultation, you have found a signature without a conversation behind it, and that usually slows things down later.
Keep the exercise to five or six decisions. Ten is more than most leaders need, and the later ones tend to repeat the names from the first few. Note the date of each decision. Influence shifts after reorganisations, departures and budget rounds, so a map drawn two years ago will mislead you about who matters now.
Write the map on one page, with a line for each influence point. Use three columns: the person, the decisions in which they were consulted, and the formal role they hold. The gaps between the columns are the useful part. A person who appears in every consultation and in no formal role presents a different management problem from a director who approves everything and is consulted on nothing. Both are worth knowing, and neither is visible on the organisation chart.
Chapter two: Pillar two: Who reverses or delays a decision
Influence is also visible in what gets undone. Pull a list of the last year's decisions that were reversed, delayed or quietly reworked. For each one, identify who raised the objection that changed the outcome, and whether that person held any formal role in the decision. Expect a small number of names to recur. Those people are usually holding something the decision-makers did not check, such as a contract term, a customer history, or a plant's maintenance record.
Record the reason, not only the name. A reversal caused by a missing fact is a different kind of influence from one caused by a close relationship with the chief executive. Both matter, but they call for different responses. The first needs better information flow into the decision. The second needs a frank conversation about how decisions are actually made, and who is allowed to make them.
Chapter three: Pillar three: Who holds the context
Some people have little formal power and a great deal of memory. They know why the pricing rule exists, which customer complaint started the warranty policy, and which system breaks if someone touches a particular field. Ask each team which colleague they would call first to understand how things really work. Count the answers. The person named most often is often not on the executive team, and is frequently the first person a change plan forgets to consult.
Treat these people as a separate category on the map. Their support rarely changes a decision, but their opposition can stop an implementation. Plan to brief them early, and give them the reasoning behind the change, not only the outcome. A briefing that arrives after the announcement is read as a courtesy, and courtesies are seldom enough to keep a plan on track. Check, too, who they report to. If that line runs through the same executive, one conversation with that executive may do more than a dozen with the holders themselves.
Redraw the map after any reorganisation, departure or large budget round. Those are the events that move influence fastest, and they are the events most often missed. When you finish the first version, set the date for the next redraw in the same meeting. A map that nobody owns goes stale within a year.
Chapter four: Pillar four: Where dependence sits in one person
This is the pillar that justifies the rest. For each influence point you have found, ask what would happen if that person were absent for a month. If the answer is that a decision stalls, a customer goes unanswered, or a site stops, you have a single point of dependence. Write down the name, the function it protects, and the nearest person who could cover it. Where no cover exists, record the gap on the risk register, and give it the same review a key supplier would receive.
Not every dependence is a problem. A specialist who is the only person able to read a legacy system may be the right person to hold that knowledge, provided the organisation is funding a successor or a second reader. The test is whether the dependence is known, costed and reviewed, not whether it exists. An unknown dependence is the one that surfaces during a resignation or an illness, when there is no time to plan.
Reduce dependence by making knowledge travel. Pair the holder with a second person on live work, not on a handover document written in a hurry before a leave. Rotate the first call on recurring problems. Expect some resistance. The arrangement can feel like recognition to the person at its centre, and a request to share the work may be heard as a criticism. Raise it as an operational question about continuity, not as a judgement on anyone's performance.
Before you start a change, check the map
Answer each question from the map you have drawn. Any no is a reason to plan earlier and to brief the named people in person.
- Have you traced your last five significant decisions to the people consulted, not only the
- Does every name on a consultation list appear on the formal approval route, or is the gap
- Have you pulled last year's reversed or delayed decisions and recorded who changed the out
- Do the people who hold organisational context appear on your change plan, with a named bri
- Can you name a cover for every single point of dependence on the map?
- Would the plan still work if your three most-consulted people were unavailable for a month
- Is the map dated, owned by a named person, and scheduled for its next redraw?
Outgrace checklist
Where it breaks
The framework fails in three predictable ways. The first is treating the map as a list of people to manage. It is a picture of how information and objections move, and the people named on it are not targets. The second is drawing it alone. A map drawn by the chief executive will show the executive team talking to itself, and will miss the operations lead who decides what actually happens on the floor. Build it with two or three colleagues from different levels. They will disagree about some of the names, and that disagreement is useful, because it marks the places where your understanding is weakest.
The third failure is keeping the map secret. Influence networks are informal, but the findings should not be hidden. If people learn that they have been mapped and the document is kept from them, the exercise starts to look like surveillance, and interviewees stop answering honestly. Tell the organisation what you are doing, why, and what you will change as a result. A short note to staff, setting out the purpose and the limits, is usually enough. Where the work touches personal data or performance records, put the method to your HR and legal advisers before you collect a single name.
On Monday, pick the decision your team made most recently that someone later reversed. Trace who was consulted, who objected, and who held the knowledge that was missing at the time. Write those three answers on one page, and against each name, write the function that would stall without that person. That page is the start of the map. It is also the first honest list of where your organisation is exposed, and it takes an afternoon to produce.