prototyping pitfalls

48
Prototyping Pitfalls Ross Belmont @rossbelmont

Upload: ross-belmont

Post on 09-Aug-2015

81 views

Category:

Design


0 download

TRANSCRIPT

Page 1: Prototyping pitfalls

Prototyping PitfallsRoss Belmont

@rossbelmont

Page 2: Prototyping pitfalls

@rossbelmont

Page 3: Prototyping pitfalls

@rossbelmont

Page 6: Prototyping pitfalls

@rossbelmont

Page 7: Prototyping pitfalls

@rossbelmont

Page 8: Prototyping pitfalls

@rossbelmont

Page 9: Prototyping pitfalls

@rossbelmont

Page 10: Prototyping pitfalls

@rossbelmont

Page 12: Prototyping pitfalls

@rossbelmont

Spend less time tweaking Photoshop comps

Page 14: Prototyping pitfalls

@rossbelmont

Page 15: Prototyping pitfalls

@rossbelmont

We crushed it.

Page 17: Prototyping pitfalls

@rossbelmont

Page 18: Prototyping pitfalls

@rossbelmont

Page 19: Prototyping pitfalls

@rossbelmont

Page 21: Prototyping pitfalls

@rossbelmont

Page 22: Prototyping pitfalls

@rossbelmont

Walkthrough (a.k.a. Storyboard)

Page 23: Prototyping pitfalls

@rossbelmont

Page 24: Prototyping pitfalls

@rossbelmont

Building a prototype is not iterating.

=

Page 25: Prototyping pitfalls

@rossbelmont

Building a prototype is not iterating.

=

Page 26: Prototyping pitfalls

@rossbelmont

Schedule Time to Iterate: Don’t Do This

Sprint 1 Sprint 2 Sprint 3

Page 27: Prototyping pitfalls

@rossbelmont

Schedule Time to Iterate: Do This Instead

Sprint 1 Sprint 2 Sprint 3

Page 29: Prototyping pitfalls

@rossbelmont

Page 30: Prototyping pitfalls

@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

Page 31: Prototyping pitfalls

@rossbelmont

Page 33: Prototyping pitfalls

@rossbelmont

Page 34: Prototyping pitfalls

@rossbelmont

Some Details Prototypes Don’t Include

Page 35: Prototyping pitfalls

@rossbelmont

Some Details Prototypes Don’t Include• Error states

Page 36: Prototyping pitfalls

@rossbelmont

Some Details Prototypes Don’t Include• Error states

• Field validation rules

Page 37: Prototyping pitfalls

@rossbelmont

Some Details Prototypes Don’t Include• Error states

• Field validation rules

• Back end data specs

Page 38: Prototyping pitfalls

@rossbelmont

Some Details Prototypes Don’t Include• Error states

• Field validation rules

• Back end data specs

• Status codes and their meanings

Page 39: Prototyping pitfalls

@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

Page 40: Prototyping pitfalls

@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)

Page 41: Prototyping pitfalls

@rossbelmont

• Thing to build • Related thing to build• Another thing to build • Related thing to build• Another thing to build • Final thing to build

Page 42: Prototyping pitfalls

@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

Page 44: Prototyping pitfalls

@rossbelmont

Sprint 1 Sprint 2 Sprint 3

Page 45: Prototyping pitfalls

@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)

Page 48: Prototyping pitfalls

@rossbelmont

Thank you! I’m @rossbelmont.