Begin with a single outcome, not a script: clarify a deadline, align on scope, or ask for help without blame. Naming one desired shift focuses listening, makes success measurable, and keeps performance playful rather than performative, especially for colleagues wary of role‑play theatrics. Narrow focus delivers practical sentences teammates remember and apply.
Craft characters whose goals legitimately collide, like a product owner guarding scope and a developer defending quality. Avoid moralizing. Realistic tension invites empathy and flexible problem‑solving, showing teams how competing goods can coexist when language is careful and needs are acknowledged explicitly. Nuance teaches influence without coercion and principled compromise.
Timeboxing sustains safety. Run ninety seconds, pause, gather reflections, then switch roles or adjust constraints. Two quick cycles reveal patterns faster than one long scene. The short debrief captures phrases that worked, moments that stung, and micro‑behaviors worth intentionally reinforcing during real collaboration. Iteration beats length for durable learning every time.