Portfolio Roadmap

Updated 15 May 2026

The Portfolio Roadmap is the artefact that makes portfolio investment sequencing visible across time. It is structured as two parallel views of the same underlying initiative set:

• A discovery roadmap showing when each initiative is expected to reach Gate 2 — the point of investment decision
• A delivery roadmap showing when each initiative is expected to be done — the point of outcome realization

Both views are needed. Discovery readiness and delivery readiness are different states of the same initiative, managed against different capacity constraints (analytical capacity for discovery; delivery capacity for delivery), influenced by different decisions, and consumed by different stakeholders. Treating “when can we invest in this” and “when will this be available” as the same question — or showing them on the same chart — hides the distinction the portfolio needs to manage.

The roadmap is not a capability and not a practice. It is an artefact produced and maintained by the capabilities around it. Its content is distributed across both views; its administration is centralized; its decisions are ratified at portfolio level.

Why two views

The portfolio operates two pipelines in parallel:

• The discovery pipeline moves candidates through Triage, Investigate, and Investment Framing — consuming analytical capacity, governed by Gate 1 and Gate 2
• The delivery pipeline moves approved initiatives through Implementing — consuming delivery capacity in the value streams, governed by Gate 2 admission and Done

Showing both pipelines on one timeline confuses two different management problems. The discovery roadmap answers: when will we have enough analysis to decide? The delivery roadmap answers: when will the outcome be available? The gap between them — analysis depth, dependency unblock, capacity availability, prioritization choices — is information the portfolio must be able to see.

A common failure mode is treating Gate 2 as the meaningful endpoint and managing only a Gate 2-readiness roadmap. This hides delivery capacity constraints until they bite. Another failure mode is managing only a delivery roadmap with implicit assumptions about when initiatives become deliverable; this hides discovery capacity constraints and gives a false sense of forward visibility.

What each roadmap shows

Each view shows three things:

Initiatives placed in planning horizons. Each initiative — approved or in-discovery — is placed in the horizon where its target event (Gate 2 for the discovery roadmap; Done for the delivery roadmap) is expected.

Capacity implications. The discovery roadmap makes analytical capacity load visible across horizons; the delivery roadmap makes value-stream delivery capacity load visible. Where capacity is concentrated, where it is sparse, and where conflicts emerge between strategic intent and what the system can absorb are all visible.

Strategic theme alignment. Each initiative on either roadmap can be traced to one or more strategic themes. The distribution of initiatives across themes — visible on the roadmap — is itself a portfolio signal.

What the Portfolio Roadmap is not

Several adjacent concepts are deliberately distinct:

Not a Gantt chart. Neither view tracks individual work items, detailed task dependencies, or week-by-week schedules. Those belong to delivery — at DVS or team level — not to portfolio governance.

Not a commitment plan. Placement on either view is not the same as a commitment to deliver. Commitments happen at Gate 2, on the Lean Business Case, with the Portfolio Leadership Group as decision authority. The roadmaps show what is currently expected; the LBC carries what has been decided.

Not a feature-level view. Both views operate at initiative level — the portfolio unit of flow. Feature-level roadmapping is a DVS-level activity, owned by the DVS leadership and not described here.

Not static documents. Both views are continuously updated as decisions are made, dependencies surface, and capacity signals evolve. Roadmaps reviewed once per planning cycle and frozen between cycles do not reflect current reality.

Structure

Both views share the same overall shape — initiatives placed on a grid of horizons and value streams — but differ in what determines the placement.

The discovery roadmap

• Time axis — planning horizons with Gate 2-target dates. Typical structure: current discovery work, the next two to three horizons for initiatives advancing through Investigate and Investment Framing, and an outer horizon for candidates in Triage or pre-Gate-1 pipeline.
• Value-stream axis — analytical capacity per value stream (or per cross-cutting analytical resource where discovery is centralized). Discovery work consumes analytical capacity, and the discovery roadmap makes that consumption visible.
• Initiatives on the grid — placed by expected Gate 2 date. Each entry shows title, owner, strategic theme, current discovery stage, and the gate it has passed (Gate 1 admitted; or pre-Gate-1 candidate visible as outer-horizon intent).

The delivery roadmap

• Time axis — planning horizons with Done-target dates. Typical structure: current delivery work, the next two to three Program Increments for initiatives in or near Implementing, and an outer horizon reflecting initiatives that have passed Gate 2 and are queued.
• Value-stream axis — delivery capacity per value stream. Initiatives that require capacity from multiple value streams are represented across all of them, with the cross-stream coupling made explicit.
• Initiatives on the grid — placed by expected Done date. Each entry shows title, owner, strategic theme, and Gate 2 status (Gate 2 passed; or expected-Gate-2 placeholder for initiatives in late discovery whose delivery timing is being planned for capacity reasons).

The two views are kept in sync through the shared underlying initiative set: an initiative appears on both, with its Gate 2-target date on the discovery roadmap and its Done-target date on the delivery roadmap. When either date moves, both views are updated.

Inputs from capabilities

Five portfolio capabilities feed the roadmap. Each contributes input to one or both views.

The roadmap is the synthesis of these inputs across both views. Its quality is bounded by the quality of the inputs.

Lifecycle

Both views update on two rhythms.

Continuous. As capabilities produce outputs in their normal operation — a Gate 1 admission, a Gate 2 decision, a dependency surfacing, a pivot ratification, a capacity signal — the relevant view (or both) is updated to reflect the new picture. The Portfolio Manager administers these updates as inputs arrive; no separate “roadmap update event” is required for continuous changes.

Periodic. At the Strategic Portfolio Review (typically per PI cadence), both views are reviewed holistically. This is where outer-horizon intent is reconsidered, where allocation across themes is reviewed, and where the roadmaps are formally snapshot-versioned for reference.

What the portfolio reads at any moment is the result of both rhythms — the continuous updates since the last snapshot, applied to the snapshot itself, across both views.

Ownership

Ownership applies to both views together — they are administered as one artefact with two presentations.

The Portfolio Manager does not decide what goes on either view; capabilities decide what is sequenced where. The Portfolio Manager ensures both views reflect those decisions correctly and that the inputs flow in on time.

The Portfolio Leadership Group does not produce the roadmap; capabilities and the Portfolio Manager produce it. The Group ratifies it where content changes affect committed investment direction — typically at the Strategic Portfolio Review, occasionally intra-cycle as exception decisions.

Relationship to other artifacts

Initiative is the unit placed on both views. Each initiative carries its own Lean Business Case as a separate artefact; the roadmaps show the initiative’s planned position in time on each axis (Gate 2-readiness and Done-readiness), not its detailed investment case. An initiative may move on either view without its LBC changing; an LBC may be updated (e.g. through pivot ratification) and the roadmap placements updated to match.

Strategic Themes (owned by Strategic Goal Management) are not artefacts in their own right; they are dimensions both views use to organize and surface the alignment between initiatives and strategic direction.

Lean Business Case lives within the Initiative artefact, not on the roadmap. The roadmaps reference initiatives; the LBC details live one level down.

Sources

• Donald Reinertsen — Principles of Product Development Flow (2009). The economic basis for thinking about portfolio investment as a sequenced flow across capacity rather than as a parallel commitment schedule; the distinction between discovery and delivery as economically distinct activities.
• David J. Anderson — Kanban (2010). Flow management at portfolio level — the visualization principles that make work-in-progress and pull visible at the level the roadmaps operate.
• Mik Kersten — Project to Product (2018). Value-stream-centric thinking about portfolio horizons — capacity as a sustained property of value streams rather than as project-specific allocation; the value-stream framing applied across both discovery and delivery dimensions.