Governance is one of those organisational concepts whose importance is rarely disputed, yet whose purpose is surprisingly easy to obscure. Few leaders would argue against accountability, appropriate oversight, transparency or effective risk management. The difficulty arises when the mechanisms created to achieve these objectives begin to acquire a life of their own. Boards generate subgroups, subgroups generate working groups, working groups generate reporting requirements, and decisions travel through increasingly elaborate institutional pathways. What began as a means of enabling responsible decision-making can gradually become an architecture for delaying it.
This matters because governance is not, fundamentally, about meetings. Nor is it about committees, papers, reporting cycles or approval gates. These are instruments of governance, not its purpose. At its core, governance is concerned with the distribution and exercise of decision rights: who has the authority to decide, on what basis, within which boundaries, subject to what scrutiny, and with what accountability for the consequences. An effective governance system should therefore be judged not by the volume of oversight it generates, but by the quality, clarity and timeliness of the decisions it enables.
When More Governance Produces Less Clarity
The distinction is more significant than it might initially appear. In complex organisations, particularly those operating within highly regulated or publicly accountable environments, there is a natural tendency to associate additional scrutiny with reduced risk. When something goes wrong, the institutional response is often additive: another checkpoint, another reporting requirement, another approval stage or another forum intended to provide assurance. Individually, each intervention may be entirely rational. Collectively, however, they can produce a governance environment in which accountability becomes dispersed rather than strengthened.
This is the paradox of excessive governance. Structures designed to increase control can ultimately weaken it.
Where several groups participate in a decision without a clear distinction between those who advise, those who assure and those who decide, responsibility becomes ambiguous. A decision may have been discussed extensively and endorsed collectively, yet it can remain difficult to identify the individual or body genuinely accountable for making it. Organisational activity increases, but organisational clarity does not necessarily increase with it.
The consequences extend beyond administrative inconvenience. Decision latency has a real organisational cost. Opportunities close, programmes lose momentum, risks remain unresolved and teams become dependent upon escalation rather than exercising judgement. There is also a significant opportunity cost associated with senior attention. Every hour that experienced leaders spend reviewing matters that could legitimately have been resolved elsewhere is an hour unavailable for the strategic questions that genuinely require their perspective.
Start With the Decision, Not the Committee
This is why effective governance must begin with decision architecture rather than meeting architecture.
Before asking which committee should consider an issue, organisations should first ask what decision is actually required. Who possesses the information and expertise necessary to make it? Where should accountability sit? What level of risk or expenditure would justify escalation? Which stakeholders need to be consulted, and which genuinely need to approve? What evidence is necessary for the decision to be responsible and defensible?
These questions often expose an important distinction between involvement and authority. Modern organisations rightly value collaboration, consultation and inclusion, but involving people in a decision is not the same as giving everyone a veto over it. Stakeholders may need to be heard without becoming decision-makers. Specialists may need to provide assurance without owning the decision. Senior leaders may need visibility without becoming operational approvers. Mature governance makes these distinctions explicit.
Authority Should Sit Where the Work Happens
There is a related leadership principle that deserves greater attention: decisions should generally be made at the lowest organisational level at which the necessary competence, information and authority reside. This is sometimes misunderstood as an argument for decentralisation without control. It is precisely the opposite. Meaningful delegation requires stronger clarity about boundaries. Leaders must establish risk tolerances, financial authorities, architectural principles, strategic priorities, service expectations and escalation thresholds. Within those parameters, however, people should be trusted to exercise the authority attached to their roles.
An organisation in which every consequential decision migrates upwards is not necessarily well governed. It may instead be demonstrating that its delegation model is weak.
This has particular significance in technology and transformation environments, where the speed and interconnectedness of decisions can expose governance weaknesses quickly. A delivery team waiting several weeks for an approval may not simply experience an administrative delay; that delay can affect dependencies, supplier commitments, programme costs and the organisation’s ability to respond to changing circumstances. Conversely, poorly controlled autonomy can create architectural fragmentation, duplicated investment, security exposure and technical debt. The challenge is therefore not to choose between control and speed, but to design governance capable of delivering both.
Proportionality Is Part of Good Governance
That requires proportionality. A low-risk operational change should not travel through the same governance machinery as a major investment decision. A technical choice that falls comfortably within agreed architecture should not require the same executive attention as a decision that materially alters institutional risk. Governance becomes more effective when the intensity of scrutiny is proportionate to the significance, reversibility and potential consequences of the decision.
Meetings themselves should be subjected to the same discipline. A governance forum should have a clearly defined decision mandate. Its participants should understand which decisions belong there, what information is required to make them and what happens afterwards. Information that can be communicated asynchronously should, wherever practical, be communicated asynchronously. The scarce resource in a governance meeting should not be presentation time; it should be collective judgement.
Measure Decisions, Not Governance Activity
This suggests a useful way of evaluating organisational governance. Rather than beginning with a map of committees and asking whether every area is represented, begin with the organisation’s most important recurring decisions and trace how they are actually made. Examine how many stages they pass through, how often they are reconsidered, where authority becomes unclear, how frequently decisions are escalated and how much time passes between identifying the need for a decision and reaching one. Such an exercise can reveal a very different picture from the formal governance chart.
It can also reveal something deeper about organisational culture.
Sometimes the Problem Is Trust, Not Structure
Excessive governance is not always a structural problem. Sometimes it is a symptom of low institutional trust. Additional approval layers can become a substitute for confidence in delegated authority. Committees can provide psychological protection because collective decisions feel safer than individual accountability. Escalation can become habitual because making a judgement personally carries perceived risk.
If that is the underlying problem, restructuring meetings will achieve relatively little. The organisation must address its relationship with accountability itself. People need to know that exercising reasonable judgement within an agreed mandate is expected, not dangerous; that escalation is appropriate when thresholds are exceeded, not simply whenever a decision feels difficult; and that accountability means being able to explain and stand behind a decision, rather than ensuring that enough people were present when it was made.
None of this diminishes the importance of governance. On the contrary, it argues for taking governance more seriously. Strong governance protects institutions from arbitrary decision-making, unmanaged risk and the concentration of authority without scrutiny. It provides transparency, institutional memory and mechanisms through which leaders can challenge assumptions and reconcile competing interests. But precisely because governance is important, we should resist confusing its visible machinery with its effectiveness.
From Governance Machinery to Organisational Purpose
The question I increasingly find useful is therefore not, “Do we have sufficient governance around this?” It is, “What decision needs to be made, who is accountable for making it, and what is the minimum governance necessary to make that decision well?”
That subtle change in emphasis matters. It moves governance away from institutional choreography and back towards organisational purpose.
A mature organisation should not measure the strength of its governance by the number of people involved in a decision, the number of forums through which it passes or the weight of the papers accompanying it. It should look instead at whether important decisions are made with appropriate evidence, challenge and accountability; whether authority is exercised at the right level; whether risks are visible and consciously accepted; and whether the organisation can act at the speed its responsibilities and environment require.
Good governance does not remove scrutiny. It makes scrutiny purposeful. It does not eliminate meetings. It ensures that meetings exist because collective judgement is genuinely required. It does not reduce accountability through delegation. It clarifies accountability by ensuring that authority and responsibility sit together.
Ultimately, the most sophisticated governance systems may not be those with the most elaborate structures, but those that make it remarkably clear who can decide what, when consultation is required, when escalation is necessary and where accountability ultimately rests.
Governance should make good decisions easier to make and difficult decisions possible to make.
If it merely creates more places in which decisions can be discussed, we have mistaken the machinery for the purpose.
If you enjoy exploring the deeper questions behind leadership, human behaviour, technology and society, you can subscribe at www.stellapoole.com to receive future articles directly in your inbox.
Discover more from Stella Poole
Subscribe to get the latest posts sent to your email.
