06 Scaling Operations
Why Teams Suddenly
Feel Heavy
Growth quietly creates operational weight.
The weight accumulation
Growth
More people, more complexity
Complexity
Systems lag behind headcount
Friction
Coordination cost rises invisibly
Slowdown
Team feels slower despite more resources
Teams don't feel heavy because people got worse. They feel heavy because the systems didn't grow with them.
Why this matters
The feeling that growth makes teams slower is one of the most common and least understood scaling experiences.
Founders who've successfully grown a team from 10 to 50 people often describe the same paradox: the company has more resources than ever, and execution feels slower than it did with half the team. More meetings. More coordination. More time spent on internal communication and less on actual work.
This is not a people problem. The team is often better than it was — more experienced, more diverse, more capable. The problem is structural: the systems, processes, and communication patterns that worked at 10 people were never updated to work at 50. The organisation grew but the operating model didn't.
Understanding what specifically creates operational weight is the first step to reducing it. Most of it is not inevitable — it's the accumulated cost of decisions that were never made about how the organisation should work as it grew.
Founder reality
Identify the sources of operational weight in your current team:
Has the number of recurring meetings grown faster than the number of decisions those meetings produce?
Are there decisions that are waiting for someone who is always in other meetings or conversations?
When a project stalls, is the cause usually unclear ownership — rather than a lack of capability?
Have informal communication patterns that worked at 15 people become bottlenecks at 40?
Is there work that requires input from many people that could be decided by one person with clear authority?
Operational weight accumulates gradually. It's rarely felt as one large problem — it's felt as persistent, low-level friction across everything.
The sources
Four sources of operational weight in growing teams
Each source is structural. Each has a structural solution.
01
Coordination overhead — the cost of keeping everyone aligned
At small scale, alignment happens informally. As the team grows, informal alignment fails — but formal processes haven't replaced it. The result is excessive coordination: meetings to align on decisions, Slack threads to check on status, syncs to understand what other teams are doing. Each instance is small. The cumulative cost is enormous.
02
Decision bottlenecks — too many decisions flowing through too few people
In early-stage companies, the founder and a few key people make most decisions. As the team grows, this centralisation becomes a bottleneck. The decisions queue. Work waits. The people at the bottleneck are overwhelmed and the rest of the team is blocked. Distributing decision authority is the structural fix — but it requires defining who decides what.
03
Ownership gaps — work that nobody is clearly responsible for
Growing teams almost always have ownership gaps: areas of work that multiple people partially own and none fully own. These gaps produce dropped balls, repeated conversations about who's responsible, and low-quality execution in areas where nobody feels fully accountable.
04
Process lag — systems designed for the team's previous size
The processes that governed work at 15 people were not designed for 40. They persist because nobody stopped to redesign them. They produce friction: approvals that go to people who no longer need to approve them, communication channels that were useful early but are now noise, and rituals that consume time without producing value.
Common mistakes
01
Hiring more people into a heavy system
More people in an operationally heavy system adds more coordination overhead, more ownership confusion, and more process lag. The system gets heavier before it gets lighter — often without a corresponding increase in output.
02
Treating heaviness as a culture problem
Operational weight is often diagnosed as a motivation or culture issue: 'people aren't moving fast enough'. It's almost always a structural issue. Fixing culture without fixing structure produces short-term energy with no lasting improvement.
03
Adding more process to solve process problems
The reflex when coordination fails is to add more coordination mechanisms. This reliably makes things heavier. The goal is less coordination through clearer ownership — not more coordination through better meetings.
04
No operational review at growth milestones
Companies review financial performance at regular intervals. Most don't review operational design at growth milestones. An operational review at 25, 50, and 100 people prevents the accumulation of structural debt.
Example scenario
A B2B SaaS company, 55 people, 18 months post-Series A. Revenue growing. Team velocity declining. CEO describing the team as 'moving through mud'. No obvious cause.
The operational audit
Recurring meetings catalogued: 34 across the organisation. Average attendee count: 6. Total meeting hours per person per week: 14.2.
Decision log reviewed: average time from decision initiation to decision made for cross-functional decisions: 11 days.
Ownership map drawn: 7 significant areas of work with no single named owner.
Processes reviewed: 5 approval workflows that required founder sign-off for decisions under €2,000.
The structural fixes (over 8 weeks)
12 recurring meetings eliminated or merged. Meeting attendee criteria defined.
Decision authority matrix created: 80% of operational decisions delegated to team leads.
7 ownership gaps addressed: each assigned a named accountable owner.
Approval thresholds raised: founder sign-off required only above €10,000.
The outcome
Average meeting time per person reduced to 7.4 hours per week. Cross-functional decision time reduced to 3.2 days average. Team described the change as 'feeling like a different company' — with no new hires made.
Takeaway
Teams feel heavy because of structural debt, not people problems.
Identify the coordination overhead, decision bottlenecks, ownership gaps, and process lag. Address them structurally. The team you have is capable of moving faster — the system just needs to let them.
Continue reading
The Meeting Problem