Most change communication tells people what is ending and what is beginning. The announcement covers the new system, the new structure, the new process. It describes what people should stop doing and what they should start doing in its place.
Nobody hands them the list of what is staying exactly as it was.
That omission is doing quiet damage. Not dramatic damage — people don’t tend to resign over it or raise it in a survey. It works at a lower register, as ambient uncertainty, as a steady background noise that makes the simplest tasks feel less reliable than they used to.
When everything feels in motion, people cannot hold the change still long enough to work with it. They start asking questions that shouldn’t need asking. Is this still the right form? Is this team still the right team? Does my manager still make this call, or has that moved? The answers were obvious last month. Nobody said they had changed, but nobody said they hadn’t either. And so the questions accumulate.
“Stability isn’t the opposite of change. It is what makes change navigable.”
The Stop/Start/Keep exercise is usually used in retrospectives. It belongs earlier. Used as a communication tool — before the go-live, before the announcement, before the town hall — it forces a discipline that most change plans avoid: naming what is not moving.
Stop
- Manual data entry into the legacy system
- Weekly status reports to the old format
- Routing approvals through the regional coordinator
- Using the shared drive for live documents
Start
- Logging activity directly in the new platform
- Weekly check-in on the new dashboard template
- Approvals direct to the line manager from 1 November
- Using Teams channels for document collaboration
Keep
- Your current reporting line — no change
- The Monday morning team standup
- The existing client contact protocols
- All current performance review processes
The third column is the one that changes how people experience the first two. It is the anchor. Without it, the Stop and Start lists land in a context where nothing feels fixed, and the mind helpfully supplies what the communication didn’t: maybe everything is changing.
What You’re Actually Communicating
When you hand someone a Stop list and a Start list with no Keep list, you are communicating by implication: “we have told you what is changing, and everything else is uncertain until further notice.” That is not what you meant. It is what they heard.
The Keep list is not hard to compile. In most change initiatives, the vast majority of what people do every day is unchanged. The reporting line is the same. The team is the same. The core process is the same. The technology might be new, but the meeting cadence, the decision rights, the client relationships — most of those are untouched.
The reason nobody puts it on paper is that it feels unnecessary. Of course those things are staying. Why would you say so? Because your people do not know what of course means to you. They are reading the same announcement everyone reads and inferring from silence. And silence, in the context of change, is never neutral.
“People can handle uncertainty about what is changing. What exhausts them is uncertainty about what is not.”
A Keep list does something else, too. It signals that the people writing the change plan have thought carefully about scope. It tells the workforce: we know what we are touching, and we know what we are leaving alone. That signal matters because its absence suggests the reverse.
If you are mid-implementation and the Keep list has never been published, it is not too late.
A note that says “here is what has not changed, and here is our commitment that it will not” does not read as a correction. It reads as clarity. Most people are grateful for it.
Build the list. Publish it. Refer to it when the noise starts.