How to map decision-making in a small organisation

Most organisations have an org chart. Very few have an accurate picture of how decisions actually get made. The chart shows reporting lines. It does not show who gets consulted before a decision is announced, who can quietly block something, or which decisions get made in the corridor rather than the meeting room. Mapping the real decision structure is the first thing Quiet Cloud Rise does in any diagnostic engagement, and it is something any organisation can do for itself.

Start with a specific decision, not a general question ¶

Pick one decision that was made in the last three months. Not a trivial one, but not the most politically sensitive one either. Something mid-range: a change to a process, a hire, a budget reallocation. Ask everyone who was involved to describe, in writing, how that decision got made. Who proposed it? Who was consulted? Who approved it? Who was informed after the fact?

You will almost certainly get different accounts. That is not a problem. The differences are the data. They show you where the formal process and the actual process diverge, and they show you which parts of the organisation have different mental models of how authority works.

Draw the actual flow, not the ideal one ¶

Once you have the written accounts, draw a simple diagram of the decision flow as it actually happened. Use boxes for people or roles and arrows for information or approval flows. Do not try to make it look like the org chart. Let it be messy if it is messy.

The most common finding at this stage is that decisions pass through more people than necessary, or that one person is a bottleneck for a category of decisions that does not obviously require their involvement. Both of these are fixable, but you cannot fix them until you can see them.

• Who proposed the decision?
• Who was consulted before it was made?
• Who gave final approval?
• Who was informed after the fact?
• Who could have blocked it but did not?

Look for the informal veto ¶

In most organisations there is at least one person whose approval is not formally required but whose objection would stop a decision from moving forward. This is not necessarily a problem. Sometimes that person holds important knowledge or represents a constituency that needs to be heard. But it is worth knowing who they are and why they hold that position.

If the informal veto is held by someone whose involvement adds genuine value, the fix is to formalise their role so the process is transparent. If it is held by someone whose involvement is a legacy of an older structure, that is a different conversation.

What to do with the map ¶

A decision map is not a deliverable in itself. It is a starting point for a conversation about whether the current structure is producing the outcomes the organisation wants. The most useful question to ask once you have the map is: which of these steps adds value, and which of them just adds time?

In most engagements, this question produces a short list of changes that are relatively easy to make: clarifying who owns a category of decision, removing a consultation step that duplicates another, or setting a time limit on the approval stage. The map makes those changes visible and defensible.

If you want to try this in your own organisation, start with one decision and one diagram. The method does not require a consultant. It requires honesty about what you find.