Roadmap Maker Online: Build a Roadmap in 5 Steps

Step 1: Define the End Point

A roadmap is a path between two points, so you need both. Write down where you are today and where you want to be. "Get better at Spanish" has no end point. "Hold a 15 minute conversation in Spanish with a tutor by June" does.

Use the same test for work goals. "Improve the onboarding" becomes "Release the new onboarding flow and test it with five new users by the end of the quarter." When the finish line is precise, the phases almost suggest themselves.

Step 2: Choose the Phases

A phase is a stage of the journey with one purpose. When it ends, something has changed: an idea is validated, a feature is live, a skill is solid. A good test is to name each phase with a verb and a result, such as "Validate the problem" or "Build the basics".

Three rules help you choose:

• Keep 3 to 6 phases. Fewer and the roadmap says nothing. More and it turns into a task list.
• One purpose per phase. If a phase name needs "and", it is probably two phases.
• No overlap. Each step should belong to one phase only.

Typical Phases by Roadmap Type

Most roadmaps follow a familiar pattern. Use these as starting points, not as rules. If you work on a product, the guide What Is a Product Roadmap? Definition, Types and Examples shows how phases change with the type of roadmap you need.

• Product (new feature): Discover, Design, Build, Test, Launch, Learn.
• Project (office move): Scope, Plan, Prepare, Execute, Close.
• Learning (new language): Foundations, Daily habit, First conversations, Real practice.
• Career change: Explore, Learn the core skills, Build proof, Apply.

Step 3: Order the Steps

Inside each phase, the order of steps matters more than their number. For every step, ask one question: "What must be true before I can start this?" The answer tells you what comes first, as the examples below show.

Then apply a second rule: do the risky part early. If one step could make the whole plan collapse, place it as early as the dependencies allow. A founder should talk to potential users before building anything. A learner should book the first tutor session in month one, not month five, to find out early what is hard.

Last, leave some room. Add a buffer step before any fixed date, such as a launch, an exam or a moving day.

• Product: you cannot write the launch email before you know the release date, and you cannot set the release date before testing ends. So the order is test, fix, set date, write email.
• Project: for an office move, you sign the lease before you order furniture, and you order furniture before you plan the moving day.
• Learning: in a new language, you learn the most common verbs before you try short conversations, because conversations need verbs.

Step 4: Set the Milestones

A milestone marks the end of a phase. It is not a task and it is not the goal. It is the proof that a phase is done.

Place one milestone at the end of each phase. If a phase lasts more than a few weeks, add one in the middle too. A long phase with no checkpoint hides delays until it is too late.

A good milestone passes the yes or no test. Compare vague milestones with checkable ones:

• Understand the users becomes 10 user interviews done and summed up in one page.
• Make progress on the move becomes lease signed and moving company booked.
• Learn the basics of Python becomes 3 small scripts written and running without help.
• Get ready for launch becomes all test bugs fixed and the release date fixed.

Step 5: Lay It Out and Adjust

Now turn the structure into a visual roadmap. Phases become the big blocks, steps sit inside them, and milestones mark the end of each block. Read it from left to right. If you can't explain the plan in under a minute, it has too many pieces.

This is where adjusting by hand helps. With a drag-and-drop roadmap online, you move a step to another phase when the order looks wrong, without rebuilding the whole plan. Common fixes at this stage:

• A step sits in the wrong phase, so you drag it where it belongs.
• A phase has ten steps and another has one, so you rebalance them.
• The total time does not fit your calendar, so you cut steps instead of hoping.

Share It and Keep It Current

If you work with a team, keep the roadmap for the big picture. Then copy the phases and steps into the tool your team already uses for daily work, such as Jira, Notion or an Excel sheet. To win support from leadership, see How to Present a Roadmap to Executives.

Once the plan is live, review it each week. Mark what is done, move what slipped and add what you learned. If your dates keep shifting, an agile roadmap without fixed dates may suit you better. For more pitfalls, read 12 Roadmap Mistakes to Avoid.