Your Team Just Absorbed a Reorg. Here's What to Actually Say to Them Monday Morning.

Omnicom told employees this month it's cutting 15,000 jobs by year-end, shrinking from roughly 120,000 people to 105,000, on the same week Oracle posted a blowout quarter, cloud revenue up 62%, full-year guidance raised, and confirmed another round of layoffs of its own. Different companies, same pattern: the business is fine, sometimes great, and a chunk of the team is still gone. This isn't a one-off. Tech-sector layoffs alone have already topped 210,000 workers across 2026, and the pace hasn't slowed even as several of the companies doing the cutting report record numbers. If you're a PM, this is the part of the job nobody prepared you for. Not deciding whether the reorg makes sense. Not modeling the org chart. Standing in front of your team on Monday morning and saying something that doesn't make things worse.

Most PMs improvise this moment. It usually goes one of two ways. Either you overcorrect into forced positivity ("this is actually an opportunity for us"), which reads as tone-deaf to anyone who just watched a colleague get walked out. Or you underplay it into a logistics briefing, here's the new reporting line, here's who owns what now, and skip the part where people are scared, angry, or grieving. Both fail for the same reason: they treat a reorg announcement as a communication problem when it's actually a trust problem.

Why this is harder than it looks

A reorg breaks the implicit contract people had with their work. Someone joined your team believing a certain version of the future: this project mattered, this manager had their back, this company was growing in a direction that included them. A reorg proves that belief was, at least partly, wrong. You can't talk someone out of that. You can only be honest about what's true now and consistent about how you behave going forward.

The added difficulty for a PM specifically: you usually have less information than your team assumes you do, and less authority than they wish you had. You didn't make the reorg decision. You often find out with a few days' lead, sometimes less. But you're the person they'll ask, because you're the one they see every day. Pretending you have more clarity than you do erodes trust faster than admitting the gaps.

What to say, in order

1. Name what happened, plainly, before anything else. Not "there have been some changes" but the actual shape of it: who left, what's being restructured, when it takes effect. Vague language reads as either evasive or as if you don't respect the team enough to be direct. If you don't know a detail yet, say that specifically, "I don't have the final headcount number yet, I'll share it the day I get it," rather than talking around the gap.

2. Acknowledge the loss before the logistics. If people left, say their names if that's appropriate, or at minimum acknowledge that real colleagues are gone and that's hard regardless of the business rationale. Skipping straight to "here's how we're restructuring the roadmap" tells the room that process matters more than people, even if that's not what you meant.

3. Tell them what stays true. This is the part most reorg conversations skip entirely, and it's the one that actually steadies a team. What is not changing? The mission the team is working on, the customer problem that still matters, the fact that the work they shipped last quarter still counts. People anchor to stability wherever they can find it. Give them something real to anchor to, not manufactured optimism, an actual fact that survived the reorg intact.

4. Be honest about what you don't know, and commit to a specific update cadence. "I don't know if there will be another round" is a true, hard sentence. Say it if it's true. Then commit to something concrete: "I'll give you an update every Friday, even if the update is 'nothing new.'" Silence between updates is where anxiety compounds; a predictable cadence, even a boring one, caps how bad the story people tell themselves can get.

5. Give them one thing they can control this week. Not a pep talk, an actual task with a real deadline that's still meaningful post-reorg. Ambiguity about what matters right now is often worse than the reorg itself. A concrete, achievable priority for the next five days gives people something to do with their attention besides speculate.

The mistake that costs you the most trust

The single biggest trust-destroyer in a reorg conversation is getting caught overselling certainty you don't have. If you say "there won't be more cuts" and there are more cuts, you've spent credibility you can't easily earn back, not just with the people who left, but with everyone who stayed and watched you be wrong. It is almost always better to say "I don't know, and I'll tell you the moment I do" than to manufacture false reassurance. Teams forgive uncertainty. They don't forgive being lied to, even accidentally.

This also means resisting pressure from your own leadership to project more confidence than you actually have. If your VP wants you to tell the team "everything is stable now," and you're not sure that's true, push back on the messaging before you deliver it. You're the one who has to look your team in the eye next week if it turns out to be false.

What this looks like when the team isn't in one room

Most of this advice assumes you can gather people and read the room in real time, which is getting harder. A meaningful share of the layoffs this year have landed on distributed teams, where "Monday morning" isn't a single meeting, it's a Slack message some people read at 7am and others read at 4pm after a full day of dread-scrolling the news. Two adjustments matter here.

First, don't let async convenience turn into async cowardice. A written message is fine, even necessary, as the first announcement, since it lets you get facts out consistently without them mutating as they pass person to person. But it cannot be the only communication. Follow it within the same day with a live conversation, video if you're distributed, where people can ask the two or three questions a written note can never anticipate. Skipping the live version because the written one was "already sent" reads as avoidance, and people notice.

Second, watch for the quiet ones. In person, you can see who's stunned, who's angry, who's quietly packing up their desk in their head. Over Slack, that same person just goes quiet, and it is easy to mistake silence for acceptance. Reach out to individuals directly in the days after, not with a script, just a real "how are you doing with this" sent privately. The team-wide message handles the facts. The one-on-one handles the person.

What not to do, even with good intentions

A few well-meaning moves reliably backfire, worth naming so you don't reach for them under pressure:

• Don't compare this reorg to a past one that "worked out fine." Even if it's true, it minimizes what this specific group is feeling right now, and it's not actually reassuring, it's a story about someone else's outcome being used to manage someone else's feelings.
• Don't promise stability you can't back. "Your role is safe" is only worth saying if you have real authority behind it. If you're guessing, say what you actually know: "I have no information suggesting your role is at risk," which is honest, is different from a guarantee, and doesn't collapse your credibility if things change.
• Don't skip straight to the new org chart. It's tempting because it's concrete and comfortable to talk about, compared to the harder, vaguer conversation about how people are feeling. But leading with structure before acknowledging loss tells the room what you actually prioritized.
• Don't let leadership's talking points replace your own words. A corporate memo is useful as a factual backbone, dates, numbers, what's changing, but delivering it verbatim, in a leadership register that doesn't sound like you, reads as outsourcing the hard part. Say it in your own voice, even if the facts come from someone else's document.

After the first conversation

The Monday morning talk is one moment. What actually rebuilds trust is what happens over the following weeks: whether you follow through on the update cadence you promised, whether the "one thing" you gave people to focus on still matters two weeks later, whether you're visibly present instead of retreating into your own anxiety about the reorg. Teams don't remember the speech. They remember whether the person who gave it kept showing up afterward.

If you're trying to figure out whether the reorg your team is inside of is actually going to work, versus one that's likely to need another round soon, that's a separate diagnostic question worth working through deliberately, not something to guess at in the moment you're also trying to steady a scared team. A framework for judging which kind of reorg you're standing inside and a broader checklist for telling a reorg that will work from one that won't are both worth reading once the immediate conversation is behind you. Give yourself permission to answer that question later, on your own, and to keep Monday's conversation about honesty and stability rather than prediction.

The skill of holding a room through bad news isn't unique to reorgs, either. It's the same muscle behind managing stakeholder conflict without burning the relationship you'll need next quarter: say the true thing plainly, protect what's still real, and let consistency do the rest of the work over time.

None of this makes a reorg easier to sit through. But the difference between a team that fractures under a reorg and one that holds together through it usually isn't the reorg's severity. It's whether the person delivering the news was honest about what they knew, clear about what was still true, and present enough afterward that the team believed them the second time too.