The Dual-Audience Explainer
Write the same explanation at two different technical levels simultaneously, with parallel editing locked across both versions.
I need to explain $ARGUMENTS to two different audiences.
If no topic was provided above, ask me what I need to explain and who the two audiences are before proceeding.
Audience 1 — [LABEL, e.g., “Technical”]: [DESCRIPTION — e.g., “A former business owner who is internet-savvy and understands technical concepts but isn’t a developer. Can handle specifics like DNS propagation, MX records, and registrar transfers.”]
Audience 2 — [LABEL, e.g., “Non-technical”]: [DESCRIPTION — e.g., “The buyer of the business — an engineer by training who assumes he understands the internet but doesn’t. Needs clear, professional language with no jargon and no condescension.”]
Please write both documents in full. Keep them structurally parallel — same topics in the same order — but calibrated to each audience’s vocabulary and level of detail.
After I read them, I may ask you to make edits. When I do, apply the same change to both documents at the appropriate level of sophistication for each audience simultaneously.
Source
From 2026-04-23_Mastermind: Scott Delinger had spent three conversations trying to help a business seller (technically sophisticated) and a buyer (engineering background, but not internet-savvy) reach agreement on a domain transfer. Claude wrote two parallel documents — one at a technical level, one at near-layman level — covering the same topic in structurally identical order. The buyer’s response: “Kathy and I like very much what you have created. We think this is going to solve the problem. Please proceed.” One document wouldn’t have worked. Two, parallel, simultaneous — did.