Core scenario
Situation: A rollback unexpectedly increases errors.
How to apply: Pause and question whether the dependency order was modeled correctly.
Outcome: Update the recovery sequence and document what the original frame missed.
Reflective thinking
Learning guide and study notes
What did our actions teach us? Use it during and after surprising outcomes.
What you will learn
- Separate what happened from the story told afterward.
- Translate an insight into an observable next experiment.
What is it?
Reflective thinking turns operational experience—especially surprises, near misses, and unexpected side effects—into durable learning by examining the mental model behind our actions and rewriting how we act next time.
Reflective practice examines the frame behind an action, especially when results surprise us, then changes future practice.
Tools and techniques
Key techniques
- Expected-vs-observed delta logRecord what you expected to happen alongside what actually occurred while operational details are fresh.
- Double-loop frame inspectionQuestion the underlying problem framing and mental model, not only the surface execution steps.
- Next-case practice revisionConvert the insight into a concrete updated sequence or checklist and verify it on the next case.
Procedure: think it through step by step
Work through these steps in order, applying the tools above. Write down the answer to each step before moving on.
- Notice surprise
Identify what did not match your expectation, during the work or afterward. [1] Source: The Open University — Schön, The Reflective Practitioner (excerpt) (opens in a new tab)
- Inspect your frame
Ask what problem you assumed you were solving and which assumptions shaped the action. [1] Source: The Open University — Schön, The Reflective Practitioner (excerpt) (opens in a new tab)
- Change the next move
Try a revised action, record its effect and carry the lesson into the next similar case. [2] Source: EEF — Metacognition and Self-Regulated Learning (opens in a new tab)
Try it now
After a surprising event, write: expected, observed, assumption, revised action, and how you will test it next time.
Visual guide
Read the workflow as text
- SituationA rollback unexpectedly increases errors.
- Step 1Notice surprise
- Step 2Inspect your frame
- Step 3Change the next move
- OutputUpdate the recovery sequence and document what the original frame missed.
Read the mind map as text
Reflective thinking
Expected outcome
Actual surprise
Hidden frame
Revised practice
Detailed examples
02 / Learning from a near-miss maintenance window
Situation: A database migration finishes two minutes before the maintenance window closes after several manual workarounds.
How to apply: Instead of marking the change “successful” and moving on, compare the planned 20-minute runtime against the 3-hour reality to inspect what the dry run missed.
Outcome: Update pre-migration dry runs to use production-scale index statistics before the next shard migration.
03 / Revising an incident communication frame
Situation: Technical recovery went smoothly, yet partner teams escalated because they did not know when to resume their batch jobs.
How to apply: Reflect on the team’s implicit frame: defining “incident resolved” as server health rather than downstream workflow readiness.
Outcome: Add a explicit downstream-resume verification step to the incident closure checklist.
Illustrative examples showing how the lens changes decisions; not measured outcomes.
Practice and keep learning
Watch out: A retrospective timeline is not reflection unless assumptions and future behavior change.
Getting better at it
- 01 · Learn the foundationPay the closest attention when an action succeeds for the wrong reason or fails despite following the runbook.
- 02 · Build daily fluencyKeep a brief decision journal recording: what we expected, what actually happened, which assumption was wrong, and what rule changes next.
- 03 · Master under pressurePractice reflection-in-action during live work—noticing within minutes when reality diverges from your model and pausing to reframe before pushing harder.
Combine this lens with others rather than relying on it alone. Browse all thinkings
Review and make it your own
The idea to remember
Reflection turns the gap between expectation and experience into a specific change for the next attempt.
An outline for your notes
Use a problem of your own. Write a short answer to each prompt, then return after trying the method.
- Expectation: record what you thought would happen and why.
- Experience: compare observed results without rewriting the original expectation.
- Learning: change one assumption or habit and define the next test.
Check your understanding
Answer from memory before opening the suggested answer.
Why write expectations before an action?
Compare with a suggested answer
It limits hindsight bias and makes the later comparison more honest. Otherwise a surprising result can be retold as something you knew all along.
What makes a lesson actionable?
Compare with a suggested answer
It names a change in behavior or assumptions, a situation in which to try it, and an observation that will show whether it helped.
Sources
These sources support the method; the examples and exercises are original teaching illustrations.
- The Open University — Schön, The Reflective Practitioner (excerpt)Reflection-in-action, reframing and tacit assumptions.
- EEF — Metacognition and Self-Regulated LearningPlanning, monitoring and evaluating practice.