Flavell: students cannot deploy a strategy they have never been taught. Teach retrieval, spacing or self-explanation explicitly as named methods before expecting independent use.
Why it works
Flavell's category of metacognitive knowledge includes knowledge of strategies, and it's knowledge like any other: it has to be taught. Students left to discover study methods overwhelmingly arrive at rereading and highlighting, because those are the most obvious and the least effortful.
How to run it
- Name each strategy explicitly when you use it in class.
- Explain what it's, what it's for, and why it works.
- Practise it in lesson before expecting it in independent study.
- Keep a running reference of the strategies the class has been taught.
Where technology serves
A strategy reference sheet, built up over the year and kept accessible, means the repertoire is available at the point of revision.
Watch for: A single assembly on study skills isn't teaching the strategies. They need practising in the subject with the subject's content.
Techstrategy reference sheetInformed byFlavell#16
Winne: conditional knowledge, knowing which strategy suits which task, is what separates skilled learners. Teach not just the method but the cues that signal when it is the right one.
Beyond knowing a strategy, students need to know when it applies. That's conditional knowledge, and it's the harder half.
Why it works
Winne identifies conditional knowledge, knowing which approach suits which situation, as a key discriminator between skilled and unskilled learners. A student with five strategies and no sense of when to use each isn't much better off than a student with one. The cues that signal which method fits have to be taught explicitly.
How to run it
- Teach the cues alongside the strategy: use this when the task looks like this.
- Give sorting activities: here are six tasks, which method suits each?
- Discuss the near misses, where two methods could apply.
- Ask students to justify the match, not just make it.
Where technology serves
Worked cases matched to methods, kept as a reference, give students examples to reason from rather than rules to recall.
Watch for: Teaching the strategy thoroughly and the conditions not at all is the most common version of this gap, and it looks like successful teaching right up until transfer is required.
Techworked cases matched to methodsInformed byWinne#17
Zimmerman: support must be withdrawn for self-regulation to develop. Move from modelled to guided to independent use, removing prompts as students show they no longer need them.
Why it works
Zimmerman's model of developing self-regulation runs through observation, emulation, self-control and self-regulation. The support has to be withdrawn for the final stage to exist at all. Fading isn't a nicety at the end of a sequence; it's the mechanism by which regulation transfers from the teacher to the learner.
How to run it
- Model the strategy fully first, thinking aloud.
- Guide the next attempt with prompts.
- Reduce the prompts to a checklist, then a reminder, then nothing.
- Fade in response to evidence rather than to the calendar.
Where technology serves
Prompts embedded in a template can be removed version by version, which makes the fading concrete rather than a matter of your restraint.
Watch for: The scaffold that stays because removing it makes results dip is the scaffold most in need of removing. The dip is the point at which the learning starts.
Techprompts gradually removedInformed byZimmerman#18
Winne: learners refine an approach by checking whether it worked. Have students trial a study method, judge it against results, and keep only what the evidence supports.
Why it works
Winne's model of self-regulated learning is adaptive: the learner evaluates the effectiveness of an approach and revises it. Most students never do this, so ineffective methods persist for years because they were never tested. Running the test explicitly, once, changes revision behaviour more than being told what works.
How to run it
- Have students name the method they'll use for the next assessment.
- Log it before, not after.
- Compare method and outcome afterwards, honestly.
- Decide together what to keep and what to drop for next time.
Where technology serves
A method log kept alongside results makes the comparison possible. Without a record, students reconstruct what they did and reconstruct it flatteringly.
Watch for: One data point is not evidence. A poor result with a good method can have other causes, and abandoning the method would be the wrong lesson.
Techmethod log with outcomesInformed byWinne#19
Willingham: strategies do not float free of subjects. Teach each one inside the content it serves, so students learn to self-regulate this topic, not metacognition in the abstract.
Teach each strategy inside the content it serves rather than in a standalone session about learning.
Why it works
Willingham's consistent argument is that strategies don't float free of subject knowledge, and that transfer between domains is much weaker than we assume. A student who has learned to self-explain in science won't automatically do so in history. Teaching the strategy in each subject, with that subject's content, is the only reliable route.
How to run it
- Teach the strategy in your subject, with your content.
- Show what it looks like specifically here, since it will differ by subject.
- Do not assume transfer from another subject's teaching of the same strategy.
- Coordinate across subjects on language, not on delivery.
Where technology serves
Subject-specific strategy banks keep the examples grounded in the content students are actually working on.
Watch for: A whole-school metacognition programme delivered in tutor time, with no subject follow-through, is the reliable way to get very little from a good idea.
Techsubject-specific strategy banksInformed byWillingham#20