Over the years, we have launched Project-Based Learning experiences in many different classrooms, grade levels, and content areas. One thing we have learned is that there is no single “right” way to launch a project.
The ideas we share here are strategies and techniques we have explored, adapted, and successfully used in our own work with teachers and students. We don't view them as a checklist or a prescribed formula. Instead, we think of them as a menu of possibilities.
Some projects begin with a mystery. Others begin with a story, an artifact, a community partner, or a real problem that needs attention. We mix, adapt, combine, and modify these approaches depending on the students, the context, and the purpose of the project.
What we are ultimately trying to accomplish on Day 1 is simple:
Hook curiosity. Create purpose. Invite students into the story.
When we launch a project, our first instinct isn't to begin by explaining everything students are going to learn. We want students to become invested in a meaningful problem and begin wondering what they will need to know to do something about it.
By the end of Day 1, we hope students can answer five questions:
What problem are we solving?
Why does it matter?
Who needs our help?
What will we eventually create?
Why am I excited to learn more?
Notice what isn't on that list: standards.
That doesn't mean the standards aren't important. They are essential to the design of the project and the learning that follows. But in our experience, students don't necessarily become invested because we tell them which standard they are learning.
We have found it more powerful to first give students a reason to need the learning.
We've also come to see the project launch as an early opportunity to begin developing Portrait of a Graduate competencies.
When students examine clues, make predictions, and begin asking questions, they are practicing critical thinking. When they imagine possibilities and generate ideas, they are beginning to act as creative innovators. When they share their thinking, listen to classmates, and discuss different interpretations, they are practicing effective communication.
Students can also begin to become more reflective and future focused as they consider what they currently understand and what they still need to learn. And when a challenge connects to a community, environmental, cultural, or societal need, students begin considering their role as global citizens.
We don't expect students to develop these competencies simply because we put them into a project. Day 1 creates the opportunity to begin practicing them intentionally.
As we've refined our approach, we have found ourselves returning to five basic elements. They don't always happen in exactly the same order, and they certainly don't need to take the same amount of time.
We use them more as a planning framework:
Create curiosity → Introduce the mission → Reveal the audience → Reveal the product → Build emotional investment.
Whenever possible, we try not to begin with:
“Today we're going to learn about…”
Instead, we introduce a little uncertainty.
We might place a mysterious package in the room, show students an unusual photograph, bring in a broken object, play a short video message, display a newspaper headline, introduce an artifact, or have an unexpected guest appear.
Sometimes it can be incredibly simple.
The goal isn't to put on a show. The hook has to serve the learning. We are simply trying to create a moment when students look at one another and think:
“Wait…what's going on?”
Once we hear students asking questions without being prompted to ask them, we know we have something to work with.
Once we've created some curiosity, we begin revealing the problem.
We've found that the language we use here matters.
Rather than announcing, “We're starting a project,” we might tell students:
“We've been asked to help.”
Who needs their help depends entirely on the project. In projects we've developed, students have been asked to think and work as scientists, engineers, historians, environmental investigators, designers, consultants, and problem solvers.
Sometimes a hospital needs something designed. Sometimes a community organization has a problem. Sometimes scientists or engineers need students to investigate something.
This shift may seem small, but we've seen it change how students perceive the work.
They aren't just being given an assignment.
They are being invited to contribute.
One of the most important lessons we've learned from our PBL work is the power of an authentic audience.
When possible, we want students to know who is going to see, use, hear, experience, or benefit from their work.
We've designed projects around audiences such as:
community organizations
hospitals
museums
businesses and industry partners
engineers and other professionals
families and community members
younger students
environmental organizations
We often frame this with one simple question:
“Who benefits if we do this well?”
That question begins moving students away from “What does my teacher want me to do?” toward “Who are we creating this for, and what do they need from us?”
We also want students to have some sense of where the project is headed.
Over the years, we've had students work toward museum exhibits, children's books, prototypes, websites, public presentations, engineering solutions, documentaries, podcasts, community events, and other public products.
We don't necessarily give students every requirement or rubric on Day 1. Too much information can actually work against the curiosity we've just created.
Instead, we want them to understand something much simpler:
“Everything we're about to learn is eventually going to help us create this.”
The product gives the learning a destination.
Finally, before we move deeply into content, we want students thinking about why the problem matters.
We might ask:
Who could this help?
Why is this problem worth solving?
What could happen if nobody addresses it?
Have you experienced anything like this?
Why might someone be asking students to help?
We've found that this part can be easy to overlook. We can create an exciting hook and an impressive final product, but neither automatically makes the work meaningful.
Curiosity gets students through the door. Purpose gives them a reason to stay.
We've experimented with many ways to launch projects, and some of the simplest have been among the most effective. Which one we choose depends on the age of the students, the content, and the story surrounding the project.
Some approaches we've used or explored include:
Mystery Box: Students examine a collection of clues and try to determine what they mean.
Mission Envelope: Students receive confidential instructions or a mission briefing.
Emergency Broadcast: A video, announcement, or message interrupts the normal classroom routine.
Artifact Investigation: Students examine photographs, maps, fossils, tools, samples, letters, articles, or other authentic objects.
Guest Expert: A community partner or expert introduces the problem. Even a short prerecorded message can work.
Story First: A children's book or short story provides an entry point before we reveal its connection to a real problem.
Role Assignment: Students immediately take on an identity connected to the work.
That last strategy has become particularly important in our work.
Instead of telling students, “You are fourth graders studying energy,” we might tell them:
“You are Energy Efficiency Investigators.”
Students might become Earth Builders, Medical Design Engineers, museum curators, historians, scientists, consultants, or environmental investigators depending on the project.
We're not pretending they suddenly possess the expertise of professionals. We're giving them a meaningful role from which to begin developing and applying knowledge.
One of the easiest changes we've made to project launches doesn't require technology, special materials, or additional planning.
We've changed our language.
Instead of:
“We're going to learn about ecosystems.”
We might say:
“Your investigation begins today.”
Instead of:
“We're studying waves.”
We might say:
“A communications company has asked us to solve a problem involving invisible energy.”
The standards haven't changed. The science hasn't changed.
What has changed is the student's relationship to the learning.
We've found that language can help establish identity, and identity can help create ownership.
We also try not to let students leave the launch empty-handed. Day 1 should produce some initial evidence of their thinking that we can revisit as the project develops.
Depending on the project, that might include:
a Mission Notebook
a Wonder Wall
a Need-to-Know List
initial predictions
first team meeting notes
a team identity
investigation questions
a personal reflection
an Evidence Log
an initial design sketch
We don't necessarily use all of these. Usually, one or two purposeful artifacts are enough.
The important thing is that students have begun thinking, questioning, predicting, and documenting where they are at the beginning of the journey.
Of all the routines we've experimented with, several continue to show up in our projects because they help connect Day 1 to the learning that follows.
The Wonder Wall gives students a place to capture the questions generated by the launch. We can return to those questions throughout the project as students discover answers—and generate new questions.
The Need-to-Know Board is one of our favorites because it changes the conversation from “What is the teacher going to teach us?” to “What do we need to know if we're going to solve this problem?”
Team Identity can help students begin seeing themselves as a group with a shared purpose. Depending on the project, teams might establish a name, roles, logo, or mission.
The Evidence Board creates a visible record of learning. We can start it on Day 1 with very little evidence and watch it grow as students investigate, learn, test ideas, and revise their thinking.
We like to keep the final reflection simple.
Before students leave, we can ask just three questions:
What surprised you today?
What do you think is happening?
What do we need to learn before we can solve this?
That third question is the bridge.
If Day 1 has done its job, students should leave with more questions than answers.
They've encountered a challenge. They've begun to care about it. They've made predictions. They've identified things they don't yet understand.
And now the content has a purpose.
That's where we move into Day 2: Build Background Knowledge.