Don't Waste Your Time: Secrets of Minimum Viable Prototyping

Don’t Waste Your Time: Secrets
of Minimum Viable Prototyping
Big (D)esign Conference 2015
@PhilipLikens

@PhilipLikens
Proportional Investment

@PhilipLikens
…and the Minimum Viable
Product.

@PhilipLikens
“The minimum viable product is that version
of a new product which allows a team to collect
the maximum amount of validated learning
with the least eﬀort.”
-Eric Ries

@PhilipLikens
Sometimes you just

need a prototype.

@PhilipLikens
Sabre Labs makes

a lot of prototypes.

@PhilipLikens
And we’ve made a lot of
mistakes.

@PhilipLikens
“A prototype is worth a
thousand meetings.”

@PhilipLikens
“A prototype is worth a
thousand meetings.”
-Ron Burgundy

@PhilipLikens
Thanks Ron. And yes.

@PhilipLikens
…And if the average meeting is
an hour long…

@PhilipLikens
…then I can spend 999 hours on my

pixel-perfect-printed-but-still-paper

prototype and still be in the black?

@PhilipLikens
Don’t waste your time.

@PhilipLikens
The Vision
Prototype 1

@PhilipLikens
Problem: We spent 3 months
building the thing

@PhilipLikens
Make the one thing that
matters high(er) ﬁdelity.
Secret 1:

@PhilipLikens
Type of Prototypes
Conceptual prototype
Work through a design–for designers and
developers, prototypes act as a way to
work through your design…
Technical prototype
Gauge technical feasibility–designers want to
do X, but can engineering do it? Do we have
the resources? Is it worth the effort?
Vision prototype
As a common communication platform–
using them to get everyone on the same
page…
Consensus prototype
Sell your idea internally–using them to sell
your design solution to internal stake
holders…
Demo
As a marketing tool–while similar to number
3, this is for an external audience.
Todd Zaki Warfel / Joe Lamantia

@PhilipLikens
Conceptual prototype
Work through a design–for designers and
developers, prototypes act as a way to
work through your design…
Technical prototype
Gauge technical feasibility–designers want to
do X, but can engineering do it? Do we have
the resources? Is it worth the effort?
Testing prototype?
What you put in front of User Testing folks?
Evolve / Test
Vision prototype
As a common communication platform–
using them to get everyone on the same
page…
Consensus prototype
Sell your idea internally–using them to sell
your design solution to internal stake
holders…
Demo
As a marketing tool–while similar to number
3, this is for an external audience.
Communication

@PhilipLikens
Pick methods based
on outcome.
Secret 2:

@PhilipLikens
Problem: We built the thing

@PhilipLikens
Working code wins
Secret 3:

@PhilipLikens
The Integration
Prototype 2

@PhilipLikens
Problem: Their API

was broken

@PhilipLikens
If you’re testing feasibility,
apply some rigor.
Secret 4:

@PhilipLikens
(again) Working code wins
Secret 3:

@PhilipLikens
Be sure your vision is correct.
Secret 5:

@PhilipLikens
Problem: Scoping

@PhilipLikens
If you’re setting vision, build only what
you need to tell your story (happy path).
Secret 6:

@PhilipLikens
(again) Make the one thing that
matters high(er) ﬁdelity.
Secret 1:

@PhilipLikens
Our
Product
Other
Product
Auth Auth

@PhilipLikens
Our
Product
Auth
Screenshot
with button
Other
Product
Auth

@PhilipLikens
Our
Product
Auth
Screenshot
with button
Error States
Sign Up
Other
Product
Auth

@PhilipLikens
The Web App
Prototype 3

@PhilipLikens
Problem: The ﬁdelity lead to the
wrong conversation

@PhilipLikens
High ﬁdelity != Low ﬁdelity
Secret 7:

@PhilipLikens
Problem: Platform lead to the
wrong interaction

@PhilipLikens
Platforms dictate interactions.
Secret 8:

@PhilipLikens
The design is the implementation.
Secret 9:

@PhilipLikens
The Product
Prototype 4

@PhilipLikens
Problem: It took up

too much time

@PhilipLikens
Your prototype is like wedding planning
- it will take as long as you give it.
Secret 10:

@PhilipLikens
Problem: We built functionality
we didn’t need

@PhilipLikens
Talking about the outcome allows
for better scope conversations.
Secret 11:

@PhilipLikens
Apple Watch
Prototype 5

@PhilipLikens
Problem: Impossible

@PhilipLikens
Ensure what you’re designing
is possible.
Secret 12:

@PhilipLikens
Design at actual (tiny) size.
Secret 13:

@PhilipLikens
This Presentation
Prototype 6

@PhilipLikens
Don’t waste your time…
Building the wrong type of prototype
2. Pick methods based on outcome.

3. Working code wins

7. High ﬁdelity != Low ﬁdelity

8. Platforms dictate interactions.

@PhilipLikens
“Building” beyond the minimum
1. Make the one thing that matters high(er) ﬁdelity.

6. If you’re setting vision, build only what you
need to tell your story (happy path).

10. Your prototype is like wedding planning - it
will take as long as you give it.

11. Talking about the outcome allows for better
scope conversations.

@PhilipLikens
Applying rigor in the wrong places
4. If you’re testing feasibility, apply some rigor.

5. Be sure your vision is correct.

9. The design is the implementation.

12. Ensure what you’re designing is possible.

13. Design at actual (tiny) size.

@PhilipLikens
You stay classy, Dallas.

@PhilipLikens
1. Make the one thing that matters high(er) fidelity.

2. Pick methods based on outcome.

3. Working code wins

4. If you’re testing feasibility, apply some rigor.

5. Be sure your vision is correct.

6. If you’re setting vision, build only what you need to tell your story (happy path).

7. High fidelity != Low fidelity

8. Platforms dictate interactions.

9. The design is the implementation.

10. Your prototype is like wedding planning - it will take as long as you give it.

11. Talking about the outcome allows for better scope conversations.

12. Ensure what you’re designing is possible.

13. Design at actual (tiny) size.
Secrets of Minimum Viable Prototyping

Don't Waste Your Time: Secrets of Minimum Viable Prototyping

More Related Content

Don't Waste Your Time: Secrets of Minimum Viable Prototyping