Methods · Perspective, simulation & context · Short guide

Stakeholder / client simulation

Handle a demanding client, patient, or user in simulation, practising translation, boundary-setting, and requirement extraction under pressure, not just solving the technical problem in a vacuum.

When to use this: While you practise
Learning impact: Strong change
Learning evidence: Credible with caveats
Where you are with the topic: Applying in new contexts
How often to use it: Worth repeating often

When to use it

You can solve the technical problem but freeze when a real client, patient, or user pushes back.
You need practice under interpersonal constraint: unclear goals, shifting priorities, limited time.
An OSCE, clinic, design review, or consulting case is coming.

What to ask AI

Type something like: “Play a sceptical hospitalist who wants a one-minute recommendation on this case. Interrupt if I waffle. Stay in role until I ask for debrief.”

Ask it to withhold the “right answer” and force a short, defensible recommendation.

You deliver; then request a supervisor-style debrief.

How it helps

Technical competence is not the same skill as handling a demanding stakeholder under time pressure.

Simulation lets you practise clarifying goals, negotiating scope, and defending a recommendation.

Fidelity is limited: a chat client is not a real person. Still useful for first repetitions.

How to run it

Define the stakeholder and what they care about.
Give yourself incomplete information on purpose.
Make a short recommendation you could defend to a supervisor.
Let the stakeholder push back once.
Debrief: what did you assume, hedge, or avoid?

Example exchange

You

You play a founder who wants an analytics dashboard “yesterday.” Budget is fuzzy. Interview me as the engineer,be impatient but fair.

I need charts by Friday. Don’t bury me in architecture. What’s the smallest thing that actually reduces my uncertainty?

You

One funnel metric with a known data lag,not a full warehouse rebuild.

Why should I trust the lag number? Two sentences, no jargon stack.

Copyable prompt

Role-play. You are [STAKEHOLDER] with this messy goal: [ ].
I am [MY ROLE]. Stay in character: be vague, occasionally contradictory, and
resistant to jargon. Do not solve the technical problem for me. After I give a
requirements summary, correct what I missed. Then pressure my recommendation.
When I say DEBRIEF, leave character and critique my elicitation.

The Tell

You know this method has flipped when the simulation agrees with you and never forces a trade-off.

A pleasant client teaches nothing.

Require pushback, time pressure, and a recommendation you can defend.

Principle evidence

Strength of the underlying learning idea, not a claim about AI products.

The underlying learning idea is rated moderate. Client/patient/user simulation is standard in professional education (simulation-based learning, standardized patients in medicine, large literature). Principle moderate-to-strong within professions; chat-AI fidelity vs live simulation remains speculative.

AI delivery evidence

Whether an AI tutor delivers this method well is a separate question.

The learning principle may be moderate, but that does not prove an AI session delivers it well. Treat AI delivery as speculative unless a study of tutoring with this method is named, and none is claimed here.