Drop the Dates: How to Run a Now-Next-Later Roadmap and Sell It to Execs

You have felt this. The roadmap review turns into a fight about dates. Someone points at a quarter you named eight months ago and asks why it slipped. Now you are defending a guess you made when you knew the least. The dates were never real, but they became the scorecard anyway.

A Now-Next-Later roadmap fixes the format. It swaps fake precision for honest priorities. But a better format does not survive on its own. If you walk into a leadership review with three columns and no plan for how to present them, execs will just ask you to add dates back. This brief is about both halves: the roadmap, and how to defend it in the room.

The deep cut

• Dates you invent early are the dates you know least. Janna Bastow built Now-Next-Later to kill false certainty, not planning.
• A slipped fake deadline reads as failure. Endless shifting dates drive the blame culture and low morale Bastow warns about.
• Pre-align before the room, not in it. Brett Truka says the review should hold few surprises.

Why timeline roadmaps fail you

The problem with a timeline roadmap is not that it is ambitious. It is that it forces you to commit to work you cannot see yet. You pick a ship date for a thing you have barely scoped, then spend the next two quarters defending or apologizing for that number. One sharp version of this take is that timeline roadmaps are a waste of time because they create false certainty and force teams to defend deviations from a fake plan.

Bastow saw this run out of Jira and release planners built for engineers. Long, detailed, unreadable to anyone outside the team. The backlog grew, the dates slipped, and every roadmap talk became a negotiation about deadlines instead of a talk about what mattered.

The damage is not just wasted planning time. Missed dates wear down the team. People do good work and still feel like the company thinks they are slow, because the work was never suited to hard deadlines in the first place. That is how you breed blame.

What the three columns actually hold

Now-Next-Later is three columns, and they are not equal. Now holds work you are actively building. It is spec'd, broken into real pieces, and you have real confidence about scope and impact. Next holds problems you expect to pick up when Now wraps, sketched with fewer details. Later holds the big, fuzzy problems you want to keep in view but are not ready to commit to.

The reason this works is that certainty gets portioned out over time. You make hard commitments only about what is right in front of you. The far stuff stays flexible because you have not locked it in. As Later items move closer, you spec them out.

The columns are not just a to-do list with better labels. Each item must tie back to a business objective. Bastow's rule is to prioritize problems, not ideas, then hang your experiments and features off each problem. Glance at the board and you should see what success looks like for the business, not just what the team is busy with.

Roadmaps earn their keep three ways

The format is only as good as what fills it. Roman Pichler argues a great roadmap is goal-oriented, shared, and actionable. Those three tests catch the roadmap that is secretly just a feature list wearing new columns.

Goal-oriented means every item points at an outcome, not an output. Shared means the plan is not yours alone; engineering, sales, and leadership own a piece of it, so no one is surprised later. Actionable means the team can actually pick up the top of the Now column and start.

Run your Now-Next-Later board through these three before any exec sees it. If an item has no objective attached, it fails goal-oriented. If only product knows it exists, it fails shared. Fix that first, or the review will find the gaps for you.

Selling it in the room

A good roadmap loses if you present it badly. Execs who grew up on Gantt charts will ask for dates the moment they feel uncertain. Your job is to remove that uncertainty before the meeting. Truka's playbook is direct: pre-align with execs one on one, so the review confirms what they already heard instead of springing news on them.

Let the visuals carry the story. Three clean columns tied to objectives read in about ten seconds, which is the whole point of the format. Save the deep detail for other audiences and other meetings. Execs want direction and tradeoffs, not your full backlog.

When you adapt this for B2B, expect pushback about customer commitments. In a conversation between Rich Mironov and Rahul Abhyankar, the practical note is that NNL bends for exec and B2B audiences, but you have to know where it breaks. If a customer contract needs a real date, say so on the board. Honesty about the one hard deadline protects the flexibility on everything else.

Three questions for your team

• Where does our current roadmap create false certainty, and what deviation are we already defending from a date we made up? Name it, then decide if that date should exist at all.
• Which items in Now, Next, and Later have no business objective attached? Anything you cannot tie to a goal does not belong on the board yet.
• Have we pre-aligned with each exec before the review, and are our visuals carrying the story without the backlog? If not, book the one-on-ones this week.