One of the biggest questions I hear from math teachers about project-based learning is a really important one:

“But when are students actually learning the math?”

It’s a fair question.

A project can be engaging. Students can collaborate, research, create, present, and make decisions. They can spend several days deeply invested in a problem. But none of those things automatically mean students are developing deep mathematical understanding.

When I design a math project, the mathematics has to come first.

The project is the context that gives students a reason to use the mathematics. My job is to intentionally design the experience so students are learning, practicing, applying, and demonstrating that mathematics throughout the project.

And one of the most important tools I use to make that happen is milestones and milestone markers.

The Project Is Not the Rigor

Sometimes we look at a project and assume that because students are doing a lot, they must be learning a lot. They’re researching, calculating, collaborating, creating, and presenting.

Yes, they are busy, but the better question is:

Where is the mathematical thinking?

A project with twenty calculations isn’t necessarily rigorous. Students could be repeating the same procedure over and over without understanding why they’re doing it. They could divide the work among group members and only understand one small piece of the mathematics. They could spend hours creating an impressive final product without being able to explain the mathematical decisions underneath it.

That’s not the kind of PBL I’m interested in.

Rigor isn’t about how much students do. It’s about the depth of the thinking they’re doing.

That applies to project-based learning just as much as it does to any other instructional approach.

Start With the Mathematics

When I design a math project, I don’t start with:

“What would be a fun project?”

I start with:

What mathematics do I need students to learn?

• What concepts do they need to understand?
• What relationships do I want them to notice?
• What mathematical decisions should they be able to make?
• What should they be able to explain by the end?

Once I know that, I can start thinking about the context, problem, product, and experience that will give students a reason to use that mathematics.

The distinction matters, because the mathematics should drive the project rather than being added afterward to make an interesting project qualify as a math project.

If I removed the mathematics, students should no longer be able to solve the problem in the same way.

That’s when I know the math is doing real work.

Don’t Backfill the Standards

This is an easy trap to fall into.

You find a project idea that sounds fantastic, and you can already imagine students getting excited about it. Then you open your standards and start asking:

“What math could I attach to this?”

Maybe there could be some percentages… or we could add a graph… or maybe we could calculate a budget…

Suddenly, we’re attaching mathematics to a project instead of designing the project around the mathematics.

That’s backwards.

I don’t want to sprinkle math on top of a fun activity.

I want students to need the mathematics in order to make progress.

That changes the role of the math completely.

Build a Mathematical Backbone

Once I know what mathematics matters, I think about the mathematical journey students need to take.

Students aren’t going to learn everything on the first day and then independently apply it perfectly for the rest of the project. PBL doesn’t mean handing students a project and disappearing until presentation day.

I’m still teaching.
Students are still learning.

There may be direct instruction, practice, inquiry, small-group support, discussion, or a mini-lesson when I notice a common misconception.

The difference is that the project gives those pieces a purpose. Students aren’t learning surface area simply because the next section of the curriculum says it’s time for surface area. They might be learning it because they need it to solve the problem in front of them. That purpose can make the mathematics feel very different.

This Is Where Milestones Matter

A strong project isn’t one giant assignment students receive on Monday and turn in two weeks later.

It’s broken into intentional pieces.
Those pieces are milestones.

A milestone represents an important stage in the learning and the project. In a math classroom, I want those stages connected directly to the mathematical understanding students need in order to keep moving.

Maybe students need to create and interpret a mathematical model before they can make a recommendation.

They might need to compare multiple options mathematically before choosing a solution.

Maybe they need to analyze whether their solution satisfies the constraints before they can move on to the final product.

Now the mathematics isn’t something students complete at the end.
The mathematics is what moves the project forward.

A Milestone Isn’t Just a Deadline

This distinction is really important.

A deadline says:

• “Research due Tuesday.”
• “Poster due Thursday.”
• “Presentation Friday.”

Those can be useful, but they’re not necessarily mathematical milestones.

A mathematical milestone asks:
What does a student need to understand at this point in the project to move forward successfully?

That’s where I want to place my checkpoints.

Instead of waiting until the final product to discover that students misunderstood the mathematics, I create intentional places to stop and look.

The project structure is now helping protect the learning.

Then We Need Milestone Markers

A milestone tells me where I want students to be.
A milestone marker gives me evidence of whether they’re actually there.

This might be a mathematical model students submit, it could be a few targeted questions, it might be that students explain why they chose a particular representation, or perhaps they complete a calculation and interpret what the result means in the context of the problem. It could even be a short teacher conference.

The marker doesn’t need to become another giant assessment.
I simply need enough evidence to answer:
Do they understand this mathematics well enough to move forward?

If they do, great.

If they don’t, I have an opportunity to respond before the misunderstanding gets buried underneath another three days of project work.

Milestones Change the Teacher’s Role

This is one of my favorite things about using PBL.

I’m not standing on the sidelines watching students “do a project.”

I’m constantly gathering information.

• What are students understanding?
• Where are they getting stuck?
• Which misconceptions are showing up?
• Who needs more practice?
• Do we need a whole-class conversation?
• Would a small group benefit from another example?
• Are students ready for the next step?

The project can actually give me more information about student understanding because I’m watching students decide when and how to use mathematics, not simply reproduce a procedure I’ve already demonstrated.

That’s valuable evidence.

Let’s Make It Concrete

Take my Wasted Space Geometry project.

Students start with an existing package, such as a snack box, carton, or can. They analyze the amount of space inside the package compared with the amount of material used to create it. Then they redesign the packaging.

The challenge is to maintain approximately the same volume while reducing the surface area.

That gives us opportunities to work with:

• surface area
• volume
• nets
• three-dimensional figures
• modeling
• constraints
• optimization
• mathematical justification

There’s also a sustainability connection because reducing packaging can potentially reduce material and waste.

Students eventually draft a persuasive letter to the company proposing their redesigned package.

It sounds like a great project, but here’s the important part:

None of that automatically makes it a rigorous math project.

Students could spend most of their time designing a beautiful package and writing a persuasive letter without deeply understanding the geometry driving the redesign.

So I start with the mathematical journey.

Milestone 1: Analyze the Existing Package

First, students need to understand the package they already have.

They identify the three-dimensional figure or combination of figures, determine the dimensions, create or analyze the net, and calculate the original volume and surface area.

But the milestone isn’t simply:

“Original package analysis due Tuesday.”

I need a marker that gives me evidence of the mathematics.

Students might submit a labeled net and their calculations. They might explain what each measurement represents or answer a question about which dimensions contribute to surface area versus volume.

I’m looking for evidence that students understand the geometry of the existing package well enough to start changing it.

If the original calculations are incorrect, we stop there.

That’s much better than discovering the problem after students have built an entire redesign on top of it.

Milestone 2: Redesign Under Constraints

Now students redesign the package.

They can’t simply make the package smaller. It still needs to hold approximately the same amount of product.

So we have a mathematical constraint:
Maintain the volume while reducing the surface area.

That changes the task.

Students have to make decisions about dimensions. They may test multiple possibilities. Their first design may not work.

That’s okay, they can revise.

A milestone marker might include the proposed design, dimensions, net, volume, and surface area.

But I also want students to explain their mathematical decisions:

• How does the new volume compare to the original?
• How much surface area did you eliminate?
• What tradeoffs did you make?

Now I’m checking more than whether students can calculate.

I’m checking whether they can use their calculations to make and evaluate a mathematical decision.

Milestone 3: Prove the Redesign Works

This is where students need to use mathematics as evidence.

They shouldn’t be able to say, “My package uses less material!,” because it looks smaller. They need to prove it.

• What’s the surface area of the original package?
• What’s the surface area of the redesigned package?
• How much changed?
• What percentage of material could potentially be saved?
• Does the redesigned package still meet the volume requirement?

Students aren’t just completing calculations, they’re using those calculations to defend a solution.
That’s a much richer mathematical experience.

Milestone 4: Communicate the Mathematical Argument

Finally, students write their persuasive letter to the company.

The letter has a purpose, but I still want the mathematics at the center.

• Why should the company consider this redesign?
• How much packaging material could it reduce?
• Does it still hold the same amount of product?
• What mathematical evidence supports the claim that the design is more efficient?

The geometry becomes part of the argument.

A student might be an excellent writer and create a beautiful letter, but that doesn’t tell me whether they understand surface area and volume.

That’s why the mathematical evidence has already been gathered through the previous milestones.

The final product brings the learning together. It doesn’t have to carry the entire burden of proving that learning happened.

Milestone Markers Can Be Individual

Collaboration is a valuable part of PBL. I want students talking through ideas, comparing designs, challenging each other’s reasoning, and working together to solve problems. But collaborative learning doesn’t mean every piece of evidence needs to be a group product.

At an important mathematical milestone, every student might independently explain why the redesigned package satisfies the volume constraint.

Maybe each student completes a short checkpoint, or I  might conference with the group and intentionally direct questions to different students.

I’m not trying to turn PBL into a series of individual tests, my goal is to make sure I have enough evidence to answer:
Does each student understand the mathematics driving this project?

Milestones Also Tell Me When to Teach

This is another reason I love milestone markers.

They don’t just tell me what students know, they tell me what I need to do next.

Maybe students are struggling to create accurate nets… That’s tomorrow’s mini-lesson.

Maybe they understand volume but keep making errors with surface area… We need more practice.

Maybe students can redesign their packages but can’t explain why one design is more efficient… That’s a great opportunity for a class discussion.

PBL doesn’t mean I stop teaching.

The project gives my teaching a purpose.

The evidence from the milestones helps me decide when students need instruction, practice, feedback, or another opportunity to think.

The Final Product Isn’t the Assessment

This is probably the biggest takeaway I want teachers to leave with.

The final product can be impressive and still tell you very little about what each student understands mathematically.

The prettiest package redesign isn’t necessarily the strongest mathematical solution.

The most persuasive letter isn’t automatically evidence of the deepest understanding.

A student who creates an incredible digital presentation isn’t necessarily the student who understands the mathematics underneath it.

That’s why I care so much about capturing mathematical thinking throughout the project.

The milestones tell the story of the learning.

The milestone markers give us evidence of the mathematics.

Together, they help protect rigor without turning the project into a traditional worksheet-based unit with a fancy final product attached.

The Project Gives the Mathematics a Purpose

Think about the difference between these two experiences.

In one, students calculate the surface area of several rectangular prisms because that’s the skill we’re practicing.

In the other, students need to understand surface area because they’re trying to redesign a package that uses less material while holding the same amount of product.

The mathematics hasn’t disappeared.

The formulas still matter.

The calculations still matter.

The practice still matters.

But now students have a reason to use what they know.

That’s one of the things I love most about meaningful PBL.

The project gives the mathematics a purpose.

And intentional milestones make sure the purpose doesn’t come at the expense of the mathematics.

A Quick Rigor Check for Your Next Project

Whether you’re creating a new project or revisiting one you’ve taught before, ask yourself:

• What are the key mathematical concepts students need to learn?
• Where does each one show up in the project?
• What will students actually have to think about mathematically?
• Where will I stop and check their understanding?
• What evidence will show me that each student understands the mathematics?
• What will I do if they don’t?

If you can’t answer all of those questions yet, that doesn’t mean you have a bad project. It means you’ve found an opportunity to strengthen the design.

Maybe you don’t need another activity.
Maybe you need a milestone.

Maybe you don’t need another page in the project packet.
Maybe you need a better milestone marker.

The Math Comes First

PBL can absolutely be engaging.

It can give students choice, collaboration, authentic problems, and meaningful reasons to use mathematics.

But those things aren’t enough on their own.

When we intentionally design the mathematical journey, build meaningful milestones, and collect evidence of understanding along the way, project-based learning can create some of the richest mathematical experiences in our classrooms.

The goal isn’t simply for students to finish a project.

It’s for students to leave the project understanding more mathematics than they did when they started.

That’s why, in my classroom, the math comes first.

Ready to Build Your Own Project?

If you’re thinking, “Okay, this is the part I’ve been missing,” that’s exactly why I created PBL Kickstart.

PBL Kickstart is my $17 on-demand workshop designed to help you take the mathematics you’re already teaching and begin building a meaningful project-based learning experience around it.

You don’t need a giant project. You don’t need to completely change your curriculum. And you definitely don’t need to hand students a project packet and hope the learning happens.

You need to know what mathematics matters, what experience will give students a reason to use it, and how you’ll intentionally structure the learning along the way.

Reflection question: If I looked only at the milestones in your project, not the final product, could I tell what mathematics you want students to learn?

Until next time, keep it real.

 Listen & Connect

Listen to the episode: https://www.buzzsprout.com/2187419/episodes/19877127

 Instagram: @moorethanjustx
Join the free FB group: The Modern Math Teacher Community

Become a Modern Math Teacher Member
 Explore more resources: www.moorethanjustx.com