This document discusses how analyzing past user experience (UX) data can help predict future issues and improve the UX. It outlines a process of collecting data, analyzing it to find issues, investigating insights, recommending and testing solutions, and identifying success metrics. As examples, the document analyzes past website usage and search data to identify problems like students struggling to find their email. It also discusses using historical attendance data to accurately project future capacity needs. The overall message is that systematically reviewing past UX metrics can reveal opportunities to enhance the user experience.
Predicting the Future and Improving UX Based on the Past
1. Predicting the Future and
Improving UX Based on the Past
Tim Schneider
Digital Analytics Manager
University Digital Strategy
May 11, 2013
2. User Experience
"a person's perceptions and responses that
result from the use or anticipated use of a
product, system or service"
http://en.wikipedia.org/wiki/User_experience
3. “I could more easily
navigate the catacombs of
Egypt with a penlight than
find the link I'm looking
for on your overly-
congested website.”
Angry Customer: Sept 2, 2012
6. Hello Tim,On your web pages A and B, under the
"Heading goes here" heading, I am wondering if it
would be possible for you to change the "Button
Label" button to link to Page X, rather than
directly to our Page Y? I have spoken with my team
and with our ____ unit, and there is key
information presented on
Page X that we expect audience to have been exposed
to prior to diving right into the Page Y, so it
would be ideal for them to be directed to that page
first.
7. “so it would be ideal
for them to be
directed to that page
first”
43. Collect DataCollect DataCollect DataCollect Data
Analyze Data / ReportAnalyze Data / ReportAnalyze Data / ReportAnalyze Data / Report
Find an issueFind an issueFind an issueFind an issue
Investigate / InsightInvestigate / InsightInvestigate / InsightInvestigate / Insight
Recommend SolutionRecommend SolutionRecommend SolutionRecommend Solution
FeedbackFeedbackFeedbackFeedback ImproveImprove ““??””ImproveImprove ““??””
Identify success metricsIdentify success metricsIdentify success metricsIdentify success metrics
44. “This year however, we have been required to
follow up via phone (which is a big drain on
resources) as many of our students can't find
where their email is. In the conversations
with them I had to walk them through going to
the ualberta.ca homepage then clicking on '
apps@ualberta.ca' to find their email
account.”
July, 2012
52. Collect Data (2010)Collect Data (2010)Collect Data (2010)Collect Data (2010)
Analyze Data / ReportAnalyze Data / ReportAnalyze Data / ReportAnalyze Data / Report
Find an issueFind an issueFind an issueFind an issue
Investigate / InsightInvestigate / InsightInvestigate / InsightInvestigate / Insight
Recommend SolutionRecommend SolutionRecommend SolutionRecommend Solution
FeedbackFeedbackFeedbackFeedback ImproveImprove ““??””ImproveImprove ““??””
Identify success metricsIdentify success metricsIdentify success metricsIdentify success metrics
- tie in this presentation to others today - designing for emotion in the next session - we all have opinions - we all know what we like - we all think we know what works - key is to take emotion out of our decisions - many people involved - how does this fit in with the team
- boss: different kinds, different moods. sometimes mind is completely somewhere else - academics / business : know their subject. assume everyone in the world is dying to know about what they do. also believe 10,000 word scientific papers are fine for general public - engineers / developers : we could never build your project in that amount of time. How come Lynx isn ’ t the most popular browser? - communications: tell our story. everything must be a story. big images rule. - consultants: sure, they ’ re trained and know what they ’ re doing, but they ’ re never around long. - be like spock: emotionless and carry a big tricorder
95 Million pageviews 30 Million visits 25 Million events in Kiss Metrics 250K through Crazy Egg
95 Million pageviews 30 Million visits 25 Million events in Kiss Metrics 250K through Crazy Egg
- viewed items - my recent searches - helps me know what my kids are up to on my ebay account “ trash packs ”
- get your pen lights out
- simplify the page - heat mapping and search data told us what the users were looking for and actually using - moving to responsive forces you to think about the mobile experience. - on a small screen, what should the user see first? - prioritize
- how much does our search traffic grow every day - related to our goals - using percent of capacity as the measure, not actual attendance - actual numbers are easily derived from percentage based on capacity of event - use an actual data point as the starting Y - events with the low actuals can ’ t really grow according to this model - percentages of growth are small - need more time OR... we ’ ll talk about this later.
- how did we do? - use actual numbers here (doesn ’ t matter)
- if you ’ re looking at a projection like this, what do you do? - move to smaller venue? - cancel - promote the hell out of it?
- what about this? - first, you need more data points at the start - daily - 17 days out: let ’ s do more. more ad words, A/B test, leverage other avenues/partners