Productive Failure

Share / assign

Why it works

Productive failure (a designed approach from Manu Kapur's research) reverses the usual order: instead of teaching a concept or method first and then having students practice, students first attempt to solve a novel, challenging problem on their own, generating and exploring their own approaches, often without fully succeeding, before the teacher provides instruction. Research shows this can lead to deeper conceptual understanding and transfer than instruction-first, because the struggle activates prior knowledge, reveals the limits of students' current thinking, highlights what matters, and prepares them to learn deeply from the subsequent instruction (they now understand why the taught method works and the problem it solves). The key is that it is designed, a carefully chosen problem, genuine student exploration, and then clear, consolidating instruction that connects to what students attempted. Failure here is productive precisely because it precedes and primes real learning.

The research: Research on productive failure (Kapur).

The run-of-show

Choose your slot. The agenda, timings, and length update to match.

The core activity: design productive failure

Teachers leave with a struggle-first, then-consolidate lesson design.

Choose a challenging, novel problem students cannot yet fully solve.
Have them genuinely explore and attempt it first (generating approaches, often not fully succeeding).
Frame the struggle as productive, not failure to be graded.
Then provide clear instruction that consolidates and connects to what they tried.

Struggle first, then teachDesigned productive failure, attempting a challenging problem before instruction, primes deeper learning. Let students explore and struggle, then teach in a way that connects to and consolidates their attempts.

Facilitator notes

Choose a challenging novel problem, and have students explore first.
Frame struggle as productive.
Follow with consolidating instruction.

Unstructured failure, or no follow-up instruction, isn't productiveProductive failure is designed: a chosen problem, genuine exploration, then consolidating instruction. Without the design and the follow-up teaching, struggle is just frustration.

Adapt it

Elementary: explore a problem first, then teach.
Secondary: novel problem, exploration, consolidating instruction.
All settings: struggle first by design, then consolidating instruction.

Participant handout

One page for every teacher. Print it, or save it as a PDF.

K12 Academics · Professional Learning

Productive Failure: struggle, then consolidate

By design: a challenging problem explored first, framed as productive, then clear consolidating instruction.

The challenging, novel problem students explore first:
How students genuinely explore and attempt it:
How I frame the struggle as productive:
The clear instruction that consolidates and connects to their attempts:
A lesson to redesign as productive failure:

Make it stick

Struggle, then consolidate:

Design productive failure.
Consolidate afterward.
Bring a productive-failure lesson to the next PLC.

Common questions

Why would I let students fail before teaching them?

Because designed productive failure, attempting a challenging problem before instruction, can deepen understanding and transfer: the struggle activates prior knowledge, reveals the limits of their thinking, and primes them to learn deeply from the instruction that follows.

Isn't failure discouraging?

Not when it is framed and designed as productive exploration before instruction, not a graded test. Students generate approaches, then learn why the taught method works. The struggle is the point, and instruction follows.

How do I design it?

Choose a challenging, novel problem; have students genuinely explore and attempt it (often without full success); then provide clear, consolidating instruction that connects to what they tried. Design, exploration, then instruction.