Rehearse the conversation you are dreading
You walk in with an opening line you believe, responses to the reactions you fear, and the wobble rehearsed out.
The problem
A conversation you need to have (roommate, parent, boss, friend) keeps getting postponed because you cannot find the words.
What you get
A working system with the steps, tools, checkpoints, and expected return made explicit.
- Setup
- 30 minutes
- Back each week
- 0.5 hours
- Difficulty
- starter
Expected return
The working case
A planning estimate, not a guaranteed result. Measure the first four weeks against your own baseline.
24
hours returned per year
At 0.5 hours/week across 48 working weeks.
1
week to earn back setup
Compare the setup estimate with the weekly time returned.
Operating contract
Input
The source material, constraints, and examples a human would need to do this work well.
Checkpoint
A person reviews judgment calls, sensitive content, unfamiliar tools, and irreversible actions.
Success signal
Track time returned, corrections required, and exceptions. Keep it only if the measured result compounds.
The steps
- 01
Set up the rehearsal.
Copy this prompt
I need to tell [who] that [the thing]. I am afraid of [their reaction / hurting them / backing down]. Help me: 1) find an opening line that is honest and kind, 2) plan for their three most likely reactions, 3) then role-play it: you play them, realistically, not worst-case, and I will practice. After each of my responses, give one line of coaching.
- 02
Run the role-play twice: once as written, once where they react badly. The second run is the one that steadies you.
- 03
Write your opening line on paper. Have the conversation within 48 hours of rehearsing, before the steadiness fades.
What it runs on
- Claude
Voice mode makes the role-play feel real enough to matter.
Where this goes wrong
- Rehearsal is for finding your words, not scripting theirs; hold your lines loosely once the real person responds.
- Do not paste identifying details about the other person; the situation matters, the name does not.
Definition of done
Run it for four weeks. Then make it earn its place.
- □ Baseline the manual time before launch.
- □ Keep a human approval step for consequential output.
- □ Record corrections and exceptions, not just successes.
- □ Expand, revise, or retire it after the first review.
Build the system around it
Related workflows
If this one stops working, tell us. Three reports in a month and it leaves the library until a person has looked at it again.