16. 1. FbDD, what is it?
“A collection of techniques for
measuring progress based on
customer interaction.”
17. Via lean startups
by Eric Ries
“translating your startup vision into a
successful business as quickly and
efficiently as possible”
http://startuplessonslearned.com
19. Where do you use this?
New projects where you are unsure of your
market
Haven’t figured out a pricing strategy
Don’t know what users really need
Don’t want to write software no one uses
24. What does FbDD look
like?
Don’t spec out entire project
Keep long-term strategy in mind
Tight iterative loops once you collect feedback
25. Minimum Viable Product
“A version of a new product which
allows a team to collect the maximum
amount of validated learning about
customers with the least effort.”
26. Minimum Viable Product
“A version of a new product which
allows a team to collect the maximum
amount of validated learning about
customers with the least effort.”
27. A starting place
Simplest implementation of your core idea
Just build enough for validated learning
Early adopters will see the potential
Not finished, should be embarrassing
32. An idea is born
Start with usual client-developer conversation
Ask three additional questions:
1. How do we measure progress?
2. What’s the expectation on how this story
will impact our metrics?
3. How long do we need to measure results?
33. Grows up
Implement with simplest version for learning
Strive for least effort to get feedback soonest
Push off unneeded decisions, commitments
Ensure we have a way for measuring in place
34. Leaves home
Deploy code to production
Measure results for agreed upon duration
Though deployed, the story is not done
35. Makes its mark
Analyze results, good, bad or indifferent
Is it a keeper?
Possibly remove it?
Need to tweak the approach some?
36. The pivot
Shifting your product direction based on
validated learning
Used when progress is no longer being made
Leverage what you’ve built
37. Types of pivots
Segment - going after different customers
Problem - solve a different problem for existing
customers
Feature - selecting specific feature and
centering company around that
44. AARRR!!
by Dave McClure
acquisition
activation
retention
referral
revenue
http://www.slideshare.net/dmc500hats/startup-metrics-for-pirates-long-version
45.
46.
47.
48.
49. flingr’s metrics
acquisition - site visits
activation - signups
retention - repeat use
referral - fling backs
revenue - upgrade to pro account
50. Drop-in service
Google Analytics (good for content/pages)
MixPanel (easy integration)
KISSMetrics (strong on funnel analysis)
StatsMix (flexible, combines many sources)
51. Roll your own
1. Your own event-driven metrics table
2. Use existing application data
54. why DIY?
Very simple to get started
You already have this data
Easily add or change what you track
As you own the data, can analyze differently
Good enough
68. What’s the point?
Lightweight way to track customer perceptions
You want to see your score improve over time
Easy way to get additional feedback
Can do small sample sizes at regular intervals
69. How it works
Tracks 3 groups:
1. Promoters (9-10)
2. Passives (7-8)
3. Detractors (0-6)
71. Triggering
Offer questionnaire every other week/month
or manually trigger
Only need a small sample size, such as 50-100
per time
Only present to each user once per 3-6 months
72. My preference
Perform small sample each week
Ask users after 3 weeks of signing up
Only ask every 6 months
Prefer in site lightbox modal to minimize
interruption
79. Guidelines
Make it easy to tell you want they think
Ever present feedback button on all pages
Shouldn’t interrupt user flow
Less clicks is better
80. Simple version
Lightbox modal with text box and email
Start with sending results in emails
Graduate to a DB table for managing
81. Full featured
Get Satisfaction or User Voice
Better at collecting and managing feedback
Downside is more clicks and extra registration
82. Live interaction
Snap-a-bug: http://www.snapabug.com/
Does live chat or offline email form
Can record what’s going on with the user’s
browser
Integrates with existing CRMs, help desk
and bug tracking solutions
Advanced remote screen capture
85. With current process
Plays nice with agile methodologies
Need to consider an extra phase for learning
once metrics are collected
Half-implemented stories will need follow-up
to build out
86. When to use
MVP: from the start
Metrics: pick 3-5 core metrics from start
A/B testing: prefer major feature rollouts or
contentious enhancements
NPS: once you get over 100 users
Direct feedback: from the start
87. Limitations
Challenging with low volume
Be prepared for a lack of significant results
Can’t replace vision, only give some guidance
on effectiveness
88. Takeaway
Feedback can be used for smarter product
development
It’s easier than you think to get started
Knowing how your customers use your
product
Can help avoid writing software no one uses
