Introduction: The "Next-Gen" Mindset

You have researched, designed, and built your solution. You have even tested it to see how well it works. But a designer’s work is never truly "finished." In the world of Design, there is always room to make things better, faster, stronger, or easier to use. Think about your favorite smartphone or video game—they are constantly being updated with new versions. This chapter, Improving the Solution, is where you use your "Next-Gen" mindset to explain how you would create "Version 2.0" of your product.

In Criterion D (Evaluating), this is specifically strand iii. It is your chance to show that you are a reflective designer who can learn from challenges and plan for future success.

What Does it Mean to "Improve the Solution"?

Improving the solution isn't about admitting you "failed." Even the best products in the world have areas that could be better. In this stage of your ePortfolio, you are looking at the data you collected during testing and the feedback you received from your target audience to suggest specific, logical changes.

Why do we do this?

  • To fix flaws: If a part broke or a button didn't work during testing, you need to suggest a fix.
  • To enhance performance: Maybe it works, but it’s a bit slow or heavy. How could you make it more efficient?
  • To improve aesthetics: Could it look more professional or appealing to the client?
  • To increase sustainability: Could you use better materials that are kinder to the planet?

Step-by-Step: How to Suggest Improvements

Don't worry if this seems tricky at first! Just follow these steps to turn your observations into high-quality design suggestions.

1. Look Back at Your Testing Results

You cannot just guess what needs improving. You must use the "authentic product testing" you did in the previous chapters. If your test showed that your digital app crashes when two buttons are pressed at once, that is a specific area for improvement.

2. Identify the "What" and the "How"

Be specific. Instead of saying "I would make it better," say "I would replace the cardboard base with 3mm acrylic."

3. Justify Your Suggestions

This is the most important part for getting higher marks. You must explain why that change would help. For example: "I would change the base to acrylic because the cardboard base became unstable during the weight-bearing test, and acrylic would provide the rigid support needed for the product to function safely."

The Command Term Ladder: Aiming for Excellence

In the MYP, the "command term" used in your project determines your achievement level. Here is how to climb the ladder for Criterion D (iii):

Level 1–2 (States): You simply list a few changes.
Example: "I would use stronger glue."

Level 3–4 (Outlines): You give a bit more detail about the change.
Example: "I would use wood glue instead of a glue gun to keep the joints together."

Level 5–6 (Explains): You describe the change and give reasons why it helps.
Example: "I would use wood glue because it creates a permanent bond between the wooden parts, whereas the hot glue peeled off during the durability test."

Level 7–8 (Critically Evaluates/Explains): You provide a deep explanation for all your suggested improvements, linking them directly to your testing data and your Design Specification. You show that you have thought about the "big picture" of the project.

Real-World Examples

To help you visualize this, here are two examples based on the different strands of Design:

Product Design Example:
"Based on the user feedback session, the handle of the recycled lamp was described as 'uncomfortable.' To improve this, I would apply ergonomic principles by adding a rubberized grip. This would increase the friction and comfort for the client, making the lamp easier to carry without slipping."

Digital Design Example:
"Testing showed that the website navigation menu was difficult to see on smaller screens. In the next version, I would implement a 'hamburger menu' (three-line icon) for mobile devices. This would declutter the user interface and ensure the solution meets the success criteria for 'ease of use' across all devices."

Common Mistakes to Avoid

Being too vague: Avoid words like "better," "nicer," or "prettier" without explaining what you actually mean.

Ignoring the "Making" process: Sometimes the best improvements come from things you realized while you were building (Criterion C). If you struggled to assemble a part, suggest a design change that makes it easier to manufacture.

Forgetting the Client: Always remember who the product is for! If your client wanted a "minimalist" look, don't suggest adding dozens of colorful stickers as an improvement.

Did you know? Many famous products, like the Dyson vacuum cleaner, went through thousands of prototypes and "improvements" before they were ever sold in a store!

Quick Review: Key Takeaways

  • Evidence-Based: Improvements must be based on your testing data and Design Specification.
  • Specific: State exactly what material, code, or feature you would change.
  • Justified: Always explain why the change would make the solution more successful.
  • Future-Focused: Show that you understand how your product could evolve into a professional-level solution.

Cross-Reference: Remember that your improvements should link back to what you discovered in the chapter "Evaluating Against the Design Specification." If you failed a specification, that’s your first place to look for an improvement!