1. Learner Experience Goal

Topic: Navigating Productive Friction: Facilitating High-Stakes Project Retrospectives.

Desired Outcome: Project managers must be able to confidently step into a tense post-mortem meeting, establish psychological safety, systematically surface real root-cause failures, and diffuse defensive finger-pointing without shutting down open dialogue.

2. Learner Context and Needs

Target Learners: Mid-level Technical Project Managers (TPMs) working in high-growth, fast-paced product environments. They are highly organized regarding timelines but feel intensely uncomfortable managing active interpersonal conflict.

The Under-the-Surface Challenge: Acute Conflict Anxiety. TPMs often avoid running honest retrospectives because they fear meetings will collapse into hostile blame-shifting matches. Consequently, they default to sterile, surface-level “everything went fine” documentation, which leaves critical process flaws uncorrected.

3. Experience Design Principles

• De-escalate the Environment First: Before expecting learners to practice conflict management, the instruction must validate that their anxiety is normal, moving them out of a defensive mental state.
• Practice in Low-Stakes Scenarios: Replace theoretical lectures with structured decision points that simulate realistic team defensiveness. This builds muscle memory without exposing anyone to active professional risk.
• Structure Over Intuition: Provide clear, simple language patterns that turn a messy, emotional situation into an organized process choice.

4. Learner Journey Overview

The experience is structured as a 2-week blended journey that moves from self-paced reflection to low-stakes application, before concluding with supported real-world deployment.

1. The Hook (Orientation & Relevance): Unpacking a case study of a major product launch that failed because the team kept silent about known issues.
2. The Sandbox (Guided Practice): Interacting with a realistic branch-logic scenario to practice responding to aggressive team dynamics.
3. The Arena (Peer Application): Participating in a live 60-minute peer-roleplay lab to practice running difficult meetings.
4. The Release (Real-World Transfer): Launching an actual internal retro using ready-made facilitator tools and checklist supports.

5. Touchpoint-by-Touchpoint Design

6. Activities and Interaction Plan

The “Reframing the Tension” Branching Challenge

In this online exercise, a virtual engineer shouts, “The marketing team completely missed our deadline, which is why the code was delayed!” The learner must choose how to respond:

• Choice A (Passive): Ignore the comment and keep reading the slide notes. (Result: The team stays quiet, and trust scores drop.)
• Choice B (Aggressive): Tell the engineer to stop attacking their colleagues. (Result: The engineer shuts down, and the meeting turns hostile.)
• Choice C (Facilitative): Reframe the comment using an objective observation model: “Let’s step back from names. What specific step in the cross-team handover process broke down?” (Result: The discussion shifts from blame to process refinement; unlocked milestone.)

7. Motivation and Support Strategy

• Normalizing Anxiety upfront: The opening lesson explicitly features senior engineering directors sharing stories of their own early project management mistakes and anxieties. This helps lower imposter syndrome and builds trust right away.
• Safety in the Labs: During live roleplay sessions, we establish a strict rule: “What happens in the sandbox stays in the sandbox.” These labs are never recorded or monitored by upper management, creating a safe space for genuine practice and mistakes.

8. Accessibility and Inclusion Notes

• Asynchronous Option: For team members with high introversion or social anxiety, we provide an alternative text-driven path for the initial practice phases. This allows them to process their reflections silently before stepping into live video roleplays.
• Simplified Language: All facilitator playbooks avoid complex academic jargon, using simple, clear conversational phrasings that work well across diverse team backgrounds and language levels.

9. Implementation Priorities

To launch this experience smoothly using a small instructional design team, split production into these three phases:

1. Phase 1 (The Foundation): Draft the 1-page facilitator playbook and script envelopes first. These can be used immediately as a manual support tool even before the online modules are developed.
2. Phase 2 (The Sandbox): Write and deploy the online branching-scenario text in your LMS, using simple formatting to keep development time low.
3. Phase 3 (The Automation): Build out the calendar integration scripts to automate the delivery of follow-up checklists, ensuring long-term reinforcement with minimal daily maintenance.