Build a Product Roadmap

Really like how clear and easy to read this roadmap is. The 12-week timeline, overlapping bars, and separation between “business goals” and “design tasks” make it obvious what’s happening when. Your UX process also feels solid – going from research and competitor analysis into IA, wireframes, UI, then prototyping and testing shows a good understanding of how a designer would actually work through the problem.

Where it feels a bit light for this specific brief is on the “product” side. Right now, it comes across more like a UX project plan than a product roadmap for a SaaS collaboration tool. I’d love to see the phases and goals tied directly to the product, e.g. Discovery → MVP → Private Beta → Public Launch → Post-launch iteration, with clear milestones like “MVP ready for first 10 teams” or “v1 launched.” Adding a small layer for metrics (activation, weekly active teams, retention) and a quick risks/mitigations section would also show how you plan to learn from real usage and de-risk the plan over time.

Overall: visually strong and process-wise very good. With a bit more focus on releases, metrics, and risks connected to the actual product scenario, this could easily feel like a senior-level roadmap.

I'll start with what I see as positive. The structure is clear, the timeline is visually clean, and the breakdown of UX work phases looks sensible. The problem is, this isn't a product roadmap in the brief's sense. This is a designer's work plan for the project, not a map of product development from concept through launch to scaling. That I think.

The brief talks about product phases, key business milestones, beta releases, feature updates, and feedback loops. Meanwhile, here I see user research, competitor analysis, wireframes - classic design process stuff. I'm missing the view of what reaches users and when, what functionalities we're implementing in each phase, how we're measuring product success.

The business goals at the top are a good direction, but they're too generic and I don't see their connection to concrete product deliverables. Where are the milestones? Where's the risk mitigation strategy? Where are the moments for gathering user feedback and product iteration?

You have a solid visual and structural foundation. Now you need to shift perspective from "how we design" to "what and when users and the business receive." That's the difference between a work plan and a product roadmap. 💪😊❤️

Good Lasika - Woking on new project - Keep up - The colors look nice, but this isn't a Product Roadmap. It’s a "Designer's To-Do List." Lets compare real business:

• Jira/Linear vs. Your Design: In real platforms like Jira or Linear, a Roadmap shows Features - The CEO doesn't care when you do wireframes. They care when the feature ships. Rename these bars to product milestones, not design homework.

• The "Ping-Pong" Eye UX: You put the bars on the left and the text explanation far on the right...Baad UX

• Business Reality: If you present this in a stakeholder meeting, you lose all credibility instantly. It shows you didn't read the brief. Always proofread.

• Week 1-12 is too Vague: Real roadmaps use specific dates (Oct 1 - Oct 15) or Quarters (Q1, Q2). "Week 5" means nothing to a stakeholder. Give me a deadline I can put on a calendar.

⭐️ You have the visual skills, but you need to learn logics - as said- need help - check my uxcel profile - Contact me there for 1:1

Great work Laksika. The clarity and hierarchy of information information represented is amazing. My take on this project

• The alignment of lines can be looked into. For example goal 1 and week 1 line.
• Loved the way you color marked each goal and their text.
• The section product research and following text looks a bit heavy and can be clusted into smaller chunks for easier readability.

I hope the feedback helps and again, amazing work. All the best. :)