A programme can still be green while the organisation has already changed how it makes decisions.
The first sign may not be delay. It may be a manager saying, "Let me just confirm." Then a routine decision appears on another agenda. A senior leader is copied "for awareness." Another stakeholder is invited into the discussion. A review that was not previously required begins to feel prudent.
None of these actions is necessarily a problem. In isolation, each may be entirely reasonable.
But when they begin accumulating around decisions that were supposedly already delegated, they may be telling us something important.
The decision has not formally moved. The organisation's behaviour around it has.
That distinction is becoming increasingly important in our work on Execution Reliability. The question is not simply whether organisations make good decisions. It is whether important decisions continue to hold where they were designed to be made when pressure increases. And some of the earliest evidence that they may not hold appears before formal escalation ever takes place.
Formal escalation may be a late signal
Most organisations know how to recognise an escalation. A customer issue reaches the executive team. A programme risk moves to a steering committee. A business-unit decision requires enterprise approval. The movement is visible.
What is harder to see is the period before that happens.
Across practitioner conversations we have been examining a recurring cluster of behaviours:
- Requests for reassurance around decisions already within someone's authority
- Routine decisions appearing more frequently in leadership discussions
- Senior leaders being copied "for awareness"
- Additional stakeholders entering reviews
- Informal validation happening before execution proceeds
- Decisions being revisited without a material change in the underlying risk
One instance tells us very little. A pattern is more interesting. Because by the time authority formally moves upward, people may already have stopped behaving as though the decision can safely remain where it was originally placed.
That suggests a different question for leadership teams: What was the first behavioural sign that people had stopped believing the decision would continue holding where it was designed to be made?
The organisation chart may say one thing. Behaviour may say another.
Consider a product leader who has clear authority to make a launch decision. The decision is made. Then a significant customer questions it. The product leader does not formally lose authority. No governance document changes.
Instead, the leader asks the executive sponsor for a quick view. Another stakeholder wants confirmation. Someone suggests bringing the issue to the next leadership meeting "just so everyone is aligned." Execution waits.
Eventually the senior executive says: "I think the original decision is right. Go ahead."
Technically, the decision remained delegated throughout. Behaviourally, something else may have happened. The organisation has learned that this class of decision becomes safer after senior confirmation.
Organisations can retain formal decentralisation while gradually becoming behaviourally more centralised. The change does not require a new approval matrix. It can happen through repeated interaction.
But why are people checking?
This is where the pattern becomes more nuanced. Additional reviews, reassurance seeking and escalation can emerge from very different organisational conditions. Two in particular can look almost identical from the outside.
People genuinely do not know who has the final call. Decision rights overlap. Accountability crosses functions. A global and local leader both believe they have authority. The manager owns the outcome without controlling the resources required to deliver it. In this situation, additional discussion is understandable - the system needs greater clarity. The intervention may involve clearer decision rights, escalation thresholds or governance.
Here, people know exactly who owns the decision. What they are less certain about is whether the organisation will continue standing behind that decision if circumstances become uncomfortable. Will the decision still hold if an important customer objects? If a senior stakeholder disagrees? If the outcome becomes politically difficult? The owner may therefore seek reassurance before acting - not because they do not understand their authority, but because they are uncertain about the durability of the organisation's support for exercising it.
From the outside, both mechanisms can produce the same behaviour: more reviews, more approvals, more stakeholders, slower decisions and greater senior involvement.
But they require very different responses.
Adding more governance may help an ownership problem. Adding more governance to a support-confidence problem may inadvertently make the problem worse - communicating that the owner was right not to trust the authority they already had.
Diagnosing which mechanism is operating matters before redesigning the process. The visible behaviour can look identical. The intervention should not be.
Advice can quietly become approval
Senior leaders should be available to their teams. A manager saying, "I would value your perspective," should not automatically be interpreted as weak ownership. Good decision systems allow people to seek information, judgement and challenge without surrendering authority.
The difficulty is that organisations do not always distinguish clearly between advice and approval.
A senior leader may believe they are providing perspective. The manager may experience the conversation as permission. The surrounding stakeholders may interpret the executive's presence as evidence that the decision was still open.
The practical test is simple: could execution have proceeded if the senior leader had disagreed? If the answer is no, the conversation may have functioned as approval regardless of how it was described.
Pressure exposes what delegation alone cannot tell us
Delegation tells us where authority is intended to sit. Pressure reveals whether it can remain there. That is an important distinction.
When conditions are stable, distributed decision-making can appear to work well. Then something changes. Commercial exposure rises. A customer pushes back. Functions disagree. The outcome becomes more visible. The possibility of being wrong feels more consequential.
At that moment, the organisation learns whether authority was genuinely transferred or merely lent while conditions remained comfortable.
This does not mean decisions should never escalate. Some absolutely should. New information may materially change the risk. Regulatory exposure may cross a defined threshold. A local decision may develop enterprise-wide consequences. Those are legitimate reasons for a decision to move.
The more useful distinction is: did the decision move because the decision itself changed - or because confidence around carrying it changed? Those are not the same organisational problem.
The pre-escalation window may matter more than the escalation itself
This is where our current field observations are becoming particularly interesting.
If leaders wait for formal escalation to identify weakening decision ownership, they may be intervening relatively late. The earlier signals may be behavioural.
- A routine decision starts receiving unusual attention
- People begin pre-aligning before meetings
- A manager asks for confirmation where they previously exercised judgement
- Stakeholders seek visibility without a clear decision role
- Senior leaders are copied into discussions that previously remained lower in the organisation
The decision is still being delivered. Nothing has necessarily failed. But the organisation is spending more effort maintaining confidence around it.
That may be the earlier intervention window. Not when authority formally moves. When behaviour begins anticipating that it might need to.
The signal and the intervention may sit in different places
There is another reason this pattern can remain invisible.
The people experiencing the change first are often not the people positioned to alter the system. They see the additional reviews. They prepare for the extra meetings. They manage the exceptions. They wait for confirmation. They carry the additional coordination.
But an individual saying, "This decision is taking more effort than it used to," can easily be interpreted as a personal capacity issue.
The signal becomes more difficult to dismiss when individual experience becomes a repeated organisational pattern. The same decisions return. The same reviews multiply. The same senior leaders are pulled back in. The same owners repeatedly seek reassurance.
At that point, the question changes from "Is this person struggling?" to "Why has the system started behaving differently around decisions that are supposedly already owned?"
This transition - from individual experience to visible system pattern - has been independently described across multiple practitioner conversations. The people carrying the additional effort should not also have to carry the burden of proving that the system has changed. Leadership needs ways to recognise the pattern without creating another reporting requirement.
Senior re-entry is particularly revealing
Among the behaviours we are examining, one deserves particular attention: senior leaders stepping back into decisions they had already delegated.
Again, one instance proves nothing. A leader may have excellent reason to intervene. But repeated re-entry can reveal something that the organisation chart cannot. Formal ownership may remain unchanged while practical authority begins migrating upward.
And every intervention can influence the next decision. Managers learn what kinds of situations require senior reassurance. Stakeholders learn what kinds of objections can reopen a decision. Senior leaders become accustomed to resolving issues personally. Over time, the organisation may require more executive reinforcement to produce the same outcome.
At that point, what looks like diligence may actually be an emerging dependency.
What should leaders look for?
Rather than starting with a large diagnostic, take one consequential decision that recently required more senior involvement than expected and ask:
Where was this decision designed to be made?
Not where the organisation chart says generally - who actually had authority for this specific decision?
When pressure arrived, where did the decision actually land?
Who became necessary before execution could continue?
What materially changed?
Was there genuinely new information, risk or enterprise consequence - or did confidence around carrying the decision change?
What was the senior leader being asked to provide?
Information? Expertise? Judgement? Authority? Reassurance? The answer changes what the organisation should do next.
Were people checking because ownership was unclear - or because they were uncertain the organisation would stand behind the owner?
This may be the most important distinction. The visible behaviour looks identical. The intervention should not be.
After senior involvement, who actually believed they owned the decision?
Formal ownership and experienced ownership may differ. The gap between them is where future escalation is built.
Has the same behaviour appeared elsewhere?
A single event is situational. Repeated behaviour begins to tell us something about the operating system, not the individuals inside it.
Our current practitioner evidence supports the existence of a pre-escalation accumulation phase: behaviours around a decision can begin changing before formal authority visibly moves. Practitioners have independently described signals including reassurance seeking, increased discussion around routine decisions, leaders being copied for awareness, additional governance and senior re-entry.
There is also emerging convergence around an important distinction: uncertainty about who owns a decision and uncertainty about whether the organisation will support the person who owns it can produce similar visible behaviour. We should not treat them as the same problem.
What the current evidence does not establish is a universal sequence through which these behaviours always develop, nor does it establish that every increase in review or senior involvement represents weakening Execution Reliability. Those remain questions under examination.
- Which behavioural signal most consistently appears before formal escalation?
- When does reassurance seeking indicate prudent judgement, and when does it indicate weakening confidence in the decision system?
- Which types of decisions are most vulnerable to practical authority moving upward?
- When senior leaders intervene, what determines whether ownership remains with the original decision-maker?
- Does repeated senior intervention increase the likelihood of future intervention?
- How can organisations detect these patterns without adding another reporting layer?
The purpose of this research stream is to identify when reasonable organisational support is helping decision capability grow - and when the organisation is beginning to compensate for a decision system that is no longer holding as intended.
Take one important decision that recently returned for additional review. Before changing the governance around it, ask: are people checking because they do not know who owns the decision - or because they are no longer sure the organisation will stand behind the person who does? The visible behaviour may look the same. The intervention should not.
Evidence basis
This Research Note draws on practitioner conversations and field observations from the Execution Reliability Observatory. It reflects an emerging field pattern and a working hypothesis under active examination, not a validated finding. No external academic sources are cited in this note; where adjacent research is used in later notes, it is presented to contextualise a mechanism, not as independent validation of the Execution Reliability model.