Tag: zone of proximal development

A student finishes the worked example, tries the next one alone, and stalls. You’re three metres away, marking book in hand. The moment asks a genuine question: do you step in, or fade the scaffold and wait ten more seconds?

Most of us know the gradual release of responsibility model well: I do, we do, you do. What it doesn’t tell you is when, inside that “you do” moment, to actually let go. That judgement call happens dozens of times a lesson. In practice, it’s rarely taught explicitly.

This is where Vygotsky’s zone of proximal development (ZPD) earns its keep. It isn’t another framework to memorise. By contrast, it’s the diagnostic tool. It tells you whether a student is ready to work without you, or still needs the scaffold.

GRR Sets the Stage, ZPD Tells You When to Move

The gradual release of responsibility model comes from Pearson and Gallagher’s 1983 research on reading comprehension instruction. They found that comprehension improved when teachers deliberately shifted cognitive responsibility from themselves to students across a sequence. In other words, that sequence — I do, we do, you do — is the structure.

Fading is what happens inside that structure. It’s the technique of reducing support in increments: fewer prompts, shorter sentence stems, more open questions. As a result, a student moves from needing you to not needing you in stages, not all at once. In other words, GRR tells you the phases exist; fading is how you move through them.

That’s where ZPD tells you when to fade the scaffold. The zone of proximal development is the gap between what a student can do alone. It’s also what they can do with support close by. For example, fade too early and you’ve asked them to work outside that zone, unsupported. Fade too late, and they stay inside it long after they were ready to leave. That has its own cost, too.

The Two Ways Calibration Goes Wrong

We’ve covered the most common GRR misfire before. It’s an “I do” phase so thorough that “you do” becomes copying, not struggle. Put simply, that’s fading too slowly. The scaffold stays up well past the point a student could carry their own weight. As a result, the task stops asking anything of them.

By contrast, the opposite failure gets less attention. Fade too fast, and you haven’t created independence — you’ve created guesswork. That happens when the worked example, sentence stem, or check-in disappears before “we do” has landed. As a result, what looks like “productive struggle” up front is often just confusion with better posture.

Even so, both are calibration errors. Neither is solved by scrapping GRR — both come down to knowing when to fade the scaffold, not whether to.

How to Fade the Scaffold, Move by Move

Fading rarely works as an all-or-nothing switch. In practice, it’s a series of small withdrawals, each testing whether a student can hold the next level of responsibility.

For example, a worked example becomes a partially worked example — the first two steps shown, the rest left blank. Beyond that, sentence stems shrink from full frames to a single connective word. At the same time, questions move from closed (“What’s the next step?”) to open (“What would you try next?”). Each version removes one layer of support while the task itself stays constant.

As a result, you’re never asking a student to jump from fully supported to fully independent in one move. You’re testing the edge of their ZPD in small enough steps. That way, you can pull back if the gap turns out to be wider than expected.

Planning the Fade, Not Just Reacting to It

In-the-moment judgement matters, but it’s easier to trust when it’s backed by planning. If you’ve already set up your lesson using our backward design approach, the same thinking applies to fading. For this reason, decide your checkpoints before the lesson starts, not during it.

First, mark two or three points before the lesson where you’ll deliberately step back and watch rather than help. For example, good checkpoints include after the first worked example, halfway through practice, or at a new question type. Second, at each checkpoint, look for the signals above rather than the clock. That way, the decision to fade isn’t a feeling you’re second-guessing mid-lesson — it’s a checkpoint you already built in.

This matters even more once lessons stop being single, standalone events. From there, planning shifts from one lesson to a sequence built around learner variability. When it does, the question of when to fade the scaffold travels with it too. Part 3 of this series answers that next.