UX Glossary | P
Product roadmap
Also: Roadmap
A strategic plan of the problems a product will tackle over time, spanning design, engineering and the business.
A product roadmap sets out what a product team intends to work on and in roughly what order. It spans every discipline: engineering, design, data, marketing, support. Its audience is the whole company and its job is to show direction, not to schedule individual tasks.
Problems, not features
The most useful roadmaps are written as problems to solve. “Reduce abandoned onboarding” is a roadmap item. “Add a progress bar” is a solution that belongs further down, in the backlog. Framing items as problems keeps the team free to find a better answer when it learns something.
The usual shape
Many teams avoid calendar dates in favour of three horizons: now, next and later. Confidence falls as you move right, and the format says so honestly. A roadmap with exact dates eight months out is a promise that someone will later be asked to keep.
Product roadmap versus UX roadmap
The product roadmap shows what the product will do. A UX roadmap shows what the UX team will do, which includes work the product roadmap never lists: research studies, accessibility audits, design system upkeep, paying down design debt. Confusing the two is how UX work vanishes from planning until the sprint it was needed.
Common mistake
Treating it as a feature list handed down to teams. A roadmap that nobody outside product helped shape will be admired once and ignored.