Failure Prediction System™
Mandate failure is not sudden. It is telegraphed, weeks in advance, through five consistent signals. Most teams don't monitor them until after the damage is done.
Founder, Majhi Group & Majhi OS
The executive search that fails in week fourteen gave its first warning signal in week three. The pipeline collapse that forces a restart was telegraphed by response rate decay six weeks earlier. The candidate who drops off at offer stage showed signs of disengagement after the second interview.
Mandate failure is not sudden. It accumulates. And it does so through a consistent set of signals that appear in the same sequence, across different searches, different roles, and different organisations.
Mandate failure is not sudden. It accumulates. The executive search that fails in week fourteen gave its first warning signal in week three.
The Failure Prediction System maps five of them. Each signal is observable in real time. Each has a specific threshold at which it transitions from a warning to an alert. And each has a specific response that, if executed when the signal appears, prevents the downstream collapse.
The five signals
```
SIGNAL 1: RESPONSE DECAY
↓
[Reply rates dropping across channels.
Not a sourcing problem.
A positioning or timing problem.]
SIGNAL 2: FUNNEL STALL
↓
[Candidates entering but not advancing.
A process or decision problem.]
SIGNAL 3: INTAKE DRIFT
↓
[Requirements shifting without documentation.
A stakeholder alignment problem.]
SIGNAL 4: RECRUITER OVERLOAD
↓
[Mandate count exceeding execution capacity.
A resource allocation problem.]
SIGNAL 5: DECISION LAG
[Evaluation cycles extending past 72 hours
per stage. A hiring manager problem.]
```
Signal 1: Response Decay
Response decay is the single most reliable predictor of mandate failure, and the most frequently ignored.
What it looks like: Outreach response rate, the percentage of messages sent that generate any reply, starts at a baseline and declines week over week. The decline is gradual enough that it doesn't trigger alarm in week one. By week four, the rate is half what it was. By week six, the pipeline has slowed to a trickle.
The thresholds:
- Week 1–2 baseline: 20–30% for well-targeted outreach to a senior candidate pool
- Warning: Rate drops below 15% or declines more than 5 percentage points week over week
- Alert: Rate drops below 10% or two consecutive weeks of decline
Why it happens: Response decay signals one of three things. The positioning is wrong: the message is not giving the candidate a genuine reason to engage. The candidate pool is exhausted: the search has reached most of the available candidates and is recycling. Or the market has received enough of this type of outreach that fatigue is setting in and a different channel or approach is needed.
The response: When the warning threshold is reached, stop sending at volume. Pull the last 20 messages sent. Read them as the candidate would. Identify whether the opening gives a specific, relevant reason to respond or a generic description of an opportunity. If it's the latter, rewrite before sending another message.
The mistake: Treating response decay as a sourcing problem and responding by expanding the candidate list. More names sent through a broken message is not a fix. It is acceleration toward a stalled search.
Signal 2: Funnel Stall
Funnel stall occurs when candidates are entering the pipeline but not advancing through it. The top of the funnel looks healthy. The middle is where everything stops.
What it looks like: Response rates are acceptable. Initial conversations are happening. But candidates are not converting from first conversation to interview, or from first interview to second. The shortlist is thin relative to the volume of initial conversations.
The thresholds:
- Warning: Conversion rate from initial contact to substantive interview drops below 40%
- Alert: Two or more candidates decline to continue after a first conversation, citing the role, the process, or the company rather than timing or fit
Why it happens: Funnel stall has two primary causes. The first is a mismatch between the opportunity as described in outreach and the opportunity as experienced in the first conversation: candidates who expected one thing and encountered another. The second is a process friction problem: the next step is too slow, too burdensome, or too poorly communicated for candidates with options to stay engaged.
The response: Review the first conversation experience. What is the hiring manager or recruiter communicating about the role in that first call? Is it consistent with the outreach message? Is there a clear, specific, and compelling reason given for why this role is worth pursuing? Is the next step communicated clearly and scheduled promptly?
The mistake: Attributing funnel stall to candidate quality ("we're not getting the right people") when the problem is candidate experience.
Signal 3: Intake Drift
Intake drift is the most insidious signal because it is invisible in the data and only visible in the pattern of rejections.
What it looks like: Candidates who match the documented brief are being rejected. Or the hiring manager is asking for profiles that don't match the documented brief. Or the criteria that were agreed at intake, the specific experience, background, and scope requirements, have quietly shifted, without a formal update to the search parameters.
The thresholds:
- Warning: Two or more shortlisted candidates rejected with reasons that don't appear in the original brief
- Alert: Hiring manager requests a profile type that was explicitly not in scope at intake
Why it happens: Intake drift occurs when the person who defined the role at the start of the search has updated their thinking, through seeing candidates, through internal conversations, through changing company priorities, without communicating that update to the search team. The search is running against an old brief while being evaluated against a new one.
The response: Pause the search. Bring the hiring manager back to the brief. Go through every rejection reason and assess whether it was in the original criteria. If criteria have changed, formally update the brief before sending any more candidates. Accept that the search effectively restarted from the point of drift, and adjust timelines accordingly.
The mistake: Accepting the rejection reasons and continuing to source, assuming the search team's targeting is off when the brief is actually off.
Signal 4: Recruiter Overload
Recruiter overload is a capacity problem that manifests as a quality problem across every mandate a recruiter is running.
What it looks like: A recruiter carrying more mandates than their execution capacity allows begins making systematic errors: slower outreach, shallower candidate research, later follow-up, less thorough brief review. The degradation is gradual and affects all mandates simultaneously, making it hard to attribute to overload rather than to individual mandate difficulty.
The thresholds:
- Warning: A recruiter's active mandate count exceeds four simultaneous VP or C-suite searches
- Alert: Response time to candidate queries exceeds 24 hours, or candidate follow-up tasks are consistently falling behind schedule
Why it happens: Executive search is execution-intensive. Each mandate requires ongoing sourcing, outreach management, candidate communication, brief alignment, and reporting. Beyond a certain mandate count, the execution quality of each mandate degrades, not because the recruiter is less capable, but because the available attention per mandate falls below the threshold required to run the search well.
The response: Mandate reallocation. If a recruiter is overloaded, the lowest-priority active mandate should be paused or reassigned before quality degradation affects all of them. Trying to run five VP searches simultaneously at the execution standard that four requires does not produce five adequate searches; it produces five compromised ones.
The mistake: Treating recruiter overload as a motivation or skill problem rather than an arithmetic one.
Signal 5: Decision Lag
Decision lag is the signal that is most directly controlled by the hiring organisation and most consistently underestimated in its impact on candidate retention.
What it looks like: The time between a candidate completing an interview stage and receiving a decision or next step exceeds 72 hours. At the VP and C-suite level, candidates who are genuinely strong have other options. Every day of silence after an interview is a day in which the alternative option becomes more attractive by comparison.
The thresholds:
- Warning: Average time from interview completion to decision communication exceeds 72 hours
- Alert: Any candidate goes more than five business days without a substantive update after completing a stage
Why it happens: Decision lag is almost always caused by hiring manager availability: the decision-maker who is required to advance the search is too busy, is waiting for internal alignment, or has deprioritised the search in favour of other work. It is occasionally caused by committee dynamics where no single person has authority to move the process forward without consensus that takes time to achieve.
The response: At the start of every executive search, agree a specific decision timeline with the hiring manager: decisions will be communicated within 48 hours of each stage. Build this into the process documentation. When lag exceeds the agreed timeline, escalate proactively, not to pressure the hiring manager, but to surface the impact to the candidate pipeline before a strong candidate accepts something else.
The mistake: Treating decision lag as a candidate management problem ("keep them warm") rather than a process problem that only the hiring organisation can fix.
Using the system
The five signals are most useful as a monitoring checklist, reviewed weekly during any active executive search:
1. What is this week's response rate? Is it above or below last week?
2. What is the funnel conversion rate? Where are candidates stopping?
3. Have any candidates been rejected for reasons not in the brief?
4. Is the recruiter's total mandate count within execution capacity?
5. What is the average decision lag at each stage this week?
A search that can answer all five questions with data, and act on any that breach threshold, will not stall without warning. The stall will be predicted and pre-empted.
Most stalls are not inevitable. They are the accumulation of ignored signals.
See also: Compounding Failure Loop™, Hiring System Health™, Hiring SLO Framework™
Sources
Google: Site Reliability Engineering, How Google Runs Production Systems (SRE Book)
McKinsey: Successfully Transitioning to New Leadership Roles
Frequently Asked Questions
What are the earliest warning signals that a VP search is about to fail?
Response Decay is the most reliable early predictor: when reply rates drop below 15% or decline more than 5 percentage points week over week, the search is giving its first warning. Most teams don't notice until rates fall below 10% (the alert threshold) or until two consecutive weeks of decline. By then the candidate pool is partially exhausted and the market has formed a view of the opportunity. The second earliest signal is Intake Drift: when shortlisted candidates are rejected for reasons not in the original brief, the hiring criteria have changed under the search without documentation. Both signals are detectable in weeks 2-3 of a search that fails in week 14.
What should a recruiter do when response decay hits the warning threshold?
Stop sending at volume immediately. Pull the last 20 messages sent and read them as the candidate would, not as the person who wrote them. The specific test: does the opening give a specific, relevant reason to respond, or a generic description of an opportunity? If it's the latter, rewrite before sending another message. The most common mistake at this threshold is expanding the candidate list, which sends a broken message to more people. More names through a broken message does not recover a search; it exhausts the pool faster while leaving the positioning problem in place.
How is Decision Lag different from the other failure signals and why is it harder to fix?
Decision Lag is the only signal that the search firm or recruiter cannot fix unilaterally: it is controlled entirely by the hiring organisation's availability and internal alignment. The other four signals (Response Decay, Funnel Stall, Intake Drift, Recruiter Overload) have interventions the search team can execute directly. Decision Lag requires the hiring manager to commit to a specific timeline and be held to it. The practical response is to build the commitment into the process documentation at the start of the search: 'decisions will be communicated within 48 hours of each stage', and to escalate proactively when the threshold is breached, framing it as a candidate retention risk rather than a process complaint.
Did this land? Push back? Add something I missed?
Reply to Manas →Continue Reading
Related writing
FrameworksCompounding Failure Loop™
When a mandate fails, the natural response is to add more inputs. This usually makes things worse. What looks like a sourcing problem is almost always a symptom of a failure that started several stages earlier.
FrameworksHiring System Health™
A hiring mandate is a system. Like all systems, it has health metrics. Most organisations measure outcomes (did we hire?) rather than health (is the system working?) By the time outcomes fail, it's too late.
FrameworksHiring SLO Framework™
In engineering, a service level objective defines acceptable performance thresholds and triggers automated responses when breached. Most hiring teams have no equivalent. That is the gap this framework closes.