The anxiety

“If they all do different things,
how do I know what any of them know?”

The most common objection to flexible learning paths is the data problem. Exit tickets and formative checks depend on students working toward the same objective — so you can compare responses and identify class-level patterns. If every student is taking a different path through the content, the data becomes incomparable. You lose the ability to identify systematic gaps because there is no common reference point.

This concern is real. The resolution is a specific design principle: flexible paths means different routes to the same destination, not different destinations. The learning objective is shared. The exit ticket is identical. The exit criteria are common. What varies is the route through the lesson — the examples used, the order of tasks, the level of scaffolding provided. These variations are meaningful to students. They do not affect the comparability of the end-of-lesson data.

💡The test for path flexibility vs objective flexibility
Ask: can I run the same exit ticket for all students at the end of this lesson, regardless of which path they took? If yes, the paths are flexible and the objective is shared. If not — if different students need different exit tickets — the objectives are different, not the paths. Objective flexibility breaks the agile loop. Path flexibility preserves it.
Three types of path flexibility

Route. Sequence. Representation.
All maintain a shared exit ticket.

1
Route flexibility: different examples, same concept
Students choose the context; the concept is the same

Give students a choice between two or three contexts that all require the same concept. A maths lesson on percentages might offer: a retail context (calculating discounts), a sports context (win percentages), or a science context (concentration percentages). The mathematical skill is identical. The context is the student's choice. The exit ticket asks for an application of percentage calculation — any context works.

Why this works
Context choice engages prior knowledge and motivation without changing the cognitive requirement. Students who find one context more familiar or meaningful learn the concept through that context — and the concept transfers because the underlying mathematics was identical across all three.
2
Sequence flexibility: different order, same destination
Students choose which sub-task to attempt first

For multi-step lessons, allow students to determine the order in which they work through the sub-tasks. Some students work best top-down (overview first, then detail); others work best bottom-up (specific examples first, then abstraction). Providing both sequences doesn't change what students learn — it allows them to enter the lesson through the cognitive route that fits them.

Design requirement
Each sub-task must be self-contained enough that either order is valid. If Sub-task 2 logically depends on completing Sub-task 1, sequence flexibility doesn't apply — the dependency makes the order fixed.
3
Representation flexibility: different format, same output
Students choose how to demonstrate understanding

The exit ticket asks a common question — the format of the response can vary. A student who thinks visually might draw a diagram. A student who processes verbally might write two sentences. A student who reasons procedurally might demonstrate a worked example. All three representations answer the same question and produce comparable data about the same conceptual understanding.

Design requirement
The question must have a correct answer that can be expressed in any of the permitted formats. 'Explain what photosynthesis is' can be answered with a diagram, a paragraph, or a flowchart. 'Write the equation for photosynthesis' cannot — only one format is valid.
The data integrity principle

How to structure flexibility
without losing comparability.

The critical design question for any flexible path lesson is: what is the common anchor point? Every flexible path lesson needs one element that all students complete in an identical format — because that element is the source of the agile data that feeds tomorrow's lesson.

In most flexible path designs, the common anchor is the exit ticket. Students took different routes through the lesson; they all complete the same 3-question check. The variation in their responses reflects differences in understanding, not differences in path. The data is comparable. The agile loop works.

Element
Fixed or flexible?
Why
Learning objective
Fixed
The shared destination — all paths lead here
Exit ticket questions
Fixed
The common data point — makes responses comparable
Task contexts
Flexible
Student choice increases engagement without affecting learning
Task sequence
Flexible (where tasks are independent)
Different cognitive entry points, same content
Response format
Flexible (where concept allows multiple representations)
Multiple valid ways to demonstrate the same understanding
Scaffolding level
Flexible (three-level structure)
Matched to prior attainment without changing the objective