Roadmapping in Detail

A roadmap is the single most important document in any sustainability transition project. It is the plan that turns analysis into action, solutions into timelines, and ambition into accountability. Without it, even the best ideas remain ideas. This unit provides the full treatment of the SiD roadmapping methodology: the reasoning behind each of the ten steps, the strategic decisions involved, and the principles that keep a roadmap alive over years and decades.

In the previous unit on Solutioning and Roadmapping, you encountered the ten-step roadmapping process in summary form. Here, we expand each step with the depth it deserves. This is the unit you return to when you sit down with your team, a large sheet of paper, and the task of charting a course from the present to a sustainable future.

What a Roadmap Is (and Is Not)

A roadmap is a timeline-based plan that shows how a system transitions from its current state to its desired state. It consists of two parts: a long-term trajectory (typically 5 to 50 years) and a short-term action plan (3 months to 3 years). The long-term trajectory provides direction. The short-term action plan provides traction.

A roadmap is not a prediction. It is not a fixed schedule. It is a strategic framework that adapts as reality unfolds. Near-term actions are mapped with firmness and specificity. Far-term actions are mapped with flexibility and breadth. The roadmap lives and breathes. It is reviewed, revised, and renewed at regular intervals throughout the project.

Making a roadmap happens after several rounds of the method cycle and is a phase of convergence. You are not generating new ideas at this stage. You are selecting, eliminating, sequencing, and committing. The brainstorming is behind you. The planning is ahead.

Size and Scale

A roadmap differs greatly depending on the size, scope, and ambition of a project. For a small community project, it may consist of a few bullet points with time frames and role divisions. For a multinational company transition, it may span decades, involve hundreds of stakeholders, and require a dedicated team to manage. Despite this diversity, the basic structure is the same. The ten steps work at every scale.

Start on Paper

Start a roadmap on paper or a whiteboard. Gantt charts and Kanban boards are useful tools, but they constrain in ways you may not notice. Paper is unbeatable for initial roadmap design. It invites collaboration. Team members can crowd around a large sheet and place items simultaneously. Once the main structure is set and the main items are planned, digitize. In practice, maintain both a digital and a paper version throughout the project. Paper keeps collaboration open. Digital keeps records clean.

The Roadmap as a Stakeholder Tool

In projects where stakeholders determine the success of implementation, the roadmap may be the central deliverable of the entire SiD trajectory. In those cases, the roadmap is best co-created with the stakeholders. A core team prepares the project, researches data, identifies and invites stakeholders, and guides them through the process. The roadmap becomes the shared agreement: what will happen, when, and who is responsible.

The Ten Steps, Expanded

Step 1. Draw the global timeline.

The timeline always starts at today and ends at the project's 100% success. Where you place that end point determines the project's ambition. Draw a horizontal line on a large sheet of paper. Mark years or months at regular intervals. If you draw the timeline in the middle of the paper, you create two working zones: the top for performance goals and milestones, the bottom for the actions required to achieve them.

The timeline may coincide with the time horizons explored during system mapping. For a neighborhood sustainability plan, you might draw from 2026 to 2040. For a national energy transition, from 2026 to 2060. For a company circularity program, from this quarter to 2035.

Step 2. Place the end-goal and set ambition level.

Setting the 100% success point of the project is the single most important performance factor. The goal should always be expressed performatively (describing the system's desired performance, not prescribing a specific solution) and at the system level.

Place the end-goal at the far right of your timeline. If the project goal was set in Step 1 of the method to include a time frame, use it. If not, this discussion becomes a priority.

The ambition of a project is not expressed by the height of the goal. The goal should always be 100% sustainable, because that is what a sustainable society requires. The ambition is expressed by the timeline. Making the world run on renewable energy by 2150 is unremarkable. By 2040 is aggressive. As the saying goes: "A goal without a deadline is a dream." You want to change the world? Set a deadline.

Step 3. Review ambition level and adjust.

Take a moment with your group to reflect. Think about everything that needs to happen between now and the end-goal. Is the timeline realistic enough to be credible? Is it ambitious enough to matter?

Consider the overstating principle from the Theory section. Complex systems resist change. Historic momentum, stakeholder inertia, and competing priorities create drag. If you aim precisely for B (your desired state), you will not arrive at B. You will arrive somewhere between the default trajectory A' and B. To actually reach B, you must aim for B*, which is beyond B. This means setting a timeline that is more ambitious than you think you can achieve, so that after the inevitable compromises, you still land in a strong position.

If the goal feels impossibly ambitious, it may inspire extraordinary effort. If it feels absurdly impossible, people will not even try. Calibrate carefully. Push for ambition, but stay within the range of credible stretch.

Step 4. Map all solutions onto the timeline.

Gather the solutions developed in previous method cycles. Write each solution on a post-it note and place it on the timeline where you think it should be implemented. If there is only one solution (and it is the goal itself), skip to the next step. Usually, there is a whole landscape of solutions that together make up the transition.

For a city sustainability plan, you might have solutions in transport, energy, water, biodiversity, education, housing, governance, and economic development. Write them all. Place them all. This is a group exercise. Have team members work simultaneously, placing their solutions and then stepping back to review together.

Review placement with the group. Expect some chaos. That is productive. Discussion about timing forces the team to think about dependencies, prerequisites, and realistic sequencing.

Step 5. Cluster solutions by channel or theme.

If your solutions come from a raw brainstorm dump, they need clustering. Group similar solutions by theme. ELSI categories provide a natural clustering structure: energy, ecosystems, materials, economy, health, happiness, culture, species. You can also cluster by organizational function (governance, operations, communications, finance) or by geographic area.

Once clustered, eliminate duplicates. Review clusters with the full group. Eliminate outliers that do not support the overall goal. For projects with many small items, replace clusters with overarching "channel" solutions. This way, a single roadmap can have many sub-projects nested beneath it. A channel called "Circular Materials Program" might contain twenty individual actions.

Step 6. Identify and solve gaps.

Your clustered solutions now sit on the roadmap. Order them neatly in time within each channel. Review the sequence. You will notice that critical preparatory steps are missing. A circular product requires a designer. A designer requires funding. Funding requires a business case. A stakeholder session requires planning and invitations. A new policy requires political alignment.

Add these missing steps. Do not go into excessive detail, but place critical enabling actions where they belong. This is also the stage to add roadmap governance channels that cluster universal management tasks. For large sustainability projects, typical governance channels include:

• Governance, management, and funding
• Data management, collection, and tooling
• Reporting and communications
• Guidelines and training
• Stakeholder engagement and alignment

These governance channels run parallel to the content channels and ensure the organizational machinery supports the transition.

Step 7. Identify transition actions.

For each channel, identify what type of transition each action represents. The SiD framework recognizes five fundamental transition types:

• Start: Initiating something entirely new (experimentation, acceleration phases)
• Stop: Phasing out something that no longer serves the system (reduction, phase-out phases)
• Change: Modifying existing practices (identification, optimization phases)
• Replace: Substituting one approach for another (implementation, institutionalization, stabilization phases)
• Scale: Expanding something that works at small scale to system-wide adoption

Each transition type requires fundamentally different management skills, investment profiles, organizational structures, and risk tolerance. Managing a "change" process is different from managing a "start" or "stop" process. A team comfortable with entrepreneurial launches may struggle with the diplomacy of phasing out an established practice.

For large projects, consider assigning different teams for different transition types. At minimum, mark each action's transition type on the roadmap. This makes the management requirements visible and prevents the common mistake of treating all actions as if they require the same approach.

Step 8. Assign responsibility to stakeholders.

The roadmap is now complete in terms of content. Without responsibility assignment, it remains a wish list. At this point, parties must be identified and committed to take ownership of each channel or solution.

For large stakeholder trajectories, this process alone can take multiple sessions. Bilateral conversations are often needed to negotiate responsibilities, legal issues, budget allocations, and reporting lines. Do not rush this. The difference between a roadmap that gets executed and one that gathers dust is whether specific people have agreed to be accountable for specific outcomes.

Establish a governance structure: who reports to whom, in what format, at what intervals. This structure should connect to the milestone and review cycles you set in the next step.

Step 9. Set milestones and checkpoints.

With responsibilities and governance in place, determine how often the project evaluates progress and commits to milestones. For roadmaps spanning decades (city transitions, national strategies), set milestones that hook into existing management cycles: fiscal years, annual management meetings, political cycles.

Performance milestones help structure the trajectory. For a 15-year roadmap with three 5-year periods, you might target 33% of the goal at the first milestone and 66% at the second. You can curve the difficulty: make early milestones easier to allow an ease-in period, and later milestones more demanding as the project gains momentum and institutional support.

Milestones serve three functions: they create urgency, they provide evaluation points, and they create natural moments for celebrating progress and renewing commitment.

Step 10. Create short-term action plans.

The roadmap is finished. To set it in motion, create a short-term action plan covering the first 3 months to 3 years. This action plan translates the roadmap's strategic direction into unambiguous, concrete, and transparent actions that each responsible party can execute independently.

The action plan should include:

• Processing and documenting the roadmap in its final form
• Securing final approval from key stakeholders
• Communications and public relations actions
• Starting the first management actions
• Scheduling required meetings (management approvals, stakeholder gatherings)
• Planning a kickoff event

The end of the first action plan should coincide with a gathering of all relevant stakeholders to evaluate progress and set the next action plan. Depending on complexity, this may be at the first milestone or sooner.

Then organize a kickoff. And kick it off.

Roadmaps Prevent Systemic Lock-in

Working without a roadmap leads to high risk of systemic lock-in. Lock-in is a situation in which a decision fixes the system's development pathway in a direction that prevents future flexibility. Choosing to invest in a machine that only accepts a specific input resource locks in the need for that resource for the machine's economic lifetime. For a machine, the example is simple. But lock-in occurs in far more obscure places: policy decisions, organizational structures, supply chain contracts, infrastructure investments.

Working with a roadmap toward 100% systemic sustainability performance helps prevent lock-in. With each solution step on the roadmap, you evaluate whether it supports both the immediate milestone and the long-term goal. If a solution leads to lock-in further down the road, it becomes obvious in the context of the full pathway.

Consider energy transition. A city might invest in natural gas infrastructure to achieve a near-term carbon reduction milestone. But natural gas is a non-renewable fossil fuel. That investment locks in dependency on fossil infrastructure for decades and may prevent reaching the long-term goal of 100% renewable energy. When the full roadmap is visible, this conflict is apparent. Without the roadmap, the near-term decision looks sensible in isolation.

The 100% goal is what makes this visible. If your goal is merely "reduce emissions by 30%," gas infrastructure looks fine. If your goal is "100% renewable," it clearly does not fit. The ambition of the goal protects the integrity of the pathway.

Symbiotic Planning: The Game Theory of Sustainability

SiD's planning approach combines the strengths of both top-down and bottom-up planning, and the result resembles game theory.

Top-down planning provides long-term vision, clear direction, and the authority to set boundaries. Its weakness is rigidity: inability to adapt, stifled innovation, and disconnection from the people who must implement the plan. Consider Brasilia, the Brazilian capital planned entirely from above. Its modernist grid works for cars but created a city devoid of the human-scale spontaneity that makes cities livable.

Bottom-up planning provides flexibility, entrepreneurship, local quality, and community engagement. Its weakness is lack of direction: no coherent long-term vision, inconsistent quality, and the inability to execute large singular projects efficiently. Bottom-up organizations tend to self-construct hierarchy as they grow. Top-down organizations tend to break down and require bottom-up initiatives to survive.

Symbiotic planning combines both. You set long-term goals and development boundaries (top-down). You then fill the roadmap with short-term initiatives discovered through bottom-up stakeholder engagement and solution development (bottom-up). You provide incentives to steer the process (management).

In game theory, you set rules and boundaries (top-down), then let the system develop itself within those rules (bottom-up), while providing incentives to steer the process (running management). SiD planning works the same way.

The process in practice:

1. Set long-term systemic goals expressed in terms of performance only, not physical prescriptions. You cannot predict what technologies will exist in 20 years. Performance goals keep the solution space open.
2. Set performance boundaries (rule-sets) that prevent development going into areas you want to avoid. These are the guardrails.
3. Create a mechanism for bottom-up development within those boundaries. This is where stakeholder engagement, community initiatives, and entrepreneurial discovery come in.
4. Initiate a "feeding mechanism" of incentives that attracts bottom-up development and kicks off the process.
5. Implement a monitoring system to ensure the performance targets are being met.

It is imperative that goals and boundaries are set on a performance basis, with no unnecessary physical constraints. You want the bottom-up execution to maximize its movement space to find ideal solutions. If you specify "solar panels on every roof" instead of "100% renewable energy," you prevent the discovery of solutions you have not imagined.

The SiD Method executes this approach. You perform systemic analysis to find performance goals and boundaries (top-down), plan these on a roadmap, and engage the community to discover execution steps (bottom-up). The subsequent execution can respond to changes in context, new technologies, and new initiatives. It creates a development plan with a long-term vision that is resilient, flexible, and open to personal initiative.

Roadmap Flexibility and Review Cycles

Roadmaps span years or decades. You cannot predict what will happen over those time spans. New technologies will emerge. Political contexts will shift. Climate events will accelerate. Economic conditions will change.

Build in flexibility by design:

• Near-term firmness, far-term flexibility. Actions in the first 1 to 3 years are specific and committed. Actions in years 5 to 15 are directional and adaptable. Actions in years 15 to 50 are aspirational and open.
• Scheduled review cycles. Program mandatory roadmap reviews at regular intervals (quarterly for the action plan, annually for the full roadmap). At each review, evaluate progress against milestones, assess whether the context has changed, and adjust the roadmap accordingly.
• Trigger-based reviews. In addition to scheduled reviews, define triggers that force an immediate review: a major technology breakthrough, a policy change, a budget shock, or a missed milestone.
• Stakeholder re-engagement. At each major review, bring stakeholders back together. This maintains shared ownership and prevents the roadmap from drifting away from the people who must implement it.

The roadmap is never finished. It is a living strategic document. Execution is not the end. It is the beginning of the next cycle.