Job stories are a powerful way to communicate the user's perspective on the "jobs to be done." Many POA Practitioners have the notion that user stories and job stories are mutually exclusive. Regardless of the Agile Framework to be used, job stories and user stories can be complementary in the context of POA, which allows common user actions to be covered through job stories, whereas more nuanced differences from user to user can be captured through specific user stories.

POA Domain	Job Stories
Applying Foundational Concepts	Job stories do not play a significant role in this domain.
Cultivate Customer Intimacy	Job stories focus on the common activities performed by most users, allowing the team to focus on the customer-specific user stories that require deeper analysis and realization of customer pain points.
Engage the Whole Team	Job stories do not play a significant role in this domain.
Make an Impact	Job stories emphasize the expected outcome which directly relates to value, providing the team the opportunity to streamline common activities, transactions, and workflows in a product.
Deliver Often	Job stories are easily integrated with Agile Frameworks like Kanban where Kanban boards can be used to accelerate product delivery.
Learn Fast	Job stories do not play a significant role in this domain.
Obsess About Value	Job stories filter out common activities so that the team can dedicate more effort to customer- focused stories to create delight for specific stakeholders. There are many activities or transactions that are not of interest to the customer but that provide business value. Such activities are better captured through job stories. A job story captures (rather than a user story): E.g., When searching for a specific insurance policy on the ABC Insurance application, a policy buyer must not be shown any ads. That way, the policy buyer can complete the transaction and not click away from the product.