When the Organisation Waits on One Person

← Playbooks

Playbook · Recurring concentration of decisions · Psychology × Organisations

Decisions concentrate on whoever the system does not absorb them for. This is a way to examine what is actually concentrating, before concluding that more delegation is the answer.

This is reusable guidance, not a record of what happened and not a procedure. It is a starting point for a situation that recurs in different forms — useful while its conditions hold, and worth abandoning where they do not.

The situation

As the organisation grows, unabsorbed decisions accumulate on one or two people faster than their time. Work waits on their attention. Delegation has been attempted and partly reverted, usually after a decision went badly.

The question

Which decisions genuinely require this person, and which are here because nothing else holds the context?

Conditions

What needs to be true, or examined, before this approach applies.

• The concentration is structural rather than a temporary period of intensity.
• The context these decisions need can be made available to someone else.
• There is willingness to accept different decisions, not only faster ones.
• The consequences of a delegated decision going wrong are survivable.

Signals

What is worth paying attention to.

• What is waiting, and specifically what it is waiting for.
• Which decisions were delegated and quietly returned, and what happened just before.
• Whether people ask for a decision or for cover.
• How often the answer given is one anyone with the same context would have reached.

Decisions

What may need to be decided, and by whom.

• Which decisions must stay, which need only awareness, and which should not arrive at all.
• What context has to travel with a decision for someone else to hold it.
• What happens when a delegated decision is made differently than it would have been.
• How the split is reviewed as the organisation changes.

A first useful move

Record every decision that reaches this person for two weeks and sort it into must decide, should know, should not arrive. The sort is more informative than any framework, because it shows what the system is failing to absorb.

Not yet

Do not hire a layer of management to absorb decisions before knowing which decisions those are. Do not announce a delegation model that will be reverted the first time an outcome disappoints — reverted delegation is harder to attempt twice.

The trade-off

Distributing decisions recovers attention and reduces coherence, because decisions previously made by one mind now reflect several. Some of the speed attributed to concentration was actually consistency.

Assumptions

What this rests on, and what would change it.

What informed this

Observation in founder-led organisations, and reasoning about how decision load accumulates. Qualitative and self-reported; no claim is made that recovered attention produced particular results.

What would change this approach

This changes where authority is legally or contractually held by one person, where the organisation is too small for a decision to have anywhere else to go, or where concentration reflects a trust problem. Trust is not addressed by a queue.

Where this stops being useful

It does not help where the person concerned does not want the decisions to move, and it says nothing about whether their decisions were good. It addresses load, not judgement.

Related

Related reading

Industry

• D2C
• Consumer Brands
• Enterprise SaaS

Knowledge · Architecture

• Keeping the reasoning outside the tools that produced it
• Separating decision cadence from delivery execution

Evidence · Observed Situation

• When routine decisions were being escalated because no system carried the context
• When unrelated frustrations turned out to share one structural cause

The situations linked above informed this guidance. They do not establish that it transfers to another environment — that remains a question about the specific organisation.

Knowledge →Work with Cralgo →