The numbers on hiring failures are brutal and well-documented. A bad hire costs between 30% and 200% of the employee's annual salary, depending on seniority. The average time to fill a position is 42 days. Seventy-four percent of employers admit to having made wrong hiring decisions. And 80% of employee turnover traces back to poor hiring choices.
These figures get quoted in every HR report, every recruitment pitch, every boardroom post-mortem. What rarely gets examined is why the failure rate is so persistent despite decades of professionalization in recruitment.
We believe the answer is structural. Most hiring processes are built backwards.
- 01Manager requests headcount
- 02HR writes job description
- 03Post → 300 CVs arrive
- 04Screen against description
- 05Hire for title match
- 01Discovery call — map the problem
- 02Process audit — deep discovery
- 03Design role from problem statement
- 04Targeted search — own network
- 05Expert verification + culture fit
The Standard Process — and Where It Breaks#
Here is how most companies hire. A manager identifies a headcount need. HR writes a job description — often recycled from the last time the role was filled, or borrowed from a competitor's LinkedIn posting. The description goes live. Applications arrive. Screening happens against the criteria in the description. Interviews confirm whether the candidate matches what was written down.
The entire process assumes the job description is correct.
It rarely is.
A job description is a hypothesis about what the organization needs. And like most untested hypotheses, it carries the biases of whoever wrote it. It reflects what the manager thinks the problem is — not necessarily what the problem actually is.
A product team with slow velocity doesn't automatically need another developer. It might need a product manager who can reduce scope ambiguity. Or a design engineer who eliminates the handoff bottleneck. Or a delivery lead who unblocks decisions that sit in someone's inbox for a week.
A company struggling with user retention doesn't automatically need a UX researcher. It might need a product strategist who can connect research that already exists to decisions that aren't being made. Or a data analyst who can surface churn patterns the team is currently blind to.
The role you need depends on the problem you're solving. And the problem you're solving requires discovery — not assumption.
Why "Generic PM" and "Generic PD" Are Expensive Mistakes#
The product management landscape has fragmented. What was once a single role now spans strategy, discovery, delivery, growth, platform, data, operations, and more. The skill set required to build a product from zero is fundamentally different from the skill set required to scale it. Maintaining a mature product demands different capabilities than launching a new one. Leading a team through a pivot requires different instincts than optimizing a machine that's already working.
Yet most job descriptions still read "Product Manager" or "Product Designer" as if those titles describe a single, interchangeable capability set.
They don't. And when a company hires a generalist for a problem that requires a specialist — or a specialist for a problem that requires someone who can think across domains — the result is predictable. Slow ramp-up. Misaligned expectations. Quiet frustration on both sides. And eventually, turnover.
Research confirms the pattern. Poorly defined job requirements are consistently cited among the top causes of bad hires. When hiring managers cannot clearly articulate what success looks like in a role, candidate evaluation becomes guesswork dressed up as process.
The fix isn't better screening. It's better problem definition.
How We Approach Hiring Differently#
At House of Product, we run recruitment as a product process. Not as an HR process, not as a staffing exercise — as structured discovery followed by precise execution.
Phase 1: Discovery Call#
Every engagement starts with a conversation. Not about the role. About the problem.
What's breaking in your product organization? Where do decisions stall? What falls through cracks that no existing team member owns? Is this a velocity problem, a quality problem, a strategic alignment problem, or a capability gap? These questions matter because the answer determines what role you actually need — which may not be the role you initially described.
This call typically reveals one of several patterns. The company is building a new product and needs someone who can lead from zero — driving discovery, shaping strategy, and working without established processes. Or the company is scaling, and the bottleneck isn't talent but structure — they need someone who can systematize what works and build the team around it. Or the product is mature, and what's needed isn't innovation but operational excellence — someone who can optimize, maintain, and defend what exists.
Each of these requires a different person. Hiring the wrong archetype for the wrong phase is one of the most common and most expensive mistakes in product team design.
Phase 2: Process Audit and Deep Discovery#
After the initial call, we spend approximately a week inside the organization. We audit processes, observe team dynamics, map communication flows, and identify where the actual dysfunction lives — not just where the symptoms show up.
This is the step that traditional recruitment skips entirely. And it's the step that makes everything else work.
By the end of this phase, we don't have a job description. We have a problem statement. And from that problem statement, we build a role specification that defines the exact combination of skills, experience, and working style that will solve the problem the organization actually has.
Sometimes the resulting role has a name the market recognizes. Sometimes it doesn't. The design engineer — someone who translates user-centered design principles into production code — didn't appear in job board taxonomies five years ago. It existed as a gap that kept costing companies time and quality. Naming it was half the solution.
Phase 3: Targeted Search and Expert Verification#
We don't post job ads and wait for 300 CVs to arrive.
We work from our own network and candidate base, built over years of working inside product organizations. We know who's strong because we've seen them work — not because they wrote a compelling LinkedIn summary.
Initial screening is ours. Technical verification is conducted by senior experts and team leaders who have done the work themselves — not by recruiters reading from a competency checklist. We verify product sense, craft quality, and the ability to operate in the specific context the client needs — building, scaling, maintaining, or transforming.
Culture fit assessment can run in collaboration with client HR or independently, depending on the organization's preference and capacity. Either way, the evaluation is structured, evidence-based, and tied to the actual working environment the candidate will enter — not to abstract value statements on a careers page.
What You Get#
You're not getting a stack of CVs ranked by keyword match. You're getting a shortlist of candidates who have been verified against the actual problem your organization needs solved.
Each candidate comes with our assessment of why their specific skill combination matches the dysfunction we identified — not just why their CV looks right on paper.
And it comes with a two-month guarantee. If the hire doesn't work, we refill the role. Because we stand behind our discovery process the same way we stand behind our consulting methodology: if the diagnosis is right, the intervention should hold.
The Cost of Not Doing Discovery#
The mathematics of hiring failures are unforgiving. A bad hire at a senior level can cost an organization upwards of $240,000 when you factor in recruitment, onboarding, lost productivity, team disruption, and the cost of re-hiring. For executive roles, estimates run to five times the annual salary.
But the hidden cost is worse than the visible one. A misaligned hire doesn't just fail to solve the problem — they create new ones. Team morale drops. Existing talent compensates for the gap, accelerating burnout. Projects stall or pivot in the wrong direction. And the original dysfunction that triggered the hire persists, now with six months of lost time added to the damage.
Most of this is preventable. Not by screening harder. Not by adding interview rounds. Not by running more personality assessments. By starting with the right question.
Not "who do we need?" but "what problem are we solving?"
Everything follows from there.