Decide what you want leaders to demonstrate: clearer prioritization, calmer incident command, inclusive facilitation, or sharper decision narratives. Write observable behaviors, examples, and anti-patterns. With well-defined outcomes, facilitators can anchor feedback, and participants know exactly which muscles they are stretching during practice.
Describe the environment with names, time zones, tools, and pressures. Reference Slack threads, shared docs, differing holidays, and Wi‑Fi hiccups. Authentic details reduce guesswork and spark empathy, so leaders respond to context, not abstractions, just like they must in a truly distributed organization.
Offer branches, timers, and resource limits that force prioritization. Start light, then increase complexity through injected surprises: a vendor outage, a regulator email, or a teammate’s family emergency. Keep difficulty purposeful, ensuring pressure reveals thinking patterns rather than merely rewarding speed or loud voices.
A talented engineer keeps missing estimates after moving time zones to support family. Use Situation‑Behavior‑Impact and curiosity‑first questions to separate skill gaps from systemic blockers. End with a co‑created experiment, clear check‑ins, and a support plan respectful of personal realities and team commitments.
A talented engineer keeps missing estimates after moving time zones to support family. Use Situation‑Behavior‑Impact and curiosity‑first questions to separate skill gaps from systemic blockers. End with a co‑created experiment, clear check‑ins, and a support plan respectful of personal realities and team commitments.
A talented engineer keeps missing estimates after moving time zones to support family. Use Situation‑Behavior‑Impact and curiosity‑first questions to separate skill gaps from systemic blockers. End with a co‑created experiment, clear check‑ins, and a support plan respectful of personal realities and team commitments.
All Rights Reserved.