I described the four governance forums conceptually in Article 10. Here I want to be practical about what they look like when they work and when they don’t — because the failure modes are instructive.
Five characteristics of a governance forum that works
- Decisions are not new to anyone. The participants have been engaged through the D-E-A process. Every stakeholder with a significant interest has been consulted, and their concerns addressed or explicitly acknowledged. By the time the forum meeting happens, the review is confirming what everyone already knows, not discovering it.
- Pre-reads are distributed and read. Artefacts arrive with participants at least forty-eight hours before the meeting. Participants arrive having read them. The meeting begins with shared understanding rather than simultaneous first reading. This sounds elementary. In most governance forums it is not the norm.
- The agenda matches the forum type. A Strategy Forum discusses strategic direction. It does not spend forty-five minutes on a detailed technical issue that belongs in a Technology Forum. Agenda drift is a symptom of unclear forum mandates, and it compounds over time until the forum is doing everything poorly rather than one thing well.
- Decisions are documented the same day. Who attended. What was reviewed. What was decided. What conditions or obligations attach. If this isn’t done before participants leave the building, detail fades and commitments blur. Decision logs are not bureaucracy; they are memory.
- Architects are advisors, not decision-makers. Architects have no managerial authority over investment decisions or project commitments. Their role is to provide analysis, advocate architectural positions, and ensure that the technical consequences of decisions are understood. An architect who attempts to behave as though they have veto authority will rapidly lose access to the conversations they need.
Four failure modes
Forum as discovery session
Artefacts arrive with participants for the first time in the meeting. Genuine new concerns surface. Decisions are deferred. This is not a governance problem — it is a preparation problem. The forum is compensating for D-E-A work that didn’t happen. Fix: invest in the Discuss and Elaborate steps before the next artefact reaches the table.
Forum as rubber stamp
The D-E-A process has been so thorough — or so politically managed — that the forum endorses everything without scrutiny. Over time, participants disengage because attendance has no consequence. The forum becomes a ritual without function. Fix: re-examine whether the right concerns are being surfaced in pre-meeting conversations.
Forum as battleground
Unresolved organisational conflicts play out in the governance meeting. Competing departments use the forum to relitigate investment priorities. This is a symptom of inadequate Strategic Alignment — when there is no agreed strategic direction, every investment decision becomes a contest. Fix: address the Strategic Alignment deficit.
Forum as technical theatre
The meetings produce rigorous, detailed review of architecture artefacts — and are attended only by architects and IT specialists. Business stakeholders stopped coming because the meetings felt irrelevant to their concerns. Fix: rewrite the agenda and reinvite business executives.
What forum your organisation has tells you more about the state of its architecture practice than what artefacts it produces.