Choosing between written and verbal communication is a risk-and-purpose decision, not a rule that \u201cimportant things must be in writing\u201d or \u201cdifficult things must be said face to face.\u201d The right channel depends on sensitivity, complexity, urgency, the need for discussion, the need for a record and the recipient’s ability to engage with the message.<\/p>\n
CIPD’s employee-communication guidance emphasises planning and tailoring communication, while Acas provides practical guidance on handling challenging workplace conversations. Those principles support a deliberate channel choice rather than defaulting to whichever tool is easiest for the sender.<\/p>\n
Source: CIPD, Employee communication, 2025<\/a><\/p>\n Source: Acas, Challenging conversations and how to manage them<\/a><\/p>\n Written communication is useful when the message needs:<\/p>\n Writing also gives the recipient time to process information before responding.<\/p>\n A conversation is useful when the issue needs:<\/p>\n It also allows the sender to notice confusion or disagreement earlier.<\/p>\n Examples include:<\/p>\n When the communication forms part of a formal HR, legal or regulatory process, use the organisation’s required procedure rather than a generic channel rule.<\/p>\n Performance feedback, conflict, emotionally sensitive topics and ambiguous disagreements can be difficult to resolve through short written messages alone.<\/p>\n A conversation can allow both people to:<\/p>\n Often the strongest option is:<\/p>\n This combines the discussion value of a live conversation with the clarity of a written record.<\/p>\n Weak approach:<\/strong> send a long email listing several concerns with no opportunity for immediate clarification.<\/p>\n Stronger approach:<\/strong> arrange a private conversation, explain the specific performance evidence, hear the employee’s response and agree next actions. Afterwards, provide the written record required by the organisation’s performance process.<\/p>\n If the matter is already part of a formal procedure, follow the applicable policy and law.<\/p>\n If several teams need to review a technical proposal, send the material first so participants can prepare. Use the meeting to resolve disagreements and make the decision. Then document the decision, owner and deadline afterwards.<\/p>\n An urgent operational problem may require a call or real-time message even when a written record will later be needed. Do not delay a safety or business-critical escalation simply because email would produce a better document trail.<\/p>\n The \u201cricher\u201d channel is not always the most accessible one. Some people may process complex information better in writing. Others may need captions, interpretation, assistive technology or more preparation time.<\/p>\n For multinational teams:<\/p>\n Do not use a group chat, shared channel or open-plan conversation for information that should be private. Use the organisation’s approved systems for sensitive personal, legal, HR or commercial information.<\/p>\nWhat writing does well<\/h2>\n
\n
What verbal communication does well<\/h2>\n
\n
Choose written when precision and reference matter<\/h2>\n
\n
Choose a conversation when interpretation risk is high<\/h2>\n
\n
Use the hybrid pattern for many difficult messages<\/h2>\n
\n
Example: performance feedback<\/h2>\n
Example: a complex project decision<\/h2>\n
Urgency changes the channel<\/h2>\n
Consider accessibility and language<\/h2>\n
\n
Consider confidentiality and privacy<\/h2>\n
A channel-choice framework<\/h2>\n