1.2.3. Creating the Solution

Today, we’re focusing on the 'Creating the Solution' stage of the MYP Design Cycle. This is where you bring your ideas to life. Who can remind me what we aimed to do in the previous stage?

We developed our ideas and made plans for our designs!

Exactly! And now we’ll follow that plan. One important thing is to construct a logical plan. Can anyone explain what a logical plan might include?

Like steps on how to build our project and what materials we need?

Yes, very good! It helps to keep us organized and efficient. Remember, we can use the acronym TDD—Tools, Designs, Documents—to help us remember what we need for this stage.

What if something doesn't go as planned?

Great question! Adaptability is key. You’ll need to problem-solve and make adjustments as needed. Always document these changes, too, as you’ll reflect on them later!

So, we take notes and take pictures while we’re building?

Correct! Documentation is crucial. Let’s recap: we start with a logical plan, gather our tools, and remain adaptable. Each step is important towards creating a successful solution.

Let’s dive deeper into the tools you will use for 'Creating the Solution.' Can anyone name some tools we might need?

We could use 3D printers or maybe some crafting materials?

Absolutely! Both physical and digital tools are essential. Think about how each tool contributes to making your solution functional. How do we ensure we’re using these tools effectively?

By knowing how to operate them and following our plans!

Exactly right! If you’re using software, for instance, be sure you understand its features. Let's create a mnemonic, 'FEAST'—Fit, Execute, Adapt, Share, Test—to remember to fit your plans with your tools, execute your ideas successfully, adapt to changes, share your progress, and test your product.

How do we test our prototypes?

Great follow-up! Testing should occur throughout your building phase. As you create, you’ll check if your design meets the specifications. Remember, the goal is always improvement, so feedback is important!

So we keep iterating until it works perfectly?

Yes! Iteration is part of the design process. Let’s summarize: knowing your tools, following your plans, and being ready to adapt are vital for a successful solution.

Now, let’s address a crucial aspect of 'Creating the Solution'—reflection. Why do you think reflecting on our changes is important?

To understand what worked and what didn’t, maybe?

Exactly! Reflection helps you learn and improve in future projects. When you tweak your design, document why you made those changes. Can anyone give an example of a change they might make?

If my prototype isn't stable, I might change the design to make it sturdier.

Perfect example! You’ll want to keep a record of that. Let’s create a memory aid: CARS—Capture, Analyze, Reflect, Sustain. Capture your changes, analyze what these changes achieve, reflect on the impacts, and sustain those successful ideas in future designs.

What if nobody gives us feedback?

If that happens, seek out opinions from peers or mentors. Gathering diverse feedback is key for improvement. Remember, reflecting on and justifying changes not only enhances your current project but fosters your growth as a designer.

So, it's like building a better version of ourselves each time?

Precisely! Every iteration builds skills and knowledge. To wrap up: reflection, documentation, and justification are your tools for continuous improvement.