Turning a Job Map into a Capability Maturity Model

When asking end-users in an Enterprise to evaluate a JTBD, it might be better to use a format they already understand

Jobs-to-be-Done (JTBD) has really been getting popular. Yet so few enterprises have actually been able to develop a rich corporate culture that is based on it. In part, it’s because there are a number of different flavors of the concept, which tends to cause more confusion than clarity. What I believe is the most actionable method (Outcome-Driven Innovation or variations on it) has so much rigor that - while it works well - it generally prohibits enterprise-wide adoption (or even product management adoption).

At the end of the day, only a portion of the enterprise is involved in product planning and development. The rest is trying to get other stuff done. JTBD techniques therefore need to be adapted for other problem-solving challenges if we’re to see broader adoption

Enterprises are complicated, which is why you see so many consulting firms introduce simple-looking frameworks for transformation. Anything more would simply be rejected...even if the simple ones don’t really work. I’ve wa…