17. Governance by Design

“Every organisation is governed by design or by accident. The only question is whether anyone intended the outcome.”

Most organisations treat governance as something that accumulates over time. Policies are written to address incidents, committees are created to improve oversight, approvals are added to reduce risk, reports multiply to satisfy executives, and controls appear wherever confidence seems lacking. Few of these decisions appear unreasonable when viewed in isolation. Each addresses a genuine concern. Yet the organisation that emerges from thousands of such local optimisations often bears little resemblance to one that has been consciously designed.

This gradual accumulation creates a peculiar illusion. Because every individual governance mechanism has a legitimate purpose, the resulting system is assumed to be legitimate as well. When organisations become slow, expensive or incapable of adapting, the response is usually to refine individual components rather than question the architecture itself. Additional policies are introduced to clarify existing policies. New committees coordinate existing committees. More reports attempt to explain why existing reports are failing to produce better decisions. Governance expands precisely because it is no longer understood as a designed system.

The preceding chapters have examined the symptoms of this condition. Decision Constipation described organisations that possess information but cannot convert it into action. Governance Theatre explored activity mistaken for effectiveness. Approval Inflation, Committee Creep, Dashboard Archaeology, Institutional Myths, Control Debt, Escalation Addiction and The Status Quo Police all revealed different ways in which governance can evolve away from its original purpose. These are not isolated organisational problems. They are consequences of governance developing through historical accident rather than deliberate design.

Design begins by asking a different question. Instead of asking what controls should exist, or which committee should approve a proposal, it asks how the organisation intends decisions to flow. Every subsequent governance mechanism becomes a consequence of that answer rather than a substitute for it.

Organisations Already Possess a Design

When executives hear the phrase governance by design, they often imagine a future transformation project. In reality, every organisation already has a governance design. The issue is that very few have ever chosen it consciously.

An organisation’s governance design is visible in the paths decisions follow. It can be observed in who is trusted to make operational choices, which matters are escalated, how disagreements are resolved and how quickly resources move from opportunity to execution. These patterns exist whether or not they have been documented. They emerge from reporting lines, historical precedents, cultural expectations, incentive structures and informal relationships every bit as much as from organisational charts and policy manuals.

This explains why organisational change is frequently disappointing. Structures are redesigned while decision patterns remain untouched. Titles change, departments merge, committees receive new names and policies are rewritten, yet employees continue behaving exactly as before because the underlying architecture of decision-making has not changed. Formal governance documents describe one organisation while everyday practice reveals another.

Seen in this light, governance is less like legislation and more like engineering. Engineers recognise that structures produce behaviour. A bridge does not persuade vehicles to cross safely; its design makes safe crossing possible. Likewise, governance does not primarily influence behaviour through instruction. It shapes behaviour by defining the environment within which decisions occur. Organisations therefore experience the governance they have designed, whether intentionally or otherwise.

Designing for Decisions Rather Than Compliance

Many governance initiatives begin with obligations. New regulations appear, audit findings require remediation, or risks demand additional assurance. These concerns are legitimate, yet they often become the organising principle for governance itself. Decision-making becomes secondary to demonstrating compliance.

The consequence is subtle but profound. Instead of asking how governance enables better organisational performance, organisations begin asking how governance can demonstrate conformity. Documentation becomes evidence rather than guidance. Meetings become opportunities to establish accountability rather than resolve uncertainty. Controls exist because external stakeholders expect them to exist, regardless of whether they improve operational decisions. Compliance becomes the design objective, even when nobody explicitly intended it to be.

Designing governance from first principles reverses this relationship. Every governance mechanism begins with a decision. Who needs to decide? What uncertainty prevents confident action? What information improves the quality of that decision? Which controls increase confidence without unnecessarily delaying execution? Only after these questions have been answered do policies, standards, controls and assurance activities emerge naturally.

This distinction changes the role of governance entirely. Rather than existing alongside operations as an oversight function, governance becomes part of the organisation’s operational capability. It improves the quality, consistency and speed of managerial judgement. Compliance remains important, but it becomes evidence that governance is functioning well rather than its primary reason for existing.

The Architecture of Flow

Well-designed governance is characterised less by the number of controls than by the ease with which decisions move through the organisation. Decisions begin with uncertainty, acquire information, involve the appropriate authority and produce action with minimal unnecessary delay. Governance exists to support this flow rather than interrupt it.

This perspective transforms familiar organisational structures. Committees cease being destinations to which problems are escalated and instead become decision-making mechanisms for issues requiring collective judgement. Policies become instruments for decentralising authority because they reduce uncertainty before decisions arise. Standards create predictable technical environments that allow operational decisions to be delegated confidently. Controls generate confidence that decisions will produce expected outcomes. Assurance verifies that these mechanisms continue functioning as intended. Each component performs a distinct architectural role within a single decision system.

Poorly designed governance exhibits the opposite characteristics. Decisions repeatedly change direction between functions. Multiple governance bodies consider identical issues from different perspectives. Information is reformatted for successive audiences without changing the decision itself. Accountability shifts as decisions move upward through management layers. The organisation experiences increasing friction because governance has ceased facilitating flow and has instead become the environment through which work struggles to pass.

Organisational throughput, explored in the following chapter, depends fundamentally upon this architectural quality. Faster organisations are not necessarily those with fewer governance mechanisms. They are those whose governance mechanisms have been deliberately arranged to minimise unnecessary decision friction.

Governance as an Organisational Capability

Designing governance deliberately requires treating it as an organisational capability rather than an administrative function. Capabilities are valuable because they enable organisations to produce repeatable outcomes under changing conditions. Governance deserves the same treatment.

This requires a broader conception of what governance encompasses. It includes authority structures, information architecture, policy frameworks, decision rights, control environments, performance measures and assurance mechanisms. None of these elements is independently sufficient. Together they determine how effectively an organisation converts knowledge into coordinated action.

Viewing governance as a capability also alters how organisations evaluate success. Traditional governance metrics frequently count activity: policies published, committees convened, audits completed, controls implemented or risks recorded. These measures reveal effort but say little about organisational performance. A capability perspective instead asks whether governance consistently improves decision quality, reduces unnecessary uncertainty and enables faster execution without sacrificing confidence. These are more difficult questions, but they align directly with the purpose governance exists to fulfil.

The distinction mirrors the evolution seen in other management disciplines. Information technology ceased being measured solely by infrastructure deployed and became evaluated according to business capability delivered. Human resources increasingly moved beyond administrative transactions towards organisational capability development. Governance is undergoing a similar transition. Its value lies not in the mechanisms it administers but in the organisational competence it creates.

Designing for Adaptation

Perhaps the greatest weakness of accidental governance is its inability to adapt. Because governance has evolved incrementally, changing one component often produces unintended consequences elsewhere. Removing an approval exposes hidden dependencies. Eliminating a committee creates uncertainty about authority. Simplifying a policy reveals that other processes had quietly depended upon its complexity. The organisation becomes reluctant to change because nobody fully understands the system that already exists.

Deliberate design creates a different form of resilience. When governance has been constructed around decision architecture rather than accumulated procedures, individual mechanisms can evolve without destabilising the entire organisation. Policies change because the underlying decision remains constant. Committees appear or disappear as organisational complexity changes. Controls adapt to emerging technologies without altering fundamental accountability. Governance becomes modular rather than historical.

This characteristic will become increasingly significant as organisations incorporate artificial intelligence into management. AI will transform information gathering, analysis and recommendation far more rapidly than traditional governance models can accommodate. Organisations whose governance has been built around specific procedures will struggle to adapt. Those whose governance has been designed around decision principles will be able to incorporate new capabilities while preserving coherence. Their architecture remains stable even as the mechanisms within it evolve.

Design therefore prepares organisations not merely for today’s decisions but for decisions they cannot yet anticipate. That capacity to adapt may become the defining characteristic of effective governance in the coming decades.

Conclusion

Governance is often presented as a collection of disciplines: risk management, compliance, policy management, assurance, audit and control. Each possesses its own vocabulary, methodologies and professional community. Yet organisations do not experience these disciplines independently. They experience a single governance system whose quality is determined by the coherence of its design.

The pathologies explored throughout this book are rarely failures of individual governance practices. They are failures of architecture. Organisations become bureaucratic not because policies exist, but because policies are disconnected from decision-making. Committees become obstacles not because collective judgement lacks value, but because authority has never been consciously designed. Controls become burdens not because confidence is undesirable, but because confidence has been pursued without considering organisational flow.

Governance by design recognises that these are architectural questions before they are administrative ones. It begins with decisions, arranges authority around those decisions and constructs governance mechanisms that increase confidence without diminishing organisational throughput. In doing so, governance ceases to be an inherited collection of procedures and becomes what it was always capable of being: an intentional system for enabling organisations to make better decisions and convert those decisions into effective action.