Add

Writing & Editing

Explain a Technical Topic to Non-Experts

Explains a technical idea to a specific non-expert audience using one analogy, plain terms and an honest note on where the analogy breaks.

Designed for general-purpose AI assistantsPublished November 2026

Customize

Fill in the fields and the prompt updates. What you type stays in this page and is never saved or sent.

Preview

Explain the technical topic below to people who are not experts in it. The goal is that they could repeat the explanation to someone else, correctly.

Topic: {{topic}}
Who the audience is and what they already know: {{audience}}
Why they need to understand it: {{reason}}
Format and length: three short paragraphs
Technical material to draw from (documentation, notes or a draft explanation), if any: none

First, in two lines, tell me what you think the audience's most likely misunderstanding of this topic is. This is the thing the explanation must fix.

Then write the explanation:
1. Start with what it is for or what problem it solves, before any description of how it works.
2. Explain the core idea with one analogy taken from the audience's world, not from computing. Use only one analogy and stay with it.
3. Introduce at most 3 technical terms, each defined the first time it appears. If a term is not needed to understand the idea, leave it out.
4. Give one concrete example with realistic numbers or a realistic scenario, labeled as an example.
5. End with what this means for them in practice.

After the explanation add a short note headed "Where the analogy breaks" that says what the analogy gets wrong or oversimplifies, so I can answer the follow-up question an attentive listener would ask.

Rules: be accurate before being simple. If making something simple would make it false, say what you are leaving out instead of stating something wrong. If you are not sure about a technical detail, say so rather than smoothing it over. Do not talk down to the audience, and avoid phrases like "simply put" and "it's easy".

3 required fields are empty and will stay as a {{placeholder}} in the copied text.

How to use it

  1. Describe the audience concretely, such as 'finance managers who use spreadsheets daily', rather than 'beginners'. The analogy depends on it.
  2. Read the predicted misunderstanding first. If it is not the one you see in practice, correct it and regenerate.
  3. Test the explanation on a real person from the audience and ask them to explain it back. Where they stumble is where to edit.
  4. Keep the 'where the analogy breaks' note for your own use, or include it in a longer version of the explanation.

Example output

Illustrative only. Real answers depend on your input and the assistant you use.

Likely misunderstanding: that "encryption" means a locked file, so people think the data is safe once it is stored, even when the key is stored next to it.

Explanation:
Encryption exists so that someone who gets hold of your data cannot read it without a secret.

Think of a mailbox that anyone can drop letters into but only you can open, because you hold the only key. Encryption works the same way: the data is scrambled using a key, and only someone with the matching key can unscramble it. The scrambled data is called ciphertext, and the process of scrambling it is called encrypting.

Example: a clinic stores patient notes in encrypted form. If a laptop is stolen, the thief gets scrambled text. But if the key is saved in a file on the same laptop, they get both the lock and the key.

In practice, this means that where the key lives matters as much as whether the data is encrypted.

Where the analogy breaks: a mailbox lock is physical and can be picked; modern encryption relies on mathematics that is practically impossible to reverse without the key, though it can still be defeated by stolen keys or weak passwords.

Tips

The predicted-misunderstanding step is what makes an explanation useful. Explaining a topic generally is easy; explaining it to fix a specific wrong belief is much more effective.

If the assistant introduces more terms than you allowed, tell it to cut them. Most explanations get clearer with fewer words they have to define.

Check any technical claim against your own knowledge or a trusted source. A simple explanation that is wrong is worse than a complicated one.

Back to the Prompt Library

Related prompts

  • Writing & Editing

    Edit for Clarity and Concision

    Tightens a draft for a specific audience while keeping your meaning, facts and voice, and explains the main changes.

    Customizable fields
    4 fields

  • Writing & Editing

    Write an Executive Summary

    Condenses a long report or proposal into a one-page executive summary that leads with the decision needed and the evidence for it.

    Customizable fields
    6 fields

  • Writing & Editing

    Get Structural Feedback on a Draft

    Reviews a draft like a developmental editor: is the argument clear, ordered and supported? Gives ranked feedback without rewriting it.

    Customizable fields
    6 fields