Review edition · Complete text lesson. Platform screenshots are being prepared.
Suppose you could…
Adapt a message for two audiences
Change tone and emphasis for two audiences while preserving the same facts.
Change tone and emphasis for two audiences while preserving the same facts.
Time is a practice estimate. Pause or return whenever you need.A useful little possibility.
Your goal is a usable work artifact, not a perfect-looking AI answer. Change tone and emphasis for two audiences while preserving the same facts.
Let’s make a start.
Use a fresh conversation in an AI tool you are permitted to use. Copy the fictional sample below, then paste the starter prompt with it. No file upload, web search or paid integration is required.
1. List the facts both versions must preserve.
2. Run the prompt.
3. Compare the versions sentence by sentence for factual drift.
4. Ask for plain language without removing uncertainty.
Your sample material
Fictional training material. No real customer information needed.
A booking form was unavailable from 09:00 to 09:40 today. It is working again. Three requests may not have been saved; the affected people are not yet identified. Support is investigating. No confirmed cause or resolution deadline for lost requests exists. Internal audience: operations colleagues. External audience: members who used the form this morning.Download sample .txt ↓
Write two updates under 100 words each, one for operations colleagues and one for members. Use the same facts but adapt emphasis and language. Do not invent a cause, restoration guarantee, affected-person list or compensation. Mark suggested next actions as suggestions, not established policy.
Keep personal and confidential information out of external AI tools. Start with the sample material.
Turn a first try into your thing.
Compare the result with the checklist before opening the worked example. Identify one specific weakness and ask for a targeted revision, referring to the original sample. If all checks pass, tighten the wording without changing the facts. Save the reviewed result in your own document; do not send or publish it as part of this exercise.
Pause for the “aha.”
Tone is not permission to alter reality. The audience changes what needs explaining, not which facts are true.
Useful beats convincing.
Check these against your actual output. Your answers stay on this device; this is self-review, not automated grading.
Finished your first try? Reveal a worked example ↓
Internal: The booking form was down 09:00–09:40 and is now working. Three requests may not have saved. Support is investigating; affected members and cause are not yet confirmed. Suggested next step: agree how to identify and follow up on missing requests.
Member version: Our booking form was unavailable from 09:00 to 09:40 this morning and is now working again. Three requests may not have been saved. We’re investigating; we don’t yet know which requests were affected.
Both versions preserve uncertainty. Neither promises recovery or invents a support channel.
A new case. Your own approach.
Apply the review principles to these new facts, not the previous sample’s specific numbers or answers.
A report is delayed because two figures are unverified. There is no revised date. Write an update for the analyst team and one for the client; keep the uncertainty in both.
One possibility leads to another.
Repeat on a small, permitted task of your own. Record what you changed and which check caught a problem. Keep using fictional inputs if workplace material is not approved for your chosen tool.
Your reusable workflow card ↓
Task: Adapt a message for two audiences Audience: [who will use this] Approved source material: [paste] Required output: Change tone and emphasis for two audiences while preserving the same facts. Constraints and unknowns: [list] Review before use: - Both versions retain the same outage times. - Possible lost requests are not reported as confirmed loss. - No cause is invented. - Internal next steps are labeled as proposals. - External wording is plain and does not overpromise.Download workflow .txt ↓
You tried something. That counts.
Keep a note of what you made or what surprised you. It stays in this browser.