The program had a weekly steering committee, a biweekly integration review, four weekly workstream standups, a monthly executive readout, and a risk review cadence that met every other Thursday. The actual program work was falling behind because the people responsible for doing it were spending their weeks preparing for and attending governance meetings. This is the anti-pattern where the operating model becomes more complex than the work it governs: a governance model with too many meetings.
Operating Model Bloat Accumulates Through Individually Reasonable Decisions
Operating model bloat rarely starts as a deliberate choice; it accumulates through reasonable decisions made independently. The executive sponsor asks for a monthly readout, which is sensible; the program lead adds a weekly steering committee to prepare for it. Each workstream lead adds a weekly standup to prepare for the steering committee. The risk owner adds a biweekly risk review, and the integration lead adds a biweekly dependency check.
Each of these decisions is defensible on its own; in aggregate, they create a meeting structure where a workstream lead spends eight to twelve hours per week in governance activities while also being the person responsible for executing the workstream. The operating model is competing with the program for the same people’s time.
Three Patterns Signal That Governance Has Outgrown the Program
When a workstream lead’s calendar shows ten hours of governance and six hours of execution in the same week, the ratio has inverted. People are spending more time in status meetings than doing the work the status meetings report on.
Governance artifacts begin going unread. The weekly status template gets filled out because the process requires it, but nobody reads it before the meeting. When artifacts exist for compliance rather than decision-making, they’re overhead rather than infrastructure.
Escalation paths that exist on paper get bypassed in practice. The workstream lead texts the VP of Technology directly because the formal path takes two weeks and the decision is needed by Friday. When people route around the governance structure to get work done, the structure is obstructing rather than enabling.
Governance Designed for Visibility Instead of Decisions Creates the Problem
The root cause is designing governance for visibility rather than for decisions. A meeting that provides visibility without requiring a decision is a broadcast, and broadcasts can be replaced by a written update. The meetings that matter are the ones where the room makes a decision the program can’t make without them: a resource reallocation, a scope tradeoff, a timeline adjustment, or an escalation resolution. Every other meeting is optional.
Every Governance Element Should Enable a Specific Decision
A minimum viable operating model applies a single test to every governance element: would the program lose a decision-making capability if this element were removed? If removing a meeting or a role would leave a type of decision without a forum, it stays. If the program can still make every decision without it, the element is overhead. This is what lightest-weight governance looks like in practice.
For meetings, each recurring session should have a named decision type it’s responsible for:
- The steering committee resolves cross-workstream resource conflicts and scope tradeoffs
- The integration review decides whether dependency handoffs are on track
- The executive readout decides whether the program needs sponsor-level course correction
Any meeting without a named decision type is either a status broadcast (which should be a written update) or a coordination session (which should happen only when there’s something to coordinate). For a case study of one team that applied this test, see the cadence inventory that cut meeting hours by 40%.
For roles, every governance role should have a decision right attached to it. The integration lead can approve or reject a dependency handoff schedule; the risk owner can escalate a risk to the steering committee. A role without a decision right is advisory, and advisory roles don’t need standing meeting slots.
For cadences, the frequency of each meeting should match the frequency of the decisions it makes. A steering committee that resolves two resource conflicts per month does not need to meet weekly. The cadence follows the decision rhythm, not the calendar rhythm.
The operating model should be the lightest structure that enables the decisions the program needs. When it becomes heavier than the work itself, the program is governing a governance structure rather than executing a plan. The practical test, as we explore in what stays after you leave, is whether your team can maintain the governance model without us still in the room.
