Professional Learning  ›  Instructional Strategies  ›  Workshops  ›  Designing Worthwhile Tasks
a ready-to-run workshopDesigning Worthwhile Tasks
Instructional Strategies · Workshop

Designing Worthwhile Tasks (Workshop)

Everything you need to lead this with your staff or PLC: a minute-by-minute run-of-show, what to say, what to hand out, and how to make it stick. Pick the length that fits your slot.

Key takeaway

Students learn from what the task makes them think about, so the task is the single biggest determinant of the thinking that happens in a lesson, and designing tasks deliberately, so they demand the worthwhile cognitive work you actually want rather than low-level compliance or busywork, is one of the highest-leverage planning moves there is.

Format
PLC / team meeting
Length
45 minutes
Group size
Any (works 4-40)
Who can run it
Any teacher-leader
You will need
Slides (5)Printed handoutA task you assignA timer
Aligned to
Learning Forward: Rigorous ContentInTASC 8: Instructional StrategiesResearch on task design, cognitive demand, and learning
Share / assign

Why it works

There is a deceptively simple principle at the heart of planning: students learn from what they think about, and what they think about is determined largely by the task you give them to do. The task, the actual thing students are asked to work on, is therefore the single biggest lever on the thinking, and hence the learning, that happens in a lesson, more than the objective on the board or the explanation at the front, because it is the task that occupies students' minds for the bulk of class time. This means task design is one of the highest-leverage and most underexamined parts of planning: a lesson with an admirable objective can still produce little real learning if the task students actually do demands only low-level work, while a well-designed task reliably produces the worthwhile thinking the objective names. The common failure is a mismatch between the thinking a teacher wants and the thinking the task actually requires. A teacher who wants students to analyze may assign a task that really only requires locating and copying; one who wants deep understanding may assign a worksheet that can be completed by pattern-matching without thought; one who wants problem-solving may give exercises that only rehearse a procedure. In each case the task does not demand the intended thinking, so the intended learning does not happen regardless of the objective, and much class time goes to busywork, tasks that keep students occupied and produce completed work but little genuine cognitive engagement. Designing worthwhile tasks means engineering the task so that doing it requires the thinking you actually want. Several principles guide it. Design backward from the thinking: decide what cognitive work you want students to do, analyze, reason, construct, evaluate, apply, and design a task that cannot be completed without doing it, so the thinking is required, not optional. Raise the cognitive demand appropriately: ensure the task demands genuine thought rather than recall or copying, while keeping it achievable, aiming for the productive-struggle zone where the work is hard but doable. Watch for the ways tasks let students avoid thinking: tasks can often be completed through pattern-matching, copying, guessing, or following a procedure mechanically, so design to close those escape routes and make the intended thinking the only path through. Make the task worth doing: a task that demands real thinking about something that matters, ideally authentic or meaningful, engages students far more than busywork, so worthwhileness is about both cognitive demand and genuine purpose. And align the task to the goal: the task is where the objective lives or dies, so the surest way to teach toward a goal is to design the task that embodies it. A few practical points: this connects closely to cognitive demand frameworks, productive struggle, and backward design; a quick test of any task is to ask what thinking a student must do to complete it and whether that matches what you want; and even small redesigns, changing a question from recall to analysis, removing the scaffold that lets students avoid the thinking, can transform a task's value. A caution: worthwhile does not mean maximally hard or elaborate; it means the task demands the right thinking at an achievable level, and a simple task that requires genuine thought beats an elaborate one that does not. The workshop helps teachers design tasks deliberately so that doing them requires the worthwhile thinking the lesson is meant to produce, rather than low-level compliance or busywork.

The research: Research on task design, cognitive demand, and the relationship between tasks and learning.

The run-of-show

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

    The core activity: design tasks that require the intended thinking

    The heart of the session is designing the tasks students do so that completing them requires the worthwhile thinking the lesson is meant to produce.

    Students learn from what the task makes them think aboutThe task is the single biggest determinant of the thinking in a lesson, so an admirable objective produces little if the task demands only low-level work. Designing tasks so completing them requires the thinking you want is among the highest-leverage planning moves.

    Facilitator notes

    Ask what thinking the task actually requiresA quick test of any task is to ask what a student must think about to complete it, and whether that matches what you want. If the task can be finished without the intended thinking, it will be, so redesign it to require that thinking.

    Adapt it

    Participant handout

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

    K12 Academics · Professional Learning

    Designing Worthwhile Tasks: the task is the thinking

    Engineer the thinking by designing the task: decide the cognitive work you want, design a task that cannot be completed without it, close the escape routes, and make it worth doing.

    1. A task I assign and the thinking it actually requires:
    2. The thinking I actually want students to do:
    3. How I redesign the task so that thinking is required, not optional:
    4. The escape routes (copying, pattern-matching) I will close:
    5. How I make the task genuinely worth doing:

    Make it stick

    The task determines the thinking, so design it deliberately. Close by setting the follow-up:

    Common questions

    Isn't the objective, not the task, what determines what students learn?
    The objective states your intention, but the task determines what students actually think about, and since students learn from what they think about, the task is what actually drives the learning, which is why a good objective with a weak task produces little. The objective on the board is a statement of what you want students to learn, and it matters for your planning and clarity, but it does not by itself cause any thinking; students do not learn from the objective, they learn from doing the task, which is what occupies their minds for the bulk of the lesson. So if the objective says analyze the causes but the task only requires students to locate and copy the causes from the text, students will spend the lesson locating and copying, not analyzing, and they will learn to locate and copy, not to analyze, regardless of what the objective said. This objective-task mismatch is one of the most common reasons lessons with admirable goals produce disappointing learning: the goal was fine, but the task did not require the thinking the goal named, so the thinking did not happen. The practical upshot is that the surest way to teach toward an objective is to design the task that embodies it, so that doing the task necessarily involves the thinking the objective describes. The objective and the task should align, with the objective naming the intended thinking and the task requiring it, but when you have to bet on which determines learning, bet on the task, because that is what students actually do, and designing it well is therefore where much of the real planning leverage lies.
    How can I tell if a task actually requires the thinking I want?
    You apply a simple but powerful test: ask what a student must actually think about to complete the task, and whether that matches the thinking you intend, paying special attention to whether the task can be finished without the intended thinking. Many tasks that appear to target higher-order thinking can in fact be completed through lower-level shortcuts, and spotting those shortcuts is the key to the test. Walk through the task as a student would, looking for the escape routes: can it be completed by copying from the text or a model, by pattern-matching to a worked example without understanding, by guessing, by following a memorized procedure mechanically, or by filling in blanks whose answers are findable without the target reasoning? If any of those routes lets a student finish the task without doing the thinking you want, then the task does not require that thinking, and students, reasonably economizing effort, will take the shortcut, so the intended learning will not happen. If, on the other hand, the only way through the task is to engage in the intended cognitive work, analyzing, reasoning, constructing, evaluating, then the task genuinely requires it. This is why the diagnostic question is not does the task relate to the thinking I want but can the task be completed without that thinking, and closing the escape routes so the answer is no is the heart of good task design. You can also tell by looking at what students actually produce and do: if their work shows copying or mechanical completion rather than the reasoning you wanted, the task was letting them avoid the thinking. So the test is concrete: trace how the task can actually be completed, find the ways it permits avoiding the intended thinking, and judge, and redesign, accordingly.
    Does designing worthwhile tasks mean every task has to be elaborate or hard?
    No, worthwhile means the task requires the right thinking at an achievable level, which is quite different from elaborate or maximally difficult, and a simple task that demands genuine thought is better than an elaborate one that does not. The goal of task design is to engineer the intended cognitive work, not to maximize complexity or difficulty, and conflating the two leads to over-engineered tasks that are busy and complicated without necessarily requiring better thinking, or to tasks pitched so hard that students cannot engage productively. A worthwhile task is one whose completion requires the specific thinking you want, analysis, reasoning, construction, at a demand that is challenging but achievable, the productive-struggle zone where the work is hard enough to require real thought but doable with effort. That can be accomplished by quite simple tasks: a single well-designed question that genuinely requires analysis is more worthwhile than a multi-part elaborate worksheet that only requires copying, and a short problem that demands real reasoning beats a long one that rehearses a procedure. In fact, elaborateness can work against worthwhileness, because a complicated task may bury the intended thinking under logistics and busy sub-steps, or may offer more escape routes for avoiding the real cognitive work. So the design aim is precision, not elaboration: identify the thinking you want and craft the task, however simple, so that doing it requires that thinking at a level students can reach. Sometimes the most powerful redesign is a small change, turning a recall question into an analysis question, removing a scaffold that let students avoid the thinking, which raises the task's worthwhileness without making it elaborate at all. Worthwhile is about the thinking required and its achievability, not about length, complexity, or difficulty for its own sake.

    Go deeper

    Build it into a bigger day