Nice to see this here. I have spent a lot of time over the last year or so studying this. myself and the rest of our UX team did a three day JBTD seminar last year. Very valuable in shifting your perception of how to create stuff that adds value in people's lives. I highly recommend it for any person building software, as well as Outcomes-Driven Innovation which offers a great framework for making new things and figuring out empirically what users (or "the market", whatever) are asking for.

I'm curious to see what improvements to your workflow and to the experience you have seen. I'm open to anecdotes but I'd love some metrics if you have any.

I can't give specifics since I'm no longer with that company and even a cursory search of my profile here could put 2+2 together, but using an outcomes-driven framework survey (~150 respondents, we were a niche industry so this was a huge sample size) we were able to add critical new features to our roadmap that were opportunities we never saw before. By using the formula in that book you are able to objectively determine underserved portions of the market "I really need the ability to do X, and currently am very dissatisfied with my ability to do so with my existing setup". And by using numbers, which is cool.

More on the research methodology here: https://medium.com/envato/a-step-by-step-guide-to-using-outc.... I realize this seems a bit OT from the original comment, but Jobs to be Done and ODI are the same authors and they are intimately tied together philosophically

There is a video of Clayton Christensen on BoS that's really worth watching.

This one? http://businessofsoftware.org/2012/02/professor-clayton-chri...

I can also recommend the HBR article mentioned above.

That one, yes! Thanks for the link... I forgot that little bit.