Teaching moves and checks, side by side
Two filterable tables. What each move is for, how long it takes, the group sizes it suits and what it does not do; then the checks, with what each one can and cannot tell you.
Two filterable tables. The first is teaching moves: what each one is for, what it costs in minutes, the group sizes it suits and what it does not do. The second is checks for understanding: what each one tells you and what it cannot. Type in the box to filter, or use the buttons to show one group.
Every row names its source. Where a figure is published, it is given; where no published figure exists, the row says so rather than supplying a number.
Teaching moves
| Move | What it is for | How long | Group sizes | What it does not do | Source |
|---|---|---|---|---|---|
| Demonstration, broken into visible steps | Showing the performance at a speed a beginner can follow | The length of the task, plus the slow repeat | Up to about eight at a bench; more with a screen or two showings | Transfer the skill. Watching is not doing | Showing someone how, so they can see it |
| Peyton's four steps | Forcing narration, then handing the describing to the learner before they touch anything | Four passes through the task | Designed for one learner; step three works with a group watching | Guarantee retention: in the trial that tested it, retention was equally low in both groups | Gradl-Dietsch et al., 2016 |
| Worked example, then fade it | Scaffolding a task where the whole solution is available, then removing it | One attempt with the example, one without | Any | Show whether somebody can work without the model, until you take it away | UW-La Crosse, cognitive load |
| Goal-directed practice with targeted feedback | The part of a session where people get better at the thing | Whatever your arithmetic gives you | Limited by stations, not by headcount | Work without a target or without feedback; that is repetition | Carnegie Mellon, learning principles |
| Spacing attempts rather than massing them | Two attempts now and two later, instead of four in a row | Costs nothing; it is the same minutes split | Any | Fit a session shorter than the gap you want. Spacing across days is stronger | Dunlosky et al., 2013, rated high utility |
| Varying the conditions of practice | A different material, tool or starting state on the last attempt | One attempt | Any | Feel like progress. It is meant to be harder | Bjork Learning and Forgetting Lab |
| Practice testing, used as a warm-up | Asking people to say the steps from memory instead of showing them again | One to two minutes | Any | Replace doing the thing | Dunlosky et al., 2013, rated high utility |
| Wait time after a question | Letting people parse, retrieve and decide before anybody speaks | 3 to 7 seconds, against a typical pause of under 1 second | Any | Work if you fill it: rephrasing resets the clock | K. Patricia Cross Academy |
| Wait time after an answer | Letting the person elaborate or correct themselves before you evaluate | 2 to 3 seconds | Any | Come naturally. The reflex is to say "yes, good" | K. Patricia Cross Academy |
| Think-pair-share | Getting an answer from everybody rather than from the fastest person | Think, then one to two minutes in pairs, then a bounded share | Works from about six upward; most valuable above fifteen | Work without a stated job for the pair | University of Connecticut, active learning |
| Prediction before a demonstration | Giving people a stake in what they are about to watch | About 15 seconds | Any | Tell you much on its own; it is a setup for the demonstration | Asking, waiting and handling what comes back |
| Repeating audience questions | Putting the question through the microphone so everybody has it | Five seconds | Any room with a microphone, and most without | Replace a sound system that does not reach the back | W3C, making events accessible |
| A job aid that leaves with each person | Carrying the session to the moment of doing, weeks later | About an hour to write, once | Any | Teach the skill on its own | Slides, handouts and materials: what you give them and when |
Checks for understanding
| Check | What it tells you | Minutes | What it cannot tell you | Source |
|---|---|---|---|---|
| Show of hands on a written question | A count, read against the 35 to 70 percent band | About 1, or 3 to 4 with pair discussion and a re-poll | Why the wrong answers were chosen, unless you wrote the options from real mistakes | SERC, ConcepTests |
| Lettered cards, held up on a count | The same count, without people seeing each other's hands first | About 1 | Anything, if people can see the cards around them. Hold on a count of three | SERC, ConcepTests |
| Show me: everybody holds up their work | The performance itself, counted against a named feature | Under 1 | Whether they could do it again without the demonstration in front of them | Checks for understanding: finding out whether it landed |
| Do it on three: everybody performs the movement at once | The hands rather than the result | Under 1 | Anything about a long task; it works for one short movement | Checks for understanding: finding out whether it landed |
| Point at it | Whether people can locate the thing on a page or a screen | Under 1 in a room; longer on a call | Whether they know what it means | Checks for understanding: finding out whether it landed |
| Minute Paper | What people think they learned, and what question remains unanswered | 1 to 2 | What they can do. It measures their account of the session | University of Connecticut, 50 CATs |
| Muddiest Point | The thing nobody would raise a hand about | About 1.5 | Whether the clear parts landed. Described as less suited to sessions emphasizing integration and synthesis | University of Connecticut, 50 CATs |
| Background Knowledge Probe | What the room can already do, before you teach | 2 to 5, before or at the start | Anything, if you do not read it before the session starts | University of Connecticut, 50 CATs |
| Everybody types at once, on a count | A count on a call, without the first answer anchoring the rest | 1 to 2 | Anything, if people answer as they go. Say "hold it until I say go" | Checks for understanding: finding out whether it landed |
| Platform poll | A clean count with a record of it | About 1, including finding the button | Reasoning. It gives you the answer and not the thinking | Checks for understanding: finding out whether it landed |
| "Any questions?" | Which confident people have a question | Variable, and often long | Anything from silence. It is not a check | Checks for understanding: finding out whether it landed |
| End-of-session feedback form | Reaction: strongly connected to motivation, moderately to self-efficacy | 2 to 3 | Learning. Modestly related to immediate knowledge, unrelated to delayed knowledge, link to skill unknown | QIC-WD, Trainee Reactions |
Reading a count
The published band comes from the ConcepTest protocol: the optimal range of correct first responses is 35 to 70 percent. Below 35, students do not understand the topic well enough to discuss it, or the question is unclear or too hard. Above 70, the question may have been too easy, and questions that consistently draw 90 percent or higher are described as a waste of class time. The same page says the percentages are guidelines rather than requirements and that they shift with the group.
| Group | 35 percent is | 70 percent is |
|---|---|---|
| 6 people | 2 | 4 |
| 8 people | 3 | 6 |
| 10 people | 4 | 7 |
| 12 people | 4 | 8 |
| 20 people | 7 | 14 |
| 24 people | 8 | 17 |
| 30 people | 11 | 21 |
With a group this small, a single person moves the percentage a long way. Treat the band as a prompt to act rather than as a measurement, and write your three responses in the checks sheet of your session plan before the day.