job-stories

Job Stories are structured narratives based on the Jobs-to-be-Done framework that articulate why a user needs a product feature. They follow the format "When [situation], I want [motivation], so I can [expected outcome]" to shift product discovery focus from user personas to user motivations and desired outcomes.

The best way to write Job Stories using the Jobs-to-be-Done framework is to identify the user's specific scenario, motivation, and expected outcome, then combine them into a single narrative sentence. This structure clarifies the exact problem the user is hiring your product feature to solve during product discovery.

Use Job Stories instead of traditional user stories for feature definition when you need to emphasize the situational context and underlying motivation of the user. Job Stories avoid persona-based assumptions and focus directly on user needs, making them ideal for user-centric product discovery and user story mapping.

Yes, you can use Job Stories for user story mapping and product discovery. By transforming user needs into structured narratives that highlight scenarios and desired outcomes, Job Stories help align feature definition directly with user motivations throughout the product development lifecycle.

To generate effective Job Stories, you need a clear understanding of user scenarios, motivations, and desired outcomes. Providing the raw user requirements or requests allows the transformation process to accurately formulate narratives that align with the Jobs-to-be-Done framework.