Generic choice vs informed choice:
the difference is structure.
The most common failure mode in classroom choice design is offering choice that students lack the knowledge to make well. “Choose which activity best matches your learning style” asks students to self-assess accurately before they have completed any part of the lesson — before they have evidence of where their understanding is strong and where it breaks down.
Choice architecture — a term borrowed from behavioural economics — is the practice of designing the options and the framing so that well-informed choices are structurally easier to make than poorly-informed ones. Applied to classrooms: the choice should be offered at the moment when students have enough data about their own understanding to make a meaningful decision, and the options should be framed in terms of what each one will help the student do — not what level or type the student thinks they are.
Consolidation. Application. Challenge.
Three options, one exit ticket.
The most reliable choice architecture for agile classrooms uses exactly three options: one consolidation task, one application task, and one challenge task. Each is designed for a specific prior attainment signal from the exit ticket data. Each leads to the same exit ticket question. The three options are not labelled by ability — they are labelled by what they offer.
The consolidation task provides scaffolded practice of the core concept with additional worked examples and structured support. It is not easier content — it is the same content with more structure. A student who has the gap will complete this task and arrive at the exit ticket with a genuine understanding of the concept.
The application task requires students to use the concept in a familiar-structure context — the type of task they will encounter in assessments. It has less scaffolding than the consolidation task but clear structure and a defined output.
The challenge task requires the concept to be used in a novel, unfamiliar context — one that requires genuine transfer. It may also require combining the current concept with a previously learned one.
Offer it after the check,
not before.
The three-option choice should be offered after students have attempted the first part of the lesson — not at the start. Specifically, it should be offered after any formative check that reveals where students' understanding currently is. This is the mechanism that connects choice architecture to agile teaching: the formative check provides the information that makes the choice informed.
The mid-lesson check is the hinge. Without it, students choose based on preference. With it, they choose based on evidence of their own current understanding. The difference in learning outcomes between these two conditions is significant — and the additional time cost is zero, because the check was already part of the agile teaching workflow.
The loop that C5 describes
connects to C6 and C8.
C5 has covered how to increase student agency in the agile classroom — using voice as data (A1), designing flexible paths that preserve the feedback loop (A2), and structuring choices that students can make well (A3). The practices in C5 generate richer data and higher engagement.
C6 — School-wide culture scales this to the school level — the structures that make these practices consistent across classrooms rather than dependent on individual teacher initiative. C8 — AI as the agile tool shows how AI generates the three-task options from a single prompt in under 2 minutes.