What is a Job-to-be-Done (JTBD) job story and how does it differ from a traditional user story?

A traditional user story follows the format: "As a [role], I want to [action] so that [benefit]." It is role-centric and focuses on features. A JTBD job story follows: "When [situation], I want to [motivation/goal], so I can [expected outcome]." It is context- and motivation-centric, removing persona assumptions and focusing on the circumstance that drives behaviour. Example — User story: "As a Sales Rep, I want to see my pipeline on the home page so I can plan my day." Job story: "When I start my work day, I want to immediately see which deals need attention, so I can prioritise my calls before my morning meeting." Job stories are more durable than user stories because they focus on the underlying need rather than a prescribed solution, avoiding the risk of building the wrong feature correctly.