Don’t Waste Your Time: Secrets of Minimum Viable PrototypingUXPA 2015 Unconference @PhilipLikens
@PhilipLikens
Thank you all.
@PhilipLikens
Thank you Lean Startup for the idea of proportional investment…
@PhilipLikens
…and the Minimum Viable Product.
@PhilipLikens
But 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.”
-Ron Burgundy
@PhilipLikens
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
No.
@PhilipLikens
Don’t wast your time.
@PhilipLikens
Building the wrong type of prototype
Don’t waste your time…
@PhilipLikens
Fidelity.
@PhilipLikens
We all know, Low fidelity prototype = Higher level feedback
High fidelity prototype = Nit-picky pixel-shifting
@PhilipLikens
Feedback matters…
@PhilipLikens
And so does fidelity…
@PhilipLikens
But our framing wrong.
@PhilipLikens
Type of PrototypesConceptual prototypeWork through a design–for designers and developers, prototypes act as a way to work through your design…
Technical prototypeGauge technical feasibility–designers want to do X, but can engineering do it? Do we have the resources? Is it worth the effort?
Vision prototypeAs a common communication platform–using them to get everyone on the same page…
Consensus prototypeSell 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
Pick methods based on outcome.
Secret 1:
@PhilipLikens
CommunicationConceptual prototypeWork through a design–for designers and developers, prototypes act as a way to work through your design…
Technical prototypeGauge technical feasibility–designers want to do X, but can engineering do it? Do we have the resources? Is it worth the effort?
Vision prototypeAs a common communication platform–using them to get everyone on the same page…
Consensus prototypeSell 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.
Evolve / Test
@PhilipLikens
So let’s say you do choose the right prototype for the outcome…
@PhilipLikens
“Building” beyond the minimumDon’t waste your time…
@PhilipLikens
Sometimes you can use paper.
@PhilipLikens
Sometimes you need to use code.
@PhilipLikens
For example.
@PhilipLikens
Sabre Product
Product we all Love
Auth Auth
@PhilipLikens
The integration is the thing
@PhilipLikens
Make the one thing that matters high(er) fidelity.
Secret 2:
@PhilipLikens
Sabre Product
Product we all Love
Auth Auth
@PhilipLikens
Sabre Product
Product we all Love
Auth AuthScreenshot with button
@PhilipLikens
Outcomes.
@PhilipLikens
Vision: How could these products interact
@PhilipLikens
Technical: Viability of the integration
@PhilipLikens
If you’re setting vision, build only what you need to tell your story (happy path).
Secret 3:
@PhilipLikens
Sabre Product
Product we all Love
Auth AuthScreenshot with button
Error States Sign Up
@PhilipLikens
That’s the minimum to tell the story.
@PhilipLikens
If you’re testing feasibility, apply some rigor.
Secret 4:
@PhilipLikens
Applying rigor in the all the wrong places
Don’t waste your time…
@PhilipLikens
We often say in the lab “working code wins.”
@PhilipLikens
We didn’t build out the whole integration.
@PhilipLikens
We thought they had an awesome API.
@PhilipLikens
We fixed a bug in their API.
@PhilipLikens
And learned this integration may not be as smooth as we thought.
@PhilipLikens
And that’s good enough for now.
@PhilipLikens
So that’s technical rigor. What about design rigor?
@PhilipLikens
Ensure what you’re designing is possible.
Secret 5:
@PhilipLikens
This may mean you dig through technical documentation.
@PhilipLikens
APIs
@PhilipLikens
Design constraints
@PhilipLikens
Or you sketch wireframes at actual size.
@PhilipLikens
Going back to our example…
@PhilipLikens
From a design perspective.
@PhilipLikens
The goals of the other company had changed since I had looked.
@PhilipLikens
And no one else had looked.
@PhilipLikens
Time and time again
@PhilipLikens
Applying “just enough” rigor has saved my…
@PhilipLikens
Reputation.
@PhilipLikens
Finally,
@PhilipLikens
The most important secret to Minimum Viable Prototyping
is simply to have…
–Meghan Trainor
“…all the right junk in all the right places.”
@PhilipLikens
Thank you for being a part of my Minimum Viable (conference)
Presentation.
@PhilipLikens
Do the Minimum: • Make the one thing that matters high(er) fidelity. • If you’re setting vision, build only what you need
to tell your story (happy path). Be sure it’s Viable: • If you’re testing feasibility, apply some rigor. • Ensure what you’re designing is possible. Choose the right type of Prototype: • Pick methods based on outcome.