My colleague Jason Zhou and I went to Jared Spool’s UX Strategy Playbook Workshop.
It was excellent. Do take a colleague with you if you go as the majority of the content is very practical.
I’ve summarised my top takeaways below.
To design a successful product we need to understand our customers—
To increase our chances of creating a really great product, we must intentionally design a working environment where, by default:
- Everyone is focussed on solving customer problems.
- We understand these problems deeply, based on first hand observation.
- Problems are prioritised based on how impactful they are to our customers and business.
- We are realistic, and take appropriate action, based on our level of confidence.
—so our whole team must become researchers.
The most effective way to encourage this environment to develop is to scale up the research capability of the team and company overall, so that everyone can help us to reach the clarity we need.
We should ask four questions:
1. Are we framing our work in terms of solving customer problems?
- Are we investing enough time in up-front exploratory research to understand how people experience our product and solve their key problems today?
- Have we mapped the existing customer experience, and do we use this to plan a roadmap that is centred around prioritised customer problems?
- How can we focus the work of our product teams on end-to-end customer experiences, not feature sets or product lines?
- What small tricks can we use to reinforce this thinking—like naming our teams after the problem they’re solving for customers (the core JTBD)?
2. Is the whole team actively participating in research?
- Are we encouraging a high level of first-hand exposure to customers? Across executives, subject matter experts, and team members — does everyone have the opportunity to directly observe customers using our product? How are we up-skilling our SMEs and stakeholders to ask better questions when they do interact with customers?
- To encourage active observation, can we give team members specific jobs to do during research and synthesis that leverage their individual strengths, such as watching for product complexity or missed expectations?
- Have we involved the team in defining a research-based, 5-year vision for the experience they’re building? This memorable and shareable narrative should be used to help teams make the day-to-day tactical decisions required, confident they are still continuing to head towards a transformative experience.
3. Are we prioritising each customer problem we could solve based on relative scale and impact?
- Have we had frank conversations with our leadership to identify what business objectives our company has? Can everyone on the team understand and communicate how these objectives map to the customer goals and problems we’re trying to solve for?
- How are we synthesising and summarising the research insights we are gathering so everyone is able to share what they have learned, and our insights about customer problems aren’t anecdotal or biased?
- When prioritising, are we gathering enough data to evaluate the scale of impact of solving the problem using both a business and customer lens? Have we quantified the areas of frustration/opportunity we have identified? How many customers are impacted by this; how much does this impact our business goals?
4. Are we being transparent about our level of confidence in our knowledge about the best solution?
- Before we do anything—before research activities, before user testing, before shipping work—are we recording up front what results we think we’ll see? Clearly stating our our hypothesis beforehand will highlight clearly how our assumptions and inferences are so often totally wrong. This will humble us, and encourage us to focus first hand customer exposure.
- We can always infer something from the available data we gather — but when is this an inference, and when is it an actual observation? Are there inferences we need to turn into observations, by studying first hand what customers are doing?
- When we have decided on a particular solution, what real indicators of performance should we be tracking, directly tailored to the problem we are trying to solve?
My focus for 2020 and my biggest lesson from the workshop—
Also published on Medium.