Evidence-Based Design Revision

A revision is purposeful when evidence—not random preference—explains why the new version should perform better.

1. Make a claim

Identify one part that should change. State the improvement you expect.

“If I change ___, then ___ should improve because ___.”

2. Name the evidence

Use at least one source:

• a measurement;
• a physical prototype or fit test;
• the printability checklist;
• a fly-through or underside view;
• peer feedback;
• a success criterion;
• a failed or successful print example.

3. Revise one variable

Change one important feature at a time where possible. This makes it easier to understand which decision affected the result.

4. Compare before and after

Capture both versions from the same view. In Notion, explain:

• what changed;
• which evidence led to the change;
• how the revision better meets a criterion;
• any new trade-off or risk.

You may accept, adapt, or reject feedback, but your decision must be supported by evidence.

Curriculum connections

A3.3: Analyze product performance using quality-control methods.
A3.4: Refine a design using data gathered during development.
A3.5: Communicate analysis and refinements.