Final Presentation
Last updated
Last updated
Final Presentation
Before the final presentation, make sure that the report covers the questions agreed on during the sprint. It should honestly represent the feedback of the users and give the client confidence when developing the product and shipping it to market.
The final presentation is a one-hour meeting to present the results and answer any questions. Reveal the results with confidence. Remember that this is the first glance for the client to see their product and learn about how it works. Here's an example:
Friends! It was an incredible week! And we have something really cool for you. In the next hour we will show you the prototype we created together and [the designers] designed, [the user researcher] will tell you how your users liked it and explain to you what that means for the product.
Final presentation structure:
| Presentation order | What to present? | Time cap |
|---|---|---|
After the above, they can ask questions and think that the session is over.
Right before concluding the call, present the open source case studies and documentation with all resources and workflows accessible for free. Explain that we encourage them to re-use the design files, learn from user research of other projects and experiment with workflows on their own. If they need advice, we're available on Discord.
1. Facilitator
Reiterate what the team has decided on during the workshops.
3 minutes
2. Product Designer
User-tested prototype with narration on the creative decisions.
10-15 minutes
3. User Researcher
Minor issues (Quick Fixes) and high-level strategic recommendations.
15-20 minutes
4. Product Designer
Prototype with the Quick Fixes included.
2 minutes