When a Hiring Freeze Puts the Pager on the Manager

When a company freezes hiring, the work doesn’t shrink. The hours customers need don’t shrink either. What shrinks is the number of people available to cover them, and the gap lands on the nearest manager’s phone. If your team lost two people this quarter and nobody changed the escalation plan, you are the escalation plan.

I wrote about the curse of the berry in August 2008: managers who never switch off because the phone in their pocket makes them reachable. Since then the economy has made it worse in a very specific way.

What did the autumn of 2008 do to support teams?

It took people away. The U.S. Bureau of Labor Statistics reported on December 5 that nonfarm payroll employment fell by 533,000 in November and that the unemployment rate rose from 6.5 to 6.7 percent. Over the previous three months, job losses averaged 419,000 a month, compared with an average of 82,000 a month from January through August.

Those are national numbers, and I’m not going to pretend I know your company’s. But the pattern inside a support operation is easy to recognise. A vacancy isn’t filled. A resignation isn’t replaced. A contractor’s term ends. Nobody announces “we will now cover nights with fewer people.” The schedule just gets thinner, and the shifts that are hardest to staff, evenings and weekends, go first.

Customers don’t notice a hiring freeze. They notice that something broke at 8pm and nobody answered. Then it becomes an escalation, and escalations go up.

How does a thinner team turn into an on-call manager?

Arithmetic, mostly. Covering a single seat around the clock takes 168 hours a week. One full-time person works about 40 of them. That’s 4.2 people per seat before you count holidays, sick days and training.

Now take a team of ten that covers a 12-hour weekday window with a small evening rota. Lose two people and you haven’t lost 20 percent of your coverage. You’ve lost the slack that absorbed sick days and holidays, which was most of the margin. Then the first person off sick on a Friday evening takes the rota below its minimum, and the gap gets filled by whoever can’t say no.

That is almost always the manager, for three reasons:

• The manager feels responsible. I said in the original post that managers feel a personal responsibility for the team’s performance. Under pressure that instinct gets worse, not better.
• The manager is free to the company. Overtime has a price. A salaried manager’s evening doesn’t show up on any report.
• The manager is the only person who knows the whole picture, because the plan only exists in their head.

It looks like dedication. It’s a coverage problem that nobody is measuring.

What should you do before you absorb it yourself?

Make the gap visible, in numbers the finance team can read. This is the part managers skip, because it feels like complaining. It isn’t. It’s the evidence for a decision somebody else has to make.

Start with a four-week log. Every after-hours contact gets a line: when it came, who it came from, what it was about, how long it took, and whether anyone other than you could have handled it. That last column is the one that matters. If most of the contacts could have been handled by a trained team lead with the right authority, you don’t have a staffing crisis. You have a delegation gap, and it’s cheaper to fix.

Then pick one of three options and put it to your own manager in writing:

• Restore the coverage. Backfill the vacancy, or a part-time evening position, and show what the log says it’s worth.
• Reduce the promise. If the company won’t staff the hours, change what customers are told they’ll get in those hours. An honest “we respond by 9am” is better than a promise nobody can keep.
• Pay for the on-call. If a person has to be reachable, say so, name them, and compensate them with an allowance or time back.

All three are legitimate business choices. What isn’t legitimate is the fourth option, which is the one that happens by default: nothing is decided and one person absorbs it.

The escalation matrix I described earlier is the tool for this. Every level needs a name, a number and a trigger. When the freeze hits, update it. If the matrix still ends with “call the manager,” it’s out of date.

Why does a hiring freeze make escalation more expensive?

Because the people left are less able to fix things at the first level. When a team shrinks, the experienced people are usually the ones who got offers elsewhere or took packages. The ones who remain are often newer. A newer agent escalates more, because they have less authority and less confidence. So the volume going up the chain rises exactly when the number of people able to take it has fallen.

I’ve found that the answer is usually to give the first level more authority rather than more supervision. A rule you can write on one page, such as “any refund under a stated amount is yours to approve, any outage affecting more than a stated number of customers goes to the manager,” removes a lot of unnecessary calls. It also gives the manager something to defend: a clear line for what should and shouldn’t reach them.

That takes a couple of hours to set up. It’s the cheapest way to get your evenings back that I know of.

What does a workable rota look like on a thin team?

It’s smaller and stricter than the one you had before. Take a team where evenings used to be covered by two agents a night. After the freeze there are four people who can do evenings, and you can’t ask any one of them for more than one evening a week without the quality of their daytime work dropping. That gives you a hard ceiling, and the ceiling tells you what service level you can honestly promise.

Work it from the bottom up. Count the evening shifts per week you need to cover, divide by the number of people who can cover them, and compare the answer with what a person can reasonably do. If you need ten evening shifts and have four people, that’s two and a half shifts each, which is too many on top of a full week. Something has to give, and there are only three things that can: the hours you cover, the number of people, or the service you promise in those hours.

Put it that way to your manager and the conversation changes. You’re not asking for sympathy. You’re showing a constraint, with the three levers laid out, and asking which one the company wants to move.

What should you say to your own manager?

Keep it to a page and keep it factual. Say what coverage the team had before the freeze, what it has now, what the four-week log shows, and which of the three options you recommend. Name the cost of each option, even if it’s only an estimate. Then ask for a decision by a date.

The reason for the date is simple. Without one, “let’s see how it goes” becomes the plan, and you’re the one it goes through. A manager who asks for a decision and receives a no has at least turned an invisible assumption into a visible choice.

How do you keep your team’s trust while you do it?

By not exempting yourself from the rule you’re proposing. If you ask your team to protect their time off and then answer every call yourself, they learn that the plan is optional. Choose one person for the evening, make it a real rota, and stick to it.

Staff need time away from work for the same reason managers do. They need to recharge. Teams that are asked to be reachable all the time stop being able to concentrate on anything, and the first symptom is usually quality. Calls get shorter and ruder, notes get skipped, and the problems you were trying to avoid come back as repeat contacts.

A freeze is temporary. The habits you form during it usually aren’t. If you set a rota, a log and a clear authority line now, you’ll have something to build on when hiring restarts. If you absorb it quietly, the company will treat your availability as part of the job description.

Being valuable doesn’t mean being reachable. The goal is a plan that still works when you’re on a plane.