The lesson that didn't work today is better tomorrow. Agile teaching's central claim is that a lesson that lands badly on Tuesday should be improved by Wednesday — not added to a long list of things to address in next year's planning cycle.
That requires a fast, low-friction iteration workflow that fits into a teacher's existing time budget rather than expanding it. This cluster gives you that workflow. A1 covers the 20-minute structured iteration process.
A2 addresses the decision point every teacher faces — is this lesson worth repairing, or does it need replacing entirely? A3 introduces the AI-powered regeneration workflow: observation notes in, improved lesson out, in under 3 minutes. ⚡ Why this cluster produces the most immediate results: Unlike observation habits (C2) or feedback systems (C3), lesson iteration produces a tangible output — an improved lesson — every time you use the workflow.
The feedback from C2 and C3 feeds directly into C4. If you only implement one part of the agile teaching cycle, make it this one.