Authority determines who may decide; governance determines whether the decision can be understood, defended and corrected.
Senior leaders often focus on decision rights because slow organisations frequently suffer from unclear authority. Responsibilities overlap, committees multiply, approvals become ambiguous and decisions migrate upwards.
Clarifying authority is necessary, but it is not sufficient.
A leader can have the formal right to decide and still make a poorly governed decision. The evidence may be incomplete. Relevant stakeholders may not have been heard. Conflicts may be undeclared. The rationale may not be recorded. The decision may be impossible to review without reconstructing events from memory.
This matters most when decisions are consequential, contested or difficult to reverse.
The supplied governance material provides a useful underlying model. Authority is delegated formally. Judgement is expected to be exercised. Evidence is considered. People affected by a decision are given a process through which concerns can be heard. Decisions and reasons are recorded. Review occurs through defined stages rather than through informal political pressure.
The enterprise lesson is straightforward:
Decision rights without decision discipline create concentrated authority, not necessarily good governance.
The Strategic Context
Organisations need managerial discretion.
A business that tries to prescribe every decision through policy will become slow, expensive and unable to adapt. Strategy itself requires judgement because leaders routinely decide under uncertainty, conflicting objectives and incomplete information.
The answer is therefore not to eliminate discretion. It is to build conditions under which discretion can be trusted.
This becomes more important as organisations scale.
In a small business, a founder may know the context behind almost every major decision. In a larger enterprise, authority is distributed across executives, functions, portfolios, programs, business units and specialist committees. No single person can observe every decision directly.
Governance must therefore perform a different function.
It must make decentralised judgement sufficiently visible, evidence-based and reviewable that the organisation can delegate authority without losing control.
That requires more than an organisation chart.
What Leaders Commonly Misread
One common mistake is to equate accountability with approval authority.
A person may be authorised to approve an investment, close a risk, select a supplier or change a program scope. But accountability also includes the quality of the process used to reach the decision and the consequences that follow.
Another mistake is to assume that documentation is administrative overhead.
Poor organisations often document decisions extensively but record the wrong things. Meeting minutes capture attendance and discussion while omitting the actual decision logic. A project change may record the revised budget but not the assumptions that justified it. A risk acceptance may name the owner but not the evidence used to determine that exposure was tolerable.
Useful records allow someone who was not in the room to understand:
- what was decided;
- who had authority;
- what evidence mattered;
- what alternatives were considered;
- what assumptions were accepted;
- what risks remained;
- when the decision should be reviewed.
The third mistake is to see challenge or review as a sign of weak authority.
In a mature governance system, review protects authority.
Leaders are more willing to delegate consequential decisions when they know there is a structured mechanism for challenge, escalation and correction. Without such a mechanism, senior executives often retain decisions unnecessarily because the organisation lacks confidence in what will happen if a delegated judgement is poor.
Reframing the Issue
Decision governance can be understood as a chain of legitimacy.
A consequential decision becomes more defensible when five conditions are present:
Authority: the decision-maker has the legitimate right to decide.
Evidence: relevant facts, risks and perspectives have been considered.
Process: the decision has followed an appropriate and fair method.
Reason: the rationale is clear enough to be explained.
Review: there is an appropriate pathway for challenge, escalation or reconsideration.
Remove any one of these and governance becomes weaker.
A decision made by the wrong person lacks authority.
A decision made without evidence is arbitrary.
A decision made through a biased process lacks legitimacy.
A decision without reasons is difficult to learn from.
A decision without a review path can force disagreement into politics, avoidance or executive escalation.
This reframing matters because it shifts governance away from the narrow question of "Who signs?" towards the broader question of "What makes this decision trustworthy?"
Strategic Analysis
Delegation should be explicit enough to survive organisational change
The supplied policy material requires delegations of authority to be made in writing. The business principle is sound.
Informal authority works until people change roles, business conditions deteriorate or a decision becomes contested.
A clear decision-rights system should identify both the authority and its boundaries.
For example, a program director may be authorised to approve scope changes up to a defined financial and benefits threshold. Beyond that threshold, the decision moves to a steering committee or executive sponsor. A procurement leader may approve supplier selection where risk remains within an accepted category, while strategic or sole-source arrangements require additional review.
The purpose is not to create more approval layers. It is to make escalation predictable.
Ambiguous authority creates two opposite problems: decisions move too slowly because nobody is sure who can act, or they move too quickly because people assume authority they do not actually hold.
Judgement should be protected, not replaced
The supplied material also recognises that discretionary decisions require sound judgement.
This is crucial.
Many governance reforms fail because they respond to inconsistent decisions by adding more rules. Eventually the procedure becomes so detailed that managers stop exercising judgement and start demonstrating compliance.
That can reduce obvious variation while creating a new risk: the organisation becomes less capable of responding intelligently to unusual conditions.
Good governance defines the boundaries of judgement.
It clarifies what evidence is required, which risks cannot be accepted locally, where conflicts must be declared and which decisions require independent review. Inside those boundaries, leaders remain responsible for thinking.
Governance should therefore constrain arbitrariness without suppressing judgement.
Evidence quality matters more when decisions are irreversible
Not every decision deserves the same governance burden.
A reversible operating decision may require little documentation. A major acquisition, plant relocation, technology-platform commitment or regulatory position deserves substantially more.
A useful principle is:
As irreversibility, exposure and enterprise consequence increase, the evidence and review standard should rise.
This is where many portfolio and transformation decisions fail. The approval process may focus heavily on the business case at the beginning but apply weaker scrutiny to later decisions that materially change the economics.
A sequence of apparently modest scope changes can eventually create a strategic commitment that would never have been approved as a single decision.
Decision governance must therefore consider cumulative consequence, not only individual approval thresholds.
Procedural fairness is not limited to formal disputes
The supplied definition of natural justice is useful because it identifies practical elements of fair decision-making: people should have an opportunity to present their case, relevant information should be disclosed, reasonable time should be provided, conflicts should be declared, relevant evidence should be considered, and decisions should be communicated with reasons.
In an enterprise context, these principles are valuable far beyond disciplinary or appeal processes.
Consider a portfolio committee deciding to terminate a project.
The project sponsor should not control the evidence presented to the committee without challenge. The delivery team should have an opportunity to explain critical assumptions. Benefits owners should contribute evidence about value. The committee should distinguish sunk cost from future value. Conflicts of interest should be visible.
This does not mean every project receives a courtroom process.
It means the organisation recognises that consequential decisions become stronger when relevant evidence can survive challenge.
Reasons create organisational memory
A decision without a rationale creates little learning value.
When circumstances change, leaders need to know whether the original decision is still valid. That requires understanding the assumptions behind it.
Suppose a manufacturer selects a new automation platform because labour availability is expected to tighten, production volume is projected to rise and integration with the existing ERP is assumed to be straightforward.
Two years later, production volume remains flat and integration costs are significantly higher than expected.
The question is not merely whether the original decision was "right" or "wrong".
The more useful question is which assumptions changed, which evidence was weak, and whether the organisation should update its decision rules.
Recorded reasons convert decisions into learning assets.
Review mechanisms should escalate proportionally
The source material uses staged review pathways rather than sending every disagreement directly to the highest body.
Businesses need the same principle.
A review system should resolve issues at the lowest level that can credibly decide them.
This protects executive capacity and prevents governance from becoming escalation by default.
A practical hierarchy may include:
- clarification or reconsideration by the original decision-maker;
- review by the accountable executive or governance body;
- independent assurance or specialist review for high-consequence matters;
- final executive or board escalation where strategic exposure warrants it.
The important point is that review should be designed before conflict occurs.
Otherwise, escalation becomes dependent on hierarchy, personality and political influence.
Decision Framework
Leaders can use a seven-part decision-governance test.
| Dimension | Test |
|---|---|
| Authority | Is it clear who has the right to decide and where that authority ends? |
| Evidence | Has the decision considered the information proportionate to its consequence? |
| Alternatives | Were credible options evaluated rather than merely validating a preferred answer? |
| Conflict | Have material conflicts of interest or incentives been identified? |
| Rationale | Can the reasoning, assumptions and trade-offs be explained clearly? |
| Record | Is there enough documentation for future review without recreating the decision from memory? |
| Review | Is there an appropriate mechanism for challenge, escalation or reconsideration? |
Not every decision requires a formal template.
The framework should be applied proportionally.
A low-cost reversible experiment may need only a clear owner and success criteria.
A long-term outsourcing contract may require independent commercial review, scenario analysis, legal scrutiny, risk assessment and explicit board-level rationale.
The governance burden should follow consequence.
From Strategy to Execution
Immediate action should begin with the organisation's most consequential recurring decisions.
Examples include capital allocation, project approval, risk acceptance, supplier selection, major scope changes, program termination, restructuring and technology commitments.
For each decision type, leaders should identify the decision owner, authority threshold, evidence required and escalation path.
Next, review recent decisions that produced controversy or unexpected outcomes. Do not ask only whether the decision was correct. Ask whether the process was governable.
Was authority clear? Was important evidence available? Were assumptions visible? Was the rationale recorded? Could someone challenge the decision without relying on informal influence?
In the medium term, build a lightweight decision record for high-consequence decisions. It should capture the decision, authority, evidence, alternatives, assumptions, principal trade-offs, residual risks and review triggers.
This can become part of portfolio, program and executive governance without creating a parallel bureaucracy.
Longer term, organisations should analyse decisions as a body of evidence.
Repeated reversals may reveal weak assumptions. Repeated escalations may indicate unclear authority. Repeated disputes may expose ambiguous criteria. Consistent success under certain decision conditions may show where more authority can safely be delegated.
The organisation then improves not only individual decisions, but the system through which decisions are made.
Signals to Monitor
Governance may be weakening when:
- major decisions depend on informal authority rather than defined decision rights;
- leaders cannot explain why a previous decision was made;
- governance forums repeatedly revisit decisions because the original rationale was not clear;
- escalation occurs only after relationships deteriorate;
- the same issue receives different decisions from different parts of the organisation;
- evidence is selected mainly to support the preferred option;
- people avoid challenging senior decision-makers because there is no legitimate review path;
- low-consequence decisions are heavily controlled while high-consequence assumptions receive little scrutiny;
- the organisation records approvals but not assumptions, trade-offs or reasons.
These are not documentation problems. They are signals that decision legitimacy is becoming fragile.
Questions for the Leadership Team
- Which decisions in our organisation are hardest to reverse, and do they receive proportionately stronger evidence and review?
- Where is decision authority still dependent on custom, personality or hierarchy rather than explicit rights?
- Could an independent leader understand why our five most consequential recent decisions were made?
- Which governance forums approve recommendations without seriously testing alternatives or assumptions?
- Where do people have no credible path to challenge a decision except escalating politically?
- Which decisions are repeatedly revisited because the original rationale and review triggers were never recorded?
- What could we safely delegate further if our evidence, decision records and review mechanisms were stronger?
Closing Perspective
Strong governance does not require leaders to surrender judgement to procedure.
It requires the organisation to make judgement trustworthy.
Authority should be clear. Evidence should be proportionate. Alternatives and conflicts should be visible. Reasons should survive the meeting in which the decision was made. Review should be available without turning every disagreement into executive escalation.
The goal is not a system in which nobody can make a mistake.
The goal is a system in which consequential decisions can be made at the right level, challenged when necessary, understood afterwards and improved through learning.
That is what turns decision rights into institutional capability.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.