Confusion compounds faster than hiring mistakes.
Kristina Golovko
MindDesign
The clarity-to-cost model
Unclear role
Mission undefined, ownership vague
Weak signal
Interviews assess the wrong things
Poor hiring
Misaligned hire or no hire
Business cost
Revenue, speed, team confidence
Lack of clarity doesn't produce a bad hire immediately. It produces a process that can't distinguish a good hire from a bad one.
Why this matters
When the role isn't defined, the interview process can't be designed. When the interview process isn't designed, interviewers evaluate on instinct. When decisions are made on instinct, they reflect the biases and preferences of whoever has the most influence in the room.
The cost of this isn't just one bad hire. It's a hiring system that cannot learn. Every process produces different results because there's no consistent framework to compare against. Over time, hiring quality becomes unpredictable — and unpredictability erodes team confidence in the process.
Clarity is not administrative overhead. It is the infrastructure that makes reliable hiring possible.
Founder reality
Test whether your current hiring process has the clarity it needs:
Can every interviewer in the process articulate the role's primary mission in one sentence?
Do your interview stages evaluate distinct, defined criteria — or general impressions?
If two interviewers disagreed on a candidate, would there be a framework to resolve it — or just a debate?
Can you describe what 'excellent in this role' looks like at 6 months without ambiguity?
Does your job description tell candidates what they will produce — or just who they should be?
If the answer to more than two of these is 'no' or 'not really' — clarity is the problem, not the candidates.
The framework
Four compounding stages. Intervene early — clarity at stage one prevents cost at stage four.
Unclear role — the signal problem begins before sourcing
A role without a defined mission produces a job description that describes a person rather than a job. The search attracts candidates who match the description of the imagined person — not candidates who can solve the actual problem. Sourcing quality degrades from the start.
Weak signal — interviews can't evaluate what isn't defined
When interviewers don't share a common framework for what 'good' looks like, they default to pattern matching, personality assessment, and personal preference. The result is a process that's inconsistent, subjective, and unreliable.
Poor hiring — wrong hire or extended vacancy, both are expensive
A wrong hire into an unclear role is especially difficult to correct — because the failure can't be cleanly attributed. Was it the person? The role definition? The process? The ambiguity makes learning impossible and correction slow.
Business cost — the compounding downstream effect
An unclear role that produces a misaligned hire creates coordination friction, management overhead, team confusion, and execution slowdown. The business pays not just for the bad hire but for the operational weight it creates across the team.
Common mistakes
01
Writing interview questions before defining evaluation criteria
Questions without criteria produce answers that can't be meaningfully compared. Define what you're assessing before designing how to assess it.
02
Letting the candidate define the role during the interview
Strong candidates fill ambiguity with their own assumptions. When the role is undefined, you end up hiring for the candidate's version of the job — not the business's.
03
Measuring hiring success by speed to fill
A role filled fast with the wrong person is not a success. Speed is only a useful metric when combined with quality indicators measured at 90 days and beyond.
04
Not sharing the role definition with the candidate
Candidates make better decisions — and perform better — when they understand what they're being hired to solve. Hiding the problem you're hiring for creates misalignment on day one.
Example scenario
A climate-tech startup, 22 people, post-seed. Has been trying to hire a Head of Growth for four months. Three finalists have declined at offer stage.
The pattern
Candidate one declined because the role felt too undefined — 'I didn't know what I'd own.'
Candidate two accepted and left after 90 days citing unclear expectations.
Candidate three declined after the CEO and COO gave conflicting descriptions of the role in interviews.
The fourth search was about to begin — with the same brief.
What was actually broken
The role had no agreed mission. The CEO wanted a demand generation leader. The COO wanted someone to own the full funnel including product-led growth. These were different roles with different profiles — and no candidate could satisfy both.
The intervention
A role definition session was run with both founders before the fourth search began. A clear mission was agreed. Ownership was scoped to demand generation with a 12-month path to full-funnel. The brief was rewritten. The search found two strong candidates within six weeks. An offer was accepted within the month.
Slow hiring is often a clarity problem disguised as a talent problem.
When a search keeps failing — offers declined, wrong hires, extended vacancies — the first question to ask is not 'where are the candidates?' It's 'do we know what we're hiring for?'
Continue reading
Questions Before Opening a Role →