Introduction: Bringing Your Ideas to Life
Welcome! You have already done the hard work of researching and planning your design. Now comes the exciting part: Creating the Solution. In this chapter, we focus on two very important parts of Criterion C: actually following the step-by-step plan you made and keeping track of any changes you make along the way.
Think of your plan like a recipe. Even the best chefs sometimes have to swap an ingredient or change the oven temperature if things aren't looking right. In Design, being able to explain why you made those changes is what helps you get those top marks!
1. Following Your Plan (Criterion C, Strand iii)
In the previous chapter (Planning Time and Resources), you created a logical, step-by-step guide. Now, your goal is to show that you can actually use that guide to build your product.
What does "following the plan" look like?
To reach the highest levels in the MYP, you must show that you followed your plan to create a solution that functions as intended. This means your final product should actually work!
- Stay organized: Use your plan as a checklist. Check off each step as you finish it.
- Document the process: The best way to prove you followed your plan is through process photos or screenshots. If your plan says "Step 1: Cut the wood to \(30cm\)," take a photo of yourself measuring and cutting.
- Consistency: If your plan says you will use a specific tool or software, try your best to use it. If you can't, that leads us to our next big topic: recording changes.
Quick Tip: Don't worry if you don't follow the plan 100% perfectly. The IB examiners want to see how you handle real-world making, not that you are a perfect robot!
2. Recording and Justifying Changes (Criterion C, Strand iv)
During the "making" phase, things rarely go exactly as planned. You might run out of a specific material, find a software bug, or realize a better way to join two parts together. This is a natural part of being a designer!
Recording vs. Justifying
There is a big difference between just saying "I changed something" and justifying it. Let's look at the "Command Term Ladder" for this strand:
- Lower Levels (State/Outline): "I changed the color from blue to red." (This just says what happened).
- Middle Levels (Describe/Explain): "I changed the color to red because I ran out of blue paint." (This says what and why).
- Highest Levels (Justify): "I changed the color from blue to red because I ran out of blue paint. This was a good choice because red still meets my Design Specification for 'bright colors,' and it makes the 'Stop' button easier for the user to see." (This justifies the change by linking it back to your goals).
Common Reasons for Changes
If you find yourself stuck on what to write, think about these three categories:
- Materials/Resources: "The 3D printer was broken, so I used cardboard instead."
- Technical Errors: "The glue wouldn't hold the weight of the shelf, so I added screws for strength."
- Design Improvements: "While building, I realized the handle was too small for a hand to fit, so I made it \(2cm\) wider to improve the ergonomics."
Key Takeaway: Every time you stray from your original plan or design, write it down immediately! It is much harder to remember these details a week later.
3. How to Document Your Progress
For your ePortfolio, you need clear evidence. A simple way to do this is by using a "Making Log" or a "Change Table."
Example of a Change Table:
4. Common Mistakes to Avoid
- Mistake: "Cleaning up" your work. Some students think that having "no changes" makes them look like a better designer. Actually, the IB wants to see how you solve problems! Recording changes shows critical thinking.
- Mistake: Forgetting photos. If you finish your product but have no photos of the steps in between, it is very hard to prove you followed a plan.
- Mistake: Ignoring the Design Specification. When you justify a change, always try to mention how it helps your product succeed based on the rules you set in Criterion B.
Quick Review Box
1. Follow the Plan: Use your logical steps to create a working solution. Use photos to prove you did it!
2. Record Changes: Note down every time you do something differently than you originally intended.
3. Justify: Explain why the change was necessary and how it affects the final product. Link it back to your Design Specification for the best marks.
Did you know? Professional engineers and architects have to record every single change to their plans in a "Change Log" so that if something goes wrong later, they can see exactly why decisions were made!
Next up in Criterion C, we will look at Technical Skills and Safe Practice to ensure you are creating your solution effectively and safely.