Page 1
It’s the Experience That Makes the Product, Not the Features.
Putting experience first from the MVP on up.
#experiencefirst @smack416 at @yousayyeah
Page 2
Let’s talk product.
Page 3
Features, therefore product.
Page 4
Engineering only products consistently fail.
Page 5
Just because something functions doesn’t mean it serves a purpose.
Page 6
“When we started talking to our customers and seeing how they used our service, it was the defining moment of success that turned the company around.”
Joe Gebbia, AirBnB @jgebbia
Page 7
User-centred design leads to better products.
Page 8
The rise of the MVP.
Photo by Kristina Servant
Page 9
Minimum Viable
ProductPhoto by Kristina Servant
Page 10
An MVP is anything you can get to market quickly and easily to prove your product’s viability.
Page 11
MVP doesn’t necessarily mean code.
Page 12
MVP does mean high-touch customer engagement.
Page 13
You need to: Find your market. Find your advocates.
Page 14
Video.
Concierge MVP.
Landing page.Newsletter.Prototype.Above all, experiment.
Page 15
Wash’n’fold concierge MVP.
Page 16
Kipu beta signup.
Page 19
Kipu features page.
Page 20
Buffer product MVP.
Page 21
Buffer price MVP.
Page 22
An MVP is a tool for turning questions into answers.
Page 23
You can’t improve without user insight.
Page 24
Get to market early and often to gain insight.
Page 25
“Shipping is a feature.” John Gruber
@gruber
Page 26
Features are a distraction.
Page 27
Features are a distraction for you.
Page 28
Features are a distraction for your users.
Page 29
So how do you decide which features to add?
Let’s look at 6 considerations.
Page 30
Does the feature add clarity to the core purpose of the product?
Page 31
Will the feature delight your users, adding unexpected value?
Page 32
Will the feature be used often?
Page 33
Will the feature be difficult to ship?
Page 34
Will users understand the feature?
Page 35
Will users talk about the feature?
Page 36
“Product/market fit means being in a good market with a product that can satisfy that market.”
Marc Andreessen@pmarca
Page 37
Construction app Bridgit, conducted 500 interviews at construction sites.
Page 38
Zappos began with no inventory.
Page 39
“In a startup no facts exist inside the building, only opinions.”
Steve Blank@sgblank
Page 40
Dropbox lessons learned.From CEO Drew Houston’s slide deck.
Page 41
Deliver an experience.
Photo by Everett Mar
Page 42
Define the core user need.Make a product that meets just that need in a delightful way.
Page 43
“I wanted to take the scheduling feature of many Twitter clients and apps and make that single feature awesome.”
Joel Gascoigne, Buffer CEO@joelgascoigne
Page 44
Think in terms of benefits, not features.
Page 45
4 clicks to auto schedule a message to a single account.
Page 46
1 click to auto schedule a message to four accounts.
Page 47
Features are a distraction from defining and measuring experience.
Page 48
Do less better.
Photo by Mr.TinDCCupcake vs Dry Cake model from Brandon Schauer, Adaptive Path
Page 49
Photo by Don Buciak II
Think big.
Page 50
Start small.
Photo by Gurjot Bhuller
Page 51
Not big and dull.
Photo by Carrie Grayson
Page 52
Photo by Ree Roebeck
And definitely not this.
Page 53
Experience every step of the way.
From Henrik Kniberg
Page 54
The simplicity of Hyperlapse.
Page 55
No user accounts. No video editing. No file manager. iOS only.
Page 56
Simple, but magical.
Page 57
But how do we get there?
Page 58
Experience is holistic.
Page 59
Experience goes well beyond the product.
Page 60
Customer expectations.
Marketing.Support.And so much more.
Page 61
But even focusing just on the product, experience is the sum of so many parts.
Page 62
Your product’s purpose.
The value to your users.Ease of use.Interactivity.Consistency.Personality.
Page 63
“PERSONALITY MAKE PRODUCT FRIEND. YOU HELP FRIEND. YOU FORGIVE WHEN FRIEND NOT PERFECT.”
Fake Grimlock@fakegrimlock
Page 64
Keep the overall experience in mind.
Page 65
“Sometimes you don’t need to change the way a product works, you need to change the story.”
Ilona Posner @ilonaposner
Page 66
Don’t be so quick to code.
Page 67
“Success is not delivering a feature; success is learning how to solve a customer’s problem.”
Scott Cook, Intuit
Page 69
Benefits, not features.
Page 70
Your product should serve just one need delightfully.
Page 71
Make your MVP an exceptional experience.
Photo by DixieBelleCupcakeCafe
Page 72
Every effort that follows needs to extend, not diminish that experience.
Page 73
Every feature you add is a distraction.
Page 74
Don’t add a feature unless it serves the core user need.
Page 75
Or you’ll end up with this.
Page 76
Being disrupted by this.
Page 77
Say Yeah!@yousayyeah
Lee Dale@smack416
Thank you.