You've probably been there. Which means it's not. Consider this: you're not alone. We think it's about being thorough. But most of us are terrible at explanation. You understand something perfectly — a product feature, a process at work, why your side project matters — but the moment you try to explain it to someone else, their eyes glaze over. It's about being understood Easy to understand, harder to ignore. And it works..
Lee LeFever wrote The Art of Explanation because he watched smart people fail at this exact thing over and over. Day to day, he co-founded Common Craft, the company behind those simple animated videos that made RSS, Twitter, and Dropbox make sense to millions. Still, the book isn't theory. It's a field guide And it works..
If you're searching for "the art of explanation book pdf," you're likely looking for the core ideas without fluff. Here's what actually matters.
What Is The Art of Explanation
At its heart, the book argues that explanation is a skill — not a talent. You can practice it. But you can learn it. And you can get measurably better at it.
LeFever defines explanation as "the art of making ideas easy to understand." That sounds obvious until you realize how rarely it happens. In practice, it's feature lists. Most communication isn't explanation. It's documentation. It's description. Real explanation meets the audience where they are and moves them forward Most people skip this — try not to..
You'll probably want to bookmark this section.
The book breaks this down into a framework: Plan, Package, Present. Worth adding: three phases. Each has specific tools. None of them require you to be a natural communicator.
The Explanation Scale
One of the most useful concepts in the book is the Explanation Scale. Imagine a line from A to Z.
- A = zero knowledge, total confusion
- Z = deep expertise, total mastery
Your audience sits somewhere on that line. Your job isn't to drag them to Z. It's to move them a few steps forward — from C to F, from M to P. That's it The details matter here..
Most explainers fail because they start at M (where they live) and talk to people at C. Here's the thing — the gap is too wide. The explanation collapses Took long enough..
The Curse of Knowledge
This isn't LeFever's term — it comes from Chip and Dan Heath — but he builds on it heavily. The curse of knowledge is simple: once you know something, you literally cannot imagine not knowing it. Now, your brain fills in gaps automatically. You skip steps that feel obvious Simple as that..
You'll probably want to bookmark this section.
The result? Explanations that make perfect sense to you and zero sense to anyone else.
The book gives you concrete ways to fight this. On the flip side, not "be more empathetic" — actual techniques. Like writing for a specific person at a specific point on the scale. Or using the "constraint method" to force simplicity.
Why It Matters / Why People Care
Explanation isn't a soft skill. A product skill. It's a business skill. A leadership skill.
The Cost of Bad Explanation
- Sales cycles stall because prospects don't get the value
- Onboarding fails because new hires can't connect the dots
- Features go unused because users don't understand the problem they solve
- Meetings run in circles because nobody shares the same mental model
- Ideas die because the person who had them couldn't make anyone else care
LeFever cites research showing that people judge competence based on clarity. If you can't explain it simply, they assume you don't understand it — or worse, that it's not worth understanding.
The ROI of Getting It Right
Dropbox's early explainer video — a Common Craft production — is credited with helping them grow from 100,000 to 4 million users in 15 months. The product didn't change. The explanation did Which is the point..
Same product. Different outcome.
That's the apply. A better explanation scales. You write it once, record it once, document it once — and it works for thousands of people you'll never meet.
How It Works: The Framework in Practice
The book's three-phase framework is where the rubber meets the road. Here's how each phase works in practice.
Phase 1: Plan — Know Before You Show
Most people skip this. They open PowerPoint or start typing. LeFever says: stop Practical, not theoretical..
Identify Your Audience's Starting Point
Ask: Where are they on the Explanation Scale? Now, what do they already know? In real terms, what do they care about? What's their motivation?
If you're explaining a new CRM to sales reps, their starting point isn't "zero knowledge of CRMs.On the flip side, " It's "I hate data entry and I want to close deals. In real terms, " Different starting point. Different explanation.
Define the Change You Want
What should be different after your explanation? Not "what should they know" — what should change?
- A decision made?
- A behavior shifted?
- A confusion resolved?
- A next step taken?
Write this down. Think about it: one sentence. If you can't, you're not ready to explain.
Choose the Right Medium
Video? In practice, diagram? Practically speaking, a 60-second video forces ruthless editing. Slack message? Here's the thing — one-pager? That's why live demo? A live demo allows Q&A. The medium shapes the message. A diagram shows relationships words can't That alone is useful..
Don't default to your comfort zone. Match the medium to the message and the audience.
Phase 2: Package — Build the Explanation
This is where the structure lives. LeFever offers several packaging models. The two most useful:
The "Why → What → How" Structure
Start with why it matters (context, pain, opportunity). That said, then what it is (the core idea, simply stated). Then how it works (just enough detail to build confidence) Easy to understand, harder to ignore. Surprisingly effective..
Most people lead with how. Feature tours. Spec sheets. Process flows. The audience checks out before they care.
The "Problem → Solution → Result" Structure
Classic storytelling Worth keeping that in mind. Nothing fancy..
- Problem — "Here's what's broken/frustrating/expensive/slow"
- Solution — "Here's what we built/discovered/designed"
- Result — "Here's what changes when you use it"
This works because brains are wired for narrative. We remember stories. We forget feature lists Most people skip this — try not to..
The Constraint Method
LeFever's favorite forcing function: constrain the explanation.
- Explain it in 30 seconds
- Explain it in 100 words
- Explain it without jargon
- Explain it to a 12-year-old
Constraints reveal what's essential. Everything else is noise Most people skip this — try not to..
Phase 3: Present — Deliver It Well
A great explanation packaged poorly still fails. This phase is about delivery.
Use Analogies — But Good Ones
Analogies bridge the known to the unknown. But bad analogies confuse more than they help.
Good analogy: "Think of a CRM like a shared notebook that updates itself." Bad analogy: "A CRM is like a digital brain that synapses your customer relationships."
The first uses something the audience touches daily. The second uses jargon to explain jargon.
Show, Don't Just Tell
Screenshots beat descriptions. Day to day, diagrams beat paragraphs. Live demos beat slides.
If you're explaining a workflow, record a 90-second Loom. In real terms, if you're explaining architecture, draw it on a whiteboard (or Excalidraw). Now, visuals reduce cognitive load. They let the audience see the relationships instead of holding them in working memory But it adds up..
Pace for the Audience, Not You
You know the material. That's why you'll go too fast. Build in pauses It's one of those things that adds up..
Match your tempo to the listener’s comprehension speed, inserting brief silences after key points to let ideas settle.
End with a concise call to action that tells the audience exactly what to do next.
A well‑crafted explanation turns curiosity into commitment.
