prototyping pitfalls

Post on 09-Aug-2015

81 Views

Category:

Design

0 Downloads

Preview:

Click to see full reader

TRANSCRIPT

Prototyping PitfallsRoss Belmont

@rossbelmont

@rossbelmont

@rossbelmont

@rossbelmont

@rossbelmont

@rossbelmont

@rossbelmont

@rossbelmont

@rossbelmont

Spend less time tweaking Photoshop comps

@rossbelmont

@rossbelmont

We crushed it.

@rossbelmont

@rossbelmont

@rossbelmont

@rossbelmont

@rossbelmont

Walkthrough (a.k.a. Storyboard)

@rossbelmont

@rossbelmont

Building a prototype is not iterating.

=

@rossbelmont

Building a prototype is not iterating.

=

@rossbelmont

Schedule Time to Iterate: Don’t Do This

Sprint 1 Sprint 2 Sprint 3

@rossbelmont

Schedule Time to Iterate: Do This Instead

Sprint 1 Sprint 2 Sprint 3

@rossbelmont

@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

@rossbelmont

@rossbelmont

@rossbelmont

Some Details Prototypes Don’t Include

@rossbelmont

Some Details Prototypes Don’t Include• Error states

@rossbelmont

Some Details Prototypes Don’t Include• Error states

• Field validation rules

@rossbelmont

Some Details Prototypes Don’t Include• Error states

• Field validation rules

• Back end data specs

@rossbelmont

Some Details Prototypes Don’t Include• Error states

• Field validation rules

• Back end data specs

• Status codes and their meanings

@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

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

@rossbelmont

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

@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

@rossbelmont

Sprint 1 Sprint 2 Sprint 3

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

@rossbelmont

Thank you! I’m @rossbelmont.

top related