Why “autopsy” instead of venting
After a bad lesson, it is tempting to blame the kids, the bell, or the day. Sometimes those matter. Often the deeper issue is structure: the plan had built-in fracture points that stayed invisible until something bumped the table.
An autopsy means naming what broke in design terms so you can fix the lesson—not so you can feel worse. This lesson introduces five common fracture points and walks you through applying them to a real flop (yours or a sample).
Fracture point 1: Unclear success criteria
If students cannot answer “What would a good finished product look like?” in their own words, they fill the gap with guessing, compliance theater, or shutdown. “Do the activity” is not a criterion.
Symptoms: endless “Is this right?”; uneven work that doesn’t match what you thought you assigned; after any disruption, nobody knows how to restart.
Structural cause: the task was clear in your head but never made observable for them—no model response, no checklist, no single prioritized outcome.
Fracture point 2: Single-path dependence
Plans that assume one explanation, one sequence, or one representation work until someone needs a different door. Then the whole lesson stalls.
Vignette: Fire drill, lost thread
Ms. Delgado’s math lesson moves from a quick demo into group work. A fire drill eats twelve minutes. When students return, she says, “Pick up where we left off,” but the room fragments: some groups restart the wrong problem, others copy neighbors, a few wait to be told what “finished” should look like. She assumed they shared her mental picture of the task.
The drill was only the trigger. The core fracture is unclear success criteria: students were never anchored to an observable “done” they could return to. Single-path dependence (one strategy, no recap slide, no Plan B entry) then makes recovery even harder—often two fractures stack.
Fracture point 3: Timing miscalculation
You planned for fifty productive minutes; fifteen vanish to announcements, login issues, or a pulled student. The closure never happens, or you rush the only part that made sense of the rest.
Symptoms: perennial “we’ll finish tomorrow”; skipping debrief every Tuesday; students leaving mid-cognitive lift because the bell cut the sense-making.
Structural cause: zero slack and no labeled cuts—you never decided in advance what shrinks if time does.
Fracture point 4: Unplanned transitions
Each jump—from mini-lesson to desk, from pairs to whole group, from tech to paper—is a place cognition can drop. Chaotic handoffs feel like behavior problems; often they are missing routines: what to bring, where to look, what to start before you speak again.
Symptoms: volume spikes, half the class “forgot” the question, you re-teach the prompt three times.
Structural cause: transition treated as dead air instead of a designed step with a cue and a first action.
Fracture point 5: Task demand vs. student readiness
A one-size task in a mixed class often yields two failures at once: some students are done in four minutes with no stretch; others never access the thinking because reading, vocabulary, or prior skill is the real gatekeeper.
Symptoms: “I’m finished” / “I don’t get it” at the same moment; you become a human shuttle running between extremes.
Structural cause: the cognitive demand of the activity wasn’t matched to entry ramps—scaffolds, chunking, or parallel tasks aimed at the same criterion.
Pressure-test before you teach (preview protocol)
Take a lesson you will use soon and run it through five quick questions:
- What is the one observable “done” I could point to on paper or in talk?
- If my main path fails, what is Plan B that still hits the same criterion?
- Where did I budget slack—and what gets shorter if I lose ten minutes?
- For each transition, what is the first student action in twenty seconds?
- Who might be under- or overloaded, and what is my adjustment without a second lesson plan?
You’ll deepen this framework in the next lessons; for now, the habit is looking for fractures before they find you.
Reflective exercise: Map your flop
Think of one recent lesson that felt worse than it should have—derailed, flat, or chaotic. For each fracture point, jot yes / maybe / no and one line of evidence (what you saw or heard).
Then circle the single fracture that, if fixed first, would have helped most. That is your leverage point for revision—not “teach it louder next time.”
Key takeaways
- Failed lessons often have structural causes, not only bad luck.
- Watch for: unclear criteria, single-path dependence, timing with no slack, brittle transitions, and readiness mismatch.
- Disruptions like drills or lost minutes expose weaknesses; they don’t create every weakness.
- A short pressure-test before teaching surfaces fractures while they are still cheap to fix.
- Autopsy ends with one prioritized repair, not a guilt spiral.