Systems & Organizations
The Shadow Role Board That Stalls Momentum
Give someone approval rights without the standing to use them loosely, and they will use them tightly.
2026-09-081 min read
Spreading approval authority is supposed to remove a bottleneck. A senior owner is the only person who can sign off, the queue backs up behind them, so a second person is granted the same rights. The mechanism that makes this fail is not incompetence. It is that approval authority and the standing to spend it are separate things, and only one of them transfers. A new approver who has no track record to draw on protects the one thing they do have, a clean record, and the cheapest way to protect it is to say not yet.
The behaviour compounds in a specific direction. Requests that would have been waved through now come back with a question attached, because a question costs the approver nothing and a mistaken approval costs them everything they have built so far. The original owner, reading the delegation as complete, stops watching. Nobody is left who has both the authority to approve quickly and the standing to absorb being wrong. The queue the change was meant to drain refills, but now it refills with items nobody is willing to end.
The second-order cost is cultural rather than mechanical. A team learns what gets approved by watching what gets approved, and a cautious approver teaches caution faster than any policy document. Within a few cycles the requests themselves get smaller, because people stop submitting the ones they expect to be questioned. At that point the delay is invisible: the queue looks healthy, approvals are fast, and the ambitious work simply never enters the system.
Key insights
Approval rights transfer instantly; the standing to be wrong and survive it does not transfer at all.
A new approver's cheapest defence is delay, so delegation biases the whole system toward caution.
When the original owner withdraws entirely, nobody retains both the speed and the cover to move fast.
Why it matters
Delegating authority without transferring standing produces a more cautious system than the bottleneck it replaced.
The failure is invisible in the metric you would use to detect it, because approval latency improves as the requests get more timid.
Use this tomorrow
1Take the last twenty approvals in your queue and count how many came back with a clarifying question first, comparing the rate for your newest approver against your longest-serving one.
2Ask your newest approver to list every request they delayed last week, then count how many were delayed for a reason about the request rather than about their own uncertainty.
Go deeper
High-reliability organisation research, particularly Weick and Sutcliffe's Managing the Unexpected, describes deference to expertise: decisions migrate to whoever knows most about the situation, regardless of rank. A shadow approval board looks like this and inverts it. Authority migrates on a schedule rather than toward knowledge, and the person receiving it is chosen for their need to learn rather than for what they already know. The practice can still be worth running, but it is a training programme wearing the costume of a bottleneck fix, and the two have different success conditions.
The usual remedy, writing clearer approval criteria, treats the problem as informational when it is reputational. A new approver who knows the criteria exactly will still hesitate at the boundary, because the cost of a wrong yes and the cost of a wrong no are not symmetric for them. What changes the behaviour is making a wrong yes survivable: the original owner publicly co-signing a reversal, or an explicit rule that approvals can be undone within a fixed window without a post-mortem. Reversibility is cheaper to grant than judgement is to build, and it addresses what the new approver is actually protecting.
