The first time you handle it shouldn't be the real time
Nobody gets good at the resistant SME conversation, or the exec who wants a scope answer in the next thirty seconds, by reading advice about it. It takes practice against something that actually pushes back — which is exactly what a written checklist can't do.
What it does
- Five stakeholder archetypes. Executive, resistant SME, scope-creeper, conflicting manager, skeptical technical lead — pick the type and give it the scenario context.
- Stays fully in character. No breaking to give advice mid-conversation; the pushback and skepticism are believable, not softened.
- Structured evaluation on request. Active listening, probing, clarification, conflict management, evidence-based reasoning, and whether you found the underlying concern.
- Cites your actual lines. Feedback references specific moments in the conversation, not a generic checklist.
- One concrete next step. A specific, stronger response for at least one weak moment, plus what to do differently in the real conversation.
Example
Illustrative dialogue, not a real rehearsal transcript.
Stakeholder type: scope-creeper. Scenario: mid-project, they're asking for "just one more" feature the day before the requirements freeze.
"Look, it's a tiny change — just add an export button. It won't move the date. Why is this even a conversation?" [after the roleplay, evaluation] Weak moment: you agreed it was "probably fine" before asking for effort or impact. Stronger response: "Let's size it before we commit — can you tell me who needs the export and by when?"
How it works with Claude
A one-time 10-minute install into your Claude account.
Choose the stakeholder type and describe the scenario.
Roleplay it out, then ask for the evaluation.
FAQs
What stakeholder types can it roleplay?
A rushed executive, a resistant subject-matter expert, a scope-creeper, a manager whose priorities conflict with another stakeholder's, and a skeptical technical lead — each with realistic, believable pushback.
Does it break character to give advice mid-roleplay?
No. It stays in character until you end the roleplay or ask for feedback, then steps out to give a structured evaluation citing specific lines from the conversation, not generic advice.