Challenge your own assumptions early — don't let them become obstacles for your learners.
Derived from the case study When Infrastructure Fails, Access Shouldn't. Every design is built against an implicit model of who will use it. This tool makes that model visible and examinable — before it gets built into something a learner has to work around.
How to use this tool
Work through the three movements in order. Be specific — vague answers produce vague insight. If you find yourself writing in generalities, go one level deeper. Use the severity ratings in Movement 3 to prioritise what to address before your next review. At the end, generate your three outputs: a positionality statement, an examined learner model, and a friction log.
Team protocol: Each evaluator completes Movement 1 independently before the session. Share positionality statements first — before discussing the design. Then complete Movements 2 and 3 independently. Compare friction logs and treat disagreements as data: different ratings reveal different standpoints, and that difference is itself a finding.
This tool works best when you treat it as a thinking instrument, not a scoring exercise. There are no correct answers. There is only greater or lesser honesty about the assumptions you brought into this design. The prompts will ask you to be specific. Vague answers produce vague insight. If you find yourself writing in generalities, that is a signal to go one level deeper.
Your outputs
Positionality statement
Examined learner model
Friction log — ranked by priority
These are not deliverables for a client. They are instruments for you — evidence that you did the harder work of designing for someone other than yourself. Bring the positionality statement and learner model to your next sprint. Update them as you learn more. The friction log gets shorter as the design gets better.