The Collective Originals —Jobs-To-Be-Done Series Roundup
Over the past month our global practitioners have written articles on the Jobs To Be Done (JTBD) theme. To round up the series, please do take a look at the shared articles — we have original content written by our London colleague James Laurie and David Leggett from New York. These features include: the history and background of JTBD, suggestions on how we can adopt this approach within our working methodology and finally ideas on how we can use the JTBD concept to improve research, processes and the product itself.
3 Ways ‘Jobs-To-Be-Done’ Improves Application Development
This article written by our colleague David Leggett, has been written for product managers, product owners and designers to help generate ideas around how to use the Jobs to be Done concept to improve research, processes, and the product itself.
The Origins of Jobs-To-Be-Done
How did Jobs to Be Done become a recognised methodology? This article written by our very own James Laurie from our London office, provides the history and background on how it rose to prominence within design.
How to do Jobs-To-Be-Done
This article, the second from our colleague James Laurie, follows on from the history and background of jobs-to-be-done, onto how we can adopt this approach within our working methodology.
