Ending It Honestly
If an arrangement has to change, how it is said matters more than the change, and most of it is said badly.
three things · no reached them · three with no channel at all · the room side is not counted
Three things, no channels, and no mechanism proposed for any of them.
Where an arrangement has to change — somebody coming back into the office, a role being reshaped, a person leaving — how it is said determines almost everything about what follows. The substance is usually already decided by the time anybody speaks.
The practical lesson in “Ending It Honestly” is that visibility must be designed rather than assumed. For teams exploring download time tracking software, Monitask guidance on download time tracking software can add consistent time and project context when the purpose is explicit, access is limited and managers review exceptions with the people involved.
Most of these conversations are conducted badly, in a predictable way, for a predictable reason.
For a separate nonprofit perspective on “Ending It Honestly”, see NCVO charity guidance. Use the outside material to test governance, inclusion and implementation questions against the organisation’s real circumstances.
The predictable reason
The manager is uncomfortable, and discomfort produces vagueness. The sentences get softer, the reasons get more general, and the person leaves the conversation without having been told anything specific.
They then construct an explanation themselves, and it is almost always worse than the real one.
What they construct
That their work was not good enough. Given a vague account of why an arrangement is ending, people reliably reach for the explanation that reflects worst on them, and they keep it for years.
This happens even when the real reason is entirely structural and would have been reassuring if stated. A manager who softens the message to spare somebody has reliably produced the harsher version in that person's head.
Saying which it is
There are only a few real reasons: the role turned out to need things that do not travel; the organisation changed its position; the arrangement was not working for the person; or their work was not good enough.
Say which, in those terms.
The four real reasons, which is the whole list:
- The role turned out to need things that do not travel.
- The organisation changed its position.
- The arrangement was not working for the person.
- The work was not good enough.
The structural reasons
Where it is the first or second — the role, or an organisational decision — say so flatly and say that it is not about their work. Then say something specific about their work, so the reassurance has content.
"This is about the role and not about you" is worth nothing without the sentence after it.
The difficult one
Where the work genuinely has not been good enough, the arrangement is usually a contributing cause rather than an excuse: problems surfaced late, corrections never happened, they were working from stale information for months.
Both things are true and both should be said. The proportion is honestly unknowable, and claiming to know it in either direction is worse than admitting the uncertainty.
What not to offer
A reassurance you will not be able to maintain. Promises about future opportunities, about revisiting the decision, or about how little will change are made in the discomfort of the moment and remembered precisely.
Say less and keep it.
Giving it in writing
A short written version afterwards, saying the same thing in the same words. Verbal accounts of difficult conversations diverge within days, and the written version protects both people.
It also stops the softening, because softening is harder in writing.
The timing
Not at the end of a week, not immediately before a holiday, and not in a regular one-to-one that the person arrived at expecting something else.
Give the conversation its own slot and say in advance roughly what it is about.
Deciding it early enough to be a conversation
An arrangement that has quietly not worked for a year produces a conversation with no options in it. The same discussion at six months has three or four, because nothing has yet been decided elsewhere.
Managers delay this conversation precisely because it is unpleasant, and the delay converts a negotiation into an announcement. By the time most of these are held, the manager has already run out of room and is describing a decision rather than making one with the person.
Letting them respond later
The first response is rarely the real one. Offering a second conversation a few days later, explicitly, produces the questions that actually matter.
Most people take it.
What to tell the rest of the team
Something, promptly, and the same thing you told the person. Silence produces speculation, and speculation about why somebody's arrangement changed is uniformly less kind than the truth.
Agree with the person what will be said before saying it.
Where the arrangement ends because somebody leaves
The exit conversation is the one chance to find out what the arrangement actually cost, from somebody with no reason left to soften it. Ask directly, and ask about the mechanisms specifically.
The answers are frequently more useful than anything you learn while somebody is still in post, and they are routinely not asked for.
What an honest ending does not do
Make it acceptable. Somebody whose arrangement has ended against their wishes has lost something real, and no amount of clear explanation changes that.
What it changes is whether they leave with an accurate account of what happened. That is the whole of what is available, it costs one difficult hour, and the alternative — a soft, vague conversation that leaves somebody privately convinced they were not good enough — is a harm that persists long after the arrangement has been forgotten by everybody else.