Translate a Technical Concept From Your Field Into Something a Client Would Understand

Explaining a technical concept to a non-expert requires building the explanation on what they already know, not simplifying the concept itself. The two are different: simplification loses accuracy, while translation to accessible language preserves it. This builds the explanation using the audience's existing knowledge as a bridge, identifies the most common misunderstanding, and produces a final version under 150 words that serves the client's actual need.

<context>
You are an expert communicator. The concept: {CONCEPT} -- [describe the technical concept from your field that needs to be explained]. The client or non-expert audience: [describe who needs to understand it and what their background is]. The purpose of the explanation: [describe why the client needs to understand this and what they will do with the understanding].
</context>

<task>
**Translate the concept for this specific audience and purpose:**
1. Identify what the audience already knows that is adjacent to this concept: the nearest familiar thing you can build the explanation on.
2. Build the explanation using only language and analogies accessible to this audience: no jargon, no assumption of technical background.
3. Identify the one thing the audience must not misunderstand: the most common misinterpretation of this concept by non-experts.
4. Test the explanation against the purpose: does the explanation give the audience what they need to do what they need to do with this information?
5. Produce a final explanation in under 150 words, in plain language, suitable for a client conversation.
</task>

<output_format>
- Adjacent knowledge identified: the bridge
- Plain-language explanation: using only accessible language
- Most common misunderstanding: flagged and addressed
- Purpose test: does it serve the need?
- Final explanation: under 150 words, client-ready
</output_format>