SAP Activate Roadmap Viewer: How to Navigate Roadmaps and Use Accelerators

The SAP Activate Roadmap Viewer helps project teams turn an implementation roadmap into an actionable delivery reference. Use it to find the relevant roadmap, understand phase objectives, review workstreams and deliverables, and open supporting accelerators.

A practical way to use the viewer is to begin with the project context, narrow the roadmap to the relevant solution and deployment approach, then move from phase-level guidance to specific activities and assets. The viewer supports planning and execution; project governance, decisions, owners, and dates still belong in the project team's delivery tools.

01Start with the right roadmap

Open the SAP Roadmap Viewer and identify the roadmap that matches the project scope. Confirm the solution area, deployment approach, and implementation scenario before using the content for planning.

For an SAP S/4HANA project, the roadmap selection should reflect the solution scope and delivery approach. A roadmap for a new implementation provides different guidance from one for a system conversion or another transition scenario. Record the selected roadmap in the project workspace so that the team uses a consistent reference.

Use the SAP Activate overview to align the roadmap with the overall methodology, phases, and governance model before building the detailed plan.

02Navigate phases and workstreams

Roadmaps organize implementation guidance into phases and workstreams. Select a phase to understand its objective, expected outcomes, and related activities. Then open the workstreams that apply to the team's scope.

A useful navigation sequence is:

1. Review the phase objective and key outcomes.
2. Identify workstreams relevant to the current project stage.
3. Open activities and deliverables under those workstreams.
4. Capture applicable tasks, dependencies, and ownership in the project plan.
5. Return to the phase view to check that the work remains aligned with the intended outcome.

The phases provide a delivery sequence, while workstreams help different disciplines organize their contributions. The viewer is most useful when the team reads both together rather than treating a phase as a standalone checklist.

03Use deliverables and activities

Open a deliverable to understand the expected result, responsible roles, and related activities. Use the content to define project tasks and acceptance points in the team's planning system.

For each relevant deliverable, capture:

• The expected business or project outcome
• The responsible role or workstream
• Prerequisites and dependencies
• Planned start and finish dates
• Evidence that demonstrates completion
• Decisions or open issues that require governance attention

Keep the project plan specific to the implementation. The roadmap provides reusable guidance, while the project team decides which activities apply, who owns them, and how completion is verified.

04Find and apply accelerators

Accelerators are supporting assets that can help a team perform an activity or produce a deliverable. Open an accelerator from the relevant roadmap content, review its purpose and prerequisites, and decide how it fits the project's working method.

Before adopting an accelerator, check its intended use, required inputs, and expected output. Assign an owner and store the working copy in the project repository when the team needs to tailor it. Preserve the source reference so later reviewers can distinguish the original asset from project-specific changes.

Useful accelerator categories include templates, process descriptions, task instructions, workshop materials, checklists, and examples. Select the smallest set that supports the current decision or deliverable. A large collection of unused assets makes progress harder to track.

05Connect roadmap content to Fit-to-Standard work

Roadmap activities often connect directly to fit-to-standard workshops, process decisions, backlog items, and configuration or extension work. Use the roadmap to establish when the work occurs, then use the workshop and backlog records to document the actual project result.

The Fit-to-Standard in SAP Activate article provides related guidance for organizing those discussions. Link each workshop outcome to the affected process, decision, requirement, or follow-up action so that roadmap progress reflects the project's real status.

06Use the viewer during agile delivery

When the project uses iterative delivery, treat roadmap activities as higher-level guidance and manage detailed work through the team's backlog, iteration plan, and review process. Break a deliverable into actionable backlog items when the deliverable is too broad for one iteration.

The SAP Activate and agile delivery article covers the relationship between methodology guidance and iterative execution. During each planning cycle, review upcoming roadmap activities, refine the related backlog items, and confirm dependencies with other workstreams.

A practical review cadence is:

• At phase planning: confirm the relevant roadmap outcomes and major dependencies.
• At iteration planning: select actionable tasks connected to current deliverables.
• At iteration review: compare completed evidence with the intended outcome.
• At phase review: confirm unresolved decisions, risks, and remaining work.

07Troubleshoot roadmap navigation

When the viewer does not appear to match the project, check the roadmap selection first. Verify the solution, implementation scenario, and scope before interpreting a missing activity as a project gap.

Use this troubleshooting sequence:

1. Reopen the roadmap selection and confirm the project context.
2. Check whether the required phase or workstream is filtered out.
3. Search for the activity or deliverable using a distinctive term.
4. Open the parent phase or workstream and follow the content hierarchy.
5. Confirm that the asset link opens and that the team has access to the referenced content.
6. Record the finding and update the project plan with the applicable action.

If the project uses a tailored roadmap or local governance model, keep the project-specific additions in the project repository and maintain a clear link to the corresponding roadmap content.

08Create a usable project reference

A roadmap becomes operational when the team connects it to project controls. Maintain a simple reference containing the selected roadmap, current phase, active workstreams, key deliverables, accelerator links, owners, and open decisions.

Review that reference at project status meetings. Mark content as applicable, completed, deferred, or replaced by an approved project decision. This keeps the roadmap useful without turning it into a second project-management system.

Practical checklist

• Confirm the roadmap and implementation scenario.
• Identify the current phase and applicable workstreams.
• Convert relevant deliverables into owned project actions.
• Review accelerators before adapting them.
• Link workshop outcomes and backlog items to roadmap activities.
• Recheck dependencies at phase and iteration reviews.
• Keep project-specific evidence in the agreed repository.