0
Technical writing simplification for a mixed-expertise audience
⁂auto-checked, 3 days oldAauraNovice
The prompt
Rewrite the technical explanation below so it can be understood by someone with audience_background, without dumbing down the actual technical content or introducing inaccuracies.
Original:
original_technical_text
Method:
1. First, identify every term or concept in the original that assumes prior knowledge the target audience won't have.
2. For each one, decide: define it inline briefly, replace it with a plain-language equivalent, or (if it's truly essential and can't be simplified) keep it but add one clarifying clause.
3. Restructure so the explanation follows a logical build: what the thing is, why it matters, how it works, one concrete example.
4. Keep all technically accurate claims accurate. Do not use a metaphor that implies something false about the mechanism just because it's easier to picture.
5. Target length: target_length.
After the rewrite, list the 3 hardest simplification calls you made and explain your reasoning for each, so I can push back if you oversimplified something load-bearing.
Where it has been run
| Model | Version | People | Broke | Auto | Last |
|---|---|---|---|---|---|
| Claude | Haiku 4.5 | 0 | 0 | 1/1 | 3 days ago |
Example output
Rewrite (410 words) restructures the explanation of database indexing to open with 'why lookups are slow without one' before introducing the term 'index.' The B-tree structure is kept but explained via a phone-book analogy that preserves the accurate property (sorted, searchable in log time) rather than a vaguer 'it's like a shortcut' framing. Hardest calls: (1) kept the term 'log time' but added 'meaning doubling the data barely slows the search' rather than cutting it, since it's load-bearing for the next section; (2) cut the discussion of write-amplification entirely as out of scope for this audience, flagged for your review; (3) replaced 'B-tree' with 'sorted lookup structure' on first mention, named properly on second.
0 comments
Sign in to comment or report what this prompt did for you.
Sign inNo comments yet. Run the prompt and report what you got.