INSIGHT
Back to Journal
Job Displacement|April 20, 2026|7 min

"We'll redeploy our people" is what firms say when they don't know what they're going to do.

Most of the time, "we'll figure it out" is what it actually means. Here's what redeployment looks like when leadership does it well, and when they don't.

By Ara Mamourian

Leadership teams love the word "redeploy." It sounds active. It sounds like a plan. It sounds better than "we'll figure it out."

Most of the time, "we'll figure it out" is what it actually means.

Here's what redeployment looks like when leadership does it well. Six to twelve months before the system goes live, the senior designer whose role is being reshaped gets a conversation. Not a company-wide memo. A real one-on-one. Her current role has her pointing people to information buried across four systems. The new system is going to make most of that unnecessary. Her managers ask her what she wants to do with the capacity she's about to get back. She tells them she wants to go back to design work, or she wants to move into design operations, or she wants to lead the rollout of the new system itself because she knows more about how the firm uses information than anyone else. They make a real plan based on her answer. She has a new role defined before the old one evaporates.

Here's what it looks like when leadership doesn't. The senior designer finds out about the new system the same way everyone else does: a rollout email three weeks before launch. She understands immediately what it means for her role. She also understands that no one has spoken to her about it. She does the math. The firm is going to need her during the transition, so she'll probably have a job for six more months. After that, she's watching for signals.

She leaves.

The firm calls this "attrition during a period of operational change." The consultants who sold the system call it "clean implementation." The people still there call it what it actually was.

The real obligation a firm has to its people during a technology transition is not a guarantee of continued employment. That's not in leadership's gift. Market conditions change. Business models change. The obligation is something smaller and more specific: tell the truth early, involve the affected people in the shape of what's coming, and invest in their ability to go somewhere useful.

"Somewhere useful" doesn't always mean somewhere inside the firm. A firm that helps a senior engineer move into a better role at a different company still earns something: a former employee who tells the story correctly, who refers junior talent back to the firm, who picks up the phone five years later when there's a consulting need. A firm that quietly manages the same engineer out with a three-month severance earns the opposite.

The math on this isn't sentimental. Professional services firms run on reputation, and reputation is downstream of how you treat people on their way out. Every senior person who leaves your firm tells the story of how they left to somewhere between five and fifty other senior people in the same industry over the next decade. If you have fifteen senior people and you handle every transition badly, you have now negatively influenced somewhere between seventy-five and seven hundred fifty professional conversations. That's a hiring problem, a client-referral problem, and eventually a business problem.

The firms that use automation as cover for cuts they were going to make anyway usually know they're doing it. They just don't say so. They tell themselves the market changed, or the workload shifted, or the new tools require a different skill profile. Sometimes those things are true. More often, leadership was already planning to reduce headcount and the new system provided convenient timing.

Here's the tell. A firm making a good transition communicates the change to affected employees before it's public. A firm using automation as cover communicates it to everyone at once. The first firm is trying to help its people land. The second is trying to minimize the window in which anyone can push back.

The thing we tell clients, when we're asked, is this: if you know you're going to reduce headcount, do it cleanly and call it what it is. Don't dress it up as a technology transition. Don't tell your people that AI is going to "free them up for higher-value work" if you've already decided not to use the capacity you're about to create.

If you don't know whether you'll reduce headcount, tell your people that honestly too. Most senior professionals can handle uncertainty. They cannot handle being lied to.

The firms that get this right don't always keep all their people. But they keep the ones who matter, they earn the ones they lose, and they stay a place worth working at.

That's the whole obligation. It's not small. But it's not complicated either.

job-displacementredeploymentleadershiptransitions

Ready to capture your
institutional knowledge?

Let's talk about how we can help your team.

Book a Discovery Call