SHORT ANSWER
A product roadmap is a statement of what problems you intend to solve, in what order, and why — not a dated list of features. The format that works is three horizons: what is being built now with committed scope, what is next with a defined problem but flexible solution, and what is later as themes. Dates belong on the now column only.
Answered by Andrew Crossley, Fractional Chief Product Officer · Updated 2026-08-01
Feature-and-date roadmaps create commitments the team cannot keep and remove the freedom to respond to evidence.
But 'no roadmap' fails too — sales, support and investors legitimately need to know direction.
Every item should be traceable to the quarter's metric or an explicit strategic bet.
Now (committed, dated, scoped), Next (problem defined, solution open), Later (themes only, no promises).
'Reduce time-to-first-invoice below ten minutes' survives new evidence; 'Build onboarding wizard' does not.
Visible rejections reduce lobbying more than any prioritisation framework. People mainly want to know they were heard.
Each review moves items between horizons based on what was learned, not on who asked most recently.
FROM EXPERIENCE
The main function of a roadmap inside a small company is alignment, not planning. It tells sales what to sell, support what is coming, and engineering what matters this quarter.
Once it is judged on forecasting accuracy rather than alignment, teams start padding estimates and hiding uncertainty — and the roadmap stops being useful for either purpose.
A themed version, yes. Never a dated feature list — it becomes a contract you did not intend to sign.
One quarter committed, two quarters directional. Beyond that, themes only.
The tool matters far less than the format. A shared document with three columns outperforms most roadmap software.
IN SHORT
Strategy, roadmap and operating model that survive contact with reality.
Read moreThe seven-stage framework that takes an idea to first revenue.
Read moreThe CPO role, when you need one, and how it compares to CTO or VP Product.
Read moreSeven stages from first idea to first revenue, with one output each.
Explore the Crossley MethodTHE FRAMEWORK
MORE ANSWERS
You become a product manager without a degree by producing evidence instead of credentials: ship something real, own a metric in an adjacent role, and document decisions publicly. Support, sales, operations and QA are the highest-converting entry routes because they give you customer contact and data. Hiring managers screen for judgement and shipped outcomes; almost none check for a degree at interview stage.
Four skills carry most of the job: customer discovery, prioritisation under uncertainty, written communication, and data literacy. In 2026 add two more: AI-assisted execution, and evaluation design for AI features. Frameworks, roadmapping tools and ceremonies are teachable in weeks; judgement about what not to build is the skill that separates senior PMs from everyone else.
Product managers usually fail for structural reasons, not talent ones: no clear mandate, no owned metric, no direct customer contact, an organisation that rewards shipping over outcomes, and an unwillingness to create conflict by saying no. Four of those five are fixable by the company. The fifth — avoiding conflict — is the personal skill most often missing in PMs who stall at mid-level.
Product managers use AI to compress the artefact half of the job: synthesising interviews, drafting specs and tickets, building clickable prototypes, summarising support and review data, and pressure-testing decisions. The best PMs also use it inside the product, designing evaluation sets and quality metrics for AI features. What they do not delegate is the decision, the customer conversation or the accountability.