How Do You Get Claude to Explain Something at the Right Level?
Describe the actual reader: their job, what they already know, and what they'll do after reading. "Explain simply" and "explain for experts" are too vague. "A finance manager who approves this budget and has never seen our codebase" tells Claude what to leave out, which terms to define and what to lead with.
Explain [concept or decision] to this reader: Who they are: [job and background] What they already know: [specifics] What they don't know: [specifics] What they'll do after reading: [decide, approve, implement or explain it to someone else] <source> [paste the design doc, ticket or notes this is based on] </source> Start with what this reader most needs for that action. Use only terms they know, or define a term in a few words where it first appears. Use an example from their work, not from software. Keep it under [length]. Base facts about our system on the source only, and tell me what the source doesn't answer.
- Executivewhy it matters
- Practitionerhow to use it
- Implementerhow it works
Try it now
- 1Pick something you recently explained badly, and paste the source material into the prompt.
- 2Fill in the reader and action, then send it.
- 3Ask a follow-up: "Now write this for [a different reader] who needs to [different action]." Compare what changed.
- 4You'll know it worked when the two versions open with different sentences, not just simpler words.
Use it when
Explaining a technical decision to leadership, writing a how-it-works page for customers, briefing a new hire, or turning an incident report into something a client can read. It also helps when you need the same content for two audiences.
Skip it when
When the question is your own and you'd rather explore. Ask, and follow up on what you don't understand. It's also the wrong tool for a very mixed audience in a single page. Layer the doc instead, or write two versions, because no single level will suit everyone.
Why it works
Anthropic's prompting guide says to give context on why you want something, because Claude can generalize from the reason. What the reader will do tells Claude what matters: someone approving a budget needs the cost and the risk, and someone implementing needs the steps.
Its guide also says a single sentence setting a role focuses Claude's behavior and tone. That applies to both sides. Tell Claude who it's writing for and, if it helps, who's writing. To avoid repeating this, Anthropic offers Instructions for Claude for details that hold in every conversation, such as your own job and field. Facts are a separate issue: for your own system, give Claude the real material, since it can't know your architecture.
Example
Say your team is moving to a new database, and you need to explain the two-hour maintenance window. For the head of support, you say she's not technical, knows the customers, and has to warn them this week. For a new backend engineer, you say he knows SQL, hasn't seen the system, and will run part of the migration. You paste the same design doc for both. The first version should lead with what customers will notice, and the second with the order of steps.
Going further
For a document you already have, select a passage in Claude for Word and ask "Simplify this section for a non-technical audience". That's one of the prompts on Anthropic's page, and it edits only the selection. It's good for one technical section inside an otherwise general report.
If you're the one learning, say so in Instructions for Claude under Settings > Your Claude (or Account in the older layout). A line like "I'm a marketing manager and know little about software" applies to all your conversations, which saves typing and means you don't get a level you can't follow.
Common mistakes
- Writing "explain like I'm five" for a work document. That gives you analogies about toys, not what a finance manager needs for a decision.
- Describing the reader's seniority without what they know. A senior lawyer and a senior engineer read a security doc very differently.
- Giving no source for your own system. Claude has to answer from training knowledge, so the result can sound right but be wrong for you.
- Leaving "Instructions for Claude" full of details about one audience. They apply to every chat, so keep audience details in a project or prompt.
Sources
- Prompting best practices, Claude Platform Docs
- Claude's personalization features, Claude Help Center
- Use Claude for Word, Claude docs
Checked 6 November 2026. Products change often, so confirm details with the vendor.