Who Takes the Buyout? Why a Voluntary Exit Program Needs the Same Strategy as a Layoff

TL;DR: A buyout lets employees decide who leaves, but it is still a reduction in force and needs the same strategic design as a layoff. Leaders still decide which teams participate, which roles are excluded, how many departures a team can absorb, and how coverage works afterward. Workforce planning analytics on capacity, collaboration, and skills gives those decisions evidence about where the work sits.

A buyout is often treated as the gentler alternative to a layoff, and in many ways it is. For those remaining, it's still a reduction. Whether leadership chooses who leaves or employees choose for themselves, the business has to absorb the work, skills, and relationships that go out the door. A program offered broadly, priced to hit a number, and left to take rates can end the same way as a layoff planned from an org chart or a spreadsheet, with a savings on paper and resulting gaps nobody intended. The companies that get the most from a voluntary program plan it the way they would plan any reduction: they decide which work the business needs first, and then decide who is eligible and what the offer is worth.

Why are companies shrinking through buyouts and attrition instead of layoffs?

More companies are reducing headcount quietly, through voluntary programs and natural attrition rather than involuntary cuts. In October, Microsoft said it was offering voluntary buyouts to about 60,000 employees, more than a quarter of its global workforce, as it looks to contain costs and help fund its AI investments, according to Reuters. Chief People Officer Amy Coleman described the offer as giving participating organizations "another way to adapt their workforce to changing needs."

Microsoft is one example of a wider pattern. The Federal Reserve's October 2026 Beige Book noted that "Five Districts reported that some firms had either reduced staffing levels (through attrition), delayed hiring, or anticipated less job creation after increasing productivity by investing in AI."

Voluntary programs appeal to leaders because they hope to avoid some of the disruption of a layoff, and legal advisers note that a well-designed program can carry less litigation risk. The same feature that makes them appealing, letting employees choose, is also where their risk comes from.

Why does a buyout need the same strategy as a layoff?

In a layoff, the risk is identifying the wrong people. In a buyout, the risk is losing people the business didn't intend to lose, because the employees most able to say yes are often the ones with the best options elsewhere. Writing about buyouts at GM, Ford, and Verizon in 2006, Knowledge at Wharton described the same concern: the most valuable workers may be the first to leave because they are confident they can find another job, and they take years of institutional knowledge with them.

Pricing sharpens the tension. An offer that appeals only to people who were already planning to leave saves very little. Ethan Kra, the then chief actuary for retirement at Mercer Human Resources Consulting, told Knowledge at Wharton: "You must make it rich enough that others take it, too. Otherwise, it's penny-wise, pound foolish." A package generous enough to move people who weren't planning to leave is also generous enough to move the people the business most needs.

Take rates are hard to predict, too. About 30% of employees eligible for Microsoft's spring of 2026 voluntary retirement program accepted, and the company expects a much smaller share to take the new offer, which has no age or tenure requirement, according to GeekWire. With that much uncertainty, a single expected headcount number is a weak basis for a plan. Modeling a low, middle, and high take rate, and deciding in advance what changes under each, keeps the plan useful whatever the final count turns out to be. The involuntary version of this decision, and what happens when it's made without evidence of the work, is covered in the AI layoff regret cycle.

What does the company still decide in a voluntary separation program?

A voluntary separation program hands the final choice to employees, but the company still designs the program around that choice. Morgan Lewis's February 2026 guide to voluntary separation programs lists the design choices employers may make. They can exclude critical roles from the eligible population, set caps by role, department, or overall participation, and reserve discretion to reject applications under an appropriate nondiscriminatory process. The firm also advises employers to "identify mission-critical roles" and to "plan contingencies for staffing needs and higher-than-expected take rates."

Microsoft made the same kind of decision at the business-unit level. It left it to business leaders to decide whether their groups participate, and its sales organization isn't participating, nor are some engineering groups and corporate functions, GeekWire reported. Coleman wrote that participation "varies based on each business's priorities, customer commitments, and workforce needs."

Each of these choices depends on knowing where the work actually sits. Which roles are mission-critical? Which teams could lose two people without dropping a commitment, and which couldn't lose one? An org chart shows reporting lines and headcount, but it can't answer either question. Eligibility rules, caps, and rejection criteria are also legal questions, so work through them with employment counsel.

What should workforce planning cover before the offer goes out?

Before a voluntary exit program launches, workforce planning should look at three things at the team and role level: how much capacity each team has, how work and knowledge move between teams, and where critical skills are concentrated.

Workforce capacity. Some teams are genuinely at capacity, and others have room. A team running at full load can't absorb even a small number of departures without missed deadlines or burnout among the people who stay, while a team with slack can. Capacity data also gives the low- and high-take scenarios something concrete to test against, because it shows which teams would be stretched under each. Prodoscore's Capacity & Workforce Planning replaces headcount assumptions with utilization data drawn from the business tools teams already use. For a primer, see Capacity planning 101.

Collaboration. Work rarely follows the org chart exactly. Organizational network analysis (ONA) maps how collaboration flows across the business and shows the knowledge hubs and cross-team connectors a formal chart misses. These are the people others go to with questions, and they often aren't the most senior names on the chart. A mid-level role that links a product team to customer support can matter more to continuity than a more senior role elsewhere, and nothing in its title says so. Prodoscore's Capacity & Workforce Planning includes ONA built from activity patterns in everyday business tools. For more on the method, see why your company needs organizational network analysis.

Skills. A team may have five people, but only one of them may hold a particular capability, such as a key system, a client relationship, or fluency with the AI tools the team has adopted. When a capability sits with one or two people, the team carries concentration risk whether or not those people accept an offer. Prodoscore Skills Intelligence measures capability from how people engage with the tools they use every day, rather than inferring it from resumes or job titles. The same view shows where adjacent skills already exist inside the company, which matters if more specialists leave than planned.

This review is for scoping the program and planning coverage. It isn't a way to predict, target, or steer which individuals accept. The goal is to know, before the window opens, which teams and roles the business can't afford to leave uncovered, and to design participation and exclusions around that. For a broader look at planning around the work rather than the headcount number, see strategic workforce planning vs. headcount planning.

What should finance weigh beyond the severance cost?

A buyout's cost is visible and paid up front. Microsoft disclosed a $900 million charge for its spring voluntary retirement program, according to GeekWire. The cost of losing the wrong work is harder to see, because it arrives later and spreads across budgets: overtime and contractors to cover the gap, slower delivery, recruiting for roles that turn out to be needed, and the time it takes new hires to rebuild knowledge that walked out.

CFOs already make this trade-off with every reduction. The question is what the program saves against what it will cost to cover or rehire the work that leaves with it. Capacity, collaboration, and skills evidence makes the second half of that equation something finance can estimate rather than guess. For the components of that cost, see how much turnover is costing your business.

What happens after the election window closes?

Once the window closes, the program's outcome is known, and the work shifts to knowledge transfer and coverage. Institutional knowledge rarely lives in documentation, so the handoff belongs in the exit timeline. Pair departing employees with successors and capture how they actually do the work, starting with the roles other teams depend on most.

Redeployment is part of how Microsoft describes its own approach. Coleman said the company will keep helping employees build new skills and move into other jobs inside the company where it makes sense, and Microsoft said it had redeployed more than 4,000 employees into new roles over the prior year, according to GeekWire. Companies that capture skills data will have visibility into who already has adjacent capabilities to step into the open work.

The teams that stay deserve the most attention. When colleagues leave, their work lands on the people who remain, and if that load isn't visible, the employees who chose to stay can become the next to leave. Tracking team-level workload in the months after the window, with Prodoscore's employee productivity insights, helps leaders spot overloaded teams early and rebalance work before strain turns into resignations. For more on how departures spread, see turnover contagion and the resignation ripple effect.

Prodoscore adds evidence about how work actually gets done to the HR and planning systems a company already uses. Through its API and MCP Connector, that behavioral layer feeds into existing workforce planning tools rather than replacing them, so a voluntary exit program can be designed with the same systems of record and better information about the work. To see how this fits into workforce analytics across the business, see where the work sits before the window opens.

Frequently Asked Questions

A voluntary separation program offers employees separation benefits, usually severance and related support, in exchange for agreeing to leave within a defined election window. Employers use these programs to reduce headcount or costs while avoiding involuntary layoffs. The employee decides whether to accept, within the eligibility rules the employer sets.
In a layoff, the company decides which employees leave. In a buyout, the company decides who is eligible and what the offer is worth, and employees decide whether to take it. That shifts the main risk from choosing the wrong people to losing people the business didn't intend to lose, because those with the best outside options are often the most likely to accept.
Model a low, middle, and high take rate and decide in advance what changes under each. Capacity, collaboration, and skills data at the team level shows which teams could absorb departures in each scenario and which couldn't.
Organizational network analysis (ONA) is the most direct method. It maps collaboration patterns across the business and shows the knowledge hubs and connecting roles that an org chart misses, the people other teams route work and questions through. Workforce intelligence platforms such as Prodoscore build ONA from activity in everyday business tools rather than from surveys, so it reflects how work happens now.
Roles that are mission-critical, thinly staffed, or hard to replace are the usual candidates for exclusion, along with teams already at capacity. Capacity, collaboration, and skills data at the team and role level helps identify them. Because exclusions and caps raise legal questions, employers should design them with employment counsel.
Workforce planning analytics uses data about how work gets done, such as team capacity, collaboration patterns, and skills, to inform decisions about headcount, hiring, restructuring, and coverage. It replaces assumptions and historical averages with current evidence, so leaders can test a plan against the work before they approve it.

How will visibility impact your business?

Get in Touch