What the User Says Is Not What They Want
summary
Users often can't articulate what solutions they want, but they can describe moments of difficulty and the problems they face; the talk explains using the Jobs-to-Be-Done framework to identify the core problem and design truly innovative, disruptive solutions. It comes from a product manager with startup and international experience at Resultados Digitais.
AI-written summary · about
chapters (7)
- 0:00Wrong model innovation
- 1:42Customer jobs vs personas
- 3:52What is a Job to be Done
- 6:43Jobs-based interviews
- 11:50Analyzing Jobs interviews
- 18:11Applying Jobs in practice
- 19:21Q&A
related talks
27m“Jobs to be Done” – workshop
24mJobs To Be Done methodology and its role in driving customer choice
40mPanel Discussion: What Users Really Want
41mHow Users Improvise Tomorrow's Experiences ...
28mBeyond the User: People at the Center
40mIs Design Thinking the Magic Wand for your product success?
34mUnderstanding UX (and UI) – a practitioner's perspective
33mWhy User Centered Design doesn't work (anymore)