May 12, 2026 · 1 min read
Leading engineering organizations at scale
Notes on growing teams from ten to a hundred without losing the thread.
A short note on what changes when an engineering org crosses fifty people, and what
stops working when it crosses a hundred.
The shape of the problem
At ten engineers, the bottleneck is execution. At fifty, it is alignment. At one
hundred, it is clarity of intent.
The instinct is to add process. The better move is to add explicit shared
context — written, versioned, and short enough that anyone can read it on a
Tuesday morning.
Three things I keep returning to
- Write the operating model down. If it isn’t written, it isn’t real.
- Optimize for handoffs, not for individual heroics.
- Make the cost of changing direction visible — and pay it deliberately.