2. Entry event
Needs Whole class · Any grade · One class period · A problem, a guest, a video, fieldwork, or a simulation
You open the project with an event that captures heads and hearts, an interesting problem for the head and a situation students can feel for, and connect it to the community and to the final product. Set the stage first by telling the class a big project is starting, and if one event won’t carry it, build several activities that lead to a call to action; PBLWorks’s list includes simulations, fieldwork, guest speakers, and a puzzling problem (Kaechele, 2020). That gives the project its stakes on day one. As written, though, an event can thrill a room without asking anything of anyone.
The fix
- Before anyone leaves, every student writes one need-to-know question.
- Each card carries the student’s name, and you collect them at the door.
The checklist has the need-to-know cards.
3. The driving question
Needs You, then the class · Any grade · An hour, then 10 minutes · A draft
You draft the question and check it against three criteria: engaging; open-ended, so it can’t simply be Googled; and aligned with the learning goals. Then you revise the usual first-draft problems (textbook language, one right answer, a slant), choose the type, either a debatable issue (“Could there be life on other planets?”) or a problem to solve (“How can we help protect an endangered species in our area?”), which is easier for younger students, and get feedback or co-write it with the class (Larmer, 2018). A good driving question gives the project stakes and makes students use the lesson. As written, though, nothing ties a part of the answer to each student.
The fix
- Write a question that splits into sub-questions.
- Each team answers the driving question, and each student owns one sub-question, with their name on it.
Needs Groups of three to five · Grades 2 to 8 · 30 to 45 minutes · A Question Focus and chart paper
You design a Question Focus, a prompt that isn’t a question, and introduce the four rules: ask as many as you can; don’t stop to discuss, judge, or answer; write each down as stated; turn statements into questions. Then you present the focus, barely explained, and students produce questions, improve them by marking each closed or open and flipping some, prioritize (three, in the founders’ example), discuss next steps, and reflect; the fullest version is on the student engagement guide. Improving the questions puts the lesson to work, and the reflection gives the class a look back. As written, though, the three belong to the group, and the focus can sit apart from the project.
The fix
- Draw the focus from the project, like the creek after a storm.
- Put a name on each of the three priority questions.
5. The need-to-know list and the project wall
Needs Whole class · Any grade · 15 minutes, then a few a week · A wall, sticky notes in two colors
You launch with the driving question, students list what they need to know, and the list is sorted into product, process, and content questions and posted on the project wall with the calendar, the standards, and the rubrics. You answer it through mini-lessons, workshops, and research, mark the answered ones, and return to it as the project shifts; when a team stalls, smaller questions go up in a second color (Brengard, 2018; Stevenson, 2016; Ray, 2019). The list becomes your lesson plan, so you lead the thinking. As written, though, Brengard suggests initials only as an option, so a question can belong to no one.
The fix
- Make initials the rule: each question carries the name of the student who’ll answer it.
- When it’s answered, the answer goes in the log.
The checklist has the three piles and the log.
6. The team contract
Needs Teams of four · Grades 3 to 8 · A period, then 20 minutes · Index cards, a talking piece
In a talking circle, each student answers “What makes for successful collaboration?” in a word or phrase, in turn, and the circle names team challenges, with groups acting one out badly, then well. Then each team picks three words, writes why each matters and how it will live up to them, writes how it should and shouldn’t react to four conflict scenarios, and everyone signs; the contract returns for reflections, conferences, and conflicts (Derian, 2019). It holds every student to how the team works, and it gives the team something to look back on. As written, though, it says nothing about the work itself.
The fix
- Add one line per student naming the part of the product they own.
- Check those lines at every checkpoint.
The checklist has the ownership line.
7. Gallery walk for critique
Needs Groups of three to four · Grades 3 to 8 · 20 to 30 minutes · Posted work, sticky notes, a timer
Teams post drafts (writing, blueprints, prototypes, sketches) on walls or tables, and reviewers get one focus and the criteria to judge it by. They walk in silence and leave notes as “I like...” statements or “I wonder...” questions, teams read the notes and plan their next steps, and for a second round you can invite parents, experts, or community members; the fullest version is on the cooperative learning guide. PBLWorks borrows Ron Berger’s rule that feedback be “kind, specific, and helpful” (Larmer and Allen, 2013). As written, though, the notes carry no names, and nobody has to act on one.
The fix
- Put a name on every note.
- During revision, each team member answers one note in writing.
See the gallery walk rebuilt for 7th grade →
8. Reflection at every checkpoint
Needs Students, teams, or the whole class · Any grade · A few minutes at each checkpoint · Journals or a discussion protocol
You anticipate the need-to-know questions from the project’s key knowledge, plan what students will reflect on, and tie a method to each checkpoint: journals or learning logs, whole-class discussions, surveys, focus groups, or fishbowl discussions. Think-pair-share walks students through a prompt (alone, with a partner, then the class), and at the end students reflect on the whole project with a self-reflection handout (Field, 2017). You lead it, and every checkpoint gets a look back. As written, though, a prompt can be answered without using the content.
The fix
- Write one content-bound prompt per checkpoint, like “Which source changed our plan for the creek, and what did it show?”
- Run it as think-pair-share with the paraphrase rule, so each partner says the other’s answer back before the pair shares.
See think-pair-share rebuilt →
9. The public product
Needs Teams of four · Any grade · One to two periods at the end, plus expert visits · An audience beyond class and family
You bring outside experts in during the project as advisors, not only at the end, and students contact the experts and organizations themselves. You prepare each guest (the project, their role, and how to question students), students anticipate the experts’ questions and prepare answers, and then they present to people beyond you, their classmates, and their parents; a few experts giving real critique can beat a big showcase. PBLWorks says a public product “ups the stakes” (Larmer, 2015). As written, though, the team presents together, and its strongest speaker can carry it.
The fix
- Have each student present the part they own.
- Give each student one expert question to take alone.
The checklist has a note for the guest.