Original sample article. Not approved Tenjin advice or published commentary.
Start with the decision, not the headline.
Before developing messages, establish exactly what has been decided, what remains uncertain and what cannot yet be shared. A communications brief that blurs these distinctions creates avoidable rework. Keep one agreed record of the decision and identify who can approve changes.
Map who needs to hear it first.
Employees, customers, partners, investors and public stakeholders will not all have the same questions. Set out the information each group needs, the appropriate spokesperson and the sequence of communication. Consider dependencies: a manager cannot confidently brief a team without first understanding the implications.
Test the difficult questions.
Build a short question bank before drafting the polished announcement. What changes? Who is affected? Why now? What happens next? Separate questions you can answer today from those that require further work. Acknowledging a genuine unknown is preferable to filling the gap with a promise that cannot be supported.
Rehearse the handovers.
Check practical details: approvals, timing, channels, escalation contacts and the person responsible for updating the question bank. Prepare a fallback if an announcement reaches one audience before another. Good coordination makes the public-facing message easier to deliver consistently.
Review understanding, not just distribution.
After the announcement, look for repeated questions and areas of confusion. These are useful signals for the next communication. The task is not complete simply because an email has been sent. A short review helps the team refine both the message and the process.