If you’ve run Jobs to be Done successfully, I definitely recommend looking into Job Maps and ODI.

It’s about understanding the job (and users) to the point were you can map its successful execution to desired outcomes. The better you understand the job and the outcomes, the easier it should be to pick the plays to build the best solution.

We’ve tried to apply ODI in a leaner way with mixed results…

Nonetheless, it is a great way to think about JTBD.