Better hiring decisions start before the role exists.
Kristina Golovko
MindDesign
The decision moment
Pressure
Speed, growth, team demand
Instinct
Feels like the right move
Role opens
Without clear thinking
Wrong hire
Or no hire at all
This playbook inserts a thinking layer between pressure and action.
Why this matters
The role is often opened on instinct, pressure or momentum — not on clear thinking about what the business actually needs.
Hiring is a structural decision. It changes how accountability is distributed and what the organisation becomes able to do.
The companies that hire well do not simply hire faster. They think better before they start.
Founder reality
Before you write the job description, answer these honestly:
Can you describe the first 90 days of output — not activity?
If this person left after six months, what would have been wasted?
Does the team that will work with them agree on what the role is?
Is this a new capability, or are you duplicating one that already exists?
Would a different process solve this without adding headcount?
If you cannot answer at least four confidently, the role is not ready to open.
The framework
These are internal clarity questions for you and your team.
Is this a capacity problem or a capability problem?
Capacity means the team is overloaded but the skill exists. Capability means the skill is genuinely absent. Hiring solves the second, not automatically the first.
What would change in 90 days if the role stayed unfilled?
If the honest answer is not much, the hire may be premature. If the answer reveals a specific bottleneck, you are naming a real role.
Who currently owns this problem?
Every unsolved problem has a current owner, even if informal. Clarify accountability before writing a job description.
Have we validated this with the people closest to the work?
The team sees constraints the organisation chart does not. Their evidence belongs in the role decision.
Are we hiring to solve a structural problem or a management problem?
Adding headcount to a broken process produces a more expensive broken process.
Common mistakes
01
Opening the role before defining the outcome
You describe the person you imagine, not the output you need. The result is a vague brief and a role that drifts.
02
Confusing urgency with clarity
Pressure to hire fast produces fast decisions, not necessarily good ones. Urgency is an emotion; clarity is a discipline.
03
Copying a competitor's job description
Their context and stage are not yours. A copied brief carries someone else's assumptions into your system.
04
Skipping stakeholder alignment
When three people hold three versions of the role, the conflict appears during interviews or at offer stage.
05
Treating a moving problem as a fixed role
Early-stage needs evolve quickly. Build a 90-day review trigger into the decision from the start.
Example scenario
A 30-person B2B SaaS company believes it needs three engineers immediately.
Initial assumption
The team cannot ship quickly enough, so more engineering capacity feels like the obvious answer.
What the questions revealed
Two unresolved architectural decisions were blocking the backend.
The shipping problem was partly a prioritisation problem.
One engineer was spending almost half the sprint on support escalation.
Nobody could define what the new engineers would own.
Decision
One targeted hire, one process change and a 90-day review trigger. Delivery improved without adding unnecessary headcount.
The goal is not to slow hiring down.
It is to ensure that the role is real, the problem is structural and the decision belongs to the organisation — not to pressure.
Continue reading
Role Clarity Before Hiring →