Week 12 Guide: Final Presentation
The Real Problem This Solves
Good work that you cannot explain loses to weaker work that is presented well. Presenting is a design skill: you shape the story for a listener, make your reasoning clear, and answer questions honestly. This is your final deliverable and the close of the programme.
Key Ideas You Need First
1. Lead with the problem, not the object
Open with the real problem and who had it. A listener cares about your solution only once they feel the problem.
2. Tell the story in the order you lived it
Problem, research, idea, test, improve, result. This arc is easy to follow and shows your thinking.
3. Show evidence, not adjectives
Do not say the design is good. Show the test result that proves it. Evidence persuades, adjectives do not.
4. Rehearse out loud
Reading in your head hides the rough parts. Say it aloud at least twice and time it.
Tools And Materials Needed
- Your Week 11 case study.
- The Final Presentation Checklist.
- The Programme Reflection Form.
- One listener, and a phone to film if presenting remotely.
Step-By-Step Walkthrough
- Draft a five-minute structure. One minute problem, two minutes process and testing, one minute result, one minute reflection.
- Pick one strong image per stage. Do not crowd your slides or hold up every artefact.
- Write your opening and closing lines. A clear first sentence and a clear last sentence carry a lot.
- Rehearse twice, out loud, timed. Cut anything that runs over or does not earn its place.
- Present to one person. Ask them to hold questions to the end.
- Gather feedback on communication. Ask what was clear and what was not, about your delivery, not just the work.
- Complete the reflection form. What you learned, your strengths, and your next steps.
Demonstrated Example
Opening line: "Students who share a desk lose the first twenty minutes of every session just clearing space. I set out to get that time back."
Middle: research showed setup time was the real cost; twenty-two ideas led to a roll-up mat; testing found sliding tools and a slow tie; iteration fixed both.
Result with evidence: "In the final test it packed away in eighteen seconds, down from over a minute."
Closing line: "The biggest lesson was that watching people struggle taught me more than any sketch. Next I want to test it with ten more students."
Why this is strong: it leads with the problem, follows the real arc, proves the result with a number, and closes with an honest, forward-looking reflection.
Your Task This Week
- Build and rehearse a five-minute presentation of your project.
- Present it to one person and gather feedback on your communication.
- Record a short video of your walkthrough, or submit your slides.
- Complete the programme reflection and next-steps plan.
Submission Checklist
| Upload item | Pass standard |
|---|---|
| Presentation video or slides | Clear five-minute story: problem, process, result, reflection. |
| Reflection form | Specific on learning, strengths, and next steps. |
| Communication feedback | A note on what a listener found clear or unclear. |
Assessment And Pass Criteria
- The presentation leads with the problem and follows the design arc.
- Claims are backed by evidence, not adjectives.
- It is rehearsed and roughly to time.
- The reflection is specific and includes a realistic next step.
Common Mistakes
- Opening with the object. Set up the problem first.
- Reading every slide word for word. Speak to the listener.
- Claiming "it works" with no proof. Show the test result.
- No rehearsal. It always shows.
- Overpromising in the reflection. Keep next steps realistic and honest.
Extension Challenge
Record a thirty-second version of your pitch. If you can tell the story well in thirty seconds, the five-minute version will be sharp.