Kate’s 3 languages:
- What are we trying to accomplish?
- What does that look like?
- How will we measure the work and track progress?
UX expertise horizons
“Your metrics will be as unique as your business” —Josh Porter
Number of downloads, average time on site, number of new sign ins etc are not the metrics we need
- They might be early indicators
- But they don’t actually answer the question of whether users find value in our product
These are the places we want to go looking for metrics for measurable value for our customers:
Some metrics and analytics to consider:
- Click tracking
- Analytics packages
- A/B testing
- Usage stats
PULSE metrics – mostly technical, a little old fashioned now
- Page views
- Seven-day active users
PIRATES metrics – esp good for start-ups
HEART metrics – from Google research labs
- Task success
Retention is the one common metric in the previous two frameworks. It’s not enough to get traffic through the funnel— people need to use the product
Read Lean Analytics for the best book on this, but the authors believe:
- A good metric measures the usage of your product by a person
Criteria for a good metric:
- Clear and specific
- Know what interactions represent desired user behaviors
- Identify the specific interactions that support that behavior or action
- Find the numbers to track these interactions
- Normalized (rate or ratio)
- Percentages are inherently comparative
- They balance out big changes in total quantities
- Captured at regular intervals
- Directly comparable over a span of time
- Changes your behavior
- “Don’t just ask questions. Know how the answers will change your behavior”
Metrics vary in quality of information:
Habitual usage is probably the most awesome things you can measure
So in this context:
- What does the user need to do?
- Where in the interface can they do that?
You can whiteboard the UX stack for this question:
Everything above usage is about users, everything below is about product. Don’t get stuck too deeply on either side
Where the company purpose and uses intersect is your value proposition
The uses area is where thinking turns into practices and plans
“Your produce must be bridge between your customers and their dreams.”—Christina Wodke
For Facebook, here could be a sample stack:
You can create these for multiple personas or scenarios, but all the teams must align on what the story of this stack is
Note your key use is at the Uses level.
- This is the area where you need to define your features around, instrument around and build your metrics around
- So ask, What can our customer do with our product that they can’t do without it?
- Use a mad-lib style diagram to answer that question:
Draw that use case as a simple picture:
Ask, Who’s our user? Where do they go and what do they do? What do they think/feel/say?
- Ideate multiple scenarios via 6-up
Make sure to do this sketching as a team! Discuss and pick one winning scenario to take further as a SCAM artist
Then take that scenario and draw it out down to the interface level:
Now add that with your key metrics to measure:
Work with your product team to figure out what the key habituation moment is in your product and design to that. Samples:
These habituation points (where users are more likely to continue use if they can get past this point) are leading indicators of your product’s long-term success
Funnels are one system
Look to storyboards or hero stories our journey maps to find funnels
Then map the stories to the funnel:
Measure these funnels over time
Instrumentation is setting up the tech to capture that numbers that matter. Data can be gathered:
- Technical by hand
- Instrumented with software
About Kate (from LinkedIn): Specialties: visual thinking, graphic recording and facilitation, sketchnoting, teaching/training, public speaking
Also skilled in Lean startup, entrepreneurship, UX for startups,
Seasoned UX generalist: User experience strategy & design, information architecture, interaction design, design research, business strategy & just enough tech to be dangerous.