Timeline and roadmap
Steering sequence, dependencies and implementation.
A roadmap is not a visualisation.
What is a project roadmap?
It connects sequence, resources and risks into a steerable logic.
Plans without logic
Dates are not enough.
Many projects have a roadmap. Phases are defined, milestones set, dates agreed. And still everything shifts. Dependencies become visible when it is too late. Decisions are delayed. Resources are missing at the decisive moment. The problem is not the timeline. The problem is the missing logic behind it.
Four dimensions of a roadmap.
A roadmap defines dates and more.
Sequence of decisions
Which decision has to be made in which phase?
Dependencies between phases
What requires what? Which external conditions must be met before the next phase starts?
Resources over time
When are which resources available? Where do bottlenecks arise that would block the project?
Risks and correction points
Where do typical breaks occur? At which points is the roadmap checked and reordered if necessary?
Planning at operational level
In practice, planning often begins at operational level. Tasks are defined without properly ordering the sequence. At the same time, the link to dependencies is missing. Systems, organisation and external partners are not integrated.
A roadmap without dependencies
A project is planned in phases and given set dates. Implementation starts on schedule. Over time it becomes apparent that systems are not ready, decisions are missing and resources are unavailable. The cause does not lie in the pace. The dependencies were not taken into account. The consequence is a reorganisation. The project becomes steerable.
Intervention point before escalation
The roadmap as a living steering instrument.
A roadmap does not stay static. Plan and progress diverge. The only question is when the gap becomes unmanageable. A sound roadmap defines intervention points where the sequence is deliberately reordered before the gap escalates. This keeps the project manageable, even when reality departs from the assumption.
Roadmap from project logic
Decision points are named and linked to dependencies. Systems, organisation and external influences are integrated. Resources are assessed realistically and prioritised.
When roadmap work becomes relevant
When projects keep shifting.
The topic becomes relevant when projects are postponed again and again. When dependencies only become visible during implementation. When resources are not available at the right time. Or when a roadmap exists but is not used as a steering instrument.
What distinguishes a roadmap from a timeline?
A timeline lists what happens when. A roadmap shows the order in which decisions must be made so that a project remains manageable.
How far into the future should a roadmap reach?
Dense at the front, open at the back. The first phases are planned in detail, later phases deliberately remain rough.
How often should a roadmap be adjusted?
At every intervention point. That is the moment when plan and progress are deliberately compared. Yoline defines these points as part of the roadmap.
Who is responsible for the roadmap?
The project lead. A roadmap that is delegated is not effective.
How does a roadmap relate to project planning?
The roadmap is part of the planning. While planning connects goal, phases and resources, the roadmap arranges these elements over time. Both are part of the same project logic.