What leaders owe people when the decision is difficult. Good communication does not remove complexity. It makes the important parts visible, including the parts we would rather not have to explain.

The dangerous comfort of a short answer

An organisation has a difficult decision to communicate. There are competing obligations, incomplete evidence and people who will experience the consequences differently. The temptation is to compress everything into a reassuring sentence. It may be short. It may even be technically defensible. But if it hides the real choice, it is not clear. Clarity is not the same as simplicity. Simplicity removes detail; clarity gives detail a useful structure. The distinction matters wherever people are asked to understand a risk, consent to a decision, carry out a procedure or trust a process they cannot see.

CONSIDER THE SETTING

Consider a public venue introducing a new emergency procedure. A notice says that 'appropriate arrangements are in place'. Staff receive a document with fifteen steps, but nobody has established who makes the first call when the usual manager is absent. The public statement is simple. The operational reality is not clear. A better account would identify the trigger for action, the first responsible person, the alternative if that person is unavailable, and the point at which outside help is sought. Those facts are less elegant than a reassuring slogan, but far more useful.

Clarity begins by deciding what matters

Before rewriting a document, ask what the reader is expected to do with it. A board member may need to decide whether a risk is tolerable. A member of staff may need to recognise when a situation has moved beyond their authority. A customer may need to understand a material limitation before making a choice. Those are different tasks, and each demands different information. Good communication begins with audience, consequence and decision—not with tone of voice. It distinguishes what is known, what is assumed and what remains uncertain. It explains the next action and the reason for it.

One useful test is to ask three people, independently, what the document requires them to do. If their answers diverge, the document has a design problem even if every sentence is grammatically correct. Another is to ask what changes if a key person is absent, a phone fails or the situation develops differently from the example. Clear instructions make those limits discussable rather than hiding them in small print.

The cost of false certainty

In high-stakes settings, confident language can be mistaken for competent judgment. 'Always', 'never' and 'fully compliant' may sound decisive, but they often conceal conditions that should be visible. The honest alternative is not a page of defensive caveats. It is a proportionate explanation: this is the current evidence; this is the decision it supports; these are the circumstances that would require review. The same principle applies to risk assessments, training materials, policy summaries and public-facing information. Uncertainty is not a failure of communication when it is real. Failing to explain it is.

A useful written recommendation might distinguish a confirmed weakness from a plausible concern. The former calls for action. The latter may call for testing, monitoring or further enquiry. If both are presented as equally certain, decision-makers cannot allocate effort intelligently. Clarity makes confidence levels visible without turning the page into a technical report.

Make understanding observable

It is possible to produce an attractive guide that nobody can use. A stronger test is whether it changes what happens next. Can someone locate the decision point quickly? Can they identify who owns the action? Can they explain the rationale to a colleague? Can they recognise when the guidance no longer fits? The answer may require a diagram, a worked scenario, a shorter form, a better conversation or a different sequence of information. It rarely requires more adjectives. Editorial quality and operational quality should reinforce each other.

For a consultancy project, I would want to see the original material, the real decision it supports, the people who rely on it and the circumstances in which it fails. The deliverable could be a revised guide, a decision map, a set of tested prompts or a documented explanation of unresolved issues. The point is not to make complexity disappear. It is to make responsibility possible.

Questions worth taking into the next meeting

Where does the current explanation ask the reader to trust a conclusion without showing the basis for it? Which important uncertainty has been softened into vague reassurance? Who is expected to act, and can they describe their first step without consulting the author? What would a reasonable person misunderstand? Those questions are more useful than asking whether the document 'reads well'.

Clear thinking is not a style choice. It is a discipline of making important distinctions visible, so that people can make decisions with their eyes open.

From the essay to the work. These reflections inform how I approach defined consultancy projects: establish the problem, test assumptions, make responsibilities clearer and leave practical material that people can use.