Roughly 58% of product organizations still organize their roadmaps around calendar slots — formats that structurally produce broken commitments. That is the headline finding from the 2026 State of B2B Product Management survey cited by ProdPad: 41% of teams use quarterly time-based roadmaps, another 9% use sprint or monthly timelines, and 8% use date-driven delivery charts. Only 27% have moved to the Now-Next-Later format, where work is sequenced by problem priority and confidence rather than quarter.

The argument, laid out by ProdPad co-founder Janna Bastow (who, with Simon Cast, invented the Now-Next-Later roadmap), is blunt: honesty scales better than certainty. Every quarter, product leaders present roadmaps that everyone nods at, and three months later the same leaders apologize for half of it not happening.

Why does the quarterly roadmap trap teams?

Gantt charts take most of the criticism, but the quarterly roadmap catches more teams because it looks reasonable — three or four open columns, no exact dates. The difference from Now-Next-Later is structural, not cosmetic.

• A quarterly roadmap says "we plan to do this in Q2." A Now-Next-Later roadmap says "this is the next most important problem, and we are currently exploring solutions."
• The moment an item sits in a Q2 column, every department reads it as "shipping in Q2." Sales starts promising it. Marketing plans campaigns around it. The disclaimers evaporate; the expectation remains.

Marty Cagan of SVPG has written that roadmaps become de facto commitments the moment they are shared, regardless of attached caveats. Each missed pseudo-deadline erodes credibility, and after a few quarters the organization stops trusting the roadmap entirely.

How does timeboxing distort prioritization?

The damage runs deeper than missed expectations.

• Buffer games and Parkinson's Law. Estimates include padding to avoid missing quarterly targets. The padding becomes baseline; work expands to fill the time given. Work that could ship in six weeks stretches to twelve because the column said Q2.
• Discovery gets crowded out. A team implicitly committed to shipping Feature X by end of Q2 has no incentive to discover Feature X is the wrong solution. This is how feature factories are born.
• Backlog gravity. Items that sit on the roadmap longest accumulate organizational weight — stakeholders told about them, customers promised them — and rise on tenure, not impact. Items slipping from Q1 to Q2 acquire urgency from being "overdue," not from strategic value.

The quarter itself becomes the timebox, and prioritization warps around protecting delivery windows instead of maximizing outcomes.

What do the Now-Next-Later columns actually mean?

They are confidence horizons, not disguised quarters.

• Now — validated, scoped, in-progress problems. Genuine external deadlines (regulatory windows, contractual obligations) attach here, to specific initiatives, where certainty lives.
• Next — well-defined problems where the team is running discovery and testing solutions. Not ready for a delivery date, which is exactly why they shouldn't carry one.
• Later — strategic bets that need significantly more discovery, and might get dropped entirely.

The organizing question is "how important is this problem, and how much do we know about solving it?" — never "what quarter does this fall in?" When a new urgent problem surfaces, the team re-prioritizes instead of watching a schedule cascade.

Should product teams abandon dates entirely?

No — and the source is careful on this point. Dates are valuable when they represent genuine external constraints: regulatory deadlines, compliance windows, contractual obligations, conference demos. The key is separating the roadmap from the release plan. The roadmap is a strategic communication tool; the release plan is a tactical delivery schedule for scoped, committed work. Time-based formats conflate the two, producing a document too rigid to be good strategy and too vague to be a good plan.

This is the structure Cagan calls high-integrity commitments: dates attached only after enough discovery to understand what is being committed to. In Now-Next-Later, real deadlines live on the OKR or initiative, not on the format.

For commercial stakeholders, a dual-direction view answers the legitimate "when" pressure: from any initiative, see which business outcomes it serves; from any OKR, see every supporting initiative and where it sits on the horizon. If everything backing a year-end revenue target sits in Later, that's a visible signal to course-correct — no status meeting required.

What should leaders ask instead of "when"?

The article proposes five replacement questions:

• "Which business outcome does this serve?" — every initiative should connect to an OKR.
• "Where does this sit on the horizon, and why?"
• "What have we learned so far?"
• "What would need to be true for this to move to Now?"
• "Are we on track for the objective, even if the plan has changed?"

If a team changed its plan three times but is hitting the Key Results, that is success. If it shipped everything on the original plan and the Key Results didn't move, that is failure regardless of punctuality.

What fails when you make the switch?

The honest tradeoff: switching requires cultural change, not a new template. Sales pipelines built on feature promises, board decks structured around delivery milestones, and compensation plans tied to ship dates all need rewinding. Organizations that make the shift consistently report delivering faster and building better products — but organizations that ignore the commercial teams' need to set expectations end up isolated from the rest of the business. Teresa Torres has said she is "a fan of Janna Bastow's Now-Next-Later roadmaps," precisely because continuous discovery requires a format that rewards changing direction when you learn something new.

As more organizations shift governance from ship dates to Key Results, the roadmap that encodes uncertainty honestly — rather than performing confidence it doesn't have — is becoming the default for product teams that intend to keep their stakeholders' trust.