The roadmap is a view of the portfolio over time. It shows the timeline of the entire portfolio , not just a single product: which product will launch when, which will be discontinued, and which products require the same team in the same quarter.
Scope
Portfolio-level calendar: Product lines, releases, and major changes appear in a single timeline.
Dependency management: Making visible how a product depends on completing another platform, certification, or supplier readiness.
Milestones and commitments: Promises made to customers, dealers, or the market must be recorded in the system.
Release packaging: Introducing minor changes to the market in planned releases rather than individually; this significantly reduces service and training costs.
Different perspectives for different audiences: Management, sales, production, and customer outreach roadmaps are generated from the same data at different levels of detail.
Sample portfolio roadmap
The value of the roadmap lies in showing overlaps , not just a single product: shared platform dependency and capacity overshoot within the same quarter are only noticeable in the portfolio view.
In the real business world
Roadmaps mostly live in presentation files. The problem is: as soon as the presentation is updated, it starts to contradict other copies. The roadmap in the hands of sales is different from the one in the hands of production; the promise given to the customer does not match the engineering plan.
The roadmap should be a view derived from actual project and product data. It should automatically update as the project timeline changes; no one should need to manually correct it.
Benefit to the customer
All units refer to the same calendar.
Addictions and conflicts appear early.
The commitments made to the customer are based on the actual plan.
Updating the roadmap will cease to be a manual task.