Team Thinking Before Phase I
|
Team Thinking After Phase I
|
The product team disagrees on who the customer is (the buyer, user, installer, influencer).
|
The product team agrees on who the customers are and why.
|
The team defines the market from a product- centric perspective (around the product or technology).
|
The team defines the market from a customer-centric perspective (around the Job-to-be-Done).
|
The team doesn’t know what job the customer is trying to get done.
|
The team agrees on what job the customer is trying to get done and on the job map.
|
The team can’t agree on what a customer need is (purpose, structure, format, content).
|
There is cross-functional agreement on what a need is.
|
The team believes customers have latent needs and needs they can’t articulate.
|
The team recognizes that customers can articulate their needs when they are defined around the Job-to-be-Done.
|
While the organization may collectively know most of the customer’s needs, there is no agreed-upon list.
|
There is a single, agreed-upon list of customer needs that is shared across functions.
|