Page 6 of 8~110 min topic

Prompts have a job

Role-play objections without mistaking practice for evidence

Simulations expose questions; they do not prove what real users believe.

~13 min this pageWorkflow loopReviewed 2026-08-08

1Learn the idea

Read

A bounded role-play

See it

A prompt with a job
RoleTaskContextFormat

Role + task + context + format = clearer output

The squad asks for three objections to its release proposal, each tied to supplied constraints. It labels the output hypotheses to investigate, not customer evidence.

Read

Use the output well

Using only the proposal below, suggest three plausible objections.
For each, identify the proposal detail that motivates it and a question
we could ask a real stakeholder. Do not claim anyone holds this view.

Read

Guided practice

Convert “Users will hate the new flow” into a testable question and name who should be asked.

Read

Independent transfer

Generate two hypotheses for an unfamiliar low-risk proposal. Design one observation or interview question for each. Keep hypothesis and evidence in separate columns.

Check your understanding

Page assessment

Answer from memory. Completion is saved from this evidence, not from opening the next page.

What wording keeps a simulated objection from being mistaken for research evidence?

1. What is one idea from this page you would apply, and what evidence would you check?

All responses are required.