Not every role deserves urgency.
Kristina Golovko
MindDesign
The prioritisation chain
Business bottleneck
Where is growth actually blocked?
Urgency score
Real constraint vs perceived pressure
Leverage
Which hire multiplies the most?
Hiring priority
The role that earns the budget
Priority isn't set by who asks loudest. It's set by where the business is actually blocked.
Why this matters
A department head escalates. A board member flags a gap. An OKR demands headcount. The result is a hiring list that reflects who has the most influence in the room — not what the business actually needs.
Every hire is a resource decision. You are allocating capital, attention, management bandwidth, and time. Done without prioritisation logic, hiring creates noise — roles that duplicate, roles that drift, roles that block each other.
The companies that hire well understand one thing: a well-prioritised hire beats three uncoordinated ones. Fewer, better decisions compound faster than more, reactive ones.
Founder reality
Before you open any role, rank it against these questions:
Which business outcome is directly blocked without this hire?
If this role was filled today, what would move in the next 60 days?
Is this hire a multiplier — does it make other people or functions faster?
What's the cost of not hiring here for another quarter?
Are you hiring to solve a constraint or to satisfy an expectation?
A high-priority hire has a clear answer to at least three of these. If it doesn't, it's not a priority — it's a preference.
The framework
Evaluate every potential role against these four lenses before it goes into the queue.
Business bottleneck — is this role blocking a critical outcome?
Identify the single most important business constraint right now. The highest-priority hire directly unblocks it. Roles that don't connect to a current constraint are optional.
Urgency — is the constraint time-sensitive or tolerance-sensitive?
Urgency should come from business reality, not from impatience. Ask: what happens if this role stays open for 90 more days? If the answer is 'we miss a revenue commitment' — it's urgent. If the answer is 'it would be nicer' — it's not.
Leverage — does this hire make other functions faster or better?
Some roles produce output. Others multiply the output of everyone around them. A VP of Engineering who unblocks five teams is a different hire than one more individual contributor. Prioritise multipliers first.
Sequencing — does this role need to be hired before another can succeed?
Hire sequencing matters. Hiring a Head of Sales before you have a working product demo is expensive. Hiring a senior engineer before you have engineering leadership creates drift. Order matters.
Common mistakes
01
Treating all open roles as equal priority
When everything is urgent, nothing is. A flat hiring list produces unfocused recruiting and slow fills across the board.
02
Prioritising by seniority of the requester
The loudest voice in the room is not a prioritisation system. Roles should be ranked by business logic, not by who asked.
03
Ignoring sequencing dependencies
Hiring a team before hiring the leader who will run them creates expensive misalignment. Sequence matters more than speed.
04
Confusing revenue-generating roles with high-priority roles
Sales roles feel urgent because they produce revenue. But if the product isn't ready, hiring more salespeople amplifies the problem.
Example scenario
An AI infrastructure startup, 18 people, seed-funded. The founder wants to open five roles simultaneously: two engineers, a head of product, a marketing manager, and a sales lead.
The founder's logic
We need to grow fast. All these functions need to be in place before we raise Series A.
What the prioritisation framework revealed
The real bottleneck was a single integration feature blocking three enterprise deals.
One senior engineer with the specific integration experience would unblock more revenue than a head of product.
Marketing and sales without a repeatable pitch or working demo would create noise, not pipeline.
The head of product role made sense — but in 90 days, not now.
The decision
One targeted engineering hire. A 90-day hiring plan for product. Marketing and sales paused until the demo loop was proven. Series A prep accelerated because the constraint was actually solved.
Hiring priority isn't about what's missing.
It's about what's actually blocking the business from moving. Fewer, better-sequenced hires create more leverage than a full hiring plan that starts everywhere at once.
Continue reading
Do You Really Need This Hire? →