Supporting the People Who Stay
Mia tells David that the remaining team is worried about heavier workloads and lost trust. They discuss how to acknowledge those concerns, set priorities, and give people a meaningful voice in the transition.
Dialogue10

I know the announcement was necessary, but people who remain are worried. They’re asking whether the work of several colleagues will simply be redistributed among the rest of us.
That’s a fair concern, and I don’t want to dismiss it with a vague promise that everything will be fine. We need to be explicit about what we know—and what we don’t.
There’s also a trust issue. Some people feel that if the company could make this decision, leadership might have more bad news waiting just around the corner.
I can’t guarantee there won’t be further changes, and pretending otherwise would undermine our credibility. I can commit to sharing confirmed information promptly, rather than letting rumors fill the silence.
Then we need to address workload, not just morale. If we keep every existing commitment and absorb the vacant roles’ responsibilities, people will burn out—or quietly start looking elsewhere.
Agreed. Let’s review every active project, identify what is genuinely essential, and decide what to pause, reduce, or stop. We shouldn’t treat capacity as an unlimited resource.
People will want a say in those trade-offs. Could we ask each team to flag the work that creates the most value, along with deadlines or dependencies that cannot realistically move?
Yes, and we should explain how their input will shape the decisions. I don’t want consultation to become theater; if a constraint is fixed, we should say so plainly.
We should also make room for mixed feelings. People can be relieved to have kept their jobs and still feel grief, guilt, or anger about colleagues who were let go.
Absolutely. No one should be expected to perform gratitude or immediately return to business as usual. Let’s hold a listening session, set weekly priority check-ins, and report back on what we change.
Vocabulary8
- dismiss it
To dismiss a concern is to treat it as unimportant or not worth discussing. Here, David says he will take the team’s worries seriously.
- vague promise
A vague promise is a commitment that is unclear or lacks specific details. The phrase is useful when explaining why reassurance alone may not build trust.
- undermine our credibility
To undermine credibility is to make people less likely to trust what you say. Here, pretending to know the future could damage leadership’s reputation for honesty.
- burn out
To burn out is to become physically or emotionally exhausted from prolonged stress or overwork. Use it to describe the risks of an unsustainable workload.
- trade-offs
Trade-offs are choices that involve giving up one thing to gain or protect another. Here, teams must decide which work to prioritize when capacity is limited.
- consultation to become theater
This means asking people for input only as a performance, without letting it influence decisions. It is a pointed way to call for meaningful participation.
- mixed feelings
Mixed feelings are several emotions that may seem to conflict with one another. In this context, people can feel relief about keeping their jobs and sadness or anger about colleagues who left.
- business as usual
This phrase means carrying on as if nothing significant has changed. Here, David says employees should not be expected to immediately resume normal routines.
Key Sentences8
- 1
We need to be explicit about what we know—and what we don’t.
This is a useful way to promise clear, honest communication even when some information is uncertain. Reuse “We need to be explicit about…” when a group needs clarity on a difficult issue.
- 2
I can’t guarantee there won’t be further changes, and pretending otherwise would undermine our credibility.
This sentence acknowledges uncertainty while explaining why false reassurance is harmful. The structure “I can’t guarantee…, and pretending otherwise would…” helps communicate limits candidly.
- 3
Let’s review every active project, identify what is genuinely essential, and decide what to pause, reduce, or stop.
This gives a practical sequence for reviewing work and making priorities explicit. Reuse the pattern “review…, identify…, and decide…” when proposing a structured plan.
- 4
We shouldn’t treat capacity as an unlimited resource.
This concise sentence states that people’s time and energy have limits. It can help challenge unrealistic expectations in planning discussions.
- 5
I don’t want consultation to become theater; if a constraint is fixed, we should say so plainly.
This is useful when inviting input while being transparent about what can and cannot change. Reuse “I don’t want [process] to become…” to stress that an effort must be genuine.
- 6
People can be relieved to have kept their jobs and still feel grief, guilt, or anger about colleagues who were let go.
This sentence recognizes that people can experience conflicting emotions at the same time. The pattern “can feel X and still feel Y” is useful for acknowledging emotional complexity.
- 7
No one should be expected to perform gratitude or immediately return to business as usual.
This pushes back against pressuring people to display a particular emotion or act as if nothing happened. Reuse “No one should be expected to…” to set a humane expectation.
- 8
Let’s hold a listening session, set weekly priority check-ins, and report back on what we change.
This sentence turns concern into concrete follow-up actions. The structure “Let’s [action], [action], and [action]” is useful for proposing a clear plan.