Couch Scholar
Professional Learning Experience

Work the Problem

Apollo 13: Crisis Leadership, Decision Rights, Constrained Innovation & Communication Discipline.

You'll learn how strong crisis teams establish command, prioritize under severe constraint, improvise safely and communicate with discipline, and you'll leave with a one-page Crisis Playbook Card for your own team.

Apollo 13

When something goes badly wrong and the clock is running, how does a team organize itself to make good decisions with what it actually has?

You'll be able to:

  • Distinguish a crisis from a bad day and stand up a clear response structure in the first minutes.
  • Name who decides, who advises and how expertise reaches the decision-maker, before the crisis starts.
  • Set explicit triage criteria, run parallel workstreams and test improvised solutions before committing.
  • Keep one clear channel to the people doing the work and communicate accurately to many audiences, including what isn't known.
  • Run a debrief that fixes the system, supports people and leads to changes that actually get made.

You'll leave with: Crisis Playbook Card

No need to have seen it first.

Begin the experience

You don't need to have seen the film. Choose "I haven't watched the film" to work from the NASA mission record, with no film scenes.

Apollo 13

The crew's return is historical fact; the choice is whether to discuss the film's scenes.

I haven't watched the film

The NASA mission record and clearly labeled hypotheticals only.

You don't need to have seen the film. We'll work from the documented 1970 mission and labeled hypotheticals, with no film scenes.

Begin with I haven't watched the film

I've watched the film

Approved film moments and NASA mission facts, clearly labeled.

We'll discuss approved film moments alongside the NASA mission record, and name where the film dramatized events.

Begin with I've watched the film

You can change stories while you are still in Observe. After that, your chosen story stays with you for the rest of the experience.

The question at the center

When something goes badly wrong and the clock is running, how does a team organize itself to make good decisions with what it actually has?

Why it matters

Crisis response succeeds less through lone heroics than through prepared relationships and dependable structures: people trust one another enough to report unwelcome facts, someone clearly holds the decision, expertise can challenge rank, priorities are explicit, improvisation is tested before it is trusted, and communication is disciplined and honest about what isn't known. The work doesn't end at the rescue; institutions that learn afterward fix the system that made the crisis possible, rather than only praising or blaming the people inside it.

The Learning Everywhere Framework™

Observe → Connect → Analyze → Apply → Reflect

  1. 1

    Observe: Mission Control

    Examine how the Apollo 13 team organized itself in the first hours, without turning it into a hero story.

  2. 2

    Connect: Your Mission Control

    Bridge from Mission Control to the learner's own institution.

  3. 3

    Analyze: Work the Problem

    Apply 2–3 concepts to diagnose what made the learner's crisis response strong or fragile.

  4. 4

    Apply: The Crisis Playbook Card

    Let's build a one-page Crisis Playbook Card for your team. Pick a realistic crisis: one you've faced or one you'd most like to be ready for.

  5. 5

    Reflect: After Splashdown

    Turn the conversation into a personal takeaway saved to My Learning.

Potato, the Couch Scholar AI learning coach

Potato™, your learning coach

Potato is calm, precise and practical. It keeps the film, the NASA record and your interpretation distinct, gives no legal or emergency-management advice, and keeps your own words central in Apply and Reflect.

What you'll walk away with

  • Distinguish a crisis from a bad day and stand up a clear response structure in the first minutes.
  • Name who decides, who advises and how expertise reaches the decision-maker, before the crisis starts.
  • Set explicit triage criteria, run parallel workstreams and test improvised solutions before committing.
  • Keep one clear channel to the people doing the work and communicate accurately to many audiences, including what isn't known.
  • Run a debrief that fixes the system, supports people and leads to changes that actually get made.
Begin the experience