Business

Roadmap

A high-level plan showing where a product, project or company is heading and in what order

What is Roadmap?

A roadmap is a high-level plan that shows where a product, project or whole company is heading, which goals it wants to reach over time and in what order it will tackle them. It works with large units – goals, initiatives and milestones – rather than individual tasks. It answers what and why, while a project plan or Gantt chart covers exactly who does what and by when. A roadmap fits on one page, can be read by management, the team and the client alike, and is updated regularly as the company learns more about its market and customers.

Why It Matters

Without a roadmap, priorities shift to whoever asks loudest for a new feature. A roadmap keeps decisions tied to goals: every item has to show which outcome it supports, which makes it easier to say no to ideas that won't move the business forward. It is also the cheapest communication tool you have – management, the team, sales and external suppliers all see the same picture, so there are fewer meetings and misunderstandings. For a smaller company juggling a new website, a CRM and automations at the same time, a roadmap shows what to do now and what can wait.

Real-World Examples

  • 1A product roadmap for a SaaS app: now simplify sign-up, next connect invoicing, later a mobile app.
  • 2A project roadmap for a new online store by phase: analysis, design, development, data migration, launch and optimisation.
  • 3A one-year company digitalisation roadmap: CRM in Q1, automated invoicing in Q2, warehouse integration in Q3.
  • 4A marketing roadmap: local SEO and a business profile now, content strategy and a newsletter in the next period.
  • 5Illustrative example: a trades business writes three goals for the year and five initiatives on one page – nothing more.

Roadmap vs project plan and backlog

A roadmap is often confused with a schedule. The difference lies in the level of detail and the question each one answers:

  • Roadmap: goals, initiatives and sequence for the coming months to a year. Answers what and why. Read by management, the team and clients.
  • Project plan (schedule, Gantt chart): specific tasks, owners, dependencies and dates. Answers who, how and by when. Part of project management.
  • Backlog: a list of individual tasks and requests the team pulls into sprints. It is a queue, not a strategy.

Good practice is for the project plan to follow from the roadmap, not the other way round. Once you start adding individual tasks and exact dates to a roadmap, it turns into a schedule and loses its clarity.

Types of roadmap: product, project and company roadmaps

  • Product roadmap: where a product – an app, online store or service – will evolve. It ranks customer problems and features by impact and often starts with an MVP.
  • Project roadmap: the main phases and milestones of a single project, such as a website redesign or a CRM rollout. Shorter, with a clear end.
  • Strategic (company) roadmap: company-wide goals for one to three years, usually split into quarters, plus the initiatives that lead to them.
  • Technology (IT) roadmap: replacing and connecting systems – hosting, workflows and automation, integrations, security.

The type of roadmap defines its audience. A product roadmap mainly serves the team and customers, a strategic one serves management and stakeholders.

Formats: timeline or Now–Next–Later

A timeline roadmap places initiatives on an axis by month or quarter. It suits situations with fixed dates – a season, a trade fair, a regulatory change. The downside: people read dates on a roadmap as promises, and every slip looks like a failure.

Now–Next–Later replaces dates with three columns based on certainty. By her own account, the format was invented by Janna Bastow (co-founder of ProdPad) with Simon Cast; they sketched the first version in 2012.

  • Now: work that is clearly defined and being built right now.
  • Next: problems to pick up once the current work is done; less detailed.
  • Later: bigger, fuzzier problems you want to keep in view but aren't ready to commit to.

A theme-based roadmap groups items by goals or themes (for example, “more enquiries from the website”) and can be combined with either format. For a small business, Now–Next–Later with a quarterly horizon for the Now column is usually the most practical.

How to build a roadmap in 6 steps

  1. Name your goals. Two to four measurable outcomes for the period, ideally with KPIs – for example, more enquiries from the website or faster order handling. They should follow from your marketing strategy and business plan.
  2. Collect input. Requests from customers, sales, support and management in one place. Don't promise anything yet.
  3. Group them into initiatives. Turn dozens of ideas into a few larger pieces of work with a clear contribution to a goal.
  4. Rank by impact and effort. Whatever delivers the most for the least effort goes into Now. A simple impact × cost score helps.
  5. Add owners and dependencies. One accountable person per initiative and a note of what it depends on (data, supplier, budget).
  6. Share it and review it regularly. Go through the roadmap at least once a quarter and after any major change; only the items in Now become a detailed plan with deadlines.

Roadmap template

To start, a spreadsheet in Excel or Google Sheets, a board in Trello or Notion, or Jira or Airtable if you already use them is enough. Each roadmap item should have these fields:

  • Goal: which outcome the initiative supports.
  • Initiative: a short name (e.g. “Online service booking”).
  • Why / metric: which problem it solves and how you will know it worked.
  • Horizon: Now / Next / Later, or a quarter.
  • Owner: one accountable person.
  • Status: proposed – approved – in progress – done.
  • Dependencies and risks: what the item relies on.

Illustrative (fictional) example for a bike repair shop aiming for “30% fewer phone calls about bookings”:

  • Now: online booking on the website, automatic e-mail confirmation.
  • Next: an annual service reminder, bookings synced to the technicians' calendar.
  • Later: a customer account with repair history, a loyalty programme.

When to build your roadmap with an expert

If your roadmap involves connecting several systems – website, CRM, invoicing, warehouse – it pays to review it with someone who can estimate the technical effort and the right order of steps. At Weboptim we plan process digitalisation and automation and web application development this way: we start from goals, break them into initiatives and choose the first steps by return on investment.

Frequently asked questions

What is a roadmap in simple terms?

A roadmap is a one-page plan showing where a product, project or company is heading and in what order it will pursue its goals. It works with goals and larger initiatives, not individual tasks.

What is the difference between a roadmap and a project schedule?

A roadmap covers what and why; a schedule covers who, how and by when. A roadmap shows goals and the order of initiatives months ahead, while a schedule (such as a Gantt chart) lists specific tasks, owners and dates.

What is a product roadmap?

A product roadmap describes how a specific product – an app, online store or service – will evolve. It ranks customer problems and features by value and gives the team, management and customers a shared view of priorities.

How often should a roadmap be updated?

Review your roadmap at least once a quarter and after any major change, such as a new release or a budget change. Items in Now change most often; Later items are simply refined over time.

Where can I create a roadmap, and is there a template?

You can create a roadmap in a spreadsheet (Excel, Google Sheets), on a board (Trello, Notion) or in tools such as Jira or Airtable. As a template, columns for goal, initiative, metric, horizon, owner, status and dependencies are enough.

Need help with Roadmap?

Our team can help you integrate this into your project.