An effective recap asks learners to rebuild the lesson from memory. A weak recap hands the summary over and calls it a review. The first one strengthens the trace. The second one just feels tidy.
The last minutes of a session are precious because they shape what gets stored. Use them for retrieval, not for a slide titled Today We Learned.
Start the recap with the question that opened the lesson. If learners can now answer it, the loop is closed and the session has a shape they can feel. If they cannot, you have found the gap while it is still fixable.
Return to the target action set at the beginning. Ask learners to do a small version of it one more time. The recap becomes a demonstration, not a speech.
Ask each learner to write the one idea they would keep if they forgot everything else. Then ask a few to read theirs aloud. The room hears several versions of the same lesson, and each version attaches to a different memory.
A recap that only reads the lesson back to learners teaches them nothing new about their own understanding.
A good recap points forward. Name the one idea from today that the next lesson depends on, and tell learners you will ask for it. That promise turns the gap between sessions into part of the practice.
Keep it to one thing. A recap that lists six items to remember gives the memory nothing to prioritize, and priority is how durable knowledge forms.
Teaching so it sticks means designing for memory, not coverage. Here is how to build lessons that learners actually retain long after class ends.
Scaffolding a lesson works when the support fades as skill grows. Here is how to build steps that help learners without doing the work for them.
Examples before definitions help learners build meaning before labels. Here is why showing first and naming second makes ideas stick harder.
Analyze a channel, extract its structural DNA, and generate scripts engineered from patterns that actually work.
Analyze a Channel