All field notes
PlanningJuly 15, 2026·6 min read

Designing a PBL Unit With a Driving Question That Actually Works

Most PBL units fail at the driving question, not the project. Here's how to tell a real one from a survey question wearing a PBL costume.

By Mr. Okafor, HS science
Teacher sketching a project-based learning unit map on paper at a cream desk, sage sticky notes, natural light

I've built PBL units that flopped and PBL units that genuinely worked, and the difference almost never came down to the final project itself. It came down to whether the driving question could actually be argued about, or whether it was a survey question wearing a project-based costume.

The test for a real driving question

A driving question fails the moment there's only one reasonable answer, or the answer is a Google search away. "What is the water cycle?" isn't a driving question, it's a definition. "Should our town invest in a new stormwater system, and how would we design one that actually works for our watershed?" is, because reasonable people, with the same facts, could land in different places, and answering it requires doing something with what you know, not just recalling it.

What separates a real one from an imposter

  • It's arguable, not answerable. If two groups doing the same research could reasonably reach different conclusions, that's a sign it's real. If everyone converges on the same answer, it was probably just a research question.
  • It's grounded in something outside the classroom. A real audience, a real constraint, a real dataset, even a fictional-but-specific scenario ("You're advising the city council on...") beats an abstract prompt every time.
  • It requires the content, not just general reasoning. The question should be unanswerable without the actual unit content. If a student could answer it with zero background knowledge, the project isn't really assessing what you taught.
  • It survives being said out loud to a 14-year-old. If it needs three sentences of academic throat-clearing before it makes sense, it's not ready. The best ones are short.

From standard to driving question, a worked example

Standard: analyze how human activity affects local ecosystems.

Bad version: "How do humans affect ecosystems?" (a definition question, not a project)

Better version: "Our school wants to redesign the courtyard. Should we prioritize a pollinator garden, a rain garden, or a native-tree grove, and what tradeoffs come with each?"

The second version can't be answered with a definition. It needs research, forces a real tradeoff, and ends in a genuine recommendation, which is the actual shape of a PBL unit.

Building the unit backward from the question

1. Write the driving question first, and stress-test it against the four checks above before building anything else.
2. Identify the milestone checkpoints, research, a draft recommendation, peer feedback, that keep momentum going instead of one big deadline at the end.
3. Decide what the final product actually is (presentation, proposal, prototype, campaign) and make sure it directly answers the driving question, not a tangential version of it.
4. Build in a real audience if you can, even a modest one, a parent panel, another class, the actual principal. Audience is what makes the stakes feel real to a 14-year-old.

Where a first draft helps

Turning a standard into a driving question that passes all four checks, then mapping out milestones and a rubric that actually assesses the reasoning instead of just the poster, is a lot of structural work before you've taught a single day of it. Our [PBL unit builder](/pbl-unit) drafts that full structure, driving question options, milestones, and an assessment rubric, from your standard and topic, so you're refining a strong first draft instead of staring at a blank unit template.

Keep reading