Roadmap Conversation Table

Why this might help

Your roadmap is a living thing. It shifts when priorities change, when something takes longer than expected, or when a customer need suddenly moves to the top of the list. This room helps your team pause, look at what changed, and talk through what comes next — together. No one should leave a roadmap conversation confused about why a decision was made. When everyone understands the 'why,' the next steps feel a lot less like guesswork and a lot more like a shared plan.

Does this feel familiar?

Someone on your team asks 'wait, I thought we were building that this month?' in the middle of a sprint.
A feature quietly moved on the roadmap and half the team found out by accident.
Your last planning meeting ended with nodding heads, but a week later people are pulling in different directions.
A stakeholder outside the core team keeps asking for updates because they don't know where things stand.

Try this together

Before the conversation starts, write down the two or three things that actually changed since last time — keep it honest and short.
Ask each person to share one thing they're uncertain about before you dive into decisions.
When something moves or gets cut, say the reason out loud — even if it feels obvious to you, it probably isn't to everyone.
End the conversation by naming the next decision your team needs to make and who's going to own it.
Send a short recap right after — even three bullet points helps people remember what was agreed.

Roadmap Conversation Guide

Open your roadmap conversation guide and fill in what's changed since your last review — be specific, like 'the onboarding flow moved from week 3 to week 5 because of a design dependency.'
List the decisions your team needs to make in this conversation, not just the updates you want to share.
Go through each change together and let people ask questions before moving to the next item.
Use the guide's decision log section to write down what you agreed on and the short reason behind it.
Before closing, check the 'open questions' section and assign each one to a person with a rough date to follow up.

Questions worth talking about

What changed since we last looked at this, and does everyone know why?

Is there anything on the roadmap right now that feels unclear or hard to explain to someone outside this team?

If we could only move one thing forward in the next two weeks, what would it be and what's standing in the way?

A few common questions

How often should we run a roadmap conversation?

There's no perfect number. Many teams find a short check-in every two weeks works well — enough time for things to actually change, but not so long that surprises pile up. If your roadmap is moving fast, go more often. If things are stable, you can stretch it out a little.

What if people disagree about priorities during the conversation?

That's actually a good sign — it means people are paying attention. Try naming the disagreement clearly instead of smoothing it over. Ask what each person is worried about losing. Often the real concern is about timing or risk, not the feature itself, and that's much easier to work through together.

Can Tindlo help us keep track of what's on the roadmap week to week?

Tindlo's Week view lets your team see work items laid out across time in shared layers, so everyone can see what's scheduled and what's coming up. It won't run your roadmap conversation for you, but it can help your team stay on the same page between conversations by keeping context — files, notes, and schedule — in one place.

Keep the story close to the schedule

A date makes more sense when you can also see the reason, the owner, and the work around it. Tindlo brings those pieces together when a calendar alone isn't enough.

See how Tindlo works →

Where would you like to go next?

Engineering Leadership ExchangeEngineering leaders Product Operations CircleProduct operations teams Project Managers' WorkshopProject managers