An eight-month, five-workstream program had accumulated twenty-three recurring meetings by the time we were brought in to redesign the operating model; the program lead estimated twelve. Nobody was lying; nobody had counted. That gap between perception and reality is where governance bloat lives.
Meeting Proliferation Is Accumulation, Not Design
Twenty-three meetings doesn’t happen by design. The program starts with a reasonable governance structure: weekly workstream meetings, a biweekly cross-functional sync, and a monthly executive readout. Then the data engineering and analytics workstreams add a weekly coordination meeting. The program lead starts weekly one-on-ones with each workstream lead. The executive sponsor requests a biweekly update separate from the monthly readout. Each addition solves a real problem at the moment it’s created, but nobody removes meetings when the problem has been resolved or when a new meeting makes an older one redundant. The meeting structure grows until the leadership team spends more time in governance meetings than in execution.
A Cadence Inventory Separates Governance from Habit
During operating model design, we ran a cadence inventory, documenting four things for each recurring meeting: who attends, how long it runs, what decisions it enables, and what artifacts it produces. The last two questions were the diagnostic. Most people could answer who attends and how long it runs; fewer could articulate what decision the meeting enables. Several meetings had no answer because the meeting didn’t enable a specific decision; it was a status update where each workstream reported progress and the group listened.
The inventory revealed three categories:
- Nine meetings had no clear decision they were responsible for. These were status-update meetings where the information being shared was useful but the meeting format wasn’t necessary to share it.
- Four meetings overlapped in scope with other meetings (the biweekly executive update covered the same ground as the monthly executive readout; two weekly coordination meetings discussed the same dependencies covered in the biweekly cross-functional sync).
- Ten meetings each had a clear decision they enabled and a clear artifact they produced.
Fewer Meetings with Clearer Purposes
The program went from twenty-three to fourteen recurring meetings. The nine status-update meetings were replaced by a structured async process: each workstream lead submitted a written update every Friday using a standard template covering milestones hit, milestones at risk, blockers, and decisions needed. The program lead compiled these into a dashboard. The four overlapping meetings were consolidated: the biweekly executive update was eliminated in favor of a redesigned monthly readout with a mid-month written brief, and the two redundant dependency meetings were folded into the biweekly cross-functional sync with a standing agenda item for dependency review.
Each of the fourteen remaining meetings was assigned a specific decision type and a specific output:
- Weekly workstream meetings decided weekly priorities and produced updated milestone trackers.
- The biweekly cross-functional sync resolved dependency conflicts and produced an updated integrated timeline.
- The monthly executive readout secured escalated decisions and produced confirmed resource commitments.
This is what lightest-weight governance looks like when applied to a real program.
Purposeful Governance Recovers Time and Improves Coordination
The reduction freed approximately twelve hours of senior leadership time per two-week cycle. The program lead recovered nearly four hours per week; each workstream lead recovered one to two hours. That time went back to execution: working through implementation problems that had previously been squeezed into whatever time remained between governance meetings.
The team didn’t feel less coordinated. They felt more coordinated because the remaining meetings were purposeful. The status information that used to consume meeting time was available asynchronously and was often more current than what had been shared in the meetings.
The operating model included a quarterly cadence review applying the same two diagnostic questions to every recurring meeting. Meetings that couldn’t answer both were candidates for elimination. The test for any meeting is whether it enables a specific decision; if it doesn’t, the information can travel through a cheaper channel. When you build the governance model this way, the operating model outlives the program because the team knows how to maintain it.
