Now, Next, Later: A Roadmap People Will Read

The analyst presents the roadmap to the leadership team on one page. It has no dates on it. The finance director raises an eyebrow, then reads the page twice and says it is the first plan he has seen that tells him how much to trust each part of it. The page does not promise. It orders, explains and admits uncertainty, and that turns out to be what people wanted. If you are joining us on day four, here is where we are. This week is five days on turning a long list of requirements into a roadmap, following one analyst at a regional online grocery retailer who has 60 requirements for the customer app and the delivery operation and has to plan the next two quarters. Day one showed that a list answers what, while a roadmap answers in what order and why. Day two grouped 52 distinct requirements into five themes, each tied to a business goal. Day three sequenced them using dependencies, risk, learning, capacity and fixed dates, placing delivery reliability and checkout first, then substitutions and loyalty, then customer service tools. Today we turn that sequence into a document people will read.

Why horizons beat dates

A date is a promise, and in the early life of a plan it is a promise most teams cannot keep. Estimates for work due in two weeks are fairly reliable. Estimates for work due in five months are guesses, however carefully they are made. Putting a date against everything gives the whole plan the same apparent certainty, so when the distant dates slip, as they will, readers conclude that the plan as a whole is unreliable, including the parts that were firm.

The Now, Next, Later format fixes this by showing confidence in the structure itself. Now holds the work that is committed and under way. Next holds the work that is likely and sequenced, but still being shaped. Later holds the intentions: things the business expects to do, with the least detail and the most room to change. The farther away something is, the less is said about it, and that is a feature of the format. Each item can carry a note on how confident the team is and what would change its position, so the reader sees reasoning and not just placement. The table below shows the example roadmap in this form.

THE EXAMPLE ROADMAP, IN NOW, NEXT, LATER FORM

Illustrative. Months are shown as ranges, not dates.

Two cautions keep the format honest. The first is that Later must not become a dumping ground. If every unloved requirement is parked there, readers learn that Later means never, and the horizon loses its meaning. Keep Later short, tied to goals the business has genuinely stated, and review it as often as Next. The second is that Now must be small enough to be true. A Now column with eleven themes is a wish list in a more attractive layout. If the team can carry two themes, Now shows two, and the confidence rating beside it means something. When readers see that Now always turns out to be what was said, they extend that trust to Next, and a plan that is believed is worth more than one that is ambitious, because stakeholders will plan their own work around a plan only when they believe it. That belief is built slowly, one quarter at a time, and lost quickly.

One roadmap, two conversations

Different readers need different levels of the same truth. The leadership team wants the themes, the goals they serve, the order and the confidence, on one page, with the trade-offs visible. The delivery team wants the detail for Now: the requirements inside each theme, the dependencies between them and the acceptance conditions. A good roadmap has a version for each, and the two must agree. The leadership page is a summary of the delivery view, never a more optimistic cousin of it.

When you present, lead with the goals, not the features. Say what the plan is meant to change for the business, then show the order, then show the confidence. Leave out technical vocabulary unless the room uses it. Say clearly what is not on the roadmap, because a readable boundary is more valuable than a long list of hopes. And record the date the roadmap was last updated and by whom, on the page itself, so anyone who finds a stale copy knows to ask for the current one.

Expect questions, and prepare short answers to the three most common. Why is this not earlier? The answer is a dependency or a fixed date, shown on the sequencing page. How sure are you? The answer is the confidence rating and what would change it. What happens if we want it sooner? The answer is the trade: something else moves, and here is what. Having these ready is not defensive. It shows the roadmap has reasoning behind it, which is the difference between a plan people accept and one they relitigate every week. If a question reveals something the plan missed, say so, note it, and update the page. That responsiveness is part of what makes the roadmap trusted.

Saying no with the plan in your hand

A roadmap changes how an awkward request feels. Without one, a new request meets a personal refusal and the analyst is in a negotiation about her own willingness. With one, the request meets a plan, and the conversation becomes about the plan. The pattern is simple: acknowledge the request, show where it would go, say what it would move, and ask whether that trade is wanted. "We can add this. It would sit in Next, which means substitutions slips by about a month, because the same team builds both. Do you want that trade?"

Most of the time the answer is no, and nobody has had to say it. Occasionally the answer is yes, because the requester knows something the plan does not, and then the roadmap earns its keep a second time: the change is visible, agreed and recorded. Either way, the analyst has stopped being the person who says no and become the person who shows the consequences. Tomorrow closes the week on keeping the roadmap honest after it is published.

Go out and be successful.

Oluwatosin Ogunkoya · Flotog BA Insights · 1:1 mentoring and coaching for BAs at every career stage · www.flotogbainsights.com

TOMORROW

Keeping the Roadmap Alive - A review rhythm, the triggers that justify a change, handling urgent asks, and what the skill means for your career.