Prototyping Pitfalls

In this session, I discussed what goes wrong when you swap out wireframes and comps for prototypes. Prototypes bring benefits to designers, but introducing them into your process affects everyone else on the team.

Transcript

1. Prototyping Pitfalls Ross Belmont @rossbelmont
2. @rossbelmont
3. @rossbelmont
4. @rossbelmont
5. @rossbelmont
6. @rossbelmont
7. @rossbelmont
8. @rossbelmont
9. @rossbelmont
10. @rossbelmont
11. @rossbelmont
12. @rossbelmont Spend less time tweaking Photoshop comps
13. @rossbelmont
14. @rossbelmont
15. @rossbelmont We crushed it.
16. @rossbelmont
17. @rossbelmont
18. @rossbelmont
19. @rossbelmont
20. @rossbelmont
21. @rossbelmont
22. @rossbelmont Walkthrough (a.k.a. Storyboard)
23. @rossbelmont
24. @rossbelmont Building a prototype is not iterating. =
25. @rossbelmont Building a prototype is not iterating. =
26. @rossbelmont Schedule Time to Iterate: Don’t Do This Sprint 1 Sprint 2 Sprint 3
27. @rossbelmont Schedule Time to Iterate: Do This Instead Sprint 1 Sprint 2 Sprint 3
28. @rossbelmont
29. @rossbelmont
30. @rossbelmont Prototyping Affects Everyone Role Unintended Effect Adjustment Designers • Added stress of hitting tight deadline • Highlighted need to iterate Smarter planning in future phases/projects Clients • Can’t react quickly enough • Want to “shop it around” • Repeated expectation setting • May still need deliverables Project managers • Increases clarity on what will be built • New work to manage Discussion needed to get comfortable with new process (at a minimum) Developers & testers
31. @rossbelmont
32. @rossbelmont
33. @rossbelmont
34. @rossbelmont Some Details Prototypes Don’t Include
35. @rossbelmont Some Details Prototypes Don’t Include • Error states
36. @rossbelmont Some Details Prototypes Don’t Include • Error states • Field validation rules
37. @rossbelmont Some Details Prototypes Don’t Include • Error states • Field validation rules • Back end data specs
38. @rossbelmont Some Details Prototypes Don’t Include • Error states • Field validation rules • Back end data specs • Status codes and their meanings
39. @rossbelmont Some Details Prototypes Don’t Include • Error states • Field validation rules • Back end data specs • Status codes and their meanings • Back end business logic
40. @rossbelmont Some Details Prototypes Don’t Include • Error states • Field validation rules • Back end data specs • Status codes and their meanings • Back end business logic • “Nonfunctional” requirements (e.g. page load times)
41. @rossbelmont • Thing to build • Related thing to build • Another thing to build • Related thing to build • Another thing to build • Final thing to build
42. @rossbelmont Story 1 Story 2 Story 3 • Thing to build • Related thing to build • Another thing to build • Related thing to build • Another thing to build • Final thing to build
43. @rossbelmont
44. @rossbelmont Sprint 1 Sprint 2 Sprint 3
45. @rossbelmont Prototyping Affects Everyone Role Unintended Effect Adjustment Designers • Added stress of hitting tight deadline • Highlighted need to iterate Smarter planning in future phases/projects Clients • Can’t react quickly enough • Want to “shop it around” • Repeated expectation setting • May still need deliverables Project managers • Increases clarity on what will be built • New work to manage Discussion needed to get comfortable with new process (at a minimum) Developers & testers • Doesn’t capture all details needed for build • Confusing when out of date Discussion needed to get comfortable with new process (at a minimum)
46. @rossbelmont
47. @rossbelmont
48. @rossbelmont Thank you! I’m @rossbelmont.