Course: Adopt The Jobs-To-Be-Done Framework In Your Product Development 

Part 1: Defining & identifying your customer

The primary reason products and services fail is a misalignment with customer needs: this happens when a product team does not agree on what the customer's “need” is, in the first place. 

The jobs-to-be-done framework offers companies an approach that shifts the focus away from the product, and places it on the customer. 

So what exactly do we call a “job to be done”?

Part 2: Capturing & Organizing Customer needs 

After breaking down customers into different categories, a company must be able to discover the customer’s “needs” associated with getting that job done. 

Jobs-To-Be-Done offers an approach to develop products based on an understanding of both the customer’s specific goal, and their thought process.

So what are the types of “jobs” that customers are getting done?

Jobs-to-be-done is a framework used by companies such as Facebook & Twitter, as a core part of their product development process.

Used by product teams to refine their understanding of users, it helps identify what problems and pain points should be prioritised and solved, on an ongoing basis.

Are you ready to use the Jobs-to-be-done needs framework internally?

Take the quiz to find out!

Sources:

• First Round Review: “Build Products That Solve Real Problems With This Lightweight JTBD Framework” 
• Harvard Business Review: “Know Your Customers’ “Jobs to Be Done”
• Harvard Business Review: “The Customer-Centered Innovation Map”
• Product Plan: “Jobs-To-Be-Done Framework”
• Ravi Kumar: “What Jobs to be Done (JTBD) Teaches Us About Our Users?”
• Strategyn, Tony Ulwick – “Jobs-to-be-Done: A Framework for Customer Needs”
• Strategyn, Tony Ulwick – “Inventing the Perfect Customer Need Statement”
• UX Collective, Zbignev Gecis: “8 things to use in “Jobs-To-Be-Done” framework for product development”