The Art of Explanation by Ros Atkins: Summary and Use

Key Ideas

1. Define the question the audience needs answered

Atkins checks both purpose and usefulness: what the explanation is trying to convey and whether it addresses the audience's questions. Applying those separate tests, knowing the topic is not enough. A presentation about a delayed release might need to explain the cause, the effect on customers or the decision required today. Those purposes overlap, but they call for different amounts and kinds of detail.

In the original mixed-audience example, operations needs to plan support coverage while finance needs to understand a cost implication. Begin by identifying the shared issue: whether the team should delay the release or reduce its initial scope. That question gives the explanation a center. Technical background belongs where it helps the audience evaluate the options, rather than forming a long introduction before anyone knows why they are listening.

Before drafting, write the audience's main question in one sentence and check it with the meeting owner if necessary. Note what the audience already knows and which term may be unfamiliar. Avoid assuming that a senior audience needs less explanation; it may need a different level of context. This matters because an explanation can be accurate yet fail to answer the task the audience brought. A clear question also creates a stopping condition. You can assess whether the selected material supplies a usable answer, rather than adding information simply because it belongs somewhere within the larger subject.

2. Keep necessary detail and remove information that has no job

Atkins separates simplicity, essential detail and complexity. The distinction is useful: accessible language does not excuse incomplete understanding, and concision does not justify deleting a qualification the audience needs. A detail belongs if it changes the understanding of cause, consequence, uncertainty or choice. Background that does none of those jobs may be better kept for a question or a separate reference.

For the project-delay explanation, first understand why the external approval is required. Then preserve the essential detail that it affects only one part of the release, while translating the technical description into accessible language. It may not need the internal names of every component involved. However, if the approval affects only one feature rather than the whole release, that qualification is essential. Removing it could make the explanation shorter while making the decision worse.

Review each paragraph and state its job in the margin. If two paragraphs do the same job, combine or choose between them. If a detail is necessary but unfamiliar, explain it in plain language rather than deleting it. Keep a reference to supporting material when the audience may need to inspect it. This matters because experts can confuse completeness with usefulness. The listener needs a faithful route through the relevant information, not proof that the speaker knows everything. Test a shorter version for changed meaning. If the edited explanation implies a broader delay, greater certainty or fewer options than the facts support, restore the qualification that protects accuracy.

3. Order the explanation around understanding rather than discovery

The route by which you discovered a problem is not necessarily the best order for explaining it. Investigation may involve false starts, technical detours and details that later became irrelevant. An audience usually needs a clearer route through the issue as it is now understood. Choosing that route is part of explanation, not an alteration of the facts.

In the delay example, the engineer could begin with several failed tests and gradually reveal the external dependency. A decision meeting may work better with the current issue first, then the relevant cause, consequence and available options. The audience can place each detail within a question it already understands. If the investigative history matters to judging the conclusion, include the important evidence without recreating every turn.

Draft a short outline before writing full sentences. Check whether the listener can understand each point using only the information already supplied. Define a term before relying on it, and explain a consequence close to the cause it follows. Avoid a dramatic reveal when the audience needs the answer promptly. This matters because poor order creates unnecessary mental work. A listener may spend the first half of a talk guessing what the details mean, then have little attention left for the decision. A useful sequence gives them orientation early and deepens the explanation in manageable steps. It lets complexity remain where it is necessary without making the path through it needlessly difficult.

4. Make uncertainty and qualification visible

Atkins's precision check concerns whether wording conveys the intended meaning; his context check concerns why the audience should care. Applied to uncertainty, those checks require distinguishing what you know from what you estimate or infer. A fluent account can make an uncertain conclusion sound settled. The useful alternative is to place the relevant qualification near the claim and explain how it affects the audience's choice. A general disclaimer at the end may arrive too late to correct the impression.

In the original project example, the team knows which approval is missing but does not know when it will arrive. State the confirmed dependency separately from the estimated timing. If a reduced-scope release avoids the dependency, explain what that option leaves out. The audience can then compare the choices without treating an estimate as a commitment or a partial release as equivalent to the complete one.

When reviewing a draft, mark claims as observed, documented, estimated or interpreted where the distinction matters. You do not need to say those labels aloud in every sentence. Use natural wording that gives the listener the right level of confidence. Remove precision you cannot support, such as a date that is only a guess. This matters because explanations often become inputs to other decisions. A listener may repeat your claim to a customer or another team. Make it easy to carry the qualification with the claim. The result is a more dependable message: the audience knows not only the apparent answer but also which part could change and what new information would require an update.

5. Test understanding with a concrete readback

A useful explanation should survive outside the speaker's own head. Asking whether everything is clear may produce a polite yes without revealing a misunderstanding. A more informative test asks a listener to describe the issue, consequence or next step in their own words. This is an original practice exercise for applying the book's clarity focus.

For the release discussion, ask a colleague what they would tell a customer about the delay. Their response may reveal that they think the whole product is unavailable when only one feature is affected. That misunderstanding identifies a specific repair: make the scope distinction more prominent. If they understand the scope but cannot identify the decision, revise the transition into the options rather than adding more technical background.

Choose a test that matches the explanation's purpose. For a process, ask what action comes next. For a comparison, ask which difference matters. For a decision, ask what remains uncertain. Avoid treating the listener's misunderstanding as evidence that they were not paying attention. It may show where the message placed too much work on them. This matters because clarity is demonstrated through use, not simply through the elegance of the draft. A short readback can reveal more than another private edit. After revising, check the repaired point rather than repeating the entire presentation. The aim is a message someone else can accurately use and pass on.