A roadmap is supposed to be a forecast — a credible statement of what the company will deliver, by when, with which confidence. In most companies, the roadmap shown in the boardroom is closer to a costume. The Q3 bar is wide because Q3 is far away and "wide" feels appropriately uncertain. The Q1 bar is precise because Q1 is now and precision is the price of admission. Nobody in the room actually believes the Q4 dates, but they are drawn with the same confident rectangles as the Q1 ones, because a roadmap with visible uncertainty looks weak in a steering committee, and the steering committee, frankly, has been trained to want the costume more than the truth.
Three giveaways that your roadmap is theatre
You can diagnose roadmap theatre in about ninety seconds if you know what to look for. There are three reliable tells, and most company roadmaps fail at least two of them.
Nothing ever moves left. Real plans shorten as well as slip. Sometimes a team gets faster, sometimes scope drops, sometimes a hard problem turns out to be easy. If every revision of your roadmap moves things to the right and never to the left, the roadmap isn't tracking work. It's tracking optimism decay — the steady process by which the leadership team's hopes catch up with engineering's reality. A roadmap that only moves right is just a slow apology in chart form.
The bars are the same width regardless of confidence. A six-week prototype with one well-scoped team gets the same visual treatment as an eighteen-month platform replatform involving four teams and a vendor migration. Confidence is invisible in the artefact, so it doesn't exist for the audience. The board cannot tell the difference between "we are 95% sure of this" and "we have written a sentence on a slide and hope it remains true." This is not the board's fault. It's a property of the chart, and the chart was designed to hide it.
No one can trace a bar to the actual work. Click the Q2 "Customer Portal" bar in your roadmap deck and ask the room: which initiatives ladder up to this, which teams are committed, what's the dependency graph, where is the work being tracked? If the answer is silence or "I'll get back to you," the bar is decorative. It looks like a commitment. It is not actually connected to anything that would make it one.
If you find all three of these tells in your current roadmap, you don't have a roadmap. You have a costume worn by a slide deck.
Why the theatre persists
Because the alternative is uncomfortable in the short term and threatening to the planning ritual. A real roadmap with visible confidence intervals, real linkage to underlying work, and items that can move left as well as right would force every leader to acknowledge how much they don't know about the back half of the year. That acknowledgement is professionally costly in a culture where confidence reads as competence. So the theatre survives, not because anyone believes it, but because nobody wants to be the first leader to put an honest chart up in front of the board.
There's a second, more structural reason. A real roadmap is derived from the underlying work — from initiatives, capacity, dependencies, and the actual state of progress. Most companies don't have those four things connected in a single system. So nobody can derive a real roadmap even if they wanted to. The only kind of roadmap they can produce is one drawn by hand, in PowerPoint, the week before the board meeting, which is exactly the kind of roadmap that ends up as theatre.
What a real roadmap looks like
A real roadmap is a view, not a drawing. It's generated, not designed. The bars resolve to live initiatives with named owners. The widths reflect confidence intervals derived from how the work is actually tracking. Items move left when scope drops or when a team gets faster, and they move right when reality intrudes. The artefact is a window into the operating system of the company, not a slide built once a quarter by a chief of staff under deadline pressure.
The first time a leadership team sees a roadmap like this, the reaction is usually discomfort. The honest version shows more uncertainty than the costume version, which feels like a step backward. It isn't. It's the first step toward planning that survives contact with reality. The costume roadmap was never being believed; it was being tolerated. The real one can actually be operated against.
What changes when the roadmap is real
Three things. Board conversations get more useful, because the board can finally ask informed questions about which bets are most at risk and which are most certain. Internal planning gets honest, because the team can no longer hide low confidence behind a wide rectangle. And the leadership team stops spending three days every quarter rebuilding a deck nobody believes, which is itself a meaningful productivity recovery.
The Vindaris view
Stop drawing roadmaps. Generate them. When goals, initiatives, and capacity sit in the same graph, the roadmap is a query result — and the theatre ends. The board gets a real picture, the leadership team gets a real plan, and the chief of staff gets the quarter back. The only thing lost is the costume, which nobody was being fooled by anyway.