When my team was eight people, I knew everything. Every feature, every tricky bug, every person's strengths and what they were working on that week. Leading felt like an extension of engineering — just with more conversations. Then the org grew past fifty, and almost everything I believed about leading quietly stopped working. Scale doesn't just make the same job bigger. It changes the job entirely.
Here's what leading 55+ engineers actually taught me — the lessons that only show up once you can't hold the whole thing in your head anymore.
The story
The breaking point wasn't dramatic. It was a Monday where I realized I no longer knew what half the org was building in detail, and I felt a flash of panic about it. My instinct, honed over years, was to fix that — to get back into the details, sit in more reviews, read more code. I tried. It lasted about two weeks before I was drowning and the teams were more stuck, because now they were waiting on a person who was spread across fifty things.
That failure taught me the first hard truth: at scale, your knowledge can't be the bottleneck, because it physically can't keep up. The job is no longer to know everything. It's to build a system where the right people know the right things and can act without you.
So I stopped trying to be the smartest node in the network and started trying to be the person who designed the network. That shift — from doing and knowing to enabling and aligning — is the whole game above a certain size.
What actually breaks at scale
Communication stops being free. At eight people, information just spreads — you overhear things, you're in every conversation. At fifty-five, nothing spreads on its own. If a priority isn't written down and repeated, half the org doesn't know it. I learned to over-communicate to the point that felt excessive to me, because what feels like repetition to the leader is often the first time most people are hearing it clearly.
Alignment beats brilliance. Fifty-five people rowing in slightly different directions produce less than thirty rowing together. I spent far more energy than I expected just making sure everyone understood why we were doing something, not just what. A team that understands the why makes good decisions when you're not in the room — which, at scale, is almost always.
You lead through leaders. I couldn't have a real relationship with fifty-five people. So my actual team became the leads, and my job became making them great. The quality of the whole org started to mirror the quality of that small group of leaders. Investing in them was the highest-leverage thing I did, by a wide margin.
At a small scale you scale yourself. At a large scale you can only scale through other people. The leaders who don't make that switch become the ceiling their org keeps hitting.
Consistency matters more than you'd like. With a few engineers, everyone can do things their own way and it's fine. At fifty-five, "their own way" times many teams becomes chaos — five different ways to deploy, to review, to handle on-call. Shared standards stop being bureaucracy and start being the thing that lets people move between teams and trust each other's work.
Key lessons
Your job is the system, not the work. Above a certain size, you create leverage by designing how decisions get made, how information flows, and how people grow — not by making decisions or doing work yourself.
Repeat yourself far more than feels natural. The message lands on roughly the fifth telling. What bores you is brand new to most of the room.
Grow leaders, not just engineers. The org will never be better than the layer of people you lead through. Pour into them.
Standardize the boring things so people can be creative about the important ones. Consistency in process frees up energy for actual problems.
Protect alignment like it's the product. Misalignment is the most expensive thing at scale, and it's invisible until it's costing you a quarter.
Action steps
If your team is growing past the point where you can hold it all in your head:
- Write down the priorities and repeat them everywhere. Make it so no one can honestly say they didn't know what mattered.
- Identify your real team — the leads — and invest in them first. Their growth multiplies; yours doesn't.
- Standardize the high-friction basics (deploys, reviews, on-call, definitions of done) so teams aren't reinventing them.
- Audit where you're still the bottleneck and systematically hand those decisions to owners.
- Spend real time on the "why." Every initiative should have a reason people can repeat back to you in their own words.
Final thoughts
Leading a large org humbled me. The skills that made me successful at a small scale — knowing everything, being in everything — were exactly the ones I had to let go of. It felt like losing control. What I gained was bigger: an org that could move fast without me, full of people who were growing because I'd finally gotten out of their way and put my energy into the system around them.
Scale is a forcing function. It exposes whether you're a great individual contributor wearing a manager's title, or an actual leader. The good news is that the switch is learnable — it just starts with admitting that the thing that got you here won't get you there.