SaaS Product Roadmapping

I used to believe Customer Success should drive the product roadmap. Here’s what I know now. The roadmap should be a collaborative design, built by Sales, CS, Support, Product, Marketing, and Leadership together. No one team sees the full picture. ▶️ Marketing sees market shifts. ▶️ Sales hears why deals are lost. ▶️ Leadership ties it all to strategy. ▶️ Product builds scalable solutions. ▶️ Support sees recurring pain points. ▶️ CS sees where customers struggle. When we isolate roadmap ownership, we build for one team. When we collaborate, we build for the entire business. Want true collaboration? Set it up intentionally: 1️⃣ Monthly cross-functional planning meetings: Bring leaders together to align on customer feedback, market signals, and business priorities. 2️⃣ Voice of Customer (VoC) programs: Collect real user feedback consistently — surveys, interviews, success metrics. 3️⃣ Closed-lost analysis with Sales: Review why deals are lost and what patterns could inform the roadmap. 4️⃣ Support ticket and escalation reviews: Identify top friction points that need attention. 5️⃣ Market research and trend studies: Analyze competitor moves and emerging trends quarterly. 6️⃣ Executive alignment sessions: Validate that roadmap priorities map directly to company strategy. The roadmap shouldn’t be a surprise. It should be a shared vision. One that every team feels connected to — and proud of. How does your company approach roadmap collaboration today? Because if you're only building with one team's input, you're only solving one piece of the puzzle. ____________________ 📣 If you liked my post, you’ll love my newsletter. Every week I share learnings, advice and strategies from my experience going from CSM to CCO. Join 12k+ subscribers of The Journey and turn insights into action. Sign up on my profile.

Your 2025 Product Roadmap will fail (And That's OK) - Here's the real way to plan After over 8 years in Product, here's what no one tells you about roadmap planning: 1. Start with problems, not solutions: Instead of: "We'll build feature X in Q1" Write: "We'll solve user problem Y, current impact: $2M lost revenue" The hard truth? 80% of PMs start with solutions. Then wonder why their roadmaps fail. 2. Kill your darlings: - That exciting AI feature everyone's pushing for? Maybe it's just FOMO - The enterprise feature your biggest client wants? Could be a distraction - The technical debt your team's been ignoring? Probably your real Q1 priority 3. Reality check your timeline: - Take your engineering estimate. Double it. - Take your expected impact. Cut it in half. - Now you're getting closer to reality. 4. The 40-40-20 rule I live by: - 40% for planned strategic initiatives - 40% for unexpected opportunities/fires - 20% for innovation and tech debt Most PMs do 80-20-0. Then burn out their teams. The hidden cost no one talks about: Context switching kills 20% of your team's capacity. That's why spreading your roadmap too thin is actually slowing you down. 5. The stakeholder game: Different stakeholders need different views: - Engineers need technical feasibility - Executives want business outcomes - Sales needs timeline confidence Most PMs create one roadmap for everyone. That's why they fail at alignment. 6. The monthly reality check: Set a calendar reminder for the first Monday of every month: - What did we learn last month? - Which assumptions were wrong? - What market changes are we ignoring? - Which dependencies are at risk? Your roadmap isn't a commitment. It's a hypothesis waiting to be proven wrong. The best PMs in 2025 won't be those who: - Ship the most features - Never miss deadlines - Always say yes to stakeholders They'll be those who: - Adapt fastest to reality - Say no with confidence - Keep their teams focused when everything is on fire Remember: A roadmap is a tool for alignment, not a prison sentence. What's your process for planning a roadmap?

Most SaaS teams are building features users will never adopt. The reason isn't bad engineering. It's bad prioritization. Traditional feature prioritization follows this broken pattern: Executives want it → Competitors have it → Engineering can build it → Ship it But what users actually need gets lost in the noise. User-centered prioritization flips this completely. Instead of guessing what matters, you let user behavior and research drive every decision. Here's how it works: ↳ Start with user research to identify real pain points ↳ Test concepts with actual users before building anything ↳ Prioritize features that solve frequent, important user tasks ↳ Focus on what drives user satisfaction and business outcomes The difference is dramatic. Companies using internal opinions to prioritize features see adoption rates around 12%. Those using user-centered prioritization consistently hit 40% or higher. User-centered prioritization isn't just a method. It's a mindset shift. ↳ Instead of asking "What should we build next?" you ask "What problems are users struggling with today?" ↳ Instead of following competitor features, you follow user workflows. ↳ Instead of building what sounds impressive, you build what creates value. This approach identifies the features that matter most before you waste engineering resources. It reduces development time by focusing on proven needs. It increases adoption because users actually want what you're building. Your roadmap should serve users first. Everything else follows from there.

Your product roadmap shouldn’t be a wish list. It should be a list of hypotheses you’re ready to be wrong about. If you’re not ready to be wrong, you’re not actually ready to prioritize. When you build your roadmap, focus on the outcome you want. For instance, you might say, “We believe Feature X will reduce churn by 10%. We’ll test that for the next two sprints.” That way, you’re tying the feature directly to a measurable result. If it doesn’t work, cut your losses and move on. If it does work, double down. This approach keeps you honest. You stop building features because they “feel right” or because someone on the team has a pet idea. You build them because you have a hypothesis about how they’ll change user behavior, and you’re open to seeing that hypothesis fail. Being wrong is an essential part of finding out what’s actually going to drive the metrics you care about. Here’s a quick example. Maybe you think adding a trial signup link to your pricing page will increase free trials by 20%. That’s your hypothesis. You put it on the roadmap, implement it, then measure the results. If you only see a 5% lift, you’ve learned something. Adjust the page again or try a new tactic. Either way, you’re making decisions based on real data, not gut feel. Another example: you might hypothesize that a chatbot in your onboarding flow will cut support tickets by 30%. Implement it, test it, and see if you’re right or wrong. If you’re wrong, you’ve still learned something about user preferences. That knowledge is gold. You can use it to decide what to build or not build next. By treating your roadmap like a series of experiments, you’ll move faster and waste less time. You’ll also build trust with your team and stakeholders because they’ll see exactly why each idea is there: it’s a hypothesis you’re willing to test. Remember, you don’t want to defend projects because you’ve already sunk time into them. You want to move on if the data says it’s time to move on. Keep your roadmap grounded in reality, always driven by an underlying guess about what will drive real impact. It forces you to put a stake in the ground about what you believe and to be ready to change course when you find out you’re wrong. That’s the whole point: you’re building a product for real people in the real world, and real data trumps wishful thinking every time.

A product only scales when its strategy is tied directly to business goals. Otherwise, features become noise, and teams burn months on “nice to have” work that doesn’t move revenue, retention, or efficiency. Business alignment means: ✓ Every feature connects to metrics that matter ✓ Every design decision supports growth or cost optimization ✓ The roadmap speaks the same language as the leadership team. ⸻ Example: Healthcare Case I worked with a medical SaaS platform that had a backlog of 120+ features. Developers pushed new releases every two weeks, but churn was growing and revenue wasn’t scaling. I ran a UX–Business audit: — Mapped every feature to a business KPI — Cut 40% of backlog items that had zero business impact. — Rebuilt the roadmap so that every quarter focused on one clear business lever . Result after 3 months: ✓ Customer support tickets dropped by 22% ✓ Retention improved by 15% because patients were guided better through their journey. ✓ Leadership got visibility: for the first time, the roadmap was linked directly to revenue forecasts. ⸻ Example: Fintech Case In a fintech startup, leadership struggled to raise the next round because their pitch deck showed features, not impact. I restructured the product narrative: — Aligned UX flows with financial metrics: fewer failed transactions, faster onboarding, higher account activation. — Designed a demo around money saved and money earned, not UI screenshots. — Synced the product roadmap with the CFO’s model, so investors could see cause–effect clearly. The outcome: They closed a $7M round. Investors saw a product tied to growth levers, not just design polish. ⸻ My takeaway Business alignment is not paperwork. It’s the discipline of turning UX work into financial outcomes. When I step in, I translate design into numbers the boardroom understands — retention, efficiency, growth. That’s how design stops being a cost center and becomes a driver of business decisions. ⸻ I’ve spent over 8 years in UX and 7 years in branding, marketing, and PR. What I do is not just design — I architect clarity between product and business goals. That’s why my work stabilizes teams, speeds up decision-making, and helps products grow in markets under pressure. 

Product roadmaps shouldn't be treated like a to-do list. They're living documents that tell the story of your product's evolution and adapt with customer needs. 🌱 I learned this lesson the hard way. Early in my career, like many founders and product folks, I viewed roadmaps as rigid plans to execute against - plugging items into project management tools and checking off boxes each quarter. While this felt satisfying, this output-based approach missed the point entirely. 😬 Here’s the roadmap philosophy I live by today: The art of roadmapping isn't about the output - it's about the process. 🏗️ Or, as Winston Churchill offers, "Plans are of little importance, but planning is essential." When viewed through this lens, startup roadmaps are a tool that helps you: 🗣️ Articulate your vision clearly to different stakeholders 🎯 Prioritize work that moves you toward that vision 🛞 Adjust quickly based on customer feedback 🤝 Unite teams around shared goals For early-stage companies, I’ve found the best way to do this is to create and maintain three versions of the roadmap, each for a distinct audience: 1️⃣ Annual roadmaps for investors: Focus on major milestones and market opportunities 6-12 months out. This shows your strategic thinking and excites investors about long-term potential. 2️⃣ Quarterly roadmaps for customers: Share concrete value coming in the next 3-4 months. This builds excitement while maintaining flexibility to pivot based on feedback. 3️⃣ Internal roadmaps for teams - Break down the work into specific problems and experiments to tackle this quarter. This connects daily tasks to bigger goals (which we manage in Linear). For each version, the key is focusing on the problems you're solving rather than features you're building. This shift in mindset leads to better products, more engaged customers, and teams that understand the "why" behind their work. ❤️ The best roadmaps aren't about checking off feature boxes - they're about delivering value by aligning your team, customers, and investors around a shared vision for the future. If you’d like to dive deeper into my thoughts around this topic, I’ve written up a post on creating your first roadmaps as a startup founder on the Clarify blog. I’ll drop the link in the comments 👇

If I were leading Product at a SaaS doing $2M–$10M ARR (I am), here’s the exact strategy I’d use to stop churn and drive expansion. At this stage, relying on gut is riskier and building the wrong thing is very expensive. Here’s the prioritization playbook: 1. Systematize customer feedback You don't have a lack of ideas; you have a lack of focus. I’d immediately move away from scattered spreadsheets and Slack threads. I’d consolidate every piece of feedback into one source of truth. Focus on: • Tagging feedback by revenue impact (What do enterprise leads actually want?)  • Identifying churn reasons automatically  • Making sure your quieter customers are represented, not just the loudest voices If you aren't building what customers are actually asking for, you’re just guessing. 2. Closing the loop Shipping features is only half the battle. If users don't know you fixed their problem, you don't get the credit (or the retention). I see so many teams ship amazing updates that get buried in a generic newsletter. I would enforce a strict workflow: • In-app notifications targeting specific users who asked for that feature  • A public, visual changelog (with video) featuring release notes • Automated "We fixed this!" emails (sent with Canny) When users see you listen to them, they stay. It’s that simple. 3. Design polish In 2026, "MVP" doesn't mean "ugly." The bar for SaaS design is incredibly high. If your product feels clunky, users will leave for a competitor that feels "modern." I’d dedicate significant resources to: • UI and UX clarity and consistency • Minimum number of clicks • Feedback on actions via the interface • Meaningful empty states Good design is a trust signal. It tells enterprises you’re ready for the big leagues. 4. Public roadmap Transparency is good marketing. I’d turn the roadmap into a sales asset. Instead of building behind the scenes, I’d put it front and center. Curate a public-facing view that shows momentum. Let prospects see that the platform is alive and evolving. It builds massive confidence during the sales cycle. 5. Founder/product content People buy from people. I’d have everyone on the team (not just marketing) write about why we built specific features. • "Why we redesigned our dashboard"  • "How we prioritized X over Y" This "Build in Public" style attracts better talent and customers who align with your product philosophy. Product teams: Are you focused on acquiring new users, or keeping the ones you have happy? Let me know 👇

If you’re a product manager at a startup or small company, chances are you’re wearing multiple hats. 🎩 You’re not just the PM handling the tactical details—you’re also covering the responsibilities of a Head of Product or VP of Product. If you’re juggling three distinct levels of roadmaps: goals, product, and features. Let’s break these down: 1. The Goals Roadmap 🎯 This is the big-picture, strategic layer. It defines the business and product goals that guide everything else. Think of it as your North Star. Example: “This quarter, we’re improving customer retention by 10%.” If you’re at a startup without a VP or Head of Product, this responsibility often falls to you. You’ll need to connect company objectives to actionable goals and communicate them effectively. 2. The Product Roadmap 🗺️ Sitting in the middle, the product roadmap focuses on initiatives—the “what” behind achieving your goals. Example: To hit that retention goal, you might prioritize launching a loyalty rewards system or revamping onboarding. This roadmap translates high-level objectives into tangible projects, aligning your team and stakeholders around the journey. 3. The Feature Roadmap 🔧 This is your tactical layer. It deals with the specific features and deliverables needed to execute the product roadmap. Example: What exactly needs to be built for the loyalty rewards system? A dashboard, notifications, and user account features? Here, you’re moving from strategy into detailed planning, ensuring the team has clarity on what to build and when. How This Differs in Bigger Companies 🏢 At larger companies, these three layers are often split across different roles: • VP of Product/Head of Product handles the goals roadmap and sets overarching priorities. • PMs focus on the product roadmap, deciding what initiatives to prioritize to meet those goals. • Team leads, or engineers often drive the execution of feature roadmaps, managing backlogs and specific deliverables. As a PM in a larger organization, you’ll usually focus on two layers: 1. Strategic Initiatives (connecting goals to product direction). 2. Tactical Execution (turning initiatives into backlog items). Why This Matters 💡 Understanding these layers—and who owns them—is crucial to navigating your role: • At startups, owning all three layers gives you a holistic view and ensures alignment across goals, product initiatives, and features. • In bigger companies, knowing where you fit helps you stay focused while collaborating effectively with leadership and delivery teams. Whether you’re at a small company or a large one, clarity around these roadmaps ensures you’re always driving the right priorities. ✅

Almost 60% of the product leaders/ CEOs that we talked to, said their product teams would often deviate from roadmap or actually function differently. Roadmaps are a function of 3 things 1) Goals - 'Acquiring 300 new users every week', 'Reducing churn by 20%', 'Increase ARPU' 2) Features/Improvements - 'Reduce drop off at onboarding', 'Launch a new feature', 'Drive adoption for value add features 3) Retrospection - Analyzing key decisions taken, focusing on what works and what did not, driving adoption, etc. At one of the orgs I worked at, we built an entire structure of how our product team would work. Each person would be responsible for their goals - CEO/ Product team / Marketing, etc. We would decide on 2 large features every week, 3-4 minor changes and at least 10 improvements for a single month + 30% time spent on ad hoc tasks. We would ship features at the start and the end of the month and spend the rest of the time retrospection, looking at the data, validating our theories and figuring out how far or close are we to our goals. :) Whenever a stakeholder would come up with an idea or feature, they would 1) Justify how it aligns with the goal 2) Source of the idea - Customer feedback, competitors, pain point 3) Validate the feature / idea with other customers. This helped us align everyone to understand what our roadmap means. :) While it wasn't perfect - it helped us efficiently drive different outcomes that needed to be prioritzed. Call it the GIR framework(Goals - Iterations - Retrospection) :D

"Feature-based roadmaps are fiction. Everyone on the product team knows it." Product roadmaps have been a source of tension for decades—product teams need flexibility to explore, while sales, marketing, and support need clarity on what's coming. This article walks through how roadmap formats have evolved to address these competing needs. You'll learn: 🎯 Why traditional feature roadmaps with dates create false certainty and erode trust 🎨 How theme and outcome-based roadmaps give teams more latitude but leave other departments in the dark 📍 Why the Now Next Later format is a better compromise between flexibility and visibility 🔄 How combining Now Next Later with opportunity solution trees (solutions → opportunities → outcomes) lets teams explore without overpromising The key insight: your roadmap should reflect what you actually know. Be specific about what you're building now, directional about what's next, and outcome-focused about the future. Check out the article: https://buff.ly/weTlTs9 ❓ Which roadmap format does your team currently use, and how well does it work for both your product team and the rest of your organization? Share your thoughts in the comments below.