Why you need a jobs-to-be-done map
How to build customer empathy by understanding the process they follow to achieve job completion and success.
šĀ Hi, Iām James.Ā Thanks for checking outĀ Building Momentum: a newsletter to help startup founders and marketers accelerate SaaS growth through go-to-market strategy, sales, and product marketing.
Sign up now to get the next edition in your inbox:
One of the many things I love about the product management world is the frameworks!
Today I want to walk you through one of my favorites, a Jobs To Be Done (JTBD) map.
A job map is a single document that details the steps your customers go through to āhireā a product for a ājobā they need to do. I think every business needs one job map per customer persona, per product.
By breaking down their process to find, complete, and review their job, we can improve our understanding of the customer - and optimize our product, marketing, and sales to better meet their needs.
What is ājobs-to-be-doneā?
Firstly, a recap. Jobs-to-be-done (JTBD) theory posits that people buy products and services to get a ājobā done. Those jobs are mostly functional, however also have emotional and social components that also need to be fulfilled. Success comes from achieving the ājobā, rather than gaining the tools to complete it.
You can read more about the JTBD methodology here, but watch Clayton Christensen in this primer:
Why use a job map?
Rather than user story maps, job maps donāt look at the individual actions that somebody takes in this journey, like clicks or searches, but instead look at the macro stages and micro-tasks that someone will do in their search to be successful.
Traditionally they have a lot of value in product management and can provide a foundation for the product discovery process. But I like to use them for two reasons: ā¦..
Create your profile
Only paid subscribers can comment on this post
Check your email
For your security, we need to re-authenticate you.
Click the link we sent to , or click here to sign in.