Day 8: Revise & Improve

The TAPAS Approach to Project-Based Learning | A 10-Day Recipe for Transformation

Turn feedback into meaningful improvement.

Day 7 gave students something incredibly valuable.

Perspective.

They shared their developing work, listened to feedback, considered different viewpoints, and began identifying what might make their solutions stronger.

Now comes an equally important step.

Doing something with that feedback.

Day 8 of our 10-Day Recipe is about revising and improving.

Students return to their prototypes, designs, drafts, or proposed solutions and make thoughtful changes based on what they've learned.

But there's an important distinction.

We're not asking students to simply make their work look better.

We're asking them to make their solutions work better.

Day 7 helps students understand what needs improvement. Day 8 gives them the opportunity to act on that understanding.

The Goal

One question should guide our planning for Day 8:

How can students use evidence and feedback to make their solutions more effective?

Depending on the project, students might redesign a component, revise an explanation, strengthen an argument, adjust a model, improve a digital product, or reconsider part of their original approach.

The particular revision depends on the challenge.

What matters is that students can explain what they changed, why they changed it, and how the revision better addresses the problem.

Revision Isn't Just Fixing Mistakes

This is an important distinction.

Students often associate revision with correcting something that's wrong.

Fix the spelling.

Repair the broken piece.

Change the color.

Add more detail.

Those changes may be necessary, but meaningful revision goes deeper.

It asks students to reconsider the effectiveness of their decisions.

Imagine students designing a model vehicle.

Their initial prototype moves, but testing reveals that it struggles to travel the intended distance.

A superficial improvement might involve changing its appearance.

A meaningful revision might involve examining friction, wheel alignment, mass, or another factor affecting performance.

The difference?

One changes how the product looks.

The other responds to evidence about how it performs.

Revision should improve the solution, not simply decorate the product.

Not Every Piece of Feedback Deserves a Change

Day 7 introduced students to multiple perspectives.

But here's something we need to remember:

Feedback is information, not an instruction to change everything.

One classmate may suggest adding a feature.

Another might recommend removing something.

An expert might identify a constraint students hadn't considered.

Students need to evaluate these suggestions rather than automatically accepting them.

Ask:

• Which feedback connects directly to our success criteria?

• What evidence supports the suggested change?

• Will this revision help us better address the problem?

• What might we lose by making this change?

• How will we know whether the revision worked?

This is where critical thinking becomes especially important.

Students aren't simply following directions.

They're making decisions.

The Teacher's Role: Focus the Revision

One of the biggest challenges on Day 8 is preventing revision from becoming endless.

Students can spend enormous amounts of time making adjustments that have little impact on the actual solution.

That's why we need to keep the work focused.

Rather than asking students to improve everything, help them identify one or two meaningful priorities.

Try asking:

"Which change would make the greatest difference in how well your solution addresses the problem?"

Then encourage students to explain their reasoning.

A simple revision plan might include:

1. What are we changing?

2. Why are we changing it?

3. What evidence supports this decision?

4. How will we determine whether the change improved our solution?

This keeps the process manageable while protecting the thinking.

Make the Improvement Visible

One of the most powerful things students can do on Day 8 is compare their original work with their revised version.

This doesn't require an elaborate documentation process.

Students might use before-and-after photographs, annotated sketches, a short reflection, a comparison chart, or a brief explanation of their design changes.

The goal is to make the learning visible.

Ask students to complete three statements:

Originally, our solution...

Based on feedback and evidence, we changed...

This improved our solution because...

When students can explain their revisions, they're demonstrating more than the ability to create.

They're demonstrating the ability to learn from evidence and apply that learning.

What If the Revision Doesn't Work?

Then students have learned something important.

Not every improvement attempt produces the expected result.

A revised model might perform worse.

A new feature might introduce an unexpected problem.

A rewritten explanation might still confuse the intended audience.

That's not necessarily a reason to abandon the work.

It's an opportunity to examine what happened.

Teachers can help students compare results, revisit their assumptions, and determine whether another adjustment is needed.

We don't have to solve every remaining problem on Day 8.

But we should help students understand that improvement is an evidence-informed process, not a guarantee of immediate success.

Portrait of a Graduate Connections

Day 8 creates meaningful opportunities to develop several competencies.

Critical Thinking: Evaluate evidence, compare alternatives, and determine whether changes improve performance.

Creativity: Reimagine possibilities and develop alternative approaches to challenges.

Collaboration: Negotiate revision priorities, share responsibilities, and make collective decisions.

Communication: Explain changes, justify decisions, and describe how feedback influenced the work.

These competencies aren't separate from the project.

They're practiced through the process of making the work stronger.

A Simple Day 8 Recipe

Keep Day 8 manageable with four moves.

1. REVIEW

Return to the feedback, evidence, and success criteria.

What did we learn about our first version?

2. PRIORITIZE

Identify one or two changes that could make the greatest difference.

What should we improve first, and why?

3. REVISE

Make the selected improvements to the prototype, design, draft, or product.

What will we change?

4. TEST & EXPLAIN

Examine the revised work and explain the impact of the changes.

Did our revision improve the solution? What evidence supports our conclusion?

That's it.

Students don't need to rebuild everything.

They need an opportunity to make purposeful improvements.

The Small Bite

If you're trying this tomorrow, don't create an elaborate revision process.

Ask students to select one meaningful piece of feedback from Day 7.

Then have them answer:

"What is one change we can make that will help our solution better address the problem?"

Give students time to make the change.

Then ask:

"What evidence shows that our solution is stronger now?"

Have students capture a before-and-after comparison and explain their reasoning.

That's Day 8.

Day 1: Launch the Challenge Day 2: Build Background Knowledge Day 3: Deepen the Learning Day 4: Investigate the Problem Day 5: Plan the Solution Day 6: Create Prototype Day 7: Feedback & Critique Day 8: Revise & Improve

Next, students will begin preparing their refined work for an authentic audience.

Day 9: Finalize & Prepare.

In TAPAS terms, we've invited others to taste our first dish, listened to their feedback, and returned to the kitchen.

Now we're adjusting the recipe.

Maybe it needs a little more of something.

Maybe something needs to change.

But we aren't making adjustments simply because someone suggested them.

We're making changes because we believe they'll improve the final result.

And that is an important lesson for our students.

Better solutions don't always come from better first ideas. They often come from what we do after the first attempt.

Small bites. Big impact.

Real problems. Real learning. Real impact.