Diagnose why your explanation keeps confusing people
If you've explained something multiple times and people still look confused, the problem is usually structural, not the audience. This prompt audits your explanation and rebuilds it with the specific failure points fixed.
I keep explaining {{TOPIC}} to {{AUDIENCE_DESCRIPTION}} and they consistently get confused or ask the same follow-up questions. I want to find out what's wrong with my explanation and fix it.
Here is my current explanation:
{{CURRENT_EXPLANATION}}
1. Read my explanation and identify structural problems. Look for: assumed prior knowledge I haven't stated, logical jumps between steps, abstract claims with no concrete anchors, definitions that use the word being defined, and ordering problems where I explain effect before cause.
2. List each problem as a specific diagnosis with the exact sentence or phrase that causes it.
3. Identify the single most likely reason this explanation fails for {{AUDIENCE_DESCRIPTION}} specifically. Consider their likely knowledge base and what they probably care about.
4. Rewrite the explanation with all diagnosed problems fixed. Keep the same core content but restructure the delivery.
5. After the rewrite, note any tradeoffs you made — for example, if you simplified something in a way that loses nuance a more advanced reader might need.
Note: If {{CURRENT_EXPLANATION}} is very short (under 100 words), this prompt will have limited diagnostic material to work with. Add more of what you actually say out loud when explaining this. {{TOPIC}}{{AUDIENCE_DESCRIPTION}}{{CURRENT_EXPLANATION}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{TOPIC}}{{AUDIENCE_DESCRIPTION}}{{CURRENT_EXPLANATION}}. - Paste it into one of the recommended tools below.
- Iterate: tighten constraints in the prompt if the output is generic.
Why this prompt is structured this way
The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.
Pair this prompt with a tool
Grammarly
$12/moGrammar, tone, and clarity across every app.
Grammarly remains the default for grammar + tone checking. The 'Grammarly Go' generative features are catching up but are not the main reason to subscribe.
Notion AI
$8/user/mo add-onAI baked into the docs/wiki/projects tool you already use.
Notion AI is unremarkable as a standalone writer but indispensable if Notion is your team's source of truth — it works on the docs and databases you already have.
Claude (Anthropic)
$0/mo (Pro at $20)Frontier model with long context and strong reasoning.
Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.
ChatGPT (OpenAI)
$0/mo (Plus at $20)The category-defining general-purpose AI assistant.
ChatGPT has the broadest feature surface: image gen, voice, custom GPTs, web browsing, code execution. Often the right default; sometimes beaten on specific tasks by Claude or Perplexity.
The PlaybookPrompts weekly
One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.
Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.