.png)
Decision Capability: The Hidden Constraint on Execution
- Julien Haye
- 36 minutes ago
- 12 min read
Decision Capability as the Determinant of Execution
Most organisations explain execution failure through planning gaps or coordination issues. These explanations are visible. They are also incomplete.
The pattern is consistent.
Programmes are approved. Governance structures are established. Reporting indicates that progress remains on track.
Then execution slows.
Decisions take longer to resolve. Issues are escalated beyond their point of origin. Work is revisited as earlier assumptions are reconsidered. Delivery continues, yet momentum declines.
No single failure explains the shift. Performance erodes through accumulated delay, rework, and uneven execution across teams.
Execution depends on whether decisions are taken at the point of ownership, at the required speed, and with sufficient quality to avoid escalation or rework. When this does not occur, work extends through coordination and intervention rather than progressing through direct resolution.
Strategy remains intact. Its translation into outcomes becomes constrained.
The difference sits in decision capability.
Executive Takeaways
For readers scanning rather than reading in full, five governing insights frame the argument:
Execution depends on where decisions are taken, not how they are reported. Delivery remains stable when decisions are resolved at the point of ownership. When decisions move across levels before resolution, execution slows and coordination increases.
Capability determines the cost of execution. When decisions are delayed, escalated, or revisited, additional time, coordination, and senior attention are required. These friction costs accumulate across programmes and reshape delivery economics.
Execution breakdown reflects decision distribution, not isolated failure. Delays, escalation, and rework do not originate from single events. They emerge from how decisions are deferred, transferred, or adjusted across the organisation.
Capability is applied through alignment, not knowledge. Judgment, behaviour, and structural conditions must align at the point of decision. Where alignment is absent, capability exists but is not applied, and execution becomes inconsistent.
Governance becomes effective when decision patterns are visible. Performance improves when organisations examine where decisions are taken, how quickly they are resolved, and how consistently they are applied. This enables intervention before delay, escalation, and rework become embedded in execution.
Capability as a Driver of Economic Performance
Capability is often positioned as a support activity. Investment is directed toward training programmes, certifications, and leadership development.
Progress is reported through completion rates and accreditation levels. These indicators provide evidence of activity. They do not reflect how decisions are taken when conditions require speed, judgment, and accountability.
Capability becomes visible at the point of decision. It determines whether work progresses where it originates or is extended through escalation and rework. In this context, capability is operational. It is expressed through how decisions are taken in practice:
Decisions are resolved where the work occurs, without unnecessary escalation
Trade-offs are assessed and concluded within the team’s authority
Outcomes remain stable, with limited need for revision or reversal
Where these conditions are met, execution remains consistent. Decision cycles are shorter, coordination is reduced, and delivery follows a predictable path.
A well-documented example illustrates the economic impact of capability in practice.
Following the Boeing 737 MAX crisis, investigations highlighted how decision-making was distributed and exercised under pressure. Engineering teams identified technical concerns related to the MCAS system. These concerns required resolution within compressed timelines and under strong commercial and programme delivery pressures.
Decisions were not consistently resolved at the point where expertise resided. They moved across organisational layers through escalation and review. Critical trade-offs between safety, cost, and time were revisited without a single point of decisive resolution.
The operational and economic consequences were substantial:
Programme delays extended as issues required redesign and revalidation
Costs increased through compensation, halted deliveries, and remediation
Senior leadership attention shifted from oversight to crisis management
Production and delivery schedules were disrupted across the supply chain
No single decision explains the outcome. The impact emerged through how decisions were taken across the organisation.
This dynamic is consistent across complex programmes. When capability does not match demand, decisions extend beyond their point of origin. Resolution takes longer, escalation concentrates effort at senior levels, and rework increases as earlier judgments are revisited.
The economic impact does not appear as a single event. It accumulates as friction costs within execution.
Friction costs are the additional time, coordination, and resource required to complete work when decisions are delayed, transferred, or revisited. They are not recorded as losses. They appear through extended timelines, increased meeting load, duplicated effort, and reliance on senior intervention.
Over time, this reshapes the economics of delivery. More effort is required to achieve the same outcome. Delivery becomes less predictable. Strategic return reduces as time, resource, and leadership attention are absorbed in completing work that was expected to progress directly.
Capability determines how much each decision costs to execute. It determines how efficiently capital, time, and leadership attention are converted into outcomes. Where capability is applied at the point of ownership, execution remains efficient and scalable. Where it is deferred or transferred, friction costs increase and performance becomes dependent on coordination.
Where Execution Breaks Down
Under conditions of uncertainty and reduced timelines, organisations rely on distributed decision-making. Work progresses across multiple teams, each expected to act within defined ownership and authority. Execution depends on decisions being taken where information is available and where action can be applied without delay. (See our article Risk Ownership vs Decision Accountability)
The constraint sits in the organisation’s ability to act at the required level and speed.
Where capability does not match demand, decisions extend beyond their point of origin. Resolution is deferred, ownership shifts through escalation, and local adjustments compensate for gaps in clarity:
Local decisions are held while additional validation is sought
Escalation becomes routine rather than exceptional
Adjustments are made reactively as upstream decisions shift
Each response is rational in isolation. Their repetition changes how execution operates.
Work no longer progresses through direct resolution. It moves through dependencies that increase time, coordination, and variability.
The effects propagate across the delivery chain.
A delay in one area affects downstream decisions that depend on it. Teams pause or proceed on provisional assumptions, creating misalignment between activities.
Rework in one team introduces further adjustments elsewhere. Decisions taken under one set of assumptions are revised as conditions evolve. Work re-enters the cycle, increasing overall effort.
Escalation concentrates decision-making at senior levels. As more decisions move upward, resolution capacity becomes constrained. Dependency on a smaller group of decision-makers increases.
These dynamics reinforce each other. Delay increases escalation. Escalation extends resolution time. Rework compounds both. Coordination increases as decisions are not resolved where they originate.
A practical illustration can be observed in large-scale regulatory programmes such as Basel III. Firms were required to interpret evolving requirements while maintaining delivery under fixed timelines.
Local teams identified interpretation questions early. Instead of resolving them within defined parameters, decisions were escalated across multiple governance layers. Each escalation introduced additional review without materially reducing uncertainty.
The result was consistent:
Interpretation decisions extended across weeks rather than days
Downstream activities paused or progressed on provisional assumptions
Rework increased as regulatory positions evolved
At programme level, delivery appeared stable. At execution level, decision cycles lengthened, dependencies intensified, and coordination effort expanded.
This illustrates the asymmetry of capability gaps.
Small delays at the point of decision create disproportionate effects as decision volume increases and dependencies expand. A single delay has limited impact in isolation. Repeated across interconnected decisions, it extends timelines and introduces variability across outputs.
Execution becomes slower and less predictable. Outcomes vary across teams facing similar conditions. Delivery depends less on defined structures and more on the ability to coordinate across unresolved decisions.
Over time, the operating model shifts. Progress is maintained through escalation and adjustment rather than consistent decision-making at the point of ownership.
Where capability is aligned with demand, decisions resolve quickly and execution remains stable. Where it is not, coordination replaces resolution as the primary mechanism for delivery.
Case Illustration: Decision Extension in Transformation Delivery
A product development programme is launched to deliver a new digital platform within a fixed timeline. Delivery is structured across multiple teams, each responsible for defined components, with governance forums in place to review progress and resolve key decisions.
At the outset, decision authority sits within delivery teams. Technical, design, and prioritisation decisions are expected to be resolved where information is available and where action can be applied without delay.
As delivery progresses, this distribution changes.
Teams begin to escalate decisions that fall within their defined scope. Design trade-offs, integration choices, and prioritisation decisions are brought to central governance forums for validation. Decisions carry broader implications, and additional input is treated as reducing risk.
Each escalation is justified in isolation.
Over time, escalation becomes routine. Decisions that were expected to be resolved within teams are deferred until reviewed at programme level. Governance forums expand in scope to accommodate the increased volume. Resolution cycles extend as decisions wait for scheduled review and alignment.
In the meantime, development activity progresses across teams, and programme reporting indicates that milestones are being met. But the underlying operating dynamic shifts.
Decision-making moves away from the point of execution. Teams wait for validation before committing to action and dependencies increase as downstream work relies on decisions that remain unresolved. Coordination effort expands to align across teams and governance forums.
Delay reflects the cumulative effect of extended resolution, repeated escalation, and deferred ownership. As timelines shrinks, pressure increases. Decisions are batched, revisited, or reconsidered in light of broader programme constraints. Rework increases as earlier assumptions are adjusted.
As a result, delivery slows, not because work has stopped, but because decisions are no longer taken where they are needed. The constraint does not come from planning, resources, or governance structure. It comes from the organisation’s ability to resolve decisions at the point of ownership.
Although execution continues, the "execution deficit" builds-up through delayed resolution, repeated escalation, and increased coordination effort.
The Resilience Capability Stack
Capability operates across three interdependent layers. Each shapes how decisions are taken under pressure. Execution depends on their alignment at the point of action.
Cognitive Capability: Quality of Judgment
Cognitive capability defines how decisions are framed and resolved under uncertainty. It reflects the ability to interpret incomplete information, assess trade-offs, and form a position within the required timeframe.
Where it is strong, decisions are clear and proportionate. Where it is insufficient, resolution slows as additional input is sought or positions remain overly cautious.
Organisations invest heavily at this level. Training, experience, and technical expertise strengthen judgment. They do not ensure that judgment is applied when required.
Behavioural Capability: Consistency of Action
Behavioural capability determines whether decisions are taken, challenged, and escalated appropriately. It is expressed through ownership and willingness to act under pressure.
Where it is consistent, decisions are taken at the point of ownership and escalation remains selective. Where it is uneven, decisions are deferred, duplicated, or revisited across teams.
Capability may exist, yet remain unused. Execution becomes inconsistent even when cognitive capability is sufficient.
Structural Enablement: Conditions for Execution
Structural enablement defines whether individuals are able to act. It includes decision rights, access to information, and clarity of escalation.
Where alignment exists, authority matches responsibility and decisions are taken where information resides. Where it does not, decisions move upward, validation increases, and escalation compensates for unclear ownership.
In these conditions, capability is present but constrained.
Interaction Across Layers
These layers interact continuously at the point of decision:
Strong judgment with unclear authority leads to escalation
Clear authority with inconsistent behaviour leads to variability
Consistent behaviour without sufficient judgment leads to poor decisions
Execution depends on alignment across all three. When alignment is present, decisions are taken quickly and applied consistently. When it is absent, resolution slows and ownership shifts across levels.
Where Imbalance Becomes Visible
Organisations tend to prioritise cognitive capability. Behavioural reinforcement and structural alignment receive less attention.
This imbalance becomes visible as pressure increases:
Decision frequency rises
Time for resolution reduces
Dependencies across teams expand
Gaps between layers then propagate across execution:
Decisions move upward where authority does not align with expertise
Execution slows as behavioural consistency weakens
Variability increases across teams facing similar conditions
The organisation continues to operate. The constraint appears in how work progresses.
Capability is not defined by knowledge alone. It is defined by how consistently decisions are taken and applied across these three layers.
How Capability Gaps Become Visible
Capability is rarely measured directly. It is inferred from outcomes within standard governance reporting. Delivery timelines, escalation volumes, and performance metrics show what has happened. They do not explain how decisions were taken to produce those outcomes.
As a result, capability remains implicit.
It becomes visible through a consistent set of signals:
Delayed delivery across programmes
High or persistent levels of escalation
Variability in performance across teams facing similar conditions
Dependency on specific individuals to resolve critical decisions
These signals are routinely captured. They are often misinterpreted.
These signals provide a view of how decisions are taken across the organisation.
A delay attributed to planning reflects decisions that are not resolved at the point of ownership. Escalation interpreted as risk awareness shows how decision-making is distributed across levels. Variability across teams reflects how consistently decisions are taken under comparable conditions. Dependency on individuals highlights where authority and information are not structurally aligned.
The implication is not to replace existing metrics. It is to reinterpret them.
Making capability visible requires linking these signals to how decisions move through the organisation. This involves examining where decisions are taken, how long they take to resolve, and how often they move across levels before resolution. It also requires assessing whether similar decisions are handled consistently across teams or depend on escalation and intervention.
Through this lens, patterns begin to emerge. Decisions are either resolved where they originate or transferred across levels. Resolution either remains stable or extends under pressure. Rework either remains contained or increases as earlier judgments are revisited. Decision-making either remains distributed or becomes concentrated in specific individuals or forums.
Capability becomes observable through these patterns.
This shifts how execution is understood. Outcomes are no longer explained solely through planning assumptions or external conditions. They are interpreted through the organisation’s ability to take decisions at the required level, speed, and consistency.
Capability gaps do not appear as isolated failure. They become visible through the way work progresses.
Board, Executive, and Risk Leadership Implications
Capability remains largely invisible at board level. Oversight focuses on outcomes such as delivery timelines, financial performance, and risk indicators. These provide a view of what has been achieved. They do not explain how decisions were taken to produce those outcomes.
Making capability visible requires shifting attention to decision patterns:
Where decisions are consistently taken above their point of origin
Which decisions require repeated escalation before resolution
Where execution depends on individuals rather than defined authority
How decision speed varies across teams facing similar conditions
This enables a clearer distinction between strategy quality and execution capability. Outcomes can then be interpreted in the context of how decisions are taken, not only what has been delivered.
For executives, the implication is operational. Execution improves when decision-making functions at the level where work occurs:
Decision rights align with where information is available
Ownership is clear at the point of action
Escalation reflects exception rather than routine activity
Performance measures include how decisions are taken, not only their outcomes
Where these conditions are not met, decisions move upward, execution slows, and dependency on coordination increases.
For risk leaders, the role expands beyond oversight of risk exposure. It includes making decision patterns visible across the organisation. This involves identifying where decisions are:
Delayed before resolution
Transferred across levels or functions
Revisited after initial commitment
These patterns show where capability exists but is not applied, creating both exposure and inefficiency.
Practical Application
Improving capability requires observing decisions under real conditions. The focus is on how decisions are taken under pressure, with incomplete information, and within defined ownership.
For Boards
Require evidence of decision quality under pressure
Challenge unexplained execution variance
Test where decisions are taken relative to their point of origin
For Executives
Align decision authority with demonstrated capability
Remove structural barriers that prevent timely action
Stabilise how similar decisions are taken across teams
For Risk Leaders
Use scenarios to test decision behaviour under stress
Track escalation patterns, delays, and rework
Identify where capability is applied versus transferred
Capability improves when decision-making is observed, tested, and aligned with the demands placed upon it. Execution becomes more consistent as decisions are taken where they are needed, without unnecessary escalation or delay.
Board Oversight Checklist
Five Questions Directors Should Ask About Decision Capability and Execution
1. Where are decisions consistently taken above their point of origin?
Decisions that move across levels before resolution indicate that capability is not being applied where work occurs. Directors should ensure visibility over where decision-making is concentrated rather than distributed.
2. Which decisions require repeated escalation before resolution?
Escalation should reflect exception. Repeated escalation signals that decisions are being transferred rather than resolved. Boards should understand where escalation replaces ownership.
3. How consistent is decision-making across teams facing similar conditions?
Variability in outcomes often reflects differences in how decisions are taken rather than differences in effort or capability. Directors should examine whether similar decisions are resolved in a consistent manner.
4. Where does execution depend on specific individuals rather than defined authority?
Dependency on individuals indicates that capability is not structurally embedded. Boards should identify where decisions rely on experience or intervention rather than clear ownership and decision rights.
5. How long does it take for decisions to move from identification to resolution?
Extended decision cycles indicate delay, rework, or escalation. Directors should ensure that decision speed is understood and monitored as a condition of execution.
Decision Capability as the Determinant of Execution
Execution depends on where decisions are taken.
When decisions are resolved at the point of ownership, work progresses with clarity and continuity. Dependencies reduce, coordination remains contained, and outcomes follow a predictable path.
When decisions are delayed or transferred, execution changes character. Work extends through escalation, outcomes are revisited, and performance becomes uneven. Cost increases through time, effort, and senior intervention.
Most organisations track the outcomes of execution. Delivery milestones, financial performance, and risk indicators provide a view of results. They do not explain how those results were produced.
The underlying mechanism sits in decision-making.
Capability becomes visible when decision-making is observed directly:
Where decisions are taken relative to where they originate
How quickly resolution is achieved under real conditions
How consistently similar decisions are applied across the organisation
These patterns determine whether capability is applied or constrained.
This reframing shifts capability from a support function to a central condition of execution. It places decision-making at the core of how performance is understood and managed.
Strategy holds its value when decisions are taken where they are needed, at the speed required, and with sufficient quality to avoid rework or escalation.
Strategy holds. Execution fails where decisions are not taken.
About the Author: Julien Haye
Managing Director of Aevitium LTD and former Chief Risk Officer with over 26 years of experience in global financial services and non-profit organisations. Known for his pragmatic, people-first approach, Julien specialises in transforming risk and compliance into strategic enablers. He is the author of The Risk Within: Cultivating Psychological Safety for Strategic Decision-Making and hosts the RiskMasters podcast, where he shares insights from risk leaders and change makers.