The Unicorn Trap: Planners, Executors, and the Roles You Can't Fill

The Roles Nobody Can Fill

Every leader has a role like this. You write the job description, interview twenty strong candidates, hire the best one, and six months later you are quietly disappointed. Not because they are weak, but because the role itself asks for two people. Product Manager is the textbook case: you want deep discovery, ruthless prioritization, and a coherent strategy - the thinking work - and in the same breath relentless shipping, unblocking, and delivery drive - the doing work. Those are not two skills you can train into one hire. They are two different minds.

The usual response is to blame the market ("great PMs are rare") or the candidate ("this one just was not strong enough"). Both miss the real problem. The role is asking a single person to run two opposing cognitive engines at full power, and the research on how those engines work explains why so few people can.

The Research: Two Modes, Rarely in One Head

Arie Kruglanski and Tory Higgins identified two independent systems of self-regulation. Assessment is the drive to compare, evaluate, and judge quality against alternatives - the planner's engine. Locomotion is the drive to move, to make things happen and keep going until they are done - the executor's engine. Because they are independent, being high in one tells you nothing about the other. The best performers are high in both, but that combination is genuinely rare, which is exactly why "unicorn" roles feel impossible to staff.

Heinz Heckhausen and Peter Gollwitzer's Rubicon model names the seam where the two modes collide: the line where deliberation must end and commitment begins. Assessment-heavy people over-stay before that line, refining the plan. Locomotion-heavy people cross it too fast, committing before they have fully looked. A role that demands living on both sides of the line at once is built for a person who mostly does not exist in your hiring pool.

What Organizations Actually Pay For

Here is the asymmetry that quietly distorts these roles. Locomotion is visible and revenue-linked - shipped features, closed deals, dates hit - so organizations pay for it eagerly and can see exactly what they bought. Assessment is invisible until it is absent - the architecture call that prevented a rewrite, the risk flagged before it detonated, the strategy that kept the roadmap coherent. Companies systematically underprice assessment right up until a CrowdStrike-scale incident makes its absence extremely expensive.

That asymmetry sets the trap. Because output is easier to see than judgment, hybrid roles get hired for their locomotion ("can they ship?") and quietly punished later for weak assessment ("why is the strategy a mess?") - or the reverse. The market reserves its biggest premium for the rare few who are genuinely high in both: founders, general managers, senior PMs. That premium is a signal that the combination is scarce, not a strategy for staffing around the scarcity.

Which Mind Fits Which Role

Most roles lean cleanly one way, and they staff best when you hire for that lean. The trouble starts with the third group.

Why the Hybrid Roles Are Defined Wrong

The problem is not the people you hire. It is the role. When a single seat demands both modes, you get one of two predictable failures. The planner-in-the-seat: rich strategy, slow shipping, a team asking "why isn't anything happening?" Or the executor-in-the-seat: fast shipping, thin strategy, a team asking "why are we building the wrong things, fast?" Then the organization concludes it hired the wrong person and runs the same impossible search again.

Product Manager is the clearest example - I have argued separately that the PM role is expanding, absorbing research, design, and delivery; this is the structural reason that expansion is so hard to staff. But the same fault line runs through the Engineering Manager (an architect's judgment plus a delivery driver's push), the Chief of Staff (strategic synthesis plus relentless follow-through), and the founder role itself. It is not a coincidence that so many enduring companies are co-founded by a visionary and an operator. They split the role that one person could not hold.

The Redesign: Three Moves

Once you see a role as two modes rather than one job, you have three levers, and all three beat "find a better candidate."

1. Split. Separate the assessment half from the locomotion half into two complementary roles. In product, that is a discovery-and-strategy lead paired with a delivery-focused owner or technical program manager. This is the Visionary and Integrator split from Gino Wickman and Mark Winters' Rocket Fuel, applied at the level of a single role instead of the whole company.

2. Pair. Keep the role, but staff it as a deliberate complementary pair. Antonio Pierro, Kruglanski and colleagues ran three field studies on regulatory-mode complementarity and found peak work performance when both modes are high - and, critically, that this holds across two people in a team, not only within one person. A high-assessment lead paired with a high-locomotion partner reliably outperforms a compromise hire who is mediocre at both.

3. Scope to the phase. The same role needs a different mode at different stages. Early-stage rewards locomotion - ship, learn, adjust; Saras Sarasvathy's research on expert entrepreneurs found they start from affordable loss and available means rather than a finished plan. Scaling rewards assessment - systems, risk, coherence. Define the role for the phase you are in, and re-scope it deliberately as you grow, instead of pretending one job description spans the life of the company.

The Counterarguments Worth Taking Seriously

The handoff tax is real, and over-splitting has its own cost. The moment you break one seat into two, you add a coordination seam. The planner's intent gets translated, compressed, and partly lost on its way to the executor, while a single mind holding both keeps the full context in one place. A badly managed seam is slower than one accountable owner and produces less coherent work, the "designed by committee" deliverable. Shatter too many roles into narrow specialisms and you trade the unicorn problem for a fragmentation problem, where everyone optimizes their own half and no one is accountable for the whole. That is its own way to lower the quality of both the decisions and what ships.

Some seats need a single throat to choke. End-to-end accountability for an outcome is itself a design requirement. If the plan sits with one person and the delivery with another, the result can fall between two chairs. This is why the default fix is usually pair, not split: a tightly coupled duo with shared accountability keeps both modes present without cutting the outcome in half.

And the genuine integrator is worth finding. People who are strong in both modes do exist, and they make better calls than any handoff can, because a good decision needs both the assessment to weigh the options and the locomotion to commit, and that crossing happens most cleanly inside one head. When you find one, put them in the seat that truly demands integration, keep them, and pay for them. The argument is not that range has no value. It is that you cannot staff a whole organization on the assumption that range is common.

So the point is not to split everything, and it is not to specialize everything either. It is to design each seat for a coherent capability while protecting end-to-end ownership: split only where the handoff is clean, pair where two modes are genuinely needed, reserve the rare integrators for the roles that require them, and keep enough overlap that the organization stays resilient. The failure to avoid is treating a role-design problem as a hiring problem, not specialization itself.

The Move for a Leader

Audit your hardest-to-fill and highest-turnover roles. For each one, ask a single question: does this seat demand a planner and an executor at the same time? If it does, you do not have a talent problem. You have a role-design problem - and unlike the talent market, role design is a lever you actually control.

If this surfaced a role in your own organization that never seems to work no matter who sits in it, that is usually the tell. It is worth a conversation about how the role is drawn, not just who fills it next.

Related Reading

• The Expanding PM - The companion argument: why the PM role is absorbing research, design, and delivery. This essay is the structural reason that expansion is so hard to staff in one person.
• The Operator-Consultant Method - How I run organizational reviews, including role and team-structure diagnostics.
• The Performance Paradox - Why teams and individuals plateau, and what actually breaks the plateau.
• Use Cases from the Field - Patterns from real organizational reviews across regulated and growth-stage tech companies.