Roadmap
topic on 4 shows · 12 statements across 11 episodes
Lenny's Podcast 
the Official SaaStr Podcast 
Top Founders 
20VC
12 statements about Roadmap, every show
Multi-year roadmaps waste tech's core advantage of iterative learning
“I think there's a second failure mode, which is people sit down and write up these long roadmaps and strategic vision docs of what we'll do over the next two or three years that kind of loses the comparative advantage we have over every other industry, which i…”
Janakiraman: Product strategy docs must not include a roadmap
“It's important not to include like a roadmap as part of a strategy doc, because the strategy doc is meant to be separate from the roadmap. It's meant to be a companion to your roadmap.”
Janakiraman: Roadmaps are built by combining 'small s' and 'big S' strategy
“And the roadmap for the company or the team is built from a combination of small s and big s work, which is like building a bridge from both sides of a river.”
Cloudflare SVP: AI Product Teams Must Review Roadmaps Every 4-6 Weeks
“Really, if you're not reviewing the roadmap and really asking yourself is the next thing that we're building the right thing you're probably waiting too long.”
Masad: Rigid product roadmaps are impossible to maintain in the AI era
“One thing that I think is really difficult now is having roadmaps, especially if you're doing anything in AI, but really any, anything that AI could affect. You want to be able to react to it really quickly.”
Atawodi: Product roadmaps should consolidate initiatives requiring under three engineers
“Usually what the rule we gave was like, if you have more than three engineers on it, less than three engineers on the problem, consolidate. More than three, it needs a line, right?”
O'Neal: Users churn when product roadmaps ignore usability bugs for features
“There are tons of things in your app that just don't work well, and when your roadmap doesn't account for those, people start churning because they get frustrated, because somebody scrappier and newer comes out and creates something better that feels less hard…”
Hila Qu: Adding PLG requires at least a 1-to-2 year commitment
“You need to commit to at least a year or even two years. Kind of roadmap to build this entire thing out and change the process internally sometimes as well to support that.”
Every team needs three documents: a charter, goals, and a roadmap
“There's just a set of documents that are like really, really viable that every sort of like, I guess, level of the organization should have throughout its life cycle. And then, you know, I think how sort of involved it is or how, like, long term it is really d…”
Salva: Production teams must own the product roadmap, not R&D teams
“It's critical that the team who is taking over from the R&D shop feels like they have control over their own future.
you can't
Really delegate roadmap to an R&D team.
The team who's responsible for maintaining the product, for building the product, who has th…”
Mehta: SaaS buyers purchase the product roadmap, unlike on-prem customers
“When you're a SAS customer, you are buying the roadmap, like in the on-prem customer, you're buying the product and you might use the roadmap, but you might just stay on that old version. But in SAS, you're buying the roadmap. And so therefore the roadmap is a…”
Erickson: Product Roadmaps Should Balance Core Strengths with Long-Tail User Fixes
“Your roadmap should be automatically prioritized as you come up with project ideas, and it should help you strike a balance between investing in your strengths and working on the long tail of features and fixes that will help turn less enthusiastic customers i…”