The Redeployment Gap: Why 77% of HR Leaders Say They Offer Programs Only 19% of Employees Have Seen

77% of HR leaders say their company offers redeployment programs. Only 19% of employees have seen one. Five moves that close the gap before your next restructuring.

Avatar photo
By Eliana Kovalenko Vardi, Director, Work & AI Experience Design, Gloat
Trulli

US employers announced 33,429 job cuts in July, down 27% from June and the lowest monthly total in two years. For the fifth month running the most-cited reason was artificial intelligence, named in 10,970 of them. Across the year to that point AI had been cited in 112,713 job cuts, close to a quarter of the year’s total, according to Challenger, Gray & Christmas. Employers are announcing fewer cuts, and the ones they announce follow work moving between people and software. That puts workforce redeployment, the practice of moving people out of roles that are changing and into roles that need them, at the center of what HR is being asked to do this year.

Visa disclosed around 2,600 role reductions in July, roughly 7% of its workforce, in a staff memo that landed the same day the company reported net revenue up 14% year over year to $11.6 billion. Personnel expense rose 40% that quarter, mostly the $563 million in severance the reduction cost. CEO Ryan McInerney wrote that AI “is also helping to accelerate this evolution and shape the way work gets done at Visa” (HR Executive). That is the restructuring HR now has to handle: profitable, deliberate, aimed at roles whose content changed. Those are the people worth moving somewhere else in the building.

Leaders then ask the wrong question first: cut or redeploy, as though the decision were still ahead of them. In most large companies it was made years ago, in favor of redeployment, and written into a policy that has since gone quiet.

Seventy-seven percent of HR leaders say their organization offers targeted redeployment and mobility programs. Nineteen percent of employees say they have experienced or recognized one. That comes from LHH’s 2026 redeployment and outplacement research, published in April, which surveyed 3,000 HR leaders and more than 8,000 employees across seven countries (reported in detail here as 8,003 white-collar employees at companies with more than 500 people). The same study found 87% of HR leaders had already conducted layoffs or were planning them within twelve months. Fifty-eight points separate what HR built from what employees can find, and programs employees cannot find are not running.

Why workforce redeployment programs go missing

The research named three barriers: weak strategic talent planning, thin AI and analytics capability, and managers hoarding talent. Intent is not the missing piece. All three barriers show up in companies that cannot say who works there and what those people can do.

A redeployment decision requires someone to know that a payroll analyst in Manila has spent two years building reconciliation logic the treasury team needs next quarter. No single person holds that fact. It is absent from the job title and from the HCM record, and the analyst’s own manager has a reason not to advertise it. So the redeployment path exists in policy, the analyst never hears about the treasury opening, and the company opens a requisition for a skill it already employs.

Only 32% of leaders in the study measure the cost savings their redeployment and mobility work produces. Thirty percent track how many redeployments they completed. A quarter measure time-to-redeploy. A program with no count of its outputs is unmanaged, and among employers that track rehiring costs, close to three-quarters say the layoff-then-rehire cycle costs more than moving someone internally. The economics have been settled for years. The instrumentation has not caught up.

Sixty-four percent of HR leaders in the same survey said continuous restructuring is taking a toll on their mental well-being. An HR team running back-to-back reductions without skills visibility is doing the hardest available version of the job.

The skills inventory arrives too late

Search for advice on workforce redeployment and the guidance converges on one instruction: build a skills inventory, then maintain the taxonomy.

The instruction is sound and the delivery date is the problem. A hand-maintained inventory can take the better part of a year to assemble across a large enterprise and describes the workforce as it was when the last review closed. Restructurings run on a clock measured in weeks. By the announcement, the taxonomy covers the roles that are going away in more detail than the roles people could move into.

Inferred skills work on a different clock. Rather than asking people to describe themselves into a form, the context engine reads signals the business already produces: project histories, internal applications, and the adjacencies between what someone does now and what a posted role needs.

That distinction between taxonomic and inferential skills intelligence decides whether the data is current when you need it. Gloat’s Knowledge Graph holds the relationships between people, jobs and skills, which turns “who could do this” from a research project into a query.

Five moves before the next announcement

1. Count what you have already done

Pull the number of internal moves your company completed in the last twelve months, split into lateral moves and moves out of eliminated roles. Most HR teams cannot produce this from a single system, which is the finding. A rough count from three systems beats the absence of one, and it becomes the baseline every later redeployment claim gets measured against.

2. Set a time-to-redeploy target and publish it

Time-to-redeploy changes behavior because it is the metric employees experience. Pick a number you would defend to an affected employee, and build it around the notice and consultation obligations that apply to you: WARN notice in the US, works-council consultation across much of Europe. Make that period the design constraint rather than the thing that runs out. Report the misses alongside the successes.

3. Open the internal market before the announcement, not after

Redeployment fails when it starts on the day someone learns their role is going away. Their manager is disengaged, and their options are whatever is posted that week. Running an internal opportunity market continuously, with projects and gigs alongside open roles, means an affected employee arrives with a visible history of internal work and a matching engine that already knows them. Invisible talent, invisible roles covers why the posting-and-hoping model misses.

4. Take the release decision away from the holding manager

Manager talent hoarding shows up in those barriers because the incentive is unavoidable: a manager who releases a strong performer absorbs the loss while the receiving team takes the gain. No amount of encouragement fixes that. Two things do: a rule that the holding manager has no veto over an internal move during a restructuring, and a measure of internal talent released that lands in that manager’s own review.

5. Model the role changes before you size the cut

The reductions in this cycle follow work moving between people and agents, which makes the redeployment question and the headcount question the same question. The headcount number gets fixed first. Scenario planning that models which tasks inside a role are changing, before a headcount number gets fixed, produces a smaller cut and a shortlist of people to move.

The clock you will be given

Most of these companies bought the right answer. They wrote the policy, funded the program, and then left it somewhere their own employees could not find it. The HCM suites are announcing agentic internal-mobility applications this year, one of the largest of them in August. None of it will help the companies that still cannot answer who inside the building could do the work.

The budget line survives every planning cycle. The program has not run since the last reorg.

Your next restructuring will arrive on a deadline you do not set. Whether redeployment is real by then depends on work that has to happen now, while nothing is on fire: the baseline count and the internal market that is already running. Neither can be stood up during the announcement. The economic and ethical case for choosing redeployment has been made many times over; what decides it is whether anyone can find the people in time.

Ask your team for one number this week: how many people moved internally out of a role that went away last year. The speed of the answer is the diagnosis.

Request a demo →

Related