Welcome to the Final Step: Evaluating Your Design!

Congratulations! You have researched, planned, and created your product. But how do you know if it is actually good? In the IB MYP Design Cycle, the final stage is called Evaluating (also known as Criterion D). Think of yourself as a professional critic or a scientist testing a new invention. In this chapter, we will learn how to look at our work honestly to see what went well and what we can make even better next time.

Don't worry if your product didn't turn out exactly how you imagined! In Design, making mistakes is just a way to learn how to improve. Even the world’s most famous designers have to evaluate and fix their work many times.


1. Testing Your Solution

Before you can say your design is "good," you need evidence. You can’t just guess! We find this evidence by testing the product.

How do we test?

There are a few simple ways to test your design:

  • Functional Testing: Does it actually work? If you made a chair, does it hold weight? If you made an app, do the buttons click?
  • User Feedback: Ask someone else (your Target Audience) to try it out. Watch them use it and see where they get stuck.
  • Expert Opinion: Ask a teacher or someone who knows a lot about the topic for their honest thoughts.

Analogy: Imagine you cooked a new meal. Functional testing is checking if the chicken is cooked through. User feedback is asking your friends if it tastes good!

Quick Review: Testing gives you the facts you need to judge your work fairly.


2. Measuring Success (The Design Specification)

Back at the start of your project (in Criterion A), you wrote a list of "rules" your product had to follow. This list is called the Design Specification.

Evaluating means looking at that list and checking off what you achieved. For example:

  • Specification: "The product must be bright blue." -> Evaluation: Yes, it is blue.
  • Specification: "The product must weigh less than 1kg." -> Evaluation: No, it weighs 1.2kg.

Did you know? It is okay to fail some of your specifications! The important part is explaining why it happened. Maybe the blue paint ran out, or the 1kg material was too weak.

Key Takeaway: Always compare your final product to your original Design Specification to measure how successful you were.


3. Suggesting Improvements

No design is ever "finished"—it can always be better. In this part of the evaluation, you explain how you would change your design if you had to do it all over again.

How to suggest improvements:

1. Identify the problem: "The handle is a bit shaky."
2. Explain why: "The glue I used wasn't strong enough for the weight."
3. Propose a fix: "Next time, I would use screws instead of glue to make it sturdier."

Common Mistake to Avoid: Don't just say "I would make it better." Be specific! Mention materials, sizes, or tools you would use differently.

Memory Aid (The "Why-How" Method): For every problem you find, say WHY it happened and HOW you would fix it.


4. Impact on the Target Audience

Design is all about solving problems for people. This section asks: "How did my product change things for the user?"

Think about the person you made the product for. Does your design:

  • Make their life easier?
  • Solve a specific problem they had?
  • Make them feel happy or safe?

Example: If you designed a more organized pencil case for a classmate, the impact is that they can now find their pens faster and don't feel stressed during tests.

Key Takeaway: A successful design doesn't just look pretty; it has a positive impact on the person using it.


Summary Checklist for Evaluating Designs

When you are writing your evaluation, make sure you can answer these four questions:

1. Did I test it? (Show your results or photos of the test).
2. Did I meet my "rules"? (Check your Design Specification).
3. How can I make it better? (Be specific about changes).
4. Did I help my user? (Explain the impact on the target audience).

Final Encouragement: Evaluating is your chance to show how much you have learned throughout the whole process. Be honest, be detailed, and remember: every "failure" is just a step toward a better design!