top of page

The Executive Hiring Trap: How Cognitive Biases Distort Recruitment — And Why Schemas Help Us See Beyond the CV

Ian Stewart
May 16
3 min read

When executive appointments fail, the post-mortem usually sounds familiar.


"The chemistry felt right."

"They interviewed brilliantly."

"Everyone was aligned."

"Their track record was exceptional."


Yet twelve months later, the board is discussing performance concerns, senior leaders are leaving, and the organisation is quietly asking how such a promising appointment went wrong. The uncomfortable reality is that executive recruitment is not simply a process of evaluating talent. It is also a process of managing human judgement. And human judgement, however experienced we believe ourselves to be, is full of predictable blind spots.


Recruiters and boards do not simply assess candidates. They interpret them. That interpretation process is heavily influenced by cognitive biases.


The problem is not that recruitment lacks rigour. Many executive searches involve multiple interviews, psychometrics, assessments and reference checks. The challenge is that these processes often evaluate presentation more effectively than behaviour under pressure.


One of the most common distortions is the halo effect. A candidate communicates with confidence. They appear calm, articulate and decisive. Very quickly, one positive characteristic begins influencing broader judgements. Confidence becomes competence. Articulate becomes strategic. Decisive becomes strong leadership. We see this constantly in executive recruitment. Interview performance can become confused with leadership capability. Charismatic individuals often create a compelling narrative around their achievements, and interview panels unconsciously fill in the gaps.


The difficulty is that organisations do not hire executives to perform in interviews. They hire them to perform under pressure.


Another bias emerges through what might be called the track record fallacy. A candidate successfully scaled a high-growth technology company. Another transformed a large division. Someone else delivered a major turnaround. These experiences matter. But they also create an assumption that success is portable.


We frequently ask: "What did they achieve?" Less frequently we ask: "What conditions allowed them to achieve it?" Perhaps they inherited a highly capable team. Perhaps strong systems protected weaknesses. Perhaps market conditions were favourable. Perhaps a founder's culture absorbed behaviours that would fail elsewhere.


Leaders do not carry results with them. They carry behavioural patterns. This becomes particularly dangerous when pressure rises. In interviews, leaders often describe themselves in aspirational terms:


"I'm collaborative."

"I empower people."

"I value challenge."


And they may genuinely believe these things. But pressure changes behaviour.

Under stress, people stop relying primarily on conscious leadership principles and increasingly rely on automatic patterns — the behaviours that feel instinctively right.


This is where schemas become useful.


Schemas are deeply learned cognitive and behavioural patterns that shape how people interpret situations and react to them. They are not personality traits, and they are not labels. Rather, they act as default operating systems that become more visible when stakes increase.


A leader who appears collaborative in calm conditions may become highly controlling during uncertainty. A leader who appears inclusive may avoid difficult conversations when relationships feel threatened. A leader who appears decisive may become rigid when authority feels challenged.


These patterns are predictable. And importantly, they can be assessed.


In our work, we often observe recurring leadership schemas emerging at executive level.

The Commander brings clarity, speed and decisiveness, but under pressure can centralise control and suppress challenge.

The Architect creates systems and long-term thinking, but can become overly process-driven and slow execution.

The Servant builds trust and loyalty, but may avoid difficult performance conversations.

The Collaborator creates alignment and cohesion, but can over-prioritise consensus at the expense of pace.


None of these schemas are inherently good or bad. The question is whether they fit the problem the organisation is trying to solve. This fundamentally changes the role of the recruiter.


Traditional executive recruitment often focuses on selecting the most impressive candidate. Schema-informed recruitment asks a different question: "How will this person's behavioural patterns interact with this organisation?"


That shift matters enormously.


Consider a turnaround environment requiring rapid decisions and restructuring. A

Commander profile may create the necessary urgency. Move the same leader into a highly collaborative culture and the exact same behaviours may reduce trust and silence challenge. Similarly, a Servant-oriented leader may thrive in a post-conflict culture requiring repair and engagement, while struggling in an activist investor environment demanding aggressive performance correction.

Success therefore becomes less about identifying the "best" leader and more about understanding behavioural fit. Schemas also help recruiters protect candidates, not just clients.


Historically, recruitment has often asked: "Can this person do the role?" A schema lens introduces another question: "Will this environment allow this person to succeed?"


Because even strong leaders can fail when placed in systems that repeatedly activate their less helpful patterns. Executive recruitment therefore becomes something larger than talent acquisition.


It becomes behavioural risk management.


The best recruiters have always done some version of this instinctively. They develop a feel for patterns through experience. Schemas simply give language and structure to what seasoned recruiters often know already: Leadership success rarely lives in a CV.


It lives in the hidden behavioural patterns that emerge when pressure arrives.


 
 
 

Comments


bottom of page