Practice · Framework
COBIT
A comprehensive framework for distinguishing enterprise governance from management and connecting objectives, processes, and accountability.
Visit the original sourceDirector capability · Management topic
Put authority with the information and accountability needed to act.
Editorially 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.
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.
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.
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.
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.
Create a decision-rights map for five recurring decisions that currently wait, bounce, or attract executive rescue.
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.
You may be ready to record Design when you can:
These prompts support a proficiency judgment; they do not confer one.
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.
Curated sources
Resources support observation and practice. Finishing one does not automatically establish capability proficiency.
Practice · Framework
A comprehensive framework for distinguishing enterprise governance from management and connecting objectives, processes, and accountability.
Visit the original sourceGo deeper · Framework
Clarifies how governing bodies, management, risk functions, and independent assurance contribute without confusing ownership.
Visit the original source