• Seymour Butz, 7 months ago

    What do you think is confusing about it? "Jobs" is meant to encapsulate what a person is trying to accomplish in a given circumstance, in other words, give context to what they are trying to do and why. Whereas writing "user needs" can lead to specs full of things like "User should be able to click on this button to do X. User should be able to filter by Y. User should be able to search by keyword. Etc" that don't capture the why.

    I'm not that well versed in JTBD, but in my limited exposure I've found it to be a useful way to think about describing new features compared to more classic user stories.

    0 points
    • Marina JukićMarina Jukić, 7 months ago

      Maybe I'm thinking about user needs on a higher level than what you've described - these seem more like engineering oriented user stories.

      I found the jobs to be done confusing because of the template I used (or tried to adjust to our needs). This is what I focused on https://i.pinimg.com/originals/a6/b6/75/a6b675a97e7a9a7c59d27d226c2dbb64.jpg

      Do you perhaps have something that works better for you?

      0 points
      • Seymour Butz, 6 months ago

        Nah I only have a cursory understanding. Sounds like Andrew knows more what he's talking about, I'd listen to him :)

        1 point
      • Perttu Talasniemi, 7 months ago

        Yet another canvas.

        0 points
      • Nelson TarucNelson Taruc, 6 months ago

        JTBD doesn't fit neatly into a template or canvas, and is more a framework than a specific workshop activity. If you really want to apply the framework into your design practice, I'd look into the articles/books that Bob Moesta and Ryan Singer have written on the subject. Moesta has shared a number of JTBD interviews online and hearing those may help.

        1 point