Agile alone produces working software. UX ensures it's the right software. This framework shows how human-centered design integrates into agile delivery cycles — giving teams the aspirational direction that transforms production speed into real product velocity.
Humans are fickle. What starts as exciting and new quickly turns into an expectation — and unmet expectations breed dissatisfaction. Teams must meet expectations, prevent experience rot, and continue to exceed expectations. Each stage presents a new set of problems to solve, new solutions, and new outcomes.
These end up being expectations over time unless we find ways to keep users excited.
Investment alone will not prevent experience rot if we don't continue to innovate.
To an extent we can 'buy' satisfaction, but only briefly.
We can really only screw these up by missing expectations.
Moving from the current state toward an aspirational future state should deliver value to users that (1) improves their life and (2) is an observable outcome. Agile alone will produce a functioning solution — UX ensures it's the right solution.
User Research: Deep understanding of users and their needs
Problems to Solve: Unmet needs, friction, tension, unmet expectations
Product/Service/Feature: Resolves a frustration, usually starts as 'How Might We…'
Outcomes: Value provided to users
Does what we created function as intended? Outputs are the things we do on the way to the outcome — important milestones, but not why we do the work.
Does our functional product solve the user's problem? Outcomes are human-centered goals with intrinsic value — they help us determine the right problem to solve and provide observable metrics.
User experience provides purpose to productivity.
Many UX practices don't neatly fit into Agile sprints — but if we shift how we approach UX within the Agile framework, it organizes processes for incremental progress that's easily measured like any other set of outputs. The key is recognizing that UX and Agile serve different layers of the work.
By framing scenarios and user stories in terms of problems to solve,
the features they deliver align to outcomes.
Front-load enough research to define the current state and fuel the initial sprints. Break larger research efforts into smaller pieces that fit into sprints to inform future work — keeping discovery continuous rather than a one-time event.
Use spike stories to carve out dedicated time for design research within sprint cycles. By framing scenarios and user stories in terms of problems to solve, the features they deliver align to outcomes rather than just functional requirements.
Employ dual-track implementation to optimize velocity — one track for discovery (UX research, design explorations) running in parallel with one track for delivery (development). Value delivered = Done.
Measuring experience is an enduring problem in output-driven project management. Agile UX suggests changes in language and perspective on both sides — project and product — to align outputs to outcomes and show the value of experience-driven technical delivery.
If we do a great job on [product/service/feature],
we will improve the life of [user's name]
by [name the outcome].
If we do a great job providing tools to show the available and upcoming projects in our pipeline, we will improve the life of Employee Experiences by allowing them to request projects that align to their passions, opening new growth opportunities, and increasing job satisfaction.
Clear objectives and consistent measurement help indicate when sentiments are changing — affording time to adjust course before things turn south. Integrating UX metrics into Agile reporting provides a richer understanding of how teams are performing against both business and experience goals.
Five metric types map directly to OKR structures, giving product and delivery teams a shared language that spans the full arc from problem to value delivered.
A human-centered approach to metrics means we need to infuse the entire organization with knowledge about the most important humans: Our Users.