Communicating Jobs-to-be-Done Opportunities to Creative People (and beyond)

A simple example of masking all the scary data into something your design team, or leadership, will embrace...maybe!

In the world of Jobs-to-be-Done the majority of the practitioners do purely qualitative exercises that are full of aspirations, biases, conflations and assumptions. Did I miss anything? They write Job Stories out of thin air, and we are asked to have confidence that “When an order is submitted, I want to see a warning message so I can avoid resubmitting the order” is useful for innovation.

Well, it’s not. What’s the difference between that Job Story and a requirement framed as “the ability to know when order information is incomplete before submitting so that…”? It’s not an input for innovation, and you can quote me on that.

I’m sure why people take this stuff seriously. I don’t see how adds anything useful to the product development puzzle, let alone the fuzzy front-end of innovation. This is not Jobs to be Done, and you should fire you whoever told you it was :)

Moving on…