Roadmap Workshop: How to Run One in 3 Weeks (+ Agenda)

9 min read ยท 2026-10-12

A roadmap workshop is a working session where the people who shape a plan agree on its goals, priorities and order before anyone draws the final roadmap. A good one takes about 3 weeks from start to finish: 2 weeks to prepare, a half day to run it, and about a week and a half to turn the output into a roadmap everyone has seen and accepted.

The workshop itself is the easy part. The real work happens before, when you pick the question you want answered and gather the facts, and after, when you turn sticky notes into a clear plan. This guide gives you the full 3-week roadmap, an agenda you can copy, and the mistakes that make workshops end with lots of ideas and no decisions.

The roadmap at a glance

Goal: Run one roadmap workshop that ends with an agreed, prioritized roadmap shared with every stakeholder. Duration: 3 weeks

  1. Define the Goal and Scope (Days 1-3)

    Decide what the workshop must answer, so nobody walks in with a different idea of why they are there.

    • Write the one question the workshop must answer, for example "What do we build in the next two quarters?"
    • Set the time horizon: one quarter, two quarters or a year.
    • List what is out of scope, such as budget, hiring or tools.
    • Get the sponsor to confirm the question and scope in writing.

    Milestone: The sponsor has approved a one-paragraph workshop brief.

  2. Gather the Inputs (Days 4-8)

    Collect the facts people need to make decisions, so the room argues about priorities, not about data.

    • Pull the company or team goals for the period.
    • Collect open requests from sales, support and leadership into one list.
    • Note fixed dates: contracts, launches, events, regulatory deadlines.
    • Ask engineering or delivery leads for rough size estimates on the biggest items.
    • Run short 15-minute calls with 3 to 5 key stakeholders to hear their top concerns.

    Milestone: A pre-read of two pages or less that holds goals, candidate items, fixed dates and constraints.

  3. Invite and Set Up (Days 9-12)

    Get the right people in the room and make sure they arrive ready.

    • Send invites with the brief, the date and the length of the session.
    • Share the pre-read at least two working days before the workshop.
    • Book a room with wall space, or set up a shared online board.
    • Prepare the board: columns, the list of candidate items as cards, voting dots.
    • Pick a facilitator who will not also defend their own items.

    Milestone: All invitees have confirmed and received the pre-read.

  4. Run the Workshop (Day 13)

    Turn a long list of items into an ordered set of priorities in one half-day session.

    • Open with the question, the goals and the rules of the session.
    • Group items into themes and remove duplicates.
    • Vote, then sort items into Now, Next and Later.
    • Check dependencies and fixed dates against the order.
    • Close with a recap of decisions, open questions and owners.

    Milestone: A photo or export of the final board with every item placed and every open question assigned to someone.

  5. Build the Draft Roadmap (Days 14-17)

    Turn the workshop board into a roadmap people can read without having been in the room.

    • Convert each theme into a phase or a lane.
    • Add milestones and the fixed dates from Phase 2.
    • Write one line under each item explaining why it is there.
    • Resolve open questions with their owners.

    Milestone: A draft roadmap that fits on one screen.

  6. Review and Share (Days 18-21)

    Confirm the plan with the people who were there and the people who were not.

    • Send the draft to attendees with a short deadline for comments.
    • Hold a 30-minute review to settle the last disagreements.
    • Get the sponsor's sign-off.
    • Share the final version with the wider team and set the date of the next review.

    Milestone: The sponsor has signed off on the roadmap and the wider team has received it.

Who to Invite and How Many People

Invite the people who decide, the people who deliver and the people who hear from customers. For a product roadmap, that usually means the product manager, an engineering lead, a design lead, someone from sales or customer success, and the sponsor who owns the final call. For a project roadmap, swap in the project manager, the delivery leads and a client or business representative.

Keep the group small. Six to eight people is a size where everyone can speak and decisions still happen. If more people want a say, hear them in the Phase 2 calls and bring their input into the pre-read instead of into the room. Before you send invites, write down who makes the final call when the group disagrees. If that is not clear before the workshop, the workshop will not make it clear.

A Half-Day Agenda You Can Copy

This agenda fits a 3.5-hour session with one break. Shorten each block if your horizon is one quarter or your item list is short.

Workshops often drift when the group keeps adding items to Now. The Reality check block stops that: it forces the group to trade items off.

  • 0:00 to 0:15, Opening. Restate the question, the horizon, what is out of scope and who decides.
  • 0:15 to 0:35, Goals check. Read the goals aloud. Ask each person to name the one goal they think matters most. Write the answers up.
  • 0:35 to 1:15, Theme sort. Place every candidate item on the wall. Group them into themes in silence for 10 minutes, then discuss the groups.
  • 1:15 to 1:30, Break.
  • 1:30 to 2:10, Vote and discuss. Each person gets a fixed number of votes. Discuss the top items first and the items with split votes second.
  • 2:10 to 2:50, Now, Next, Later. Place each item in one of three columns. Check fixed dates and dependencies as you go.
  • 2:50 to 3:20, Reality check. Ask the delivery leads if Now can really fit in the time available. Move items out until the answer is yes.
  • 3:20 to 3:30, Close. Read back the decisions, list open questions, assign owners and set the date the draft will be shared.

Three Exercises That Create Decisions

Brainstorming produces ideas. A roadmap workshop needs decisions. These three exercises are simple to run and they push the group to choose.

If the group gets stuck between two items, ask a single question: "Which one moves our main goal more in this period?" Then let the decision owner choose. Note the losing item in Next or Later so people see it was heard, not dropped.

If the workshop shows that a big item is still an untested idea, do not force it into Now. Testing it first in a design sprint can be the better next step.

  • Silent theme sorting. Everyone moves cards into groups without talking for 10 minutes. This keeps the loudest voice from shaping the themes and surfaces duplicates fast.
  • Dot voting with a limit. Give each person fewer votes than there are items, for example a third of the list. A small number of votes forces each person to show what they really care about.
  • Now, Next, Later sorting. Three columns with no dates. Now is what the team commits to. Next is what is likely if Now goes well. Later is what is kept in view without a promise. Teams agree faster on order than on exact dates.

Running a Remote or Hybrid Workshop

A remote roadmap workshop works if you plan for shorter attention. Split the half day into two sessions of about 90 minutes on consecutive days, with the theme sort in the first and the vote and Now, Next, Later sort in the second. Use one shared online board, such as Miro or FigJam, and set it up the day before so nobody spends time learning the tool live.

Ask everyone to join from their own screen with camera on, even people sitting in the same office. Hybrid sessions where half the group shares one room and the other half dials in can leave the remote people out. Give each person a named area on the board for their votes and comments, and have the facilitator read out what is being moved, so everyone follows the same change at the same time.

Turning Workshop Output Into a Roadmap

The board at the end of the session is not your roadmap. It is a record of decisions. In Phase 5, rebuild it as a plan someone outside the room can understand in a minute. Each theme becomes a phase or a lane. Each Now item gets a milestone that can be checked, such as "beta available to 10 accounts" instead of "work on beta."

Add one short reason under each item. When someone asks six weeks later why an item is in Now, the answer is already on the roadmap. Keep the draft to one screen. If it does not fit, the plan is too detailed for a roadmap and the extra detail belongs in a project plan or a backlog. Many teams start by rebuilding the board in a slide deck or a spreadsheet, then move to a visual roadmap tool once the plan needs regular updates. If you want a starting layout, begin from a roadmap template.

Common mistakes to avoid

  • Inviting everyone who asks, which turns the session into a debate. Keep the room to six to eight people and gather other views in Phase 2 calls.
  • Skipping the pre-read and spending the first hour explaining the data. Send two pages two working days before the workshop.
  • Leaving the decision owner undefined, so ties never get broken. Name who decides in the brief and repeat it in the opening.
  • Letting Now grow until it holds every popular item. Run the Reality check with delivery leads before you close.
  • Ending without owners for open questions. Assign one name and one date to each question before people leave.
  • Sharing the final board photo as the roadmap. Rebuild it as a one-screen plan with phases, milestones and a reason for each item.

Frequently asked questions

How long should a roadmap workshop be?

A half day is enough for most teams planning one or two quarters. A full day can make sense for a yearly plan with many teams involved. For remote groups, two sessions of about 90 minutes on consecutive days usually work better than one long call.

Who should facilitate a roadmap workshop?

Pick someone who knows the process but does not own items on the list. That can be a product ops person, a project manager from another team or an outside facilitator. If the product manager must facilitate, ask someone else to take notes and track time.

What is the output of a roadmap workshop?

The direct output is a sorted list of items in Now, Next and Later, with open questions and owners. Within a week, that output should become a draft roadmap with phases, milestones and a short reason for each item. The workshop is finished when the sponsor signs off on that roadmap.

How often should you run a roadmap workshop?

Run a full workshop when you plan a new period, such as each quarter or each half year. Between workshops, short monthly reviews are enough to update progress and move items. A new full workshop is also worth it when goals change or a major event shifts priorities.

Can you run a roadmap workshop for a personal or learning goal?

Yes, the same steps work with fewer people. Write the goal and horizon, list everything you could do, sort it into Now, Next and Later, and check what fits your available time each week. Ask a mentor or friend to play the role of the reality check.

Generate this roadmap with AI