Design Documentation

How, When, and Why should you document your design

Transcript

1. Design Documentation Facilitated by Thelma Dike Presentation for Treford Bootcamp
2. Thelma Dike - Product designer, data at softcom. - I enjoy taking pictures of nature and arts.
3. Brief Introduction to what Product design is
5. Let’s become more practical
6. This is Lanre - He’s a designer. - He has 2 designers on his team. - And has been asked to design a mobile app to help with international payment and investments
7. Lanre informs his team, and they get started by carrying out stakeholder interviews.
9. Every designer goes to their desks and does their work individually and locally.
10. Before the design phase started, Lanre was moved to another project, Seun was now asked to take over.
12. Seun is clueless about everything, and doesn’t know where to start
13. Now, imagine that at every phase of the design process, their thoughts & decisions were recorded.
14. This brings us to why we’re here
15. Design Documentation What is is, why we should do it & How it should be done.
16. The process of taking snapshots of your thoughts & decisions at every given time. What’s design documentation?
17. Why should we document?
18. Communicate & collaborate effectively. Why we should document
19. Present your team in the lime-light. Why we should document
20. Gain clarity with stakeholders. Why we should document
21. How should we document?
22. Documentation should be done during every phase of the design cycle.
23. Research phase Empathize and define
24. Answer the WHAT, WHO, WHY questions. What happens here
25. What to documents Product overview, requirements & deadlines.
26. Tools to use Notion, Dropbox paper, Google docs.
27. What else to document Surveys, User interviews, User stories, User Flows
28. Tools to use Miro, Google drive, whimsical, Google forms.
29. Design phase Ideate and Prototype
30. Sketch ideas, create wireframes, styleguide, Lo-fi & Hi-Fi designs. What happens here
31. Miro, Sketch, Figma, SketchPad, Paper & Pen, Stickers. Tools to use
32. Testing phase Testing and Iterate
33. Test your solutions with potential users, get feedback and iterate. What happens here
34. Figma prototype, Invision, Principle, Lookback, Dovetail, Zoom. Tools to use
35. Things to note while carrying out your documentation.
36. Ensure your documentation is usable for your target audience. Things to note
37. Update your documentation when changes are made. Things to note
38. Be brief and straight to the point. Things to note
39. Add images where necessary Things to note
40. Thank you! dikethelmak