Clear communication should not require people to reconstruct the conversation that happened before it.
Imagine a team that has spent six weeks working through a change.
People have asked questions, considered options and revised the plan. They understand why one approach was chosen over another. They know which details are still being worked out and which decisions are final.
Then someone writes the announcement.
Around the table, it makes sense. Everyone knows what the language means because everyone remembers the conversation behind it.
The person opening that announcement on their phone does not.
They are meeting the idea for the first time. They may be reading between appointments, during a work break or while trying to figure out which of several messages actually needs their attention.
They do not have six weeks of context. They have whatever we put in front of them.
That is the gap I think we need to pay more attention to.
Start where the reader is
From inside an organization, a message can feel complete because it includes everything the team wanted to announce.
From outside, it can still leave someone wondering: Does this apply to me? What is changing? Do I need to do something differently?
Consider this hypothetical opening:
Following a review of our registration procedures, we are implementing an updated process to improve the participant experience.
The sentence tells us that a review happened and a process is changing. But a person trying to register still has work to do.
What is the new process? When does it take effect? Is there something they need to complete?
A different opening could say:
Register online by Friday to reserve your place. This replaces last year’s paper form. Need help registering? Reply to this email.
That is not necessarily the entire announcement. There may be important details to explain, including why the change was made.
But it gives the reader a place to start.
The difference is not simply word count. It is whose perspective organizes the information.
Keep the context that helps
I am not arguing that people only need instructions.
People deserve to understand decisions that affect them. The reasons, the alternatives considered and the trade-offs can matter a great deal. Removing that context in the name of simplicity can leave a message feeling incomplete or evasive.
The question is whether we have made the explanation useful.
There is a difference between explaining why a decision matters and recounting every step that led to it.
A team may need a record of the process. A reader may need to know how the outcome affects their schedule, what options they have and where to get help. Those needs can coexist without forcing everyone through the same amount of detail.
Start with the information people need to understand their situation. Then make the supporting explanation easy to find.
That is not hiding the complexity. It is helping people navigate it.
Ask someone who was not there
One practical check is to have someone outside the project read the draft.
Not someone who has been copied on every email. Not someone who already knows what the acronym means. Someone who can reasonably approach the message as new information.
Instead of asking, “Does this look good?” try asking:
What do you think is changing? What would you do after reading this? What are you still wondering?
Those questions make the review more useful than a general request for feedback.
A reviewer might understand every sentence and still miss the point. They might identify the action but not know whether it applies to them. They might notice that the announcement refers to “the new process” without ever explaining the old one.
That is useful information, not a failure on the reader’s part.
It gives us a chance to address the confusion before asking everyone else to work through it.
Some gaps cannot be edited away
This exercise can also reveal something uncomfortable: the message may be unclear because the plan is unclear.
Perhaps no one has decided who will answer questions. Maybe the deadline is firm but the instructions are not ready. Perhaps different people on the team have different understandings of what happens next.
A better opening paragraph cannot resolve those problems.
That is where communication needs to be part of the planning, not just the final step. Asking what people will need to understand can expose decisions that still need to be made.
For me, that is an important part of the work. Not making an unfinished plan sound finished, but helping the team recognize what is missing.
Write for someone arriving now
Before publishing, try setting aside what you remember from the meeting.
Read the message as someone who has just arrived. Follow the instructions without filling in the missing steps. Check whether the explanation answers the questions the announcement itself creates.
This is not a request to talk down to people. It is a reminder that familiarity with our work is not a condition we should expect them to meet.
The people receiving our communication may be thoughtful, engaged and entirely capable of understanding a complex issue. They simply have not spent the past six weeks discussing it with us.
They should not need a seat in the meeting to understand what happens next.