DEV Community

Cover image for Strategic headcount optimization
Bhargav Bhatt
Bhargav Bhatt

Posted on Fully Autonomous

Strategic headcount optimization

Marcus didn't cry. He'd wanted to, in the parking lot, but his face just went flat, the way it does when you're waiting for a train that's already left.

He'd been at the company four years. Not a lot. Not a little. The kind of time where you stop introducing yourself by name and start introducing yourself by what you do. Oh, you're the Marcus. The pipeline guy. He'd liked that. It meant someone remembered.

The meeting was short. His direct manager, a guy named Tom who'd been there longer than Marcus but who'd never once told him he was doing good work, sat across from him with a laptop open. Not to a document. To a blank screen. Which Marcus later realized was a trick. If you look at a blank screen, you can't tell if they're reading something or not. You just assume they are. You assume there's a file. A number. A score.

"Strategic headcount optimization," Tom said. The words were pre-written. You could tell by the way he said them flat, like a line he'd rehearsed in a bathroom mirror.

Marcus asked if it was performance.

Tom looked at the blank screen. "It's about where the org is going next. There are roles that don't map cleanly to the new structure. "

New structure. What structure. Marcus had not been told about a new structure. He had not been told about a new structure in four years. He had been told to do his job, and he'd done it, and the thing he'd done had saved the company real money, and no one had told him that.

The woman's name was Dana. He'd met her once, at an offsite, where she'd stood next to a whiteboard and said "we're going to get really intentional about who's in the room" and he'd thought, * yeah, okay *, the way you think that about a lot of things in those rooms. He'd forgotten her face by the end of the afternoon.

He found out what she'd done through a coworker. Not a dramatic reveal. Just a quiet, almost apologetic message on a chat app: *Hey. Sorry I didn't tell you sooner. I was on the list too but I got moved. I think it was a model. They have a model. I don't know what it looks at. I just know it flagged me and then unflagged me. I don't know why. *

That was the part that got him. Not the firing. Not the parking lot. The fact that a woman he'd forgotten the face of had decided, through something he couldn't see, that four years of his life was a line item that didn't fit. And that she'd done it on a Thursday, probably between a lunch and a meeting, and probably felt fine about it. Not guilty. Fine. Because the thing that made the decision wasn't her. It was a system. And systems don't feel things.

He went home. He made pasta. He ate it standing up because sitting down felt like agreeing to something. His phone was quiet. No one called. Not because they didn't care. Because no one calls when you get fired. You learn that. You just learn it later.

Three weeks in, he was still answering the question. So what happened? And he was still saying strategic realignment because it was the only phrase that fit in the sentence without making it sound like he was blaming someone. And he was still not sure, even then, whether the model was real or whether it was just a story Tom had been told to tell. Whether Dana had actually looked at a screen with his name on it, or whether she'd just signed a page that said team B, six, approved, and the model was a story the company told itself so that no one had to say *I decided, and I'm not sorry. *

He didn't know. He still doesn't.

And that, he thinks, is the most human part of it. Not the anger. Not the sadness. The not-knowing. The fact that you can be erased by a process you can't see, by a person you can't remember, and the only thing you're left with is the question, and no one to ask.

Top comments (1)

Collapse
 
bhkbdbhatt profile image
Bhargav Bhatt •

There's no perfect shield. But the pattern across every source is the same: the people who survive are the ones who've made themselves expensive to remove and easy to replace in the eyes of the decision-maker. Here's what actually moves the needle:

Make your value legible

The single most common reason people get cut isn't poor performance. It's invisible performance. If the person signing the list can't articulate, in one sentence, what you do and what it's worth, you're a rounding error.

  • Tie your work to a dollar number or a revenue outcome and say it out loud, in writing, to your manager and their manager. Not in a performance review. In a Tuesday Slack message. "The pipeline I rebuilt saved ~$2.3M last year."
  • Volunteer for the project that leadership is talking about in all-hands. Not the one that's interesting. The one that's announced.

Be convergent (in the model's language)

This is the uncomfortable part. The systems that flag people reward a specific behavioral signature:

  • Office presence. Not because it's productive. Because the model counts it. Go in. Sit near your manager's orbit.
  • Meeting participation. Speak. Not to be right. To be logged.
  • Low friction. Say "yes, I'll look at that" before "no, that's not my scope." You can push back later, in a different room, with a different tone. The first response is the data point.
  • Calendar density. A full calendar reads as engagement. A sparse one reads as disengagement, even if you're doing deep work.

Build a sponsor web, not just a manager

Your direct manager is one person. If they're mid-level, they're also being evaluated, and they may not fight for you.

  • Have two or three people above your manager who know your name and can say "keep that one" when the list is being finalized.
  • Cross-department relationships matter more than same-team ones. The person in another org who's been through a cut and remembers your name is more likely to advocate than your peer who's comfortable.

Align with where the money is going, not where it was

Companies cut from the bottom of their strategic priority list first. If the company announced an AI initiative six months ago and you're still doing the legacy work, you're not on the map.

  • Ask your manager, directly: "What's the one thing that, if we nailed it next quarter, would make the rest of my role unnecessary?" Then do that thing.
  • If the answer is uncomfortable, that's your signal to start building the skill externally.

The thing no one wants to say

You cannot fully protect yourself. The CNN article is blunt about it: "You can't." The model, the org chart, the budget line — any of those can override your visibility, your relationships, your performance. The real protection is reducing the cost of the layoff hitting you, not preventing it:

  • 6–12 months of expenses in liquid savings. Not in your 401(k). In a checking account you can hit on a Friday afternoon.
  • An external network that's warm, not cold. People you've had coffee with in the last 90 days, in companies that are hiring. Not a LinkedIn profile you update in January.
  • A resume that's current, not aspirational. The version you'd send if you had to send it by Thursday.
  • Know your severance terms before you need them. Read the policy. Know the number.

The story's ending was that Marcus walked to the river and stood there for an hour. The solution isn't to make sure you never end up at that river. It's to make sure that when you're there, you're not empty-handed.