The vector problem
Consider each person on your team as a vector — with both magnitude and direction. Magnitude is their skill, their depth, what they can produce. Direction is their alignment with where the company is headed and how the team works together.
When people are aligned in direction, their magnitudes add up. The total output of the team is greater than what any individual could produce alone. But when direction is off — even slightly — the total sum drops. And here's the part that rarely gets said out loud: a highly capable person who is misaligned can subtract more from the team's output than they add individually. Their skill is real, but the friction they create, the focus they pull, the misalignment they introduce into a previously coherent team — all of that reduces the sum.
This idea comes from Elon Musk. It's a simple model, but it explains something that most hiring processes ignore: a technically brilliant developer who doesn't fit how your team operates, communicates, or makes decisions can be a net negative. Not because they lack talent, but because their vector points the wrong way. And the reverse is equally powerful: when you hire someone whose magnitude is strong and whose direction is genuinely aligned, the effect on the team compounds far beyond their individual contribution.
This is why staffing is harder than it looks. It's not primarily a technical matching problem. Technical skills matter, obviously. But alignment to the culture, values, and direction of the company is in most cases even more important than raw capability.
The four things you never stop adjusting
Every company that scales successfully has to continuously adjust four things. Not once. Not during a reorg. Continuously, as the company grows.
The first is how you operate. Process, structure, communication — the machinery that keeps teams moving in the same direction. As a general rule, you want as little overhead and process in place as possible: enough to remain efficient and organised without killing innovation.
The second is how you scale. What works at five people breaks at fifteen, and what works at fifteen becomes a bottleneck at fifty. Growth pace, coordination overhead, and org design all need constant adjustment. This isn't the same problem as day-to-day operations — it's about anticipating the next stage and restructuring before things break.
The third is how you build. Your technology stack, architecture, and delivery practices compound over time. Early choices either accelerate delivery or introduce complexity that slows everything down. And as we'll explore in this series, what you build on directly determines the talent pool you'll be recruiting from.
The fourth is how you staff. This is by far the most difficult and the most important. You can have excellent operations, a clear scaling plan, and a strong technical foundation and still achieve nothing if you hire the wrong people. You also need different people at different stages — and some will grow with the company while others won't. That's not a failure. It's a structural reality of scaling.
Vision sits above these four — what you're building and why. It's the one most leaders naturally gravitate toward, the one that gets the most airtime in board meetings and strategy sessions. We won't dive into it in this series. Not because it doesn't matter, but because it's the one that already gets the most attention.
Alignment isn't agreement
Alignment isn't just about agreeing on the company mission in the abstract. It's about the specific, daily things: why are we on this team together? What exactly are we building and for whom? Do we share a sense of what matters most? Do we have mutual trust and respect? These questions sound soft, but they determine whether a team's vectors add up or cancel out.
There's also a meaningful difference between rational compliance and genuine buy-in. The phrase 'disagree and commit' sounds mature, but in practice, someone who commits without real conviction never produces at the same level as someone who is fully aligned. Genuine excitement about the work acts as a multiplier on everything else — speed, initiative, quality, resilience. Without it, you get compliance. With it, you get momentum.
What this series covers
This series covers all four pillars — how you operate, how you scale, how you build, and how you staff — and the relationships between them.
Why doesn't adding more people make you faster? What changes after product-market fit that makes your early hiring playbook stop working? Why does your technology stack constrain your talent pool more than you think? What makes one talent market fundamentally deeper than another? And why does most staffing fail before anyone even looks at a CV?
The thread that connects all of them is one principle: the best developers are made by working alongside other great developers. Talent is the raw material. The environment is what refines it. Every decision in this series — from how you identify your key people, to what you build on, to where you look, to how you match — flows from that principle.
