Hello there.

My name is Mrs. Dhami.

Thank you for joining me for your Design and Technology lesson today.

Now, the big question for today is how can we develop your absolutely wonderful design ideas into successful design solutions that fulfil your design requirements? Now, to do that, we are going to have to make lots of really effective design decisions.

So hard hats on let's get cracking.

Our outcome for today is we will be able to use a variety of methods to develop our designs during our iterative journey.

Our keywords for today are iterative, design requirements, and design decisions.

Let's recap what those words mean.

Iterative, we are on our iterative journey and it is a process of refining and improving our ideas.

Design requirements are something which is needed or wanted to make a product successful.

And then design decisions, which we're going to be doing a lot of today, is a deliberate choice to meet a requirement or solve a problem.

Our lesson will follow two learning cycles today.

First of all, design decisions and second of all, iteration.

Let's get cracking with design decisions.

The big picture for our iterative journey today is we are going to identify what we need to develop to make our ideas into a successful design solution.

We will explore and select a range of methods to develop your ideas and we will explore how to make effective design decisions.

Now a quick note, the iterative journey is a process where we constantly refine and improve throughout to develop a successful design solution.

It is not a linear process, meaning that additional research and design decisions can be made throughout at any point.

Just because we are developing doesn't mean that research is over.

You can research, you can develop, you can make design decisions at any point.

I am sure you probably have loads of wonderful design ideas at this point, but now what you need to do is shortlist those design ideas to either one or two that you would like to develop.

There's a few ways that you could do this.

One way is testing against your design requirements.

Now, they're are likely to fulfil all of your design requirements at this point, but what you are looking for is the potential for those design ideas to be able to fulfil your design requirements.

Now, you could ask stakeholders to vote or comment.

You could put all of your design ideas out.

You could give your stakeholders some little counters and they could go round and vote by placing a counter on their favourite designs.

That might be one nice way and you could also gather some of their comments.

And one more way could be getting feedback from your primary user.

Perhaps you could text some pictures of your design ideas or have a video call with your primary user so that they can have a little look and give you their ideas and their feedback as to which designs they like the look of.

There's lots of other ways too.

You might find a different way to shortlist your design ideas.

In the real world and in the school workshop a product rarely goes from a sketch design to a final product.

Some do, but often they are unsuccessful.

So Jacob says, "Why might they be unsuccessful?" What I'd like you to do is have a little think about this perhaps chat to the person next to you.

Come back to me when you've got an idea and we'll address that on the next slide.

To be successful, a design needs to fulfil its design requirements.

To achieve this, there are likely to be many design decisions during the iterative journey, so it's very unlikely like the last slide, to go from a quick drawn concept to a final design solution that very, very rarely happens.

So let's take a closer look at Lucas's iterative design journey.

Now you can see in the top left of his page is his initial sketch, one of his design ideas.

And if you look at the bottom left of his page, you will see his final design solution.

But if you follow, the arrows are all the way round to his final design solution.

They are all the different iterations and the design decisions that he made along his iterative journey.

Now what I'd like you to do is pause the video and take a closer look and see what you can identify that Lucas did for his iterative development? Come back to me when you've got an idea.

Okay hopefully, that time has given you a bit of time to notice a few things and maybe you noticed his cardboard prototyping.

Maybe you noticed the CAD/CAM.

Maybe you noticed prototypes made with further materials.

Maybe you noticed a bit of material exploration.

Maybe you noticed that the design really changed and developed and refined.

That really fits nicely in with the definition of iterative, doesn't it? Refining and improving to become the final design solution.

Now your iterative journey will not look exactly the same as Lucas's, but it might have a few elements from that for your design journey.

A design decision is a deliberate choice to meet a design requirement or solve a problem.

Design requirements were collated into your specification.

A design requirement is something which is needed or wanted to make a product successful.

Referring to or measuring against your design requirements ensures that you make the correct design decisions for your iterative journey.

Effective design decisions ensure your product or solution is successful.

So go dig out your specification and find those design requirements.

Time for a quick check-in.

Referring to or measuring against your something ensures you make the correct something.

So potential answers: A, design decisions? B, iterative journey? C, design strategies? D, design requirements? Pause the video, come back to me when you have got an idea.

Well done if you identified A and D.

Referring to or measuring against your design requirements ensures you make the correct design decisions for your iterative journey.

Methods to test or measure your developments against your design requirements include: primary user or stakeholder feedback.

Prototype testing including ergonomic considerations, obtaining specific measurements, visual inspections, safety checks, simulations.

So outcomes from continuous testing enable you to decide what to develop and make effective design decisions to take the design forward.

Is a common misconception that testing only happens once you've produce the final prototype or the final design solution.

When actually, testing needs to happen throughout your iterative journey so that you can keep making those refinements and improvements.

Aisha wasn't too sure what to develop on her iterative journey, so she had a great idea.

She decided to ask her stakeholders what they thought she could develop on her chosen design idea.

So she showed them her idea.

She gave them little slips of paper and she asked them to write down their thoughts.

This instantly produced six different routes for her to develop.

Let's zoom into one.

So one of them said, how will you prevent the jar from spinning? This got Aisha thinking.

Let's have a little look what she did with that idea next.

Aisha used her findings to identify her next steps for development.

And you can see she sketched a few ideas by each of the points that her stakeholders identified she could develop.

Let's zoom into one.

She identified that perhaps a gradual change in depth might help to solve the problem that the stakeholder had found.

This was great as it helped her then to go on to research, choose the right method to develop and go on to make successful design decisions.

This was a great idea, Aisha, and an idea that you may or you may not want to use yourselves.

As you develop your designs, remember to record your design decisions.

This will help you to stay focused on your design requirements and ensure you develop successful design solution.

So let's go back to Lucas.

If we zoom into part of his iterative journey, you can see some of his development in CAD.

Lucas says, "External and internal ribs enhance structural integrity, allowing reduced wall thickness to meet the lightweight design requirement." And he recorded that in his NEA in his iterative journey.

This keeps an eye on track to fulfil all of those design requirements.

Well done Lucas.

Which statements are correct about design decisions? A, they can only be made by the primary user? B, they can be made throughout the iterative design journey? C, collated, they make a specification? D, they help to make a more successful design solution? Have a think.

Come back to me when you've got an answer.

Well done if you manage to get B and D.

Design decisions can be made throughout the iterative design journey because of course they help to make a more successful design solution.

On to task A.

Part one, I would like you to shortlist your design ideas based on your design requirements and primary user stakeholder feedback.

Part two, define design decision.

And part three, identify which aspects of your idea you need to develop in order to as many of your design requirements as possible.

Good luck.

Come back to me when you've got some great answers.

Answers could include, for part one, I asked you to shortlist your design ideas based on your design requirements and primary users stakeholder feedback.

So you could speak with your primary user or stakeholders in person or via perhaps a video call.

You could ask your stakeholders to vote with the counters like the idea I showed you earlier and you could compare your ideas against each other and against your design requirements.

Part two, a design decision is a deliberate choice to meet a design requirement or solve a problem.

Design decisions are important because they enable the designer to stay focused when developing a design, ensuring it meets all design requirements and produces a successful design solution.

Part three, identify which aspects of your idea you need to develop in order to meet as many of your design requirements as possible.

So you could test or measure your idea against your design requirements to identify design decisions for development.

You could ask your primary user or stakeholders for their ideas and how they would like to see your idea develop.

Hopefully you've got some great ideas now to develop.

On to learning cycle two, iterations.

We are going to explore a variety of iterative methods for developing your designs along your iterative journey.

Now, you are not limited to the methods we share.

Some will be right for your iterative journey and others will not.

Now please remember when developing your designs, you may identify a design decision at any point.

What you need to do is remember to record it.

You could highlight it, circle it, write it in another colour, however you like.

Just please make sure you record and evidence it in your NEA.

As we said in learning cycle one, primary user and stakeholder feedback is great for iterations.

You could do interviews, video calls, votes, you could get them to test your prototypes.

So it's a really good idea for providing opinions, ideas, and further direction for your iterative journey.

And of course you are going to make design decisions as you find this out.

So please remember to record these.

CAD is a great way to develop some of your ideas.

It's a great idea for mathematical modelling but also rapid development.

So if you take a look at the top picture, that's some development using electronic modelling programmes.

It means you haven't gotta get out all of these components.

You can test it on the computer, which is great.

And on the bottom you can see some development using CAD for a seating system.

And you can see the differences in the two sets of pictures, how that design has been developed without producing anything actually physical, great for rapid development.

But please don't forget, record all of those design decisions that you will make.

Hopefully, you might have access to a variety of CAM in your school.

So Computer-Aided Manufacturer such as laser cutters, 3D printers, CNC routers, embroidery machines, vinyl cutters, you name it.

The list is endless.

CAM is a great idea for rapid prototyping, but also testing with prototypes, so having something physical to test.

Now if we look at the example on the right hand side, first of all it starts out off as a very simple laser cut cardboard prototype.

You can see huge developments, massive design decisions between the first cardboard prototype and the second cardboard prototype, and then obviously into the next one, which is the 3D printed PLA prototype.

These are all ideas and developments for a seating solution.

And as we've just seen loads of design decisions there.

Please do not forget to record them in your NEA.

AI is an exciting way to develop your designs in ways that you might not have thought of before.

And that's great, even if you don't go down that route, it might give you ideas for how to get to where you might be heading on your iterative design journey.

So you could develop it by changing the input words to see what you could create.

And you could also use sketch to image where perhaps you put some sketches of your own or pictures of models of your own into AI, which then AI can develop and render those sketches.

But please, as I've said before, AI applications will need attributing because it's not you who has produced that development.

It is the AI application.

Obviously this is going to give you loads and loads of design decisions to make along the way.

Don't forget to record them.

Of course, you can use sketching as well to develop your ideas, that could be 2D, 3D, freehand, isometric, oblique, orthographic, perspective, whatever you feel confident with and whatever fits your design iterative journey correctly.

It's a great idea for rapid developments and experimenting with multiple options.

And there's a lovely example there done by Lucas.

Please don't forget though, record those design decisions that you make.

Laura says, "I cannot draw.

All my friends have drawn beautiful developments.

I am not going to be able to iterate as well as them." Is Laura's statement true or is it false? Have a think.

Come back to me when you've got an idea.

Well done if you worked out that Laura's statement is false.

Successful communication of iteration uses a range of methods and is not just limited to sketching.

Use your strengths when choosing an iterative development method.

A great way to develop is using prototypes because it gives you something physical to handle and to test and to get feedback on.

So your designs could be developed in 3D using things such as construction sets, modelling clay, paper, cardboard, breadboards or scale timber, polymer, metal or textile prototypes, whatever works for your iterative journey.

Again, though, you are going to make tonnes of design decisions.

Please do not forget to record them in your NEA.

If you do make physical 3D prototypes, then a great idea is to photograph those prototypes, pop them onto a page, print those off, and then that enables you to be able to draw on top of those photographs and sketch by the side, add annotations to be able to explain the design decisions that you might make from having made those prototypes.

This is a great way to get the thoughts in your mind from those prototypes onto paper.

And naturally, it records your design decisions.

Some of your design solutions may require you to use a material that perhaps you're not particularly confident with, or perhaps you haven't used particularly much throughout your education.

So it's a great time for you in developments to be able to experiment and research materials that will be right for your design solution.

So Jun had exactly that.

He wanted to use a material that was environmentally friendly, so he decided he'd make his own melting bottle tops to form his own sheets of HDPE.

But Jun wasn't sure how he could then go on to use these sheets.

He wasn't sure of the capabilities or the limitations or the achievable finishes he could get with HDPE.

So what he did was he cut lots of little strips out.

He had to go at bending it, you can see there using the strip heater.

He then had to go at drilling different sized holes using a cone drill and then he had to go at reshaping it.

So he popped a bit in the oven, good work using the protective glove there, Jun.

He then created himself his own little former, you can see with that wiggle shape.

And he put his HDPE into that and experimented with the shapes that he could produce.

This was great and this is a really good idea for you with whichever materials you are thinking of using so that you can identify the capabilities and the limitations, the workability, and what finishes can be achieved for that particular material.

It's a great chance to experiment.

Just please, you are going to make lots of design decisions.

Don't forget to record them.

Simulations are a great way of virtually testing ideas so that you can make some tweaks and develop them further.

So for example, you can see we've got a circuit simulation at the top and at the bottom, a static stress simulation.

This is a great idea for testing or developing before you actually go to manufacture so that you don't waste materials and components.

And of course you are going to make lots of design decisions with simulations.

Don't forget to record them.

Everybody's iterative journey will look completely different to each other and that is absolutely fine.

So at this point you might want to do some additional research, but that is likely to be very different to the people sat next to you in your classroom.

Have a think, what do you need to find out to help you produce the most successful design solution that you can? This is a great idea for meeting design requirements that you may not have researched previously.

So if your design idea is not quite meeting some of your design requirements, what could you find out to help you enable that to happen? Of course, you are going to make loads of design decisions.

Do not forget to record them and enjoy this part.

Alex says, "I already know what I want to design, and I have drawn the idea and made a cardboard prototype.

I do not need to develop it any further." Is Alex's statement true or is it false? Have a think.

Come back to me when you've got an idea.

Well done if you got false.

And why is that? Well, using a range of iterative methods ensures that you consider all of your design requirements and identify potential problems to solve before you manufacture.

So instead of developing a design solution, you develop a really successful design solution.

On to task B.

Part one, I would like you to identify suitable iterative methods for developing your ideas.

And remember, it is fine if your methods are different to the people in your class.

Part two is the exciting part.

I'd like you to use a variety of methods to develop your ideas and identify potential design decisions.

Now enjoy this part.

This is the part where you are going to create a wonderful and successful design solution.

Enjoy the journey.

For part one, Sofia says, "I have chosen circuit simulations to design a successful circuit for measuring how dry or wet the soil of a plant is using a variety of inputs and outputs." Sam says, "I have chosen prototyping.

I will create multiple prototypes starting in paper, moving to cardboard, and then onto fabric for my collapsible shade for dogs.

I will explore, experiment, and research which fabric might be suitable to use." Those two answers sound completely different and that is absolutely fine.

And so will yours within your classroom too.

Part two, I said use a variety of methods to develop your ideas and identify potential design decisions.

Hopefully you have really, really enjoyed developing your design ideas, but please, I hope that you have remembered to refer back to your design requirements and your primary user and stakeholder opinions when making effective design decisions.

If you haven't, please make sure you go back and you add that in.

Well done with all of your hard work.

That brings us to the end of our lesson today.

Let's summarise what we have found out.

The iterative journey is a process where we refine and improve throughout to develop a successful design solution.

Referring to or measuring against your design requirements ensures you make the correct design decisions.

Effective design decisions, ensure your product or solution is successful.

There are many iterative methods to develop your ideas, including: primary user stakeholder feedback, CAD/CAM/simulation, sketching, prototyping, AI.

Material or process experimentation or research and additional research.

Hopefully, you have and will really enjoy iterating and developing your design ideas.

Enjoy the rest of your iterative design journey and hopefully, I will see you soon take good care.

Bye-bye.