Stalled Decisions
Complex organisations rarely stall because nobody is working. They stall because uncertainty no longer has a clear path to resolution.

The meeting has been held. The data has been presented. The recommendation is clear. Three departments need to agree before anything moves. Two have signed off. The third is waiting for something. Nobody knows what. The decision has been sitting for six weeks.

Cross-functional decisions do not stall because teams are disorganised. They stall because the governance architecture that should convert uncertainty into a binding commitment was never built. No single role owns the call. No evidence threshold triggers resolution. No escalation pathway moves the decision before the delay compounds.

By the time the stall becomes visible in reporting, the programs depending on that decision have already absorbed weeks of preventable delay.

XD Thinking™ examines the decision architecture underneath recurring stalls — where authority is unclear, evidence does not bind and escalation depends on relationships rather than structure.
You are seeing this if
Everyone Is Involved But Nobody Is Authorised
  • Decisions requiring more than one department are taking significantly longer than decisions within a single team
  • The CEO or GM is regularly pulled into cross-functional disputes that should have resolved at a lower level
  • Action plans are agreed in meetings and then sit without movement until someone follows up
  • Nobody can clearly state who has the authority to make the final call on a cross-departmental decision
  • Programs stall at handover points when one department passes responsibility to another
  • When the right people are not in the room, the decision waits — it does not move through a defined process
These are not communication failures. They indicate an organisation whose decision architecture was not designed for the level of cross-functional complexity it is now managing.
What is actually happening

Decisions do not stall because people stop working. They stall because the decision architecture was never designed for the level of complexity being asked of it.

When a decision crosses departmental boundaries, it enters a space where no one has formal resolution authority. Information is gathered. Positions are stated. Meetings are held. But without a defined authority structure — who decides, based on what evidence, at what point — uncertainty circulates rather than resolves.

Escalation happens informally — through relationships rather than a defined pathway. When it eventually reaches someone with enough authority, the immediate decision resolves. The structure that produced the stall does not change.

The operational impact accumulates silently. Programs absorb delay at each stall point. The organisation becomes structurally slower without anyone deciding to slow it down.

Cross-functional decision required — uncertainty enters without a clear resolution pathway
↓
No single role holds resolution authority — input arrives from all departments, closure from none
↓
Escalation depends on relationships — path undocumented, timing unpredictable
↓
Reassessment loops form — meetings repeat, the same positions restate
↓
Commitment diffuses — informal agreement reached, never formally closed, revisited at the next trigger
↓
Operational drag compounds — programs slow, leadership bandwidth absorbed, delay recorded as complexity

Until resolution authority is formally assigned — who decides, based on what evidence, at what point — uncertainty will continue circulating rather than resolving.

What This Pattern Costs
Executive bandwidth absorbed at the wrong level
When no one below the CEO has authority to resolve a cross-functional dispute, every contested decision travels upward. The executive becomes the de facto resolution point for problems that should never have reached them.
Delivery delay that compounds
Programs that stall at decision points fall behind schedule. Other programs dependent on their outputs stall in turn. A single ungoverned decision point can hold up a chain of work across multiple teams.
Accountability that disappears at boundaries
When a decision stalls between departments, nobody formally owns the delay. It is visible to everyone and the responsibility of no one. The organisation cannot hold itself accountable for something no one was authorised to resolve.
What this calculates to
Most organisations do not measure the cumulative delay created by decisions that stall at authority boundaries.
  • If cross-functional decisions stall for 2–4 weeks before resolution — through escalation, committee referral or informal negotiation
  • and a program encounters 20–40 such decision points per year across procurement, approvals, design, delivery and operations
  • that represents 40–160 weeks of cumulative decision delay absorbed annually
equivalent to one to three major programs delayed each year — not by complexity, not by resourcing, but by decisions that were never formally owned.
Reviews of infrastructure and capital program delivery in Australia consistently identify unclear authority, unresolved cross-functional disputes and relationship-dependent escalation as primary contributors to schedule slippage. The decisions themselves are rarely the problem. They are often straightforward once someone has the authority to make them.
Cost of doing nothing
Over successive program cycles without defined decision authority, cumulative delay compounds — eroding delivery confidence, absorbing executive bandwidth, and converting a governance gap into an organisational assumption about how long things take.
Figures are illustrative. They are a way to test whether the pattern — decisions stalling at authority boundaries — is present in your environment and at what scale.
The decision is not complex. The authority structure around it is. Capable people in capable organisations are waiting for a governance structure that was never built.
The Pattern That Emerges
When stalled decisions are examined, the same structural conditions appear regardless of organisation size or decision complexity.
  • 1 No one owns the cross-functional call — each department is accountable for its own contribution, but no single role is formally accountable for the decision that requires all of them to agree.
  • 2 Escalation depends on relationships rather than structure — when a decision cannot be reached, it moves upward through whoever has the right connection or enough seniority. The path is not documented and not repeatable.
  • 3 Handover points are where accountability disappears — the incoming team inherits the task without formally inheriting the authority, so the decision stops at the boundary until someone informally assumes it.
  • 4 Meetings produce agreement but not decisions — without a formal authority structure, the agreement has no mechanism to become a binding commitment and the next meeting revisits the same ground.
This is not a culture problem or a capability problem. It is a decision authority problem.
The discussion keeps moving.
The decision does not.
What Most Organisations Try First
What Does Not Move the Decision
What XD Thinking™ Changes
When Authority Is Defined
More meetings
Creates additional opportunities for agreement without creating the authority structure that turns agreement into a binding commitment. The decision recirculates through a larger group.
Cross-functional authority formally documented
A named role owns the cross-functional call. That role can declare sign-off complete, resolve disagreement and hold the decision. The authority is documented before the next program begins.
A working group or steering committee
Creates a forum for discussion without authority to decide. Meetings increase. The stall point moves to the working group. Resolution still depends on who has enough seniority in the room.
Escalation paths defined and documented
When a decision stalls, it routes to the right authority automatically. The path does not depend on relationships or on someone deciding the delay has gone on long enough.
Escalate to the CEO
Resolves the immediate decision. Does not change the authority structure that produced the stall. The next cross-functional decision travels the same path upward.
Handover points transfer authority explicitly
When a program moves between departments, the incoming team formally inherits both the task and the mandate. The decision does not stop because neither team knows who can make it.
Improve collaboration and reporting tools
Improves the speed at which the stall is visible. Does not address why the decision cannot be reached. Better information about a stuck decision does not unstick it.
CEO bandwidth freed for strategic decisions
Cross-functional disputes resolve at the level they were created. Operational decisions do not travel upward because a formal authority structure handles them before they need to escalate.
These responses create visibility and pressure without creating authority. The decision continues to stall because the structure that would move it was never built.
Decisions that should be simple become simple. Not because the people changed but because the authority structure finally matches the complexity of the work.
Before the next cross-functional decision stalls in the same gap. If this pattern is familiar, the issue is rarely about the decision itself. In most organisations, the decisions are straightforward — once someone has the authority to make them. The governance structure that should create that authority was never formally built. Discuss Your Situation or Check Your Decision Friction Risk A 5-minute decision authority stress test. Results shown on screen.