Managing Technical Organisations Through Growth
Technology organisations face specific challenges as they scale from small teams to large engineering organisations. The practices, structures, and leadership approaches that work at 10 engineers become bottlenecks or break entirely at 100. Managing through growth requires deliberately evolving the organisation as the headcount increases.
The Scaling Inflection Points
- ~10 engineers: Informal coordination works. Everyone knows everything. The CTO/engineering lead can be in every decision.
- ~20-30 engineers: Need formal team structure. Communication channels multiply. Code ownership and architectural decision-making need structure.
- ~50-70 engineers: Multiple teams need coordination mechanisms. Platform/infrastructure team becomes necessary. Engineering management layer required.
- 100+ engineers: Organisational design (Spotify model, DDD-aligned teams) becomes critical. Standardisation vs autonomy tension intensifies.
Preserving Engineering Culture at Scale
Early-stage engineering cultures — high trust, autonomy, fast decision-making, shared context — are fragile under growth. Process, bureaucracy, and coordination overhead can kill them. Preserve culture intentionally: document and articulate values, hire for cultural contribution (not just cultural fit), maintain engineering-driven spaces (hackathons, tech talks, architecture reviews), and protect maker time from management overhead.
Hiring and Talent Strategy
At scale, hiring quality matters more than individual technical decisions. A hiring bar that weakens over time under growth pressure compounds over years. Invest in structured interviewing, calibration sessions, strong engineering employer brand, and competitive compensation to attract and retain strong engineers throughout growth.