job-stories

Job stories in the Jobs-to-be-Done framework are written using the format: When [situation], I want to [motivation], so I can [outcome]. This structure captures user context, motivations, and desired outcomes to define clear product development needs.

Acceptance criteria for user stories should be generated as detailed, outcome-focused conditions tied to the specific motivation and expected outcome. This ensures backlog items have measurable success conditions directly reflecting the user's desired result.

Job stories focus on user context and motivations using a situation-motivation-outcome format, whereas traditional user stories typically center on persona-based role-action-benefit structures. Job stories prevent assumptions about specific user personas during product development.

Use job stories in product management when you need to emphasize the situational context and underlying motivations driving user behavior. This approach is ideal for defining backlog items where user personas are ambiguous or secondary to the functional job.

Yes, job stories focus on the situational context and functional motivations rather than specific user personas. You can define measurable outcomes by structuring the desired result around what the user needs to accomplish in that specific situation.

To define acceptance criteria for a weekly spending tracker, generate outcome-focused conditions based on the job story: when viewing finances, users want to track spending so they can monitor budgets. Criteria should specify measurable success for data aggregation and display.