When organizations feel slow, the usual explanations are about people. Teams are too cautious. Legal is a bottleneck. Approvals take forever. Leadership asks for urgency, and everyone promises to move faster.
In my experience, most people are trying hard to move quickly. What stops them is uncertainty about whether they are allowed to.
That is a decision-clarity problem, and it calls for a different fix.
The questions that stall work
Underneath much organizational slowness is a simple question: who gets to decide what happens next?
It shows up in many forms. Can I make this call on my own? Do I need Legal? Security? Procurement? Does someone more senior have to approve this? Can we use this data this way? Can we launch this feature? Can I grant this exception?
When nobody knows the answer, the safe move is to ask someone else. That person often does not know either, so they ask someone else. Before long, five people are involved in a decision one person could have made.
From the outside, that looks like bureaucracy. Often it is a design failure. The organization never clearly defined how authority should flow.
Decision architecture
I have started calling this decision architecture: who can act, under what conditions, with what oversight, and when a matter needs to move upward.
Most companies have pieces of an answer. Policies. Approval matrices. Delegations of authority. Contracts. Playbooks. And, often, whatever people remember the CEO saying at the last all-hands.
The problem is that these pieces rarely connect. A policy says one thing, the approval matrix says another, and practice follows a third path that lives in a few experienced people’s heads.
Why informal systems are breaking down
In a stable environment, informal decision-making works reasonably well. People learn the organization. They know whom to call. Institutional instinct fills the gaps.
That stops working when conditions change constantly. Products ship continuously. Regulations shift. AI tools let people act faster and across more tasks. The volume of decisions rises, and you cannot send all of them upstairs.
When informal authority cannot keep up, work waits. Leaders see the delay and ask people to hurry, which does little when the obstacle is permission rather than effort.
What clarity looks like
Clear decision architecture answers a few questions in advance:
- Who owns this type of decision?
- What can proceed without review, and within what limits?
- What conditions or evidence are required before acting?
- What triggers escalation, and to whom?
- What happens when circumstances change?
When those answers are visible, people act with confidence on routine matters, and senior attention goes to the decisions that need it.
Where to start
If your organization feels slow, try this before pushing for speed:
- Pick one process that routinely stalls and trace where it waits.
- At each stop, ask whether the delay comes from the work itself or from uncertainty about who can approve it.
- Write down the decision rights people are guessing at, and make them explicit.
- Set thresholds so routine, low-risk decisions can move without escalation.
You may find the organization was never slow. It was unclear. And clarity is much easier to fix than culture.
