The Art of Backward Design: A Comprehensive Guide for Educators

Ask most first-time course creators how they build a course, and the answer is usually some version of: write the content, then figure out how to test it. Backward design, developed by Grant Wiggins and Jay McTighe under the name Understanding by Design, reverses that order entirely, and once you've worked with it, it's hard to go back to designing any other way. The method starts by defining exactly what evidence would prove a learner has achieved mastery, and only then works backward to decide what content and activities would actually produce that evidence.

Want expert help putting this into practice? Course Writer can guide you through it.

Stage one: identify the desired results

The starting point isn't a list of topics to cover — it's a clear statement of what learners should understand and be able to do by the end, expressed specifically enough that you could recognise it when you saw it. Wiggins and McTighe draw a sharp distinction between "understanding" and mere factual recall: a learner who can recite a definition hasn't necessarily understood a concept well enough to apply it in an unfamiliar situation, and backward design pushes you to be explicit about which of those two things you're actually after.

This is harder than it sounds, because most subject-matter experts default to listing topics rather than outcomes. The useful discipline here is to keep asking "what would someone be able to do with this that they couldn't do before" until the answer stops being a topic and starts being a capability. "Understands supply and demand" is a topic. "Can predict the direction of a price change given a described shift in either supply or demand, and explain why" is a desired result.

Stage two: determine acceptable evidence

Related: Coursewriter - Expert Advice for Effective Course Design.

This is the stage that gives backward design its name, and it's the one course creators skip most often under time pressure. Before writing a single lesson, you decide what assessment would actually demonstrate the outcome from stage one — and critically, this needs to happen before you design the content, not after. Designing the assessment first forces a kind of honesty that's easy to avoid otherwise: if you can't describe what evidence would prove mastery, you probably haven't actually defined the outcome clearly enough in stage one, and you're sent back to fix it.

• Performance tasks: authentic, applied demonstrations — a case analysis, a built artefact, a simulation.
• Other evidence: quizzes, observations, self-assessments, short-answer checks that support but don't replace performance evidence.
• A rubric or clear success criteria defined at this stage, not improvised when grading begins.

This stage also protects against a common failure of assessment design: writing quiz questions that test recall of facts mentioned in a lecture, when the actual desired result was an applied skill. If the outcome is "can diagnose a faulty argument," a multiple-choice question about the definition of a logical fallacy is weak evidence, no matter how neatly it fits into an LMS quiz template. Defining evidence before content keeps this mismatch from creeping in unnoticed.

Stage three: plan the learning experiences

Only in the third stage do you actually decide what to teach and how — the readings, activities, explanations, discussions, and practice opportunities. Because stages one and two are already fixed, this stage becomes a much more constrained and efficient design problem than starting from scratch: every piece of content earns its place by asking "does this move a learner closer to producing the evidence defined in stage two," rather than "does this feel like something that belongs in a course on this topic."

This constraint is where backward design saves the most time in practice. Course creators who start with content routinely end up with material that's interesting but doesn't actually build toward what's being assessed — a tangent the instructor finds fascinating, a case study that doesn't map to any evaluated skill. Backward design's third stage has a built-in filter against exactly this kind of drift.

The WHERETO framework as a practical checklist

See also: Coursewriter Best Practices for Effective Learning Design.

Wiggins and McTighe supplement the three stages with a checklist for stage-three planning, often abbreviated WHERETO: ensure learners know Where the course is headed and Why; Hook them early; provide opportunities to Explore and Equip them with needed skills; build in Rethink and Revise opportunities; let learners Evaluate their own progress; Tailor the design to different learners' needs; and Organise the sequence for maximum engagement and effectiveness. It's not a rigid checklist to satisfy item by item, but a genuinely useful diagnostic when a lesson plan feels flat — checking it against WHERETO often reveals exactly which element is missing.

Where backward design earns its reputation

The method's real value shows up in courses that used to suffer from a common and specific problem: content and assessment that quietly drifted apart over multiple revisions, until what was being taught and what was being tested barely resembled each other. Backward design, applied properly, makes that drift structurally difficult, because the assessment was locked in before the content was ever written, and every content decision has to justify itself against it.

Applying all three stages rigorously across a full course — and keeping content, activities, and assessments consistently aligned to the same defined outcomes across every module — is exactly the kind of structural consistency that's easy to lose under deadline pressure. Course Writer builds courses with this alignment built in by default: define the outcomes you want, and it generates a complete curriculum, sequenced lessons, and assessments in under thirty minutes, ready to export into Canvas, Blackboard, or Moodle, with content and evidence already pointed at the same target.

A discipline worth the extra planning time

Backward design asks for more upfront thinking than most course creators are used to giving before writing a single lesson, and that's precisely its value. The extra time spent defining outcomes and evidence before content pays for itself many times over in a course that stays coherent, where every activity has a clear reason for existing and every assessment genuinely measures what the course claims to teach.