# Reflection: A Framework You've Actually Used Is One You'll Trust Under Pressure

You just solved two real, different failures — a CrashLoopBackOff and a broken Service
selector — using the same seven-step framework both times. Take a few minutes to consolidate
this.

## Reflection questions

1. Which framework step did you personally find easiest to skip or rush through across both
   Labs? Why do you think that step specifically tempts shortcuts?
2. Compare how you approached `crashloop-fix` versus `endpoint-fix-task`. What was IDENTICAL
   about your process, and what was different only because the evidence looked different?
3. Now that you've practiced this framework on two failures you'd never seen exact instructions
   for, how confident do you feel applying it to a THIRD, completely unfamiliar Kubernetes
   failure? What would you still want to double-check?

## Real Ops takeaway

**The framework's value shows up most on failures you've never seen before.** Anyone can
memorize "if X symptom, do Y fix" for a handful of common problems — that knowledge doesn't
transfer. Observe → Evidence → Hypothesis → Test → Repair → Validate → Prevent Recurrence
transfers to failures nobody has specifically taught you, because it's a PROCESS, not a lookup
table.

**"Prevent Recurrence" is what separates incident response from firefighting.** Both Labs in
this module had a real, nameable prevention practice (verify command strings before deploying;
keep label keys consistent between a Deployment and its Service). Teams that consistently ask
this question after every fix accumulate fewer repeat incidents over time — not because they got
lucky, but because they closed the actual gap each time.

This module is complete. Continue to the next module.

## Instructor Notes

**Discussion questions for a live classroom:** question 1 tends to produce honest, useful
answers — "Prevent Recurrence" and "Form Hypothesis" (skipping straight to a guessed fix) are
the two most commonly admitted shortcuts, both worth normalizing as a real temptation to resist
rather than treating as a personal failing.

**Approximate timing:** 8-10 minutes live discussion; 5-7 minutes self-paced writing.

**Optional extension:** ask students to apply the framework, from memory and without re-reading
this module, to a THIRD failure type they haven't practiced yet (e.g., a Pod stuck `Pending` —
not built as a hands-on Lab in this module, just a thought exercise) to test genuine
transferability.