One of the biggest reasons for thinking about the customer needs in terms of a ‘job’ — rather than a customer want in terms of ‘benefits’ — is that customers are usually ambiguous and imprecise with what they are actually looking for. This tends to then muddy and dilute the problem space, which can lead to product teams building functions and features for the wrong reasons.

Read on Bootcamp.

One response to “How To Understand The Job To Be Done (JTBD) Like A Product Manager | by Ian Khor | Bootcamp”

  1. Jason 🛥️🏄‍♂️ Avatar

    @baxbridge good read! Learned this the hard way when I first tried to configure a management system for a translation/interpretation services office with 60+ employees. Unfortunately, we started wasting a lot of time trying to create what people said they needed. Later, we had to reconfigure much of the system after listening to what employees do and ensuring the system could support their job.