1. Understand the roots of the problem — Empathize
Which questions to ask someone, how to listen, how to sort out someone's problem. Let's practice the user interview!
2. Identify the job to get done — Define
What's the job that our interviewee is trying to get done? Concept coming from Clayton Christensen.
3. Map the ins and outs of the user journey — Ideate and refine
With sticky notes, map the before/ during/ after of the journey of our persona. Identify the touch points, must-haves, nice-to-haves, pain points, ad-hoc solutions, expectations. Then look for patterns: what stands out? What's obvious?
4. Sketch the job to be done — Prototype
Starting with mobile app paper template, low-fi sketches of one possible answer to the job to be done.
5. Pitch your prototype — Test
Throw your prototype out there and get peer feedback.
Right balance between macro and micro level
The first phase — the problem understanding — was challenging. Going further anyway help understand the big picture. And everyone was eventually comfortable with the prototype and pitching phase.
Getting the job done
We often want to jump head first in a solution. Keeping focused on defining what's the job to be done is crucial.
Length can be improved
The workshop was dense and long, with more practice, it could be dense and short.
It was key to pair with Frances to run this workshop, and apply that to the exercises too.