Good governance does not require executives to decide everything; it requires them to define what teams may decide and when deviation becomes an enterprise decision.
Weak governance can fail in two opposite ways. Executives can become involved in routine decisions, slowing delivery and weakening accountability, or they can remain distant until a problem has grown beyond the authority or options of the delivery team.
The hardest part is rarely the technique itself. It is deciding where the technique belongs in the enterprise system, what evidence should change the decision, and who is accountable when assumptions fail. Tolerance-based governance creates a boundary between delegated control and required escalation.
The Strategic Context
The source material on project progress, tolerances, exceptions and structured control supports management by exception: establish authorised limits around key objectives, monitor forecasts and escalate when the expected outcome will exceed delegated authority.
At enterprise level, executive attention should be reserved for deviations that threaten strategic value, risk capacity or major commitments. At portfolio level, common tolerance concepts help compare where senior intervention is most needed across initiatives. At program or transformation level, cross-project consequences may require escalation even when a single project remains within local limits. From a systems perspective, decision rights should sit close enough to information for speed while preserving escalation paths for consequences that exceed local authority. These lenses prevent a narrow solution from being mistaken for a complete strategy.
What Leaders Commonly Misread
Escalation means loss of control. Timely escalation is evidence that the control system detected a boundary breach. Punishing escalation encourages concealment and late surprises.
Tolerance is only about cost and schedule. Scope, quality, risk, benefits and strategic constraints can also require boundaries. Governance should reflect what the enterprise truly needs protected.
Executives need detailed visibility of everything. Excess detail can consume attention while material exceptions compete for the same forum. Governance should filter without hiding consequence.
Reframing the Issue
Define governance as a set of decision rights, tolerances and escalation rules. Delivery teams should have enough authority to manage within agreed boundaries; governance bodies should intervene when forecasts show those boundaries will be breached or when enterprise consequences exceed local scope.
For governance by tolerance, a stronger framing is to ask three questions together: what outcome matters, what constraint governs that outcome, and what evidence would justify changing course. That moves management away from defending a preferred solution and toward managing a decision. It also makes opportunity cost visible: every commitment of capital, scarce capability or executive attention displaces something else.
Strategic Analysis
Tolerances Need an Economic and Risk Logic
A tolerance should reflect the consequence of deviation, not an arbitrary percentage applied to every project. A small schedule slip may be immaterial on one initiative and commercially critical on another.
Tolerance design should consider contractual, safety, customer, benefit and dependency effects. Too-tight limits create constant escalation; too-wide limits allow preventable loss to accumulate.
Forecast Breach Before Actual Breach
The control value comes from escalating when the team forecasts that delegated limits will be exceeded, not after the threshold has already been crossed. This preserves options for intervention.
Forecast quality becomes central to governance effectiveness. Teams may hesitate to escalate uncertain forecasts if culture rewards optimistic status.
Escalate the Decision, Not the Problem Description
A strong escalation states the boundary at risk, cause, consequences, options, recommendation and decision required. This prevents senior forums from becoming diagnostic workshops for issues that should have been analysed earlier.
Executive attention is converted into timely choice. Some issues genuinely require joint problem-solving when authority and expertise are distributed.
Protect Delegated Authority
Once tolerances and accountabilities are clear, senior leaders should avoid repeatedly overriding routine delivery decisions. Delegation without decision space creates responsibility without control.
Teams learn to manage outcomes rather than wait for permission. Executives must still challenge weak evidence or emerging systemic risk even when local measures remain within tolerance.
The Enterprise Test in Practice
Consider a hypothetical large transformation organisation facing a material decision about governance by tolerance. The leadership team deliberately avoids beginning with a preferred solution. Instead it tests protected outcome, delegated authority and forecast trigger as separate questions. That changes the discussion because the team must compare the intended outcome with the constraint, evidence and exposure surrounding it. The familiar assumption that escalation means loss of control becomes visible as an assumption rather than an operating truth.
The team then defines a bounded decision rather than a permanent commitment. It agrees what evidence will be reviewed, which trade-off is being accepted and what would justify a different path. Two signals receive particular attention: Executive micromanagement, because routine delivery decisions repeatedly rise to senior forums., and Late exceptions, because breaches are reported only after recovery options have narrowed.. Neither signal is treated as a dashboard decoration. Each is linked to a management conversation about whether the original logic still holds and whether additional capital, capacity or organisational disruption remains justified.
At scale, this way of working changes more than the immediate decision. It creates a repeatable habit of distinguishing commitment from evidence and local optimisation from enterprise consequence. The value is not that every uncertainty disappears. The value is that leaders can see where uncertainty sits, which part of the system carries it and how quickly they can adapt before the cost of reversal rises. That is how governance by tolerance moves from a specialist topic into an executive management capability.
Decision Framework
A useful framework should make judgement more disciplined without pretending that judgement can be automated. For tolerance-based governance, leaders should test the following criteria before committing further resources:
- Protected outcome: Which objectives or constraints are important enough to require an explicit tolerance?
- Delegated authority: Who may decide within the boundary, and what resources or trade-offs may they use?
- Forecast trigger: What forecast condition requires escalation before actual breach?
- Decision package: What minimum analysis and alternatives should accompany escalation?
- Cultural safety: Can teams escalate bad news early without being punished for surfacing it?
For governance by tolerance, the criteria should be considered together. A proposal can be attractive on one dimension and still be unacceptable overall. Where evidence is weak, the answer is not automatically to reject the proposal; it may be to reduce the commitment, run a bounded experiment, create a review gate or preserve an exit route. Reversibility is itself a strategic asset.
From Strategy to Execution
Immediate action. For major initiatives, define material tolerances and confirm that the person accountable for each outcome has matching authority within them. The purpose of the first move is to improve the quality of the next decision, not to create the appearance of momentum.
Medium-term capability. Standardise exception reporting around forecast breach, consequence, options and decision required rather than status colour alone. This is where governance, data, routines and ownership need to become repeatable rather than dependent on a few capable individuals.
Long-term positioning. Build governance culture in which delegated teams act confidently within boundaries and senior forums concentrate on enterprise-level exceptions and trade-offs. Over time, the organisation should be able to make the decision faster, with better evidence and lower coordination cost. That is a capability advantage, not simply a process improvement.
Signals to Monitor
For governance by tolerance, leading indicators matter because financial or delivery outcomes often become visible only after choices are expensive to reverse. Monitor:
- Executive micromanagement — routine delivery decisions repeatedly rise to senior forums.
- Late exceptions — breaches are reported only after recovery options have narrowed.
- Status optimism — teams remain green until a threshold is physically crossed despite worsening forecasts.
- Authority gaps — accountable managers cannot make the trade-offs needed to remain within tolerance.
- Escalation stigma — bad news is softened or delayed because escalation is treated as failure.
Questions for the Leadership Team
- Which decisions are consuming executive time that should remain delegated?
- What forecast breach should trigger escalation before the actual limit is exceeded?
- Do our tolerances reflect real business consequence or inherited percentages?
- Does accountability match authority at each governance level?
- How does leadership respond when teams surface bad news early?
Related ERANORTH Articles
- Related article: Project Controls Should Drive Decisions, Not Reporting
- Related article: Risk Culture: Why Constructive Challenge Is a Governance Capability
- Related article: Projects Deliver Outputs; Programs Must Deliver Outcomes
Closing Perspective
Governance works when it concentrates attention where consequence is highest while preserving local decision speed. Tolerances make that boundary explicit and convert escalation from a sign of weakness into a normal control mechanism.
The leadership responsibility is therefore not to maximise activity around governance by tolerance. It is to make the underlying choice explicit, govern the assumptions, protect the enterprise from avoidable downside and direct scarce capacity toward the outcomes that matter most. That is the difference between managing a topic and leading a system.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.