Lesson 4.1 Challenge: What is failure data?

This is the Stage where many cohorts almost stop. We are warning you in advance because we want you to keep going.

In the first three Stages, you have been building. You have answered the Call. You have found Allies. You have begun to imagine yourself as a learner-heroine of STEM. Then, in this Stage, something will break.

Your sensor will fail. Your simulation will produce the wrong number. Your code will throw an error you cannot debug. Your sample will be contaminated. Your data will get corrupted on a memory card. The exact failure differs across cohorts; the category of failure does not. Every learner-heroine, in every cohort, has at least one Stage 4 moment. We have been running variants of this journey since 2019. The Stage 4 moment has shown up 100% of the time.

Most students, when this happens, feel a small, sharp shame. They write — or worse, they think — “I’m sorry”. They want to apologise to the Tutor, to the Buddy, to themselves. They want to hide the failure or fix it before anyone notices. Some of them quit at this Stage, or quietly disengage, telling themselves that they are “not really STEM kids after all”.

We are asking you to do something different.

We are asking you to treat failure as data.

The phrase comes from professional engineering. In a well-run laboratory, a failed experiment is not a tragedy; it is information. Engineers at NASA, at ESA, at every reputable research institution write failure reports with the same care as they write success reports. The Apollo 13 mission was, by some measures, a failure (it did not land on the Moon). The mission’s failure analysis, however, is studied to this day as one of the most important pieces of operational learning in space history. The mission almost killed three people. The failure report taught a generation how to survive things going wrong in space.

When something breaks in this Stage — and something will — we are asking you to do four things, in order:

1. Stop. Do not try to fix it immediately.
2. Document. Open the Astronaut Notebook (Stage 4 section) and write what happened, in your own words, with timestamp.
3. Classify. Was the failure procedural (you or someone made a mistake in following the protocol)? Instrumental (the equipment failed)? Or conceptual (the underlying assumption was wrong)?
4. Decide what to learn. Only after the documentation is done do you ask: what does this teach us?

This is the practice of the Storm Walker. The walker who, when the storm comes, does not run. They write the storm down, they classify it, and they walk through.

—

📓 Read the Stage 4 section of your Astronaut Notebook before doing today’s lab activity. Be ready to fill it in if (when) something breaks.