A hiring freeze gets announced on a Monday. By Wednesday you find out what your organization was actually made of, because the thing that was holding most of it together has just been withdrawn.
I have been at both ends of that curve. At Grammarly the design team went from five people to fifteen in a year, and across product, design and research we brought in roughly seventy people in under two years (the recruiting was most of my job in that period, whatever my title said). A year later I was at Pitch, drafting a new product organization in the same week a freeze was announced, with a run of departures already under way.
The second one taught me considerably more than the first.
What a freeze actually removes
Apart from the obvious thing, which is headcount, what a freeze removes is your default answer.
While you are growing, "we'll hire for that" settles almost every argument. A discipline with a gap in it, a leader stretched across too many surfaces, an area nobody owns, a cross-functional relationship that keeps failing: all of it gets deferred into a requisition. The requisition becomes the plan. And because requisitions keep getting approved, you never have to find out whether the plan was any good.
Then they stop, and you discover how much of what you were calling organizational design was a hiring plan wearing organizational design's clothes.
I would put the test bluntly. If you cannot describe your team without referring to roles that do not exist yet, you do not have a team structure. You have a wishlist with reporting lines drawn on it.
The seam work goes first
Design operations, research, design systems, program management, the accessibility work (the functions with no surface of their own). These functions share a property: they are justified by scale, because coordination cost grows faster than the team does. Which means their entire business case seems to disappear the moment the team stops growing. We are not scaling, so we can stand down the scaling functions.
I think that reasoning is wrong, and wrong in a way that takes about three quarters to become visible, which is exactly long enough for whoever made the call to have moved on.
The seam work was never a tax on growth. It is what stops a static team re-deciding the same twenty questions every quarter. At Grammarly we pushed accessibility into the design system at component level rather than running it as a review checklist, and the reason was durability: a standard encoded in a component survives the person who cared about it, and a standard living in someone's head leaves when they do. A freeze is exactly the moment that distinction starts to matter, because a frozen team is a team that is slowly losing people it cannot replace.
Growth hides an enormous amount of bad organizational design. A freeze is where the hiding stops.
Scope is the only currency you have left
When the Pitch freeze landed, I spent the week redrawing the product organization rather than waiting for guidance, and the whole exercise came down to moving scope, because scope was the only thing left to move.
I carved the organization into the three things it actually contributed: product management, design and research. One director was retitled to describe a remit they had already been carrying informally for two quarters. A quality function moved under the director whose work it constrained. I moved a designer into a product role owning a single growth metric end to end, because they wanted the surface and the metric had no owner. And a design leader got art direction over marketing without getting the marketing team.
Two rules came out of that week and I have kept both.
Retitle to describe what someone is already doing, not what you hope they will do. The first is a correction and lands as recognition. The second is a bet you are asking the person to fund out of their own credibility.
Scope only counts if it comes with a decision. More surface without more authority is just more work, and everyone can tell the difference by about week three. If the new remit does not change what the person is allowed to decide alone, you have not promoted anyone; you have redistributed load and attached a nicer noun to it.
I should be honest that several of those moves were promotions that cost the company nothing, and that this is a well-understood maneuver. It is defensible. It is also a debt, and you will be asked about it in six months by someone who has been counting.
What you owe the people who stay
Be specific about what has changed. "There is no realistic promotion path for the next eighteen months" is a survivable sentence; people can plan around it, and a surprising number will stay anyway. "We are still figuring it out" is not survivable, because it converts a known constraint into an open-ended anxiety, and people resolve open-ended anxiety by taking calls.
The harder obligation is the one nobody wants. In a freeze your strongest people take on more work and receive less progression, which is the standard recipe for losing exactly the people you cannot afford to lose. So you have to say, out loud, to someone very good: there is nothing here for you for a while, and if you find something better I will write the reference. Some of them stay after that conversation. All of them trust you more afterwards.
Does the work get better or worse
Better, for about two quarters. A settled team carrying no onboarding load is the most productive arrangement in software, and the first months after a freeze can be the best work a group ever does. Then it turns.
What decays is ambition. Teams calibrate what they propose against what they believe can be resourced, and they do it without noticing, so within a year the proposals coming up to you are all correctly sized for a team that is not allowed to grow. Nobody decided this. Nobody can point to the meeting. The ceiling simply becomes the horizon.
The correction is unglamorous and it works: keep one piece of work in flight that is clearly too large for the team you have. Not as a stretch goal with a date attached, which is a way of setting people up to fail. As a standing argument about what the company should be, worked on badly and slowly by whoever has room that month. Its function is not to ship. Its function is to keep the team's sense of scale from shrinking to fit the budget, so that when hiring reopens you still have people who can think at the size of the opportunity.
Most of them will not remember the freeze as the hard part. They will remember the year afterwards, when nothing was wrong and nothing was moving.
I've led design and product organizations at Honor, Lyft, Grammarly and Pitch, through both a hiring spree and a freeze. The counter-argument I take seriously: plenty of teams are better after a freeze than before it, because the growth was itself the problem, and a year of not hiring is the only thing that ever forces a company to find out which of its roles were load-bearing. I think that is true and I would still rather find out some other way.
© 2026 Renato Valdés-Olmos