Who Tells the Team, and in What Words
Agreeing the departure announcement with the person, why the first version is the one that sticks, and the constraint it places on every reference that follows.
Agree one sentence with the person before they leave, and use that sentence everywhere. Something will be said whether or not anybody plans it, the first version that circulates is the one everyone remembers, and the organisation has very little control over it once an unmanaged version is out.
The handover issue in “Who Tells the Team, and in What Words” is easier to manage when current projects, recorded time and unfinished work can be reviewed before access closes. A team evaluating the product page for task switching cost should set a clear cutoff, export what is genuinely required and avoid retaining unnecessary activity data after the departure workflow is complete.
The announcement is also the document that binds everything afterwards. Whatever the organisation says internally on the day constrains what it can say in a reference, to a client, or to anybody who asks in two years.
For an independent reference relevant to “Who Tells the Team, and in What Words”, consult the FBI counterintelligence resources. Use it to test record quality, access, retention, fair process and exception handling against the organisation’s real departure workflow.
Agreeing it with the person
Ask what they would like said. Most people ask for something brief and neutral, many ask for nothing at all beyond the fact, and a few want to write their own note — which is usually fine and occasionally needs a conversation about tone.
Agreeing it takes five minutes and buys three things: the person is not blindsided, the organisation has a form of words it can repeat, and there is a record of what was agreed if anybody later says something different.
What the sentence should and should not do
| Says | Effect |
|---|---|
| "X is leaving on Friday; Y is taking over A and B" | Factual, useful, repeatable |
| "X has decided to move on to new opportunities" | Fine unless it is untrue |
| "X is leaving to pursue other interests" after a dismissal | A statement the organisation may not be able to stand behind |
| "X has left with immediate effect" | Says more than intended, invites questions |
| Nothing at all | Filled by whoever speaks first |
The third row is where organisations get themselves into difficulty by being kind. A departure described as voluntary when it was not can sit awkwardly against everything that follows, including anything the organisation says to an adviser later.
When to say it
The team should hear before external people do, and the person's close colleagues should hear before the general announcement. Finding out that somebody has left from a client, or from an automatic reply, is the version that generates resentment entirely unnecessarily.
Where a departure is immediate, this is harder and matters more. A short message on the day, saying only that the person has left and who to contact, is far better than a two-day silence while something is drafted.
What managers must not add
The explanation. A manager who tells the team why somebody was dismissed has made a public finding, often in front of people who were witnesses, and has said something the organisation may have to answer for.
Give managers the agreed sentence and a second sentence for when they are pushed: that it would not be appropriate to discuss it further. Then tell them that the second sentence is not a prelude to the real answer over drinks on Friday.
Clients, suppliers and the outside world
External messages need the same discipline and an additional element: who to contact now, by name, with a direct route. Most external recipients do not care why somebody left and care a great deal about who answers their email tomorrow.
Where the person held relationships, an introduction from them before they go is worth more than any announcement. That depends on the exit having been handled civilly, which is one more reason to.
Internal systems that announce for you
Directory updates, automatic replies, meeting invitations disappearing, removal from a group chat — these broadcast a departure on their own schedule, and that schedule is usually earlier than the announcement.
Sequence them deliberately. A person's calendar invitations vanishing two days before anybody is told is the kind of detail that makes an organisation look as though it is handling something badly even when it is not.
The person who has not gone yet
Announcements are often made at the start of a notice period, which leaves somebody working for several weeks after everybody has been told they are leaving. That is uncomfortable and it is frequently handled badly.
Agree with them when the announcement happens, not just what it says. Some people want it immediately so they can stop pretending; others want it as late as possible. Either is workable. What is not is finding out that the team was told the previous Friday.
Consistency afterwards
Write the agreed sentence into the file. Six months later somebody will be asked why the person left, and the answer should be the same one the team heard, the same one the client heard, and consistent with whatever reference is given.
That consistency is the whole point, and it is achieved by one sentence written down on the last day rather than by everyone independently remembering to be careful. It is a question worth settling once, at the point of departure, when everybody involved is still available to agree it.