For years, the user story has been the fundamental unit of work in agile development. We’ve all mastered the ‘As a [user], I want [feature], so that [benefit]’ format. But lately, I’m seeing more and more discussion questioning if this trusty tool is still fit for purpose, especially as we move towards outcome-based roadmaps and AI-driven development.
The core critique is that user stories often box us into thinking about features (outputs) rather than customer problems and value (outcomes). They can become a checklist of ‘things to build’ that lack a clear connection to the larger strategic goals or the ‘why’ behind the work.
Frameworks like Teresa Torres’s Opportunity Solution Trees and the ‘Jobs to Be Done’ format for Job Stories are gaining traction precisely because they force a deeper focus on the customer’s context and desired progress. They re-center the conversation on solving problems, not just shipping features. As AI tools begin to handle more of the ‘how’ in development, our ability as PMs to define the ‘why’ with absolute clarity becomes our most critical skill.
Is the classic user story becoming a bottleneck for true innovation and customer-centricity? How is your team evolving the way you define and communicate the work to be done?