Your Delivery Problem May Be a Decision-Making Problem
Your Delivery Problem May Actually Be a Decision-Making Problem
A team can be skilled, committed, and technically capable and still deliver slowly.
Sometimes the problem is not how the team works.
It is how quickly the organization makes decisions.
The Team Was “Too Slow”
In one workshop, a senior delivery leader was frustrated with a team that had missed an important commitment.
The initial diagnosis was simple:
“The team needs to improve its delivery.”
But when we looked at what had actually happened, the team had spent only a few days doing the work.
Much of the elapsed time was spent waiting:
waiting for a priority clarification
waiting for an architectural decision
waiting for a business trade-off
waiting for someone to accept a risk
The team was being measured on delivery time. The organization was not measuring decision waiting time.
That distinction matters.
Work Time Is Not the Same as Waiting Time
Suppose a piece of work requires three days of actual effort but takes ten days to reach completion.
The natural question is:
“How can we make the team faster?”
A better question is:
“Where did the other seven days go?”
If the answer is waiting for decisions, adding people, changing ceremonies, or pushing the team harder will not solve the underlying problem.
The constraint exists somewhere else.
Decision Making is Part of the Delivery System
Delivery depends on more than development. Teams regularly wait for decisions about:
priority
scope
architecture
funding
risk acceptance
customer trade-offs
release decisions
These decisions are not separate from delivery. They are part of the system through which value moves.
If an important decision takes two weeks, the work cannot simply pretend those two weeks do not exist.
When Nobody Knows Who Decides
One of the most common sources of organizational waiting is surprisingly simple:
Nobody is sure who has the authority to decide.
Consider an architectural question.
The team asks the architect.
The architect wants the product perspective.
The Product Owner wants to consult another leader.
That leader wants the security team's opinion.
Eventually, the question reaches someone senior enough to make the decision.
The team has been “working” throughout this period but the work itself has not moved.
The problem is not a lack of collaboration.
It is a lack of decision ownership.
Consultation Is Not Decision Authority
Organizations often assume that involving more people will produce better decisions.
Sometimes it does.
But involvement and authority are different things.
People can provide information, raise concerns, challenge assumptions, or recommend alternatives without everyone having veto power.
McKinsey's research on organizational decision-making found that faster decision-making organizations can also make higher-quality decisions. The issue is not choosing between speed and quality; it is creating clarity about who decides and involving the right people at the right level.
The goal is not:
“Make every decision immediately.”
It is:
“Make the right decision at the right level, with the right input, without unnecessary delay.”
When Escalation Becomes a System Problem
Escalation is sometimes necessary. But repeated escalation of similar decisions is a signal.
If every significant decision eventually reaches the same senior leader, the organization may have an authority problem, not a people problem.
Ask:
What decisions are repeatedly escalated?
Why can't they be made closer to the work?
Who should actually own them?
What information or authority is missing?
McKinsey's research has identified unclear organizational roles, overreliance on consensus, “death by committee,” and a lack of empowerment as common sources of dysfunctional decision-making. In one example, a healthcare executive sat through the same 90-minute proposal three times because no one knew who was authorized to approve it.
Decision Latency Is a Hidden Flow Constraint
We usually look for bottlenecks on the team's workflow. But some of the most expensive queues exist outside the team's board.
A work item can be technically ready and still wait because someone needs to decide.
That creates:
longer delivery time
more uncertainty
more dependencies
delayed feedback
more difficult forecasting
frustrated teams
This is decision latency: the time between recognizing that a decision is needed and having an actionable decision.
And in some organizations, it is one of the biggest constraints on flow.
Faster Does Not Mean Reckless
There is an important distinction here. Good decision-making is not about making every decision faster at any cost. Some decisions deserve careful analysis. Others are reversible and can be made quickly. The real question is whether the organization knows the difference.
A healthy decision system makes it clear:
what kind of decision is being made
who owns it
who should provide input
what information is needed
when the decision needs to be made
That creates speed without sacrificing judgment.
What This Means for Agile Teams
We often talk about giving teams autonomy. But autonomy without decision authority is limited autonomy. A team may be empowered to solve a problem but still depend on someone outside the team to decide:
whether the problem matters
which trade-off is acceptable
whether the risk can be taken
whether funding is available
whether the customer need takes priority
So when a team appears slow, don't immediately examine the team's practices. Examine the decisions surrounding the team.
A Simple Diagnostic for Leaders
When an important piece of work is waiting, ask:
What decision is holding it up?
Who owns that decision?
Does that person actually have the authority to make it?
How many people need to be consulted?
Is every consultation genuinely necessary?
Why did this decision require escalation?
Could similar decisions be made closer to the work?
The most important question may be the simplest:
Which decisions are currently holding up value?
That question can reveal a very different delivery problem. Because sometimes the team does not need to work faster.
The organization needs to decide faster.
And that is not just a leadership question.
It is a flow question.
-----------------------------------
About the Author
Prateek Nigam
Founder, Agility Wave | Business Agility Coach | Accredited Kanban Trainer (AKT)
Prateek helps organizations see where value gets stuck and improve the leadership, decisions, and systems that determine how well it flows. His work spans organizational agility, Scrum, Kanban, flow, and AI-enabled ways of working.
Comments