Good governance does not maximise participation or centralisation; it matches the decision process to the consequence, expertise, urgency and need for acceptance.
Leadership debates often reduce decision-making to style. Some leaders are described as participative, others directive. Contingency and normative decision thinking offer a more disciplined proposition: different decisions justify different processes.
The supplied material notes that normative decision theory focuses on specific decision procedures and considers both decision quality and acceptance. That distinction is strategically useful even without treating any one model as a rigid formula.
The Strategic Context
A routine operational decision with clear rules and one accountable owner does not need the same process as a major transformation affecting several functions. A safety-critical emergency does not justify the same consultation cycle as a long-term portfolio investment. A technical decision may require specialist input even when an executive holds formal authority.
The governance question is therefore: Who should decide this decision, and how should others participate?
What Leaders Commonly Misread
One mistake is assuming broad participation always improves decisions. Participation adds value when relevant knowledge is distributed or acceptance is necessary for implementation. It adds delay when the issue is clear, low-risk and already within legitimate authority.
Another is assuming seniority produces better judgement. A higher-level leader may have broader context but less technical information.
A third is using consultation to avoid accountability. Leaders can collect wide input and still need to own the final choice.
The fourth is failing to adjust decision processes during crisis. Temporary centralisation may be appropriate, but it should not automatically become the permanent model after conditions stabilise.
Reframing the Issue
Decision rights should be treated as dynamic governance architecture.
For each material decision, leaders should consider quality requirements, information distribution, implementation dependence, urgency, reversibility and formal accountability.
High-quality decisions sometimes require broad input but narrow accountability. The group contributes evidence; one person or governing body decides.
Decision Framework
Use six tests:
Consequence: How much value, risk or mission outcome is at stake?
Reversibility: Can the decision be changed cheaply if wrong?
Expertise: Where does the information required for quality sit?
Acceptance: Does successful implementation depend on active support from those affected?
Urgency: How much time is genuinely available?
Authority: Who is legitimately accountable for the decision?
The process should be no broader or slower than these conditions require.
From Strategy to Execution
Immediate action: identify recurring decisions that are over-escalated or trapped in unnecessary consensus. Clarify who decides and who contributes.
Medium-term capability: create simple decision classes for projects and programs: local, cross-functional, executive, safety-critical and strategic, each with defined participation and escalation expectations.
Long-term strategic positioning: review decision architecture as organisations grow or restructure. Decision rights that worked in a small business can become bottlenecks at scale; decentralised rights can also become dangerous when interdependence increases.
Related article: RACI Is Not Accountability: Designing Decision Rights in Matrix Projects
Related article: When Strong Teams Make Bad Decisions
Strategic Analysis: Reversibility and Acceptance Change the Process
Two decisions with similar financial value may deserve very different governance. A reversible technology trial can often be delegated because evidence will arrive quickly and the organisation can change course. A structural reorganisation, major contract or irreversible capital commitment may justify wider challenge and higher authority because the cost of being wrong is harder to recover.
Implementation dependence matters as well. A technically correct decision can fail if it requires sustained cooperation from groups that were excluded from relevant design choices. Conversely, requiring universal acceptance before every action can create paralysis. Leaders need to identify where acceptance is a genuine condition of execution and where clear authority is sufficient.
This is particularly important in programs. Different decision classes coexist: technical design, benefit ownership, schedule trade-offs, funding, risk acceptance and organisational change. Assigning all of them to one governance forum is inefficient and often weakens accountability. Decision architecture should route each class to the lowest level that has the competence, context and legitimate authority to decide it safely.
A mature governance system therefore behaves less like a hierarchy of approvals and more like a network of explicit decision rights with defined escalation triggers.
Signals to Monitor
Warning signs include every significant issue escalating to senior executives, repeated consultation without decisions, people discovering too late that they never had authority, and crisis-era controls remaining long after the crisis.
Positive signals include faster low-risk decisions, deliberate broadening of participation for complex choices and clear accountability even when many people contribute.
Questions for the Leadership Team
- Which decisions are currently too centralised for their consequence?
- Which decisions are too decentralised for their enterprise risk?
- Where does critical expertise sit outside the formal decision authority?
- When is acceptance essential enough to justify wider participation?
- What crisis controls should now be removed?
A useful discipline is to review decision rights after major organisational change. Growth, restructuring, new regulation or increased interdependence can make yesterday’s sensible delegation either too restrictive or too risky.
Closing Perspective
Decision governance is effective when it is proportionate. Leaders should not ask whether they are participative or directive. They should ask which process gives this particular decision the best balance of quality, speed, legitimacy and commitment.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.