Workplace communication strategies fall into two categories that behave very differently. Training changes what individual people are capable of, and standards change what the organisation produces regardless of who does the work. Only the second survives turnover, because a standard belongs to the process while a trained skill leaves with the person who learned it.
Training Is an Investment That Walks Out the Door
Communication training is bought in response to a real symptom. Updates arrive late and vague, escalations are unclear, meetings run without decisions, and handovers lose information.
The response is usually a workshop. Managers spend a day learning to give feedback, structure a message or run a meeting, and the material is often good.
What happens afterwards is predictable. Behaviour improves for a few weeks, competing pressures return, and the practices that were not built into anything decay back to the previous baseline.
Even where the training holds, it holds inside one person. The skill is stored in an individual, applied at that individual discretion, and lost entirely when the individual moves on.
Turnover then charges the same cost again. The replacement did not attend the session, has no access to the material, and reverts to whatever they did at their last employer.
A business with normal staff movement is therefore buying the same improvement repeatedly. The spend recurs and the capability never accumulates anywhere durable.
The recurring nature of the spend is rarely made visible. Training appears as a line item in the year it is bought, not as a permanent cost of employing people who eventually leave.
A Standard Is a Format, Not a Skill
A communication standard specifies what a piece of communication must contain and where it must go. It says nothing about how well written it is.
That distinction is the whole argument. A skill is a property of a person and a standard is a property of the work product, which means the standard can be enforced by anyone.
A status update standard might require the current state, the change since last time, the blockers and the next date. A person with modest writing ability who fills those fields produces a usable update.
A gifted writer with no standard produces something engaging that may omit the blocker entirely. The reader has no way to know what is missing, because nothing defined what should have been present.
Standards also make absence visible. A missing field is obvious in a way that a missing thought never is, and that visibility is what allows correction without confrontation.
The enforcement cost is low for the same reason. Asking someone to complete a field is a process request rather than a judgement about their communication ability.
Standards travel between people in a way that skills cannot. A format can be handed over in a sentence, applied on the first day, and checked by someone who has never met the author.
Standards Raise the Floor and Training Raises the Ceiling
Most organisational damage comes from the floor rather than the ceiling. The expensive failures are missing information, not inelegant phrasing.
A decision made without a known constraint costs real money. A decision made from a slightly clumsy but complete brief costs nothing at all.
Training works on the ceiling. It takes people who are already adequate and makes them better, which produces improvements that are genuine and hard to detect at the level of business outcomes.
Standards work on the floor. They prevent the specific failures that cause rework, missed deadlines and repeated meetings, and those failures are where the money actually goes.
The two are also priced differently. A workshop carries a per-person cost that repeats with every hire, while a written format is created once and applied indefinitely.
That asymmetry compounds. Each new employee inherits the standard on their first day at no marginal cost, and each new employee requires training to be purchased again.
Standards further reduce the training burden that remains. A new manager who receives the formats already knows most of what a general workshop would have covered about structure.
There is a second effect that is easy to miss. Standards reduce the volume of communication as well as improving it, because complete messages generate fewer follow-up exchanges.
Incomplete updates create their own traffic. Each missing detail produces a question, a reply and often a meeting, none of which would have been needed had the format been followed.
What a Small Set of Standards Looks Like
Standards do not need to be numerous to change output. A handful covering the highest traffic communication types is enough for most small and mid-market businesses.
The first is the status update. A fixed set of fields, a fixed destination and a fixed rhythm removes the most common source of manufactured check-ins.
The second is the escalation. A stated problem, the impact, what has already been tried and the decision being requested, which prevents escalations that are really just complaints.
The third is the meeting request. A meeting that cannot state the decision it exists to reach becomes an email, which removes a substantial share of recurring calendar load.
The fourth is the decision record. What was decided, who decided it, what it was based on and who needs to know, written in a place that can be found later.
The fifth is the handover. What is in progress, what is at risk, what the receiving person needs to do first, and who to ask about the parts that are unclear.
These overlap with the wider set of practices that determine how information moves through a business, which is where formats stop being administrative detail and start affecting operating results.
Each standard should fit on a single screen. A format long enough to require study will be ignored, and an ignored standard is worse than none because it teaches staff that standards are optional.
The list should be reviewed rather than accumulated. Formats that stop earning their place should be retired, and the review itself is what prevents standards from turning into paperwork.
Why Standards Are Mistaken for Bureaucracy
The objection arrives quickly and usually from senior people. Formats are described as rigid, as treating adults like children, or as adding process to work that was moving fine.
The objection is understandable and mostly wrong. Bureaucracy is process that consumes effort without changing an outcome, and a format that prevents a missing blocker changes outcomes directly.
The complaint often reveals something else. Senior people have usually built private habits that already cover the same ground, so the standard feels redundant to them specifically.
It is not redundant for the newer half of the organisation. Those private habits are invisible, untransferable and unavailable to anyone who has not spent years developing them.
Rigidity is a real risk where standards are written badly. A format that demands information nobody uses becomes ritual, and ritual is what gives the objection its force.
The test is whether a field ever changes a reader decision. Fields that never do should be removed, and removing them regularly is what keeps a standard credible.
Standards should also be visibly revisable. A format that can be challenged and amended through a known route attracts far less resistance than one that arrives as an instruction.
A further advantage is that standards make performance conversations concrete. Feedback about a missing field is specific and actionable, while feedback about someone being unclear is neither.
That specificity protects the relationship as well as the process. Managers who can point at a defined expectation are not asking staff to guess what better would have looked like.
Where Training Still Earns Its Cost
Some communication cannot be reduced to a format. Delivering bad news, handling a dispute, negotiating a contested priority and giving difficult performance feedback all depend on judgement in the moment.
These situations are genuinely skill dependent. There is no field to complete that makes a manager competent at telling someone their performance is not acceptable.
Training aimed at these narrow situations is worth the cost. It targets exactly the cases where individual capability is the binding constraint rather than the format.
The mistake is buying general communication training for problems that are structural. A workshop on clarity does not fix a business where nobody agreed what an escalation should contain.
The sequence matters more than the choice. Standards first, because they reveal which remaining problems are actually about skill and which were about missing definition.
After standards are in place, the training need usually shrinks. It becomes specific, smaller, and directed at named people rather than delivered to everyone as a general improvement exercise.
The awkward part of this argument is that it makes communication less personal. Formats feel mechanical next to the idea of an organisation full of thoughtful and articulate communicators. The mechanical version is the one that still works in the third year, once the people who attended the workshop have moved on. Those who replaced them inherit a documented way of working rather than a memory of a good day.
Frequently Asked Questions
How many communication standards should a business start with?
Three to five is usually the right starting range. Status updates, escalations and meeting requests cover the highest traffic and produce the most visible improvement. Adding more before those are established tends to dilute attention and reduce compliance across all of them. Additional standards can follow once the first set has become habitual.
Do standards work when staff resist them?
Resistance usually reflects a format that asks for information nobody uses. When each required field visibly changes what a reader does, compliance follows without much enforcement. Where resistance persists against a useful format, the problem is often that the standard was announced rather than agreed. Involving the people who will use it during drafting removes most of the friction.
Is communication training ever the right first move?
Rarely, though it is not useless. Training is the right first move when the failures are concentrated in a few named individuals who handle difficult conversations badly. When the failures appear across many people and many situations, the cause is structural and training will not hold. Diagnosing which pattern applies takes very little time.
What makes a written standard actually get used?
Brevity, a single location and consistent modelling by senior people. A format that fits on one screen and lives where the work happens gets used, while a document in a shared folder does not. The strongest signal is whether leadership follows the same format in their own updates. Standards that senior people exempt themselves from decay within weeks.
How do standards affect onboarding?
They shorten it considerably, because a new employee inherits an explicit description of what good output looks like. Without standards, newcomers spend their early months inferring expectations from observation and correction. Written formats replace that inference with instruction. The effect is largest in businesses with frequent hiring or seasonal staff.
Can standards be applied to informal channels?
Yes, and the most useful application is defining which channel carries which kind of message. A standard that routes decisions to a written record and keeps chat for coordination prevents important agreements from disappearing into message history. The format itself can stay light in informal channels. What matters is that anything decided ends up somewhere it can be found.
No comments:
Post a Comment