Roadmap.
aka product roadmap, now next later, feature plan
The plan for what gets built next, and what waits.
What it actually means
A roadmap is a plan that shows what a product or technology team intends to work on over the coming months and why. It sets direction and priorities, grouping work into themes or time horizons, so everyone from engineers to sales knows what is coming, what is later and what is not planned at all.
A good roadmap answers three questions: where are we going, what are we doing first, and why that order. Some teams lay it out by quarter. Many now use a simpler format called now, next, later: what the team is building right now, what comes after, and ideas further out that are still fuzzy. The further out an item sits, the less certain it is. Roadmaps often group work into themes, like faster checkout or better onboarding, rather than listing every small feature, because themes tie the work to a goal instead of a wish list.
The nuance people get wrong is treating a roadmap as a promise of dates. It is a statement of direction and priorities based on what the team knows today. When customers change, a competitor moves or a technical problem shows up, the roadmap should change too. That is why experienced product managers are careful about putting exact dates on later items, especially in front of customers. The hard part of a roadmap is not what goes on it but what stays off, because every yes uses time that could have gone somewhere else.
Where you'll hear it
Offline mode is on the roadmap, but it's in later, not next. If we pull it forward, the reporting work slips a quarter, so let's decide which one matters more.
Translation: the feature is planned but not soon, and moving it up has a real cost somewhere else.
Also in sales calls, where customers ask what is on the roadmap before they buy, in engineering, where teams keep technical roadmaps for upgrades and infrastructure, in company strategy decks that show a multi-year direction, and in public roadmaps that some software companies share so users can see what is planned.
The pop-culture version
Think of a tour poster for a band. At the top are confirmed dates: specific cities, specific venues, tickets on sale. Halfway down, the dates get looser, maybe just a month and a region. At the bottom, in smaller letters, it says more cities to be announced.
That is basically a roadmap. The top is now, locked in and being worked on. The middle is next, likely but still being arranged. The bottom is later, ideas the band wants to do if demand, money and time line up. Nobody is shocked when a TBA city never happens.
The poster also shows priorities. The band chose these cities over others, maybe because that is where the fans are. A roadmap does the same: it says where the team is putting its limited time, and quietly, where it is not.
The practical rule: treat anything in now as close to committed, next as likely, and later as an intention. If you need a firm date for something, ask the product team directly instead of reading it off the roadmap.
Say it like you mean it
“It's on the roadmap for next quarter, but I can't commit to a date until the design work is done. I'll update you once it moves into now.”
It shares the plan honestly while being clear about how certain it is.“Don't worry, it's on the roadmap, so it'll definitely ship in March.”
A roadmap shows direction and priority, and treating it as a guaranteed delivery date sets up broken promises.You will also hear people ask to get something on the roadmap, meaning they want it prioritized. And when a team says it is roadmapping, it usually means working out what to build next and in what order.
A step-by-step guide to building a product roadmap, with practical methods for prioritizing features and balancing customer requests against strategic goals.
Decoded next
Decoded by the Kurums editorial team. Kurums Decoded translates the language of business for people who are new to it. Definitions are kept short on purpose; the serious version above goes deep. Nothing here is financial, legal or career advice.
Discover more from Kurums | Business Intelligence
Subscribe to get the latest posts sent to your email.