The pressure to move fast on talent is real. A board approves a new strategic direction, the CEO announces an evolution, and the first visible action is a wave of leadership hires. It signals momentum. It demonstrates commitment. And it almost always creates problems that take years to unwind.
The issue is sequence. Hiring leaders before you've designed the operating system they'll work within is like building a team before you've drawn the field. The leaders arrive with their own assumptions about how decisions get made, how resources get allocated, and how accountability works. Those assumptions collide with each other and with the existing organization. The result is the friction, misalignment, and underperformance that gets labeled an execution problem — when it was actually a design problem from the start.
What Operating System Design Actually Means
When we talk about operating system design, we mean the set of structural choices that determine how an organization actually functions: who owns which decisions, how resources flow to priorities, what the accountability structure looks like, and how the leadership team interacts. These aren't abstract concepts — they're the practical mechanisms that determine whether a strategy gets executed or gets stuck.
Most organizations have an operating system. The problem is that it's often implicit, inherited from a previous era, or misaligned with the current strategy. An evolution initiative that doesn't address the operating system is building on a foundation that will undermine it.
The Hiring Trap
When leaders are hired before the operating system is designed, several predictable problems emerge. First, each new leader optimizes for their own domain rather than the whole. Without clear decision rights and accountability structures, the rational move is to maximize your own team's resources and influence. The result is a leadership team that competes internally rather than coordinates.
Second, the new leaders spend their first months trying to understand how things actually work — which is different from how the org chart says they work. That's time not spent on the work they were hired to do.
Third, when performance disappoints, the diagnosis is almost always wrong. The board sees execution failure. The real cause is design failure. The response is to replace leaders rather than fix the system — which restarts the cycle.
The Right Sequence
The organizations that execute evolutions well do the design work first. They define the operating model, clarify decision rights, and establish the accountability structure before they hire the leaders who will work within it. This takes longer upfront. It requires the CEO and board to make hard choices about structure before they have the full leadership team in place. But it produces dramatically better outcomes.
It also produces better hires. When you know what operating model you're building, you can hire leaders who have succeeded in that model before — rather than hiring generically strong executives and hoping they figure it out.
If you're planning a leadership build for an evolution initiative, the most valuable conversation we can have is about sequence. Getting that right changes everything downstream.
