Dont be a tool
•
2 likes•291 views
The document discusses various methods and tools for designing systems and prototypes quickly, including: 1. Agile and lean methodologies that emphasize iterative design, minimum viable products, and customer feedback. 2. Design sprints, which are 5-day events to solve problems through research, solution generation, prototyping, and user testing. 3. The importance of design systems to create reusable components and quickly build high-fidelity prototypes. 4. Different types of design and prototyping tools that can help implement the above methods, including graphic tools, prototyping tools, and tools to record user testing sessions.
Report
Share
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (9)
Similar to Dont be a tool
Similar to Dont be a tool (20)
Recently uploaded
Recently uploaded (20)
Dont be a tool
- 1. use the right tools DON’T BE A TOOL
- 3. Methods1 The ultra brief walkthrough of iterative design methods
- 5. Doesn’t work well with rapid changes or complex projects Methods1 Waterfall
- 6. When to use an agile approach Methods1 Anarchy aka Crazytown Simple Complicated Complex Humans Technology Requirements Close to certainty Far from certainty FarfromagreementClosetoagreement Agile
- 8. Methods1 Agile manifesto Individuals and interactions Working software over processes and tools over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
- 9. Methods1 Agile UX Agile UX describes update of Agile Software Methodology with UX Design methods.
- 10. Methods1 Agile UX The ultimate goal of Agile UX is to unify developers and designers in the Agile process of product development.
- 11. Methods Lean1 Specify value Establish flowImplement pull 1 Map the value stream2 34 Work to perfection 5
- 12. Methods1 Lean Startup Ideas CodeData Minimum ❤ Product Build Measure Learn Unit tests Continous integration Incremental deployment Usabilty tests Split tests, Funnel analysis, Cohort analysis, NPS. Analysis results Interviews Hypotheses validation
- 13. Methods1 Lean UX Ideas PrototypeTesting Minimum ❤ Product Build Measure Learn Sketches Wireframes Prototypes Code Split tests, Funnel analysis, Cohort analysis, NPS. Interviews Hypotheses validation
- 14. Methods1 Design Sprints Solve big problems and test new ideas in just five days Google ventures http://www.gv.com/sprint/
- 15. Methods1 Design Sprints Monday Tuesday Wednesday Thursday Friday Role definitions Long-term goal Sprint questions Maping / Flowchart Asking experts How Might We notes Pick a target
- 16. Methods1 Design Sprints Monday Tuesday Wednesday Thursday Friday Role definitions Long-term goal Sprint questions Maping / Flowchart Asking experts How Might We notes Pick a target Lightning demos Four-step sketching
- 17. Methods1 Design Sprints Monday Tuesday Wednesday Thursday Friday Role definitions Long-term goal Sprint questions Maping / Flowchart Asking experts How Might We notes Pick a target Lightning demos Four-step sketching Chose solutions Storyboard
- 18. Methods1 Design Sprints Monday Tuesday Wednesday Thursday Friday Role definitions Long-term goal Sprint questions Maping / Flowchart Asking experts How Might We notes Pick a target Lightning demos Four-step sketching Chose solutions Storyboard Chose the right tools Assign roles Prototype
- 19. Methods1 Design Sprints Monday Tuesday Wednesday Thursday Friday Role definitions Long-term goal Sprint questions Maping / Flowchart Asking experts How Might We notes Pick a target Lightning demos Four-step sketching Chose solutions Storyboard Chose the right tools Assign roles Prototype User testing Record interviews Review sprint
- 20. Methods1 Design Sprints Monday Tuesday Wednesday Thursday Friday Role definitions Long-term goal Sprint questions Maping / Flowchart Asking experts How Might We notes Pick a target Lightning demos Four-step sketching Chose solutions Storyboard Chose the right tools Assign roles Prototype User testing Record interviews Review sprint Research and solution searching by hand drawing All know what to build and test
- 21. Methods1 Design Sprints Monday Tuesday Wednesday Thursday Friday Role definitions Long-term goal Sprint questions Maping / Flowchart Asking experts How Might We notes Pick a target Lightning demos Four-step sketching Chose solutions Storyboard Chose the right tools Assign roles Prototype User testing Record interviews Review sprint Research and solution searching by hand drawing All know what to build and test
- 22. Methods1 Design Sprints Prototype mindset Prototype are disposable. Build just enough to learn, but not more
- 23. Methods1 Design Sprints Goldilocks quality The prototype must appear real as possible. Create a prototype with just enough quality to evoke honest reactions from customers.
- 24. Methods1 Design Sprints An real as possible prototype in one day. How can we get there?
- 26. Design systems2 In order to quickly mock up something in high fidelity, we need to have a design system
- 27. Design systems2 So we don’t spend too much time on elements that just are scenery around the solution we are testing
- 28. Design systems2 So what is a design system?
- 33. Design systems2 Build your own Bootstrap http://keynotopia.com/bootstrap/
- 34. Design systems2 Atomic design http://bradfrost.com/blog/post/atomic-web-design/
- 35. Design systems2 What tool should be for this?
- 37. Tools3 Overview Graphic tools Craft by InVision Prototyping tools In between tools
- 38. Tools3 Overview
- 39. Tools3 Future of design tools https://medium.com/sketch-app-sources/designing-with-meaningful-data-5456b40e172e#.oaxvp9oc0
- 40. Tools3 Focus on tools Graphic tools Craft by InVision Prototyping tools Recording usertests In between tools