Shane Goodwin
Aug 8, 2017 · 1 min read

Excellent article and points, we’ve been through this pain :)

We now use both job stories and user stories. We create job stories at the level of the problem (the job :) ) and around user behaviours, to give context and to generate the UI design and then user stories. This means effectively that we go from problem-focused job stories to solution focused-user stories — we need the solution-focused bit to handle estimation, dependencies etc. but we want and need to capture the motivation. Yes, technically we could just use an epic in a user story, but we’ve found keeping the form of expression distinct keeps people thinking at the right levels, and now everybody from product managers through designers, BA’s and developers work with both.

    Shane Goodwin

    Written by

    Pixels, products, people.