Evaluating and Optimizing Solutions

Active learning works for this topic because students must grapple with real data and trade-offs to make informed decisions. Prototypes and tests become meaningful when students analyze results in context, not from abstract principles. Collaboration and iteration turn evaluation into a skill they can see working.

• Grade 9
• Science
• 4 activities
• 30 min–50 min

Learning Objectives

1. Analyze performance data from prototype testing to identify areas for design improvement.
2. Evaluate the relative importance of different criteria (e.g., cost, safety, efficiency) when selecting the best solution.
3. Justify design modifications based on test results and identified constraints.
4. Optimize a proposed solution by making specific, evidence-based changes to meet performance targets.
5. Critique a design solution by comparing its performance against established criteria and constraints.

Gallery Walk

⏱ 45 min·Small Groups

Gallery Walk: Design Critiques

Display student prototypes around the classroom. Small groups visit each station, score designs using a shared rubric on criteria like strength and cost, and leave sticky-note feedback. Designers review notes and sketch one optimization per prototype.

Prepare & details

Explain how we determine which criteria are most important when evaluating a finished product.

Facilitation Tip: During the Gallery Walk, circulate with a clipboard to listen for students citing specific test data or rubric criteria in their critiques, not just opinions.

Setup: Wall space or tables arranged around room perimeter

Materials: Large paper/poster boards, Markers, Sticky notes for feedback

• Understand
• Apply
• Analyze
• Create
• Relationship Skills
• Social Awareness

Decision Matrix

⏱ 50 min·Pairs

Iteration Cycles: Paper Bridge Challenge

Pairs construct bridges from paper and tape to span a gap and hold weight. Test prototypes, record failure points, then iterate twice based on data and partner input. Final tests compare initial and optimized performance.

Prepare & details

Justify why it is essential to consider constraints like cost and materials during the design phase.

Facilitation Tip: For the Paper Bridge Challenge, ensure groups document each iteration’s changes and their reasoning before moving to the next cycle.

Setup: Groups at tables with matrix worksheets

Materials: Decision matrix template, Option description cards, Criteria weighting guide, Presentation template

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management

Decision Matrix

⏱ 40 min·Small Groups

Constraint Simulation: Budget Builds

Provide limited materials and a mock budget. Small groups prototype devices, track costs, test functionality, and optimize by reallocating resources. Class shares data to vote on most balanced solutions.

Prepare & details

Optimize a design solution based on feedback and performance data.

Facilitation Tip: In Budget Builds, provide students with a fixed set of prices and material limits so constraints feel tangible and unavoidable.

Setup: Groups at tables with matrix worksheets

Materials: Decision matrix template, Option description cards, Criteria weighting guide, Presentation template

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management

Decision Matrix

⏱ 30 min·Whole Class

Criteria Ranking Debate

Present a design scenario with multiple criteria. Whole class debates and ranks priorities via dot voting, then applies rankings to evaluate sample prototypes and suggest refinements.

Prepare & details

Explain how we determine which criteria are most important when evaluating a finished product.

Facilitation Tip: Use the Criteria Ranking Debate to model how to defend a choice with evidence, not preference.

Setup: Groups at tables with matrix worksheets

Materials: Decision matrix template, Option description cards, Criteria weighting guide, Presentation template

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management

Teaching This Topic

Experienced teachers approach this topic by framing optimization as a puzzle with multiple valid paths. They avoid presenting evaluation as a checklist and instead use student-generated data to drive decisions. Research shows that when students see their peers’ prototypes succeed or fail, they internalize the value of iteration. The teacher’s role is to guide students to notice patterns in their results and ask, 'What can we learn from this?' rather than 'What is the right answer?'

What to Expect

Successful learning looks like students using evidence to justify design choices, adjusting solutions based on feedback and constraints. They should frame their decisions with measurable criteria and recognize that optimization is an ongoing process. Peer discussions and data comparisons become part of their reasoning toolkit.

Watch Out for These Misconceptions

Common Misconception

During the Gallery Walk, watch for students assuming the first prototype they see is the best solution. Redirect them by asking, 'Which test results or data points support that claim?'

What to Teach Instead

Use peer feedback cards during the Gallery Walk that require students to cite specific evidence from the prototype’s test results or rubric scores before offering a critique.

Common Misconception

During the Iteration Cycles, watch for students prioritizing appearance over function when redesigning. Redirect them by asking, 'How does this change improve the measured outcome, like load capacity or efficiency?'

What to Teach Instead

Provide a data table template for each iteration cycle that forces students to record measurable changes and their impact on the prototype’s performance.

Common Misconception

During Budget Builds, watch for students ignoring cost constraints when proposing changes. Redirect them by asking, 'Does this improvement justify the added expense within your budget?'

What to Teach Instead

Require students to submit a cost-benefit analysis for each proposed change, showing how it affects both performance and budget.

Assessment Ideas

Quick Check

After the Iteration Cycles: Provide students with a scenario like, 'A team’s bridge prototype held 500g but cost $10. They want to hold 800g. List two criteria they should prioritize and two constraints they must consider for their redesign.'

Peer Assessment

During the Gallery Walk: Peers evaluate each prototype using a checklist that asks, 'Does the redesign address a specific weakness identified in testing?' and 'Are the changes realistic given common constraints?' Students rotate and provide written feedback on sticky notes.

Exit Ticket

After Budget Builds: Students receive a simple graph showing prototype performance over several iterations. They answer, 'What does this graph tell you about the success of the design changes?' and 'What is one more change you would suggest to further optimize this solution, and why?'

Extensions & Scaffolding

• Challenge: Ask early finishers to redesign their solution for a different constraint, such as minimizing weight while maintaining strength.
• Scaffolding: Provide sentence starters for reflections, like 'The data showed that... so we changed...' to help students articulate their reasoning.
• Deeper exploration: Have students research a real-world product that went through multiple iterations, such as the design of a reusable water bottle, and present how constraints shaped its final form.

Key Vocabulary

Criteria	Standards or principles by which something is judged or evaluated. In design, these are the specific requirements a solution must meet to be considered successful.
Constraints	Limitations or restrictions that must be considered during the design process. Examples include budget, materials, time, and safety regulations.
Prototype	An initial model or sample of a product developed to test a concept or process. Prototypes are used to gather data and identify areas for improvement.
Optimization	The process of making a design as effective, perfect, or functional as possible. This often involves making changes based on testing and feedback.
Performance Data	Information collected during testing that measures how well a prototype or solution functions. This data is used to evaluate success and guide improvements.