Creators and evolvers are different people.
The most expensive misdiagnosis in leadership hiring
When a senior engineering hire fails, the post-mortem almost always lands on the person: wrong caliber, wrong culture fit, oversold in the interview. Sometimes that's true. More often, in our experience, the diagnosis is wrong. The person was genuinely talented — and genuinely wrong for the stage of the thing they were hired to run.
Companies hire one profile to build a thing and a different profile to scale and run it. The first — call them creators — do their best work at zero-to-one: no product, no team, no constraints worth respecting, and a blank page they get to fill. The second — evolvers — do theirs in the middle of something that already exists: a working platform, a team they didn't hire, customers who depend on the thing not breaking, and a mandate to take it from where it is to where it has to go.
Neither profile is the senior version of the other. They are different people, energized by opposite conditions. A creator handed an evolver's job experiences it as a demotion into maintenance, and eventually treats the existing platform the way they treat every obstacle to building: as something to replace. An evolver handed a creator's job experiences it as a void — they wait for inputs that aren't coming, build process for a product that doesn't exist, and optimize a machine with nothing in it. Both look, from the outside, like talent problems. Both are actually the same mistake made in opposite directions: the search never asked which stage the role was really at.
Get the full paper
The complete paper — the rest of the argument, the working detail, and the record — as a PDF.
Hiring for a role like the ones in this paper?
Start with the question we open every search with: if we're successful a year from now, what are we talking about that really worked out well — with the candidate we place?