Skip to capability
Tree of ManagementE
Your tree
Governance & Ethics

Governance & Ethics

Governance & decision rights

Put authority, accountability, and escalation where they can work.

Essential question

Is authority placed with the information and accountability needed to act, with clear boundaries and escalation?

Build the capability

Practices to build

  1. 01

    Accountable owners

    Name one owner for the decision or outcome.

  2. 02

    Decision forums

    Give each forum a mandate, inputs, membership, and closure rule.

  3. 03

    Policy and exceptions

    Define the rule, the rationale, and how exceptions are governed.

  4. 04

    Traceability

    Preserve material decisions, evidence, and obligations.

Put it to work

Fieldwork

Create a decision-rights map for five recurring decisions: decider, contributors, guardrails, evidence, cadence, and escalation.

Keep exploring

Connected ideas

Go deeper

Field guide

Edited by Ethan Hussong · Last reviewed

Governance is how an organization directs, decides, monitors, and assures. It is not the number of committees in the calendar. A good governance design puts authority close enough to relevant information to act, while preserving clear accountability, boundaries, and escalation.

When decision rights are vague, organizations compensate with meetings, pre-approval, private lobbying, or executive rescue. The cost appears as delay and rework, but the deeper problem is that no one can tell where judgment is supposed to live.

Map recurring decisions

Start with decisions that materially affect outcomes and repeatedly create confusion. For each one, identify:

Consultation is not shared accountability. A decider owes contributors a fair hearing and a clear rationale, but the final ownership should remain legible.

Separate governance from management and assurance

Governing sets direction, appetite, and accountability. Management organizes and executes within that direction. Risk and control specialists support and challenge. Independent assurance evaluates whether the system works.

Combining these roles can create blind spots. A control function that owns the business decision cannot independently challenge it; a committee that merely receives updates is not governing.

Design escalation as a change in conditions

Escalation should not mean “the senior person wants to see it.” Define triggers such as exposure beyond appetite, a cross-boundary conflict, unresolved legal or ethical risk, a material commitment change, or evidence that the delegated decision is failing.

An escalation should state the decision required, evidence, options, recommendation, time boundary, and consequence of delay. Seniority is not a substitute for a decision-ready brief.

Close the loop after a decision

Record the choice, owner, rationale, material dissent, guardrails, and review trigger. Communicate it to the people who must act and those whose constraints shaped it. Then inspect outcomes rather than repeatedly reopening the choice through informal channels.

Revisit when the agreed evidence or conditions change, not merely when a different stakeholder enters the room.

Practice with five decisions

Create a decision-rights map for five recurring decisions that currently wait, bounce, or attract executive rescue.

  1. Name the decision and the outcome it serves.
  2. Assign one decider and the required contributors.
  3. State guardrails and objective escalation triggers.
  4. Define the smallest evidence set and review cadence.
  5. Run the model through one real cycle.
  6. Record where authority was bypassed or accountability became diffuse.
  7. Revise the design and remove a meeting or approval that no longer earns its cost.

Use resources with context

COBIT provides a broad framework for connecting enterprise objectives, governance, management, and accountability. The IIA Three Lines Model clarifies the contributions of governing bodies, management, risk functions, and independent assurance.

Use these frameworks to ask sharper role questions. Do not reproduce every process or line mechanically in a smaller organization.

Evidence of Practice

You may be ready to record Design when you can:

These prompts support a proficiency judgment; they do not confer one.

Continue through the tree

Organization design & team topology supplies the boundaries in which authority operates. Goals, planning & operating cadence gives decisions a recurring forum. Decision writing and Influence across boundaries make evidence and commitment travel across the system.