08 Difficult Hiring Moments
Hiring Freeze
Decisions
Stopping hiring changes the system.
The freeze management system
Freeze
Hiring paused due to business conditions
Workload shift
Coverage redistributed across existing team
Prioritisation
Clarity on what gets done and what doesn't
Adaptation
Team adjusted to new operational reality
A hiring freeze is not just a budget decision. It is an operational decision that changes what the team is expected to deliver — and requires explicit management to avoid silent overload.
Why this matters
Hiring freezes are often announced without the operational redesign they require.
When a hiring freeze is announced, the focus is usually on what won't happen: the roles won't be filled, the costs won't be incurred, the growth plans will be adjusted. What rarely receives the same attention is what will happen: the work those roles were supposed to do will still need to go somewhere, and without deliberate management, it will distribute quietly across existing team members who already have full workloads.
The least visible cost of a hiring freeze is the gradual overload it creates through diffuse redistribution. Without explicit decisions about what gets deprioritised, teams absorb the additional work without explicit agreement — and the cost shows up later as burnout, attrition, or quality degradation.
A hiring freeze handled well is one that includes explicit decisions about workload redistribution, priority reduction, and team communication — not just the announcement that the freeze is happening.
Founder reality
Design the operational response before announcing the freeze:
Which open roles are being frozen — and what work were those roles supposed to absorb?
Where will that work go — and is the destination team aware of and willing to absorb it?
What priorities are being deprioritised because we no longer have the capacity to pursue them?
How will we communicate the freeze to the team — including the reasoning, the implications, and the plan?
What is the trigger that would end the freeze — and is that trigger defined clearly enough to be credible?
The trigger question is the one most often skipped. A freeze with no defined end condition produces indefinite uncertainty — which is more damaging than the freeze itself.
The system
Four decisions that make a hiring freeze manageable
Make all four before the freeze is announced. The announcement without these decisions creates the problems the freeze was meant to avoid.
01
Scope — which roles are frozen and which are essential
Not all open roles are equally freezable. Some roles are frozen with no operational impact. Others are being recruited for because a critical gap already exists. Define clearly which roles are frozen and which, if any, continue. Freezing all open roles without distinction is a blunt instrument — sometimes the right call, but always a deliberate one.
02
Redistribution — who absorbs what, explicitly
Every frozen role was supposed to deliver something. Map the work. Assign the coverage explicitly — not to 'the team' but to specific people, with named ownership. The people absorbing additional work deserve to know: this is the specific additional thing I'm taking on, and this is what I'm deprioritising to make room for it.
03
Priority reduction — what stops being done
A hiring freeze that doesn't reduce the priority list is asking the existing team to do more with the same capacity. Something must stop, reduce in scope, or be delayed. Making this explicit is more respectful than the implicit expectation that the team will somehow absorb the gap. State clearly what won't get done during the freeze.
04
End condition — what would end the freeze
Define the trigger: a revenue milestone, a cost-to-revenue ratio, a specific external condition. The end condition doesn't need to be guaranteed — it needs to be honest. 'The freeze ends when ARR reaches €X' is more trust-building than 'we'll reassess in Q3'. The team needs something concrete to orient around.
Common mistakes
01
Announcing the freeze without announcing the plan
A freeze announcement that doesn't include what happens to the work creates immediate anxiety about workload and direction. The announcement and the plan should be communicated together.
02
Freezing strategically critical roles to save short-term costs
Some roles are frozen because they're expensive. Some roles are expensive because they're critical. Freezing a role that creates a strategic bottleneck to save the cost of the hire is often a false economy — the bottleneck cost exceeds the hire cost.
03
No explicit priority reduction alongside the workload redistribution
If the team is asked to absorb additional work without explicit permission to deprioritise existing work, the implicit expectation is to do everything — which is not sustainable. Permission to deprioritise must be as explicit as the assignment of additional work.
04
No communication update when the freeze conditions change
If the freeze was tied to a revenue milestone and that milestone is reached, the team needs to know — promptly and clearly. Allowing the freeze to persist beyond its stated end condition erodes credibility and signals that the original communication wasn't genuine.
Example scenario
A 45-person SaaS company entering a freeze with 6 open roles (3 engineering, 2 sales, 1 ops). Leadership planned to announce the freeze at the next all-hands.
The pre-announcement work (3 days before all-hands)
Engineering freeze: 2 of 3 roles fully frozen. 1 role (security engineer) reclassified as essential — search continues.
Sales freeze: 2 roles frozen. Head of Sales briefed: 2 existing AEs absorbing pipeline coverage with named territory assignments.
Ops freeze: 1 role frozen. COO explicitly deprioritised 3 operational projects to create capacity.
End condition defined: freeze ends when MRR reaches €400K or raises materially. Current MRR: €280K.
The announcement
All-hands: freeze announced with reasoning (6-month runway extension), scope (which roles, one exception explained), redistribution (explicitly named coverage assignments), priority reduction (3 projects paused), and end condition (€400K MRR trigger). Q&A: 40 minutes of direct questions, all answered.
The outcome
No voluntary attrition in the 12 weeks following the freeze. Team survey: 71% said they understood what the freeze meant for their workload. MRR reached €400K at week 19. Freeze lifted. Three of the original frozen roles reopened — with updated definitions reflecting what had been learned during the freeze period.
Takeaway
A hiring freeze is an operational decision, not just a financial one.
Define the scope, design the redistribution, reduce priorities explicitly, and state the end condition. The freeze announcement without these decisions creates the problems — the decisions prevent them.
Related thinking
Continue reading
Leaving Without Breaking the Team