Why Executive Search starts too late.

Most Executive Search mandates begin with a vacancy.

The position has been approved. A job title has been agreed. A job description has been prepared. Compensation has a range. Reporting lines have been drawn.

Then the search begins.

Operationally, this makes sense. There is little reason to approach candidates before an organization knows it intends to hire.

Methodologically, however, something important has already happened. A series of assumptions about the hire have become requirements — often before they have been tested.

The organization has decided what the position is called, which experience it requires, how senior the person should be, where the person should live and approximately what the market should cost.

Executive Search is then asked to find someone who fits.

That is why Executive Search often starts too late.

A vacancy is the end of an internal process

Consider how a new leadership position typically emerges.

Something inside the organization creates pressure. A business is entering Mexico. A commercial organization is not growing quickly enough. A plant needs stronger leadership. Service performance is deteriorating. A founder needs to delegate. A regional structure has become too complex. A senior employee leaves.

Those are business situations. They eventually become hiring requirements.

But during that translation, organizations naturally move toward what is familiar: a title, reporting line, experience requirement and job description.

The original question might have been: "How do we build our Mexican operation?"

By the time it reaches the market, it may have become: "We need a Country Manager with 15 years of experience in our industry."

Those are not the same question. The second is one possible answer to the first.

"A hiring requirement is already a hypothesis about how to solve a business problem."

That distinction matters because Executive Search should be capable of testing the hypothesis — not merely executing it.

Requirements harden quickly

Once a requirement has been documented, it gains authority.

Ten years of experience becomes a minimum. Industry experience becomes mandatory. A particular degree becomes preferred. The candidate needs to live in a specific city. A certain title becomes the benchmark for seniority.

None of these requirements are necessarily wrong. The problem is that their origin is often difficult to reconstruct.

Why ten years rather than seven? Why must the candidate come from the same industry? Why is experience managing 50 people important? Why does the role require an engineering degree? Why is relocation unacceptable?

Sometimes there is a strong answer. Sometimes the answer is simply that this is how the organization imagined the profile.

The distinction only becomes visible when someone asks.

Search should separate the problem from the proposed solution

A better starting point is to temporarily put the candidate profile aside. Before discussing who should be hired, understand what needs to change.

Suppose an industrial equipment manufacturer wants a new Service Manager. The job description might emphasize:

• mechanical or mechatronic engineering;
• ten years of industry experience;
• five years managing technicians;
• advanced English;
• experience with similar equipment.

All reasonable criteria.

But now consider the underlying situation. The company already has technically capable technicians. Its real problem is inconsistent planning, weak communication with customers, limited service revenue and poor coordination between Mexico and international headquarters.

That changes the search.

Technical depth still matters, but perhaps the strongest candidate is not the person who knows the machinery best. Perhaps the company needs someone who can build processes, lead technicians, communicate commercially with customers and create confidence across borders.

The business problem has changed the weighting of the candidate criteria. The search is already better before a single person has been contacted.

The cost of starting late appears in the market

When assumptions are not examined before sourcing, the market eventually examines them for us.

Candidates may consistently reject the compensation. The required combination of technical expertise, leadership experience and English may be exceptionally scarce. Strong candidates may exist, but not in the specified location. People from the preferred industry may repeatedly lack another capability the role requires. Candidates who meet every technical requirement may not want the travel intensity.

The search starts to feel difficult.

At this point, organizations often ask for more candidates. But more sourcing does not solve a specification problem.

If the market repeatedly produces the same signal, the right response may be to revisit the assumptions behind the search.

"When the same constraint appears across candidate after candidate, it stops being candidate feedback and becomes market evidence."

This is one reason the first weeks of a search are so informative. The market is testing the organization's hiring hypothesis.

Earlier does not mean sourcing earlier

Starting Executive Search earlier does not mean contacting candidates before the organization is ready. It means beginning the reasoning earlier.

There is a useful period between: "We think we need to hire." and: "Start sending us candidates."

That period is where some of the highest-value search work can happen.

What business outcome should the hire create? What will this person inherit? What should be different after twelve months? Which capabilities are essential to producing that outcome? Which requirements are evidence of those capabilities, and which are simply proxies? Where can the organization compromise? What would cause us to change the profile? What does the relevant market actually look like?

Answering these questions does not delay a search. It prevents the search from spending weeks answering the wrong question.

Alignment matters before evaluation

Starting earlier also exposes another problem: decision makers may not actually agree on the hire.

A CEO may want a builder. A regional leader may want an experienced operator. HR may prioritize leadership maturity. The direct manager may want deep technical expertise. Headquarters may expect someone comfortable within an established corporate structure.

Each perspective can be reasonable. The disagreement becomes expensive only when it remains invisible.

If it surfaces during final interviews, the candidates absorb the consequences. One interviewer sees a strength where another sees a weakness because they are evaluating against different definitions of success.

This can look like a candidate problem. It is often an alignment problem.

The right moment to discover that disagreement is before the search begins.

The Discovery Experience is part of the search

This is why we treat discovery as part of Executive Search rather than as an administrative kick-off.

The purpose is not simply to collect information required to write a job description. It is to understand the decision well enough to construct a search hypothesis.

That means exploring the business context, expected outcomes, organizational constraints, candidate market, decision makers and uncertainties surrounding the role.

The output should not be more documentation. It should be greater clarity.

By the time sourcing begins, the organization should be able to explain:

• why the hire exists;
• what success looks like;
• which evidence matters most;
• where flexibility exists;
• and which assumptions the market still needs to test.

That is a very different starting point from an approved job description.

A better search begins before the vacancy

Executive Search will always need to find people. But finding people is increasingly the easier part of the problem.

The more consequential work begins earlier: understanding what the organization is trying to accomplish and translating that understanding into a decision the market can test.

Sometimes that process confirms the original requirement. Sometimes it changes the compensation. Sometimes it broadens the target market. Sometimes it removes a requirement that sounded important but was not connected to success.

And occasionally it reveals that the organization should not hire the position it originally imagined at all.

That is not search failure. It is exactly what good methodology should uncover.

The search should not begin when we know the title. It should begin when we start asking why the hire needs to exist.