Community

translate Automatic translation · View original

From the Roadmap to the Honest Roadmap: How to Present Uncertainty Without Losing Credibility

From the Roadmap to the Honest Roadmap: How to Present Uncertainty Without Losing Credibility
You're in a meeting with stakeholders, presenting your quarterly roadmap, when someone asks, "When will feature X be ready?" You know the question is a trap. If you give a date, you commit. If you say "I don't know," you lose credibility. If you say "it depends," you seem evasive. And yet the reality is that you work with constant uncertainty: changing priorities, discoveries in discovery, unforeseen technical dependencies. How are you supposed to present a roadmap that reflects reality without appearing to have no control?

There is something deeply contradictory in how we treat product roadmaps. On the one hand, we all know they will change. Teresa Torres documents in Continuous Discovery Habits how continuous discovery means solutions emerge from experimentation, not from detailed planning. And yet we keep creating roadmaps that look like Gantt project plans: columns by quarter, specific features placed on concrete dates, dependencies marked with arrows. Everything perfectly aligned, everything apparently predictable. Why?

Detailed roadmaps persist not because they are useful for product teams, but because they give psychological comfort to executives and stakeholders who confuse detailed planning with control. The roadmap has become organizational theater where everyone acts as if the dates were real, even though no one truly believes it.

This dynamic creates a systemic problem. Product teams know they need flexibility to respond to what they learn, but stakeholders interpret that flexibility as a lack of professionalism or an inability to execute.

There is also a fundamental semantic confusion between commitment and estimation. When you put a date on a public roadmap, stakeholders read it as a contractual commitment. From the product side, however, it is often just a preliminary estimate subject to validation and change. This disconnect generates recurring conflicts: "But you promised me it would be ready in June!" versus "No, we said we were aiming for June if there were no technical blockers."

The problem is made worse because admitting uncertainty is culturally perceived as professional weakness in many organizations. If you say, "I don't know exactly when it will be ready because it depends on the results of experiments we haven't run yet," some stakeholders hear, "This PM doesn't know what they're doing." Corporate cultures that value the appearance of control over real adaptability implicitly penalize honesty about uncertainty.

The Hidden Costs of Roadmaps That Fake Certainty

When we build roadmaps that hide uncertainty, the consequences run deeper than they appear. On the surface, there is the loss of trust when dates inevitably slip, and the burnout of teams that burn themselves out trying to meet unrealistic commitments. But there are less visible costs that erode organizational capacity in more insidious ways.

One is what John Cutler calls "output theater": teams optimizing to deliver the roadmap rather than to generate impact. If your evaluation as a PM depends on the "percentage of roadmap delivered on time," you are incentivizing conservative roadmaps full of low-value work that you can control, instead of risky but important strategic bets. The organization looks productive (look how much we delivered) while losing competitive ground, because no one is working on the hard problems that really matter.

Another cost is the death of genuine discovery. If you have already publicly committed to building a "push notification system in Q2," what incentive do you have to do honest discovery that might reveal notifications aren't the best solution? The roadmap becomes a self-fulfilling prophecy: we do what we said we would do, regardless of whether it is still the right thing, because changing course would mean admitting we were wrong.

There is also the accumulated political cost. Each time a roadmap changes without adequate explanation, you accumulate small amounts of distrust with stakeholders. Over time, this credibility debt becomes paralyzing: no one believes your roadmaps anymore, but you still have to create them, generating cynicism among everyone involved.

Roadmap Formats That Structurally Communicate Uncertainty

The good news is that the problem is not inherent to the concept of a roadmap, but to how we design them. There are alternative formats that communicate strategic direction while staying honest about uncertainty.

Now-Next-Later

This format was popularized by Janna Bastow of ProdPad. Instead of specific quarters (Q1, Q2, Q3), it groups work into three vague time horizons:

  • "Now" represents the coming weeks, with high certainty about what you will work on.
  • "Next" covers the coming months, with medium certainty.
  • "Later" is the distant future, where you have direction but little specificity.

This format visually communicates that precision decreases with time distance, which is honest about how product work actually happens.

The power of this approach is not only the visual format, but how it changes conversations. When a stakeholder asks, "When will we have X?" you can answer, "It's in Later, which means it is part of our strategic direction but we don't yet have enough information to commit to a specific date." It is honesty that doesn't sound like an excuse, because the format itself validates the answer.

Problem-Based Roadmaps

Problem-based roadmaps, which focus on problems instead of solutions, offer another powerful alternative. Instead of listing "push notification system - Q2," you write "improve reengagement of inactive users - Q2." This preserves flexibility about the specific solution (perhaps notifications won't be the best answer once you investigate) while communicating which problem you are tackling and roughly when.

This format also educates stakeholders about how modern product development works. If someone asks, "But what exactly are you going to build?" the answer is: "That is precisely the question discovery will answer. What we know is that inactive users are a critical business metric and we need to improve it. How we will do it will emerge from understanding better why they are inactive." It is pedagogy built into the artifact.

Roadmaps With Explicit Confidence Levels

Roadmaps with explicit confidence levels add another dimension of honesty. You can keep a relatively traditional format but accompany each initiative with a confidence indicator:

  • green for high confidence (already validated, only execution remains),
  • yellow for medium confidence (clear hypothesis but not yet validated),
  • red for low confidence (exploration area, may change completely).

This sets expectations differently: no one is surprised if something red changes, but people do expect more stability in the green items.

Bets

The "bets" format takes honesty a step further. Instead of a traditional roadmap, you present: "These are our three main bets this quarter. We believe that if we invest here, we will get Y result. If it doesn't work, we will pivot." It is explicit language about uncertainty but from a position of strength: we are making informed decisions based on the best available information, but we acknowledge we may be wrong and we are prepared to adjust.

Roadmaps With Explicit Options

Some teams experiment with roadmaps that include explicit options. For example: "In Q2 we will work on improving trial-to-paid conversion. Options under consideration: onboarding gamification, a referral program, more flexible pricing. We will choose based on experiment results in May."

This format is especially useful in contexts where stakeholders need to take part in strategic decisions but can tolerate tactical uncertainty.

The Communication Techniques That Turn Static Roadmaps Into Conversations

No roadmap format, however well designed, works if the way you present and discuss it perpetuates expectations of certainty. Communication techniques matter as much as the artifact.

One transformative practice is what we could call "continuous narrative updating." Instead of presenting the roadmap as a definitive document revised quarterly, treat it as a living document that is constantly updated with explanations of why. Every significant change comes with context: "We moved the Salesforce integration from Q2 to Q3 because discovery revealed that our main segment doesn't use Salesforce as much as we thought, so we prioritized the HubSpot integration instead." This is not instability; it is an intelligent response to new information.

This practice has an important secondary cultural effect: it normalizes change. If the roadmap changes every two weeks and everyone knows it because they receive brief updates explaining why, changes stop being uncomfortable surprises. They become visible evidence that the team is learning and adapting, which is exactly what being agile is supposed to mean.

Another crucial technique is "framing dependencies and hypotheses." When you present roadmap initiatives, make explicit what they depend on and what hypotheses underlie them. For example: "This feature assumes we can integrate with the payments API without major changes to its architecture (we are verifying this with the platform team). It also assumes users value this capability enough to pay for it (we will validate this with interviews in March)." This language does two things: it protects you because you have been transparent about risks, and it educates people about the conditional nature of planning.

The practice of "explicit trade-offs in real time" also changes the dynamics of roadmap conversations. When a stakeholder asks to add something, instead of simply saying "yes" or "no," respond: "Sure, we can consider that. If it goes into the roadmap, what from what is currently planned should we remove or delay?" This turns one-way requests into collaborative negotiations in which whoever asks for changes shares responsibility for the consequences. It also teaches about finite resources: it is not that the team is slow, it is that time is limited and everything has an opportunity cost.

Systematically using "hypothesis and validation language" also helps. Instead of "we are going to build X," say "we believe X could solve problem Y. We plan to validate it with Z experiment on date W. Depending on the results, we will continue, adjust, or pivot." This language positions everything as progressive learning, not as closed promises. And when something changes, the conversation is different: it is not that you failed to deliver, it is that you learned something and adjusted intelligently.

It is also worth adopting "flexible time anchors" instead of exact dates. Instead of "it will be ready on June 15," say "we are aiming for the end of Q2." And if pressed for an exact date: "It could be between mid-June and mid-July, depending on whether we find technical complexities in the integration with the legacy system. We will know more after the technical spike we are doing in May." You give a range, not a point, and explain what the variation depends on. This is professional honesty, not vagueness.

When Honesty About Uncertainty Clashes With Organizational Realities

In some organizational contexts, all this honesty about uncertainty is simply not politically viable. In some teams, admitting uncertainty can be interpreted as incompetence. Stakeholders are not interested in the discovery process; they only want to know when it will be ready. The roadmap is used as a top-down control tool, not as a tool for collaborative alignment, and corporate culture rewards the appearance of certainty over real adaptability.

In those contexts, the options are limited and none is perfect. You can try to educate people gradually, looking for allies in leadership who understand the problem. You can make incremental changes where you have autonomy, demonstrating with results that there are better ways to work. You can maintain two parallel roadmaps: a public, simplified one that meets political requirements, and an internal, more honest one that truly guides the team's work.

But if the culture fundamentally penalizes honesty about uncertainty and you lack the power to change it, you will eventually face an uncomfortable choice: commit to roadmaps you know are fiction and live with the constant stress of not meeting them, or look for an organization that operates more maturely when it comes to product development.

The Real Problem: Roadmaps as a Symptom of Organizational (Dis)trust

This conversation about honest roadmaps is not really about formats or communication techniques. It is about organizational trust. When stakeholders obsessively press for exact dates and specific details, they are often expressing "I don't trust that you are working on the right things, or that you will keep me informed, or that you will deliver something of value." And when product leaders avoid any time specificity or resist all commitment, they are sometimes saying "I don't trust that you will understand the unpredictable nature of product development, or that you won't punish me when things change."

Organizational psychological safety is a prerequisite for honest conversations about uncertainty. In high-trust cultures, saying "I don't know exactly how we will solve this, but here is our plan to find out" is perfectly acceptable. In low-trust cultures, admitting you don't know something marks you as incompetent or unreliable.

Building that trust does not happen with a new roadmap template. It requires consistent behavior over time: delivering frequent, transparent communication about what is happening and why, keeping the commitments that really matter, being honest when things don't go as expected and explaining what you learned and how you will adjust, and demonstrating with results that your process produces value even when the specific path changes.

It also means making the effort to understand the pressures your stakeholders face. Your sales director needs to give timelines to potential clients because that affects real deals that impact their commission and career. Your CTO needs to plan hiring with months of lead time and a limited budget. These are not irrational demands or whims; they are legitimate needs of other parts of the business that also have work to do.

The answer is not to ignore these needs in the name of "true agility" or "product integrity." It is to find ways to balance the flexibility product needs to respond to what it learns with the reasonable planning needs of other areas. Sometimes that means committing to certain things more firmly than you would like, because the business cost of uncertainty is genuinely high. Other times it means explaining why certain flexibility is non-negotiable if they want product to actually solve problems rather than just execute orders.

Start Where You Can

If all of this seems overwhelming, the good news is that you don't need to revolutionize how your organization works overnight. You can start with small changes within your circle of control.

The point is to begin. Not from a place of cynicism ("nobody believes roadmaps anyway") but from professional honesty ("my job is to solve important problems for the business, and that requires both strategic direction and tactical flexibility"). The best roadmaps are not the ones that never change; they are the ones that change for the right reasons, in ways that build trust instead of eroding it.

How do you handle the tension between strategic direction and honesty about uncertainty? Have you found formats or communication practices that work in your context?

References

  • Bastow, J. (2016). "Stop Using Timelines in Your Product Roadmap." Mind the Product. https://www.mindtheproduct.com/stop-using-timelines-product-roadmap/
  • Biddle, G. (2021). The Art of Product Management: Lessons from a Silicon Valley Innovator. Self-published.
  • Blank, S. (2013). The Four Steps to the Epiphany: Successful Strategies for Products that Win. K&S Ranch.
  • Cagan, M. (2017). Inspired: How to Create Tech Products Customers Love. Wiley.
  • Cagan, M. (2020). Empowered: Ordinary People, Extraordinary Products. Wiley.
  • Cutler, J. (2023). The Beautiful Mess: Notes on Strategy, Teams, and Product Management. Leanpub.
  • Edmondson, A. C. (2018). The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth. Wiley.
  • Patton, J. (2014). User Story Mapping: Discover the Whole Story, Build the Right Product. O'Reilly Media.
  • Perri, M. (2018). Escaping the Build Trap: How Effective Product Management Creates Real Value. O'Reilly Media.
  • Ries, E. (2011). The Lean Startup: How Today's Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses. Crown Business.
  • Spool, J. (2018). "The Evolution of a New UX Design Resolution." UIE Articles. https://articles.uie.com/new-ux-design-resolution/
  • Torres, T. (2021). Continuous Discovery Habits: Discover Products that Create Customer Value and Business Value. Product Talk LLC.