06 Scaling Operations
The Meeting
Problem
Too much coordination quietly kills momentum.
The meeting trap
Unclear ownership
Nobody decides independently
Dependency
Everything requires alignment
Meetings
Coordination mechanism for unclear systems
Execution drag
Less time for actual work
Meetings multiply when ownership is unclear. Fixing meetings without fixing ownership just makes them shorter — not rarer.
Why this matters
Meetings are a symptom. The disease is unclear ownership and systems that don't support independent decision-making.
Every organisation that grows past a certain size develops a meeting problem. The calendar fills. Deep work time disappears. Energy that should go into execution goes into coordination. The team is busy — but the busyness doesn't translate into output at the rate that the headcount would suggest.
The instinct is to fix the meetings themselves: shorten them, add agendas, introduce better facilitation, or implement no-meeting days. These interventions help at the margins. They don't fix the structural cause — which is that the organisation has more coordination need than its ownership structure can handle independently.
Reducing meetings sustainably requires asking why the meetings exist. Usually the answer is: because something is unclear, decisions can't be made without checking, or multiple teams have overlapping ownership of the same area. Fix those things — and the meetings become optional.
Founder reality
Diagnose the meeting problem structurally before designing a fix:
If you removed 30% of your recurring meetings today, which ones would you actually miss — and why?
For each standing meeting: could the outcome be achieved asynchronously if the right ownership and clarity existed?
Which meetings exist primarily because someone doesn't have the authority or information to decide independently?
How many hours per week does each person spend in meetings — and is that consistent with what their role actually requires?
Are the people who most need deep work time the same people most burdened by meetings?
Mapping meeting purpose to ownership gaps reveals which meetings are structural and which are habitual.
The system
Four meeting types and what they signal
Categorise your meetings. The category reveals the structural cause.
01
Status meetings — information sharing that could be async
Status updates, progress reports, and 'what did everyone do this week' meetings exist because information isn't systematically available without a meeting. The fix: make information transparent by default (shared dashboards, async updates, documented decisions) so that the meeting becomes unnecessary rather than more efficient.
02
Alignment meetings — decisions that require too many approvals
Cross-functional meetings to align on a decision that one person could make signal an authority gap. Either the decision-maker hasn't been identified, or the decision-maker doesn't have confidence in their authority. The fix: define who decides, give them the authority, and remove the requirement to align before acting.
03
Coordination meetings — work handoffs that lack clear process
Weekly syncs between teams that need to hand work off to each other exist because the handoff process is unclear. The fix: define the handoff protocol explicitly — what information is needed, in what format, by when — so the sync becomes a process check rather than a negotiation.
04
Relationship meetings — useful, rare, hard to systematise
Not all meetings are coordination overhead. Some are genuine relationship investments, creative sessions, or complex multi-party decisions that genuinely require real-time discussion. Protect these. Reduce the others so that attention is available for them.
Common mistakes
01
Implementing meeting-free days without addressing the cause
No-meeting Wednesdays move meetings to other days. They don't reduce the total meeting load. The meetings that were happening on Wednesday now happen on Tuesday and Thursday — with more scheduling friction.
02
Shortening meetings rather than eliminating them
A 30-minute status meeting is still a status meeting. The question is not 'how do we make this meeting shorter' but 'why does this meeting need to exist?'
03
Blaming meeting culture without addressing meeting structure
Telling the team 'we have too many meetings' without changing the ownership structures that create meeting need produces short-term reduction and long-term rebound. Culture changes when structure changes.
04
Protecting deep work time without redistributing the meeting burden
When senior people protect their calendars, the meeting burden shifts to junior people. The problem moves rather than reduces. Calendar protection must be accompanied by ownership clarification that reduces the total coordination requirement.
Example scenario
An engineering team, 28 engineers, averaging 16 meeting hours per person per week. Engineering manager calculating that half the team's productive time was consumed by coordination.
The meeting audit
22 recurring meetings catalogued. Purpose categorised per framework.
Status: 8 meetings. All replaced with async written updates in a shared Notion workspace.
Alignment: 6 meetings. Decision authority for 5 of 6 delegated to individual engineers or leads.
Coordination: 5 meetings. 3 replaced with a documented handoff protocol and a shared ticket system.
Remaining: 3 meetings retained as genuinely valuable.
The outcome
Meeting time per person reduced from 16 to 5.5 hours per week within 6 weeks. Engineering output (measured by feature completion velocity) increased 34% over the following quarter — with no new hires.
Takeaway
Fix the system that creates meeting need — not the meetings themselves.
Make information transparent, distribute decision authority, and define handoff protocols. When the structural causes are addressed, most meetings become optional — and the remaining ones become better.
Continue reading
Operational Bottlenecks in Growing Teams