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 as designers produce effective evaluations that lead to successful modifications throughout our whole iterative journey? So hard hats on, let's get cracking.

Our outcome for today is we will be able to identify modifications informed by evaluation.

We have four keywords today.

Evaluation, which means judgments based on testing findings.

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

Design decisions, a deliberate choice to meet a requirement or solve a problem.

And lastly, modifications, which is making changes or adjustments to improve.

We have two learning cycles for our lesson today.

First of all, "Evaluation," and then leading on to "Modifications." So let's get cracking with "Evaluation." The big picture for our iterative journey today is we are going to understand the importance of evaluation, not just at the end, but throughout our whole iterative journey.

We're also going to explore how evaluation can identify modifications, again, throughout our iterative journey.

So let's put a bit more context to that.

Design decisions lead to lots of incremental, so tiny, modifications throughout your iterative journey to develop your successful design solution, whereas final modifications after manufacture are suggestions for future manufacture.

Basically, the ones after manufacture are kind of like design decisions that you don't have time to implement.

They're just more suggestions.

Evaluations are judgments based on the findings of testing.

Let's remind ourselves, testing measures against design requirements and manufacturing specifications.

Therefore, those judgements have to also revert back to design requirements and manufacturing specifications.

Evaluation is required throughout the iterative journey to ensure that successful design decisions are continually made and a successful design solution is developed.

Let's put this into a diagram to explain it a little bit more.

So we have testing.

Testing is always followed by evaluation, and then the evaluation informs your design decisions.

Now this can happen multiple times.

This can happen within your design ideas, within your design development, throughout your manufacture.

So this can happen lots and lots of times, there is not a set amount.

But hopefully the more that this happens, the more successful the final design solution is.

Quick check-in.

Evaluations are judgments based on the findings of, A, design decisions; B, a manufacturing specification; C, modifications; or D, testing.

Have a little think, come back to me when you've got an answer.

Well done if you got testing.

Evaluations are judgments based on the findings of testing.

You've got to have something substantial to be able to create that judgement , and that is the testing.

Evaluation throughout the iterative journey can be presented in many different ways.

For example, you could have a comparison chart, or you could use annotations, or you could use a mixture of both or your own methods.

Evaluation after manufacture in school informs final modifications.

So once your design solution has been manufactured, you then test it again, but this time you've got your final prototype.

You therefore evaluate based on that testing, and that leads to your final suggestions for modifications, but these are the ones that you might not have time to fully make.

Lucas chose to collate his evaluations against his design requirements.

Great idea, Lucas.

Let's zoom into one.

He says, "The primary user tested a variety of jar lids and commented that the cone-shaped feature allows multiple size lids to be opened easily without needing to adjust the product to fit.

This meets the design requirement and shows a successful feature." Let's take that in a little bit more detail.

First of all, he refers to his testing findings.

He then refers to his design requirement.

And lastly, he makes a judgement , saying that it is a successful feature.

Therefore, Lucas, that is an effective evaluation.

Lucas then goes in to zoom into another requirement, and he says, "Having chosen three stakeholders to test the prototype with dry and wet hands, all stakeholders agreed that the handle fit perfectly into the shape of the hand and was comfortable to hold.

However, when wet, it was slippery to use.

This shows that the shape of the handle meets the design requirement, but the material used is not suitable and does not meet the second part of this design requirement." Now this is an effective evaluation because, first of all, it refers to his testing findings.

He tried it, didn't he, with three of his stakeholders, and he got them to try it with dry and wet hands.

He also referred to the requirements, the design requirements.

And then lastly, he made a judgement.

So the judgement was obviously with dry hands it was perfect, but with wet hands it proved that it was not suitable and did not meet that part of the design requirement.

Please don't worry if your design solution doesn't fulfil all of your design requirements.

It just then gives you something to be able to modify.

Time for a quick check-in.

Sofia says, "Evaluation is only carried out once the design solution has been manufactured." Is this statement true or false? Have a think, come back to me when you've got an answer.

Well done if you got false, and why is that? Evaluation is required throughout the whole iterative journey to ensure that successful design decisions are made and a successful design solution is developed.

Evaluation after manufacture informs final modifications.

Task A, part one.

I'd like you to define evaluation.

Part two, identify the stage that should inform an evaluation.

And part three, explain the importance of carrying out evaluations, firstly throughout the iterative journey, and secondly, after manufacture.

Good luck, come back to me when you've got some answers.

Onto feedback, so answers for part one could include evaluations are judgments based on the findings of testing.

Part two, testing should inform your evaluations to make them successful judgements.

And part three, evaluation is required throughout the iterative journey to ensure that successful design decisions are made and a successful design solution is developed.

Evaluation after manufacture in school informs final suggested modifications.

Onto learning cycle two, which is "Modifications." We're now going to use our evaluations, our successful evaluations, to create successful modifications.

Modifications enable products to improve.

So for example, UK law has modified plastic use by shifting from wasteful to eco-friendly alternatives.

You may have seen that some fruit packaging is shifting from polymers over to cardboard, and that's great as an eco-friendly alternative.

You may have noticed that some shops are now providing 100% compostable polymer bags rather than the wasteful alternatives.

Let's take a look at mobile phones.

Now you may not remember the phone on the left.

I do.

Look at the screen size of that.

So, modifications over time include larger screens for better usability, faster processors and better cameras.

Without modifications, products would not improve.

Modifications will happen throughout the whole iterative design journey, but final modifications should naturally develop from evaluations after manufacture.

Now these final suggested modifications are suggestions and do not need to be manufactured.

You don't at the end have to make your whole prototype again.

So Lucas chose to refer, return, sorry, to his evaluations to help produce his final suggested modifications.

So, as we saw in learning cycle one, Lucas asked three stakeholders to test his prototype, firstly with dry hands and then with wet hands.

All the stakeholders agreed that the handle was slippery to use when it was wet.

So Lucas says, "I asked them whether a grip, for example, a silicon grip, would benefit the design.

They all agreed, therefore this would be an effective modification." Lucas didn't just pluck that out of thin air, Lucas got that modification from his evaluation, and that is how to make successful modifications.

Evaluations will identify many ideas for modifications.

For example, materials, manufacture, aesthetics, safety, technology, and ergonomic.

Now, this isn't an absolute final list, your evaluations might identify many other areas, but this just shows the broad range of modifications and things that you might need to think about from your evaluations.

Successful modifications, suggest an improvement, are justified, so provide a why, and originate from evaluations.

Therefore, if they originate from evaluations, they need to relate to the testing because the testing informs the evaluation.

Therefore, it's got to have primary user, stakeholder, or expert opinions in that.

And it needs to address design requirements.

Quite a lot to consider there to make a successful modification.

Again, you can't just pluck it out of thin air.

It needs to have some substance.

Time for a check-in.

Successful modifications, A, are generated by your own thoughts only; B, address design requirements; C, address primary user, stakeholder, or expert opinions; and D, provide justification.

Have a think, come back to me when you've got an answer.

Well done if you've got B, C, and D.

Successful modifications address design requirements, address primary user, stakeholder, expert opinions, and provide the why, the justification.

Suggested final modifications can be presented using a variety of methods, including explanations, sketches, CAD drawings or simulations, scale prototypes and tables or charts.

Again, you might think of your own way and that is absolutely fine too.

Lucas chose to present his modifications as sketches with annotations, so let's zoom into one of his annotations.

He said, "Silicon with raised indentations will allow for grip when hands are wet.

This is important in a kitchen when hands are frequently washed and wet.

The flexibility of silicon creates extra comfort in the handle." Presented beautifully, Lucas.

So is Lucas's modification that we've just read out on the previous slide successful? Let's take the criteria for successful modifications that we saw a couple of slides ago.

First point says, "Suggest an improvement." Well, yes, he does that.

He suggests silicon with raised indentations for extra comfort.

Next point is, is it justified? Yes, because he says hands are frequently washed and wet, therefore it's going to need some type of grip.

Next point says, "Originate from evaluations." Well, yes, we know that because when we first saw Lucas's evaluation, he had asked three stakeholders to test the prototype and all stakeholders agreed that the handle was slippery to use.

Therefore, it comes from his evaluation.

It uses his stakeholder opinions and it relates to the testing.

And then lastly, you can see it does obviously address his design requirement, as he makes quite clear.

Therefore, this is a successful modification.

Well done, Lucas.

Remember, you can use that success criteria to return to when you are producing your own modifications.

Izzy chose to use CAD with annotations to present her modifications.

Izzy says, "Comfort was identified in testing as a weak point.

Creating a sloping back, with a slot to enable a custom padded cushion to be inserted, will provide comfort when sitting for a long time." And you can see all of these images here clearly show that modification being added to her design.

This is a really great way to visually explain your modifications.

And again, look at how that has come from testing.

Well done, Izzy.

Laura decided to present her modifications using simulations with annotations.

She says, "The primary user identified that they would like to be able to turn this circuit off when they go on holiday, so a switch will be added to override the LDR when required." Great idea, Laura, and again, that she hasn't plucked that out of thin air.

She has used her testing with the results from her primary user to inform this modification.

I have not used CAD to manufacture my product, so I cannot present my modifications using CAD.

Is this 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? You can be creative with the methods or techniques that you use to present your modifications, and you are welcome to use more than one method.

Onto Task B.

Part one, I'd like you to explain how final modifications could be successful.

And then part two, identify modifications for your own final prototype.

Good luck, come back to me when you've got some great answers.

Answers could include successful modifications suggest an improvement, are justified and originate evaluations.

Therefore, if they originate from evaluations, they must relate to your testing.

If they relate to your testing, your primary user, stakeholder, or expert opinions should appear in there.

And lastly, but not by means of least, they must of course address design requirements.

Part two, identify modifications for your final prototype.

Hopefully you started with your own evaluations and followed the suggestions above to identify modifications suitable for your own iterative journey.

Well done with all of your hard work.

This brings us to the end of our lesson today.

Let's summarise what we have found out.

Evaluations are judgements based on the findings of your testing.

Evaluation is required throughout the iterative journey to ensure successful design decisions.

Evaluation after manufacture in school informs modifications, final modifications.

Successful modifications, therefore, suggest an improvement, are justified, originate from evaluations.

And if they originate from evaluations, they must relate to testing.

With testing, that must relate to primary user, stakeholder or expert opinions, and they must address design requirements.

I'd like to take this opportunity to say real well done for all of your efforts along your iterative design journey.

Take good care and hopefully see you in a lesson soon.

Bye bye bye.