How to Explain an Idea So Someone Can Use It

Colorful handwritten sticky notes pinned to a pale board.
Photo: Patrick Perkins / Unsplash

Apply Made to Stick to one explanation: choose the essential point, show a concrete example, and ask the reader to use it in a new situation.

Updated 20 October 2026.

An explanation becomes useful when another person can recognize the situation it applies to and take the next step. Choose one central point, show what it looks like in practice, and check understanding with a fresh example. A memorable sentence is only the beginning.

Made to Stick by Chip Heath and Dan Heath examines why some ideas are understood and remembered. The authors' overview describes qualities including simplicity and concreteness. Our explanation exercise uses those themes without attempting to reproduce their complete framework or claim that one format guarantees recall.

Decide what the person needs to do

Before polishing the wording, finish this sentence: “After reading this, the person should be able to…” Choose an observable task, such as identifying a suspicious invoice or submitting a complete support request.

“Understand security” is too broad for a short explanation. “Check whether the bank details changed before paying this invoice” creates a practical boundary. You can introduce additional material once that first decision is clear.

Also identify the audience's starting point. An example that is concrete to an experienced engineer may be opaque to a new colleague. Ask what terms or background the explanation assumes.

Replace abstract advice with a visible situation

Take a sentence such as “Improve the quality of project communication.” Ask what someone would see or hear if the advice were followed.

A more usable version could ask the project owner to include the current status, the blocked decision, and the next owner in a weekly update. Those are our example details, not a formula quoted from the Heath brothers.

Keep the explanation honest when simplifying. If a rule has an important exception, include it close to the action. Removing necessary conditions may make a message shorter while making it less accurate.

A worked example: a support request

Imagine an internal team repeatedly receiving messages that say only “the report is broken.” The proposed explanation needs to help colleagues send enough information for someone to investigate.

Instead of a broad request for clarity, the writer shows a fictional example:

  • Expected: the weekly report includes yesterday's completed orders.
  • Observed: the total stops at Tuesday.
  • Context: report name, time checked, and the filter used.
  • Next need: confirm whether the delay affects this week's review.

The example makes the desired behavior visible without including real customer data. It also distinguishes a description of the problem from a guess about its cause.

The writer then shows a second fictional request and asks the reader which information is missing. That tests whether the explanation transfers beyond the first example.

Check use, not agreement

Asking “Does that make sense?” often produces a polite yes. Instead, invite the person to apply the idea to a different scenario or explain the next step in their own words.

Treat errors as information about the explanation. If several people miss the same condition, revise that part before deciding the audience needs to pay more attention.

The communication learning path provides broader practice. Here, the deliverable is one explanation with one example and one transfer question.

Keep a small explanation record

Save the audience, intended action, example, exception, and question you used to check understanding. After the explanation is used, record where someone hesitated and what you changed.

Remember that comprehension, memory, and action are different observations. A person can repeat your sentence without knowing when it applies. A person can understand it and still lack the authority or time to act.

For recall, close the page and explain why a concrete example needs a different follow-up scenario. Then choose one explanation in your own work and replace an abstract instruction with something the reader can actually recognize.

Continue with ReadSprint

Read the linked author or publisher resource for this book's framework. For a related ReadSprint summary, explore Never Split the Difference. Use the free Book-to-Action Plan to organize your own takeaways into practice and review phases; the tool arranges the entries you supply rather than validating the method or predicting results.

Source checked 20 October 2026: The Heath brothers’ Made to Stick overview. The source supports the attributed book concept. The scenarios, questions, and practice steps in this article are original ReadSprint suggestions; example outcomes are hypothetical.

Try one idea, then return to it.

Choose one useful idea, save a practical action, and give yourself a reason to revisit it.

Keep this book

Save it to your library and return to this review after signing in.

Save one action

Write down an idea you want to use in your work or daily life.

Come back to review

Sync your notes and review dates, then find due books on your dashboard.

14-day trial • No credit card required • Sign in with Google