EDT is a writing framework that helps you plan, develop, and write conceptual works. It stands for Explain, Define, Teach. Unlike many writing frameworks, it specifically addresses the needs of the receiver, the person reading or listening to your piece. 

Use Cases: how-to style posts, teaching posts, whitepapers, series, pitch decks, non-fiction books. Especially suited to work over 5,000 words.

Writing Framework: Explain, Define, Teach

EDT uses the principles of good writing alongside teaching pedagogy. It’s built off two key teaching concepts: explicit teaching, and Bloom’s taxonomy. Explicit teaching is when a teacher uses an I do, you do lesson to help students work through a concept, then try it out for themselves. Bloom’s taxonomy sets out a learning path that applies across many fields and styles of learning: remember, know, understand, analyze, create. Together, these ideas help you craft a piece that clearly explains the problem, your conceptual solution, and your actual (how-to) solution. It can be used as an overarching framework for a book or series, in conjunction with an existing framework such as PIGS, or for smaller how-to pieces. EDT is also a good fit for big ideas and thought leadership works, with at least three things contributing to the key concept. Using the EDT framework helps you:

  • explain why your piece matters
  • define a clear outcome for your work
  • provide enough background for your receiver to understand the importance of what you’re writing and how it affects them
  • teach a key concept or solve a problem

Although EDT is broken into three pieces, the percentage weight for each varies according to the use case. In a speech, the Teach step is smaller than it would be in a book. In a book, the Define step is smaller than it would be in a speech. Another way to conceptualise this is to rework the writing tools you learnt in high school.

Before starting out with EDT, spend a few minutes working out what your end game is. If you’re writing a pitch deck, your end game is to bring on a new client. If you’re writing a whitepaper, your end game could be to sell your company’s new service. Be as clear as you can.

Explain: What/Why?

This is a grounding step. First, clearly state your idea or key point. This is the what of your piece — what matters, what’s coming up, what your receiver cares about. Keep it clear and simple, but ensure it’s related to your end goal. Ensure you provide all the background information your receiver needs to know. Don’t leave anything out — if you have too much detail, it can be cleaned up in post.

This is an especially important step because most folks jump straight into the why of a piece. Jumping straight into the why is a completely valid approach, and it fits lots of scenarios, but it requires a base level of knowledge in the receiver. But if you’re writing about anything — anything — that’s outside your audience’s general knowledge base, jumping straight into “why” can be confusing. This first step, Explain, is a comfort step. If you skip it, you risk dropping your receiver into a special kind of intellectual Hell: they know what you’re saying matters; they feel like they should understand it, but are struggling; they feel stupid. No one wants to feel stupid, so your receiver:

  • pretends they understood
  • leaves

Neither are good options. So you use this step, the Explain step, to state your idea and seed information. At the end of this section, your receiver will remember the important information, and know why your work is important. Most of the time, this section is around 30% of your piece.

Define: Restating the what

Now you’ve established the key concept and the background, it’s time to restate the concept again. Define it clearly. Although this may seem repetitive, this restatement of your concept is the hinge in of the piece. When you first stated the concept, you used a hook, but your receiver didn’t have any context. It was just a statement, a lead in to the important stuff. Now, your receiver has context. Now, when you restate your key idea, the receiver understands what you’re saying and why they should care about your words. At the end of this step, your receiver moves from remembering and knowing to understanding your concept. Most of the time, this is around 20% of your piece.

Teach: All About The How

This is where you get things done. It’s usually the biggest part of the piece, because you have to step your receiver through your process. Be as clear as you can. Include lists, images, and examples where relevant. At the end of this step, your receiver moves from understanding your concept into analysing it, breaking it into pieces, then creating with it. Most of the time, this is around 50% of the piece.

When you’re finished, go back over the material and tighten it up. Work through each piece and ask:

    • Explain: what/why
      Is it clear what my idea is? What’s the context my receiver needs? Have I ensured they have everything they need? Have I given enough context for them to understand why they should care? What does my receiver remember and know at the end of this section? Spend time cutting out any extraneous material.
    • Define: what
      Have I restated my idea clearly? What does my reader understand at the end of this point?
    • Teach: how
      Have I set up clear steps my receiver can follow? Have I provided a clear how-to? Can my receiver break down the idea I’ve explored then apply it to their own situation?

The percentages here are not hard and fast; they will shift according to the type of material you’re working on. In a business book, your chapters might use EDT with a 30/20/50 breakdown, but the book itself is more 40/40/20. Remember: before you start, work out what your end game is. Once you’re done, go back and make sure you’re hitting it.

Need a framework for something smaller? Try out PEER, which is well-suited to simpler, individual pieces under 2000 words, like blog posts and press releases.