Experience-Based Roadmap: Triage for Product Teams

WHY IT EXISTS: Traditional roadmaps often rank features by stakeholder pressure or technical convenience, which produces tools users do not need. UX researchers needed a way to translate qualitative journey data into a prioritization framework that forces product decisions through the lens of actual user suffering rather than internal opinion.

THE MENTAL MODEL: Think of it as triage for product development. Just as an emergency room treats patients by the severity of their condition rather than the order they arrived, an experience-based roadmap schedules work by the intensity and frequency of user friction. The unit of planning is not a feature; it is a validated pain point at a specific stage of the user journey.

HOW IT WORKS: Teams map the end-to-end user journey and tag each stage with observed pain points, support tickets, usability failures, and behavioral drop-off data. Each pain point is scored by reach, how many users hit it, and severity, how much it blocks the core job to be done. The roadmap then sequences initiatives that attack the highest combined scores first. Crucially, the roadmap item is framed as an experience outcome, reduce checkout abandonment, rather than a feature, build a one-click button, so the solution remains negotiable while the problem stays fixed.

WHEN TO USE IT: Use this when qualitative research keeps surfacing friction that does not align with the current backlog, when retention or conversion metrics are flat despite shipping features, or when you need to justify deferring a stakeholder request because the user evidence points elsewhere.

WHEN NOT TO USE IT: Do not use it when the product goal is purely technical, such as a compliance mandate or a platform migration with zero user-facing changes. It also fails if the underlying journey map is built from assumptions rather than observed behavior, because garbage-in becomes a polished but wrong plan.

ONE CANONICAL EXAMPLE: A SaaS onboarding team discovers through interviews and funnel analysis that users abandon not because the signup form is long, but because they cannot find the invitation email. The experience-based roadmap prioritizes fixing email deliverability and adding an in-app resend trigger before any form redesign, even though the form redesign was already half-built. The roadmap entry reads eliminate email verification dead ends in week one, not redesign signup UI, keeping the team focused on the verified blockage rather than the presumed one.