Sharebird
Sign Up / Sign In

What does the roadmap process look like for growth product teams? And Is it working well?

Answer
5 Answers
Growth Product Management
  1. Bruno Gobbis
    Bruno Gobbis

    Nuvemshop Director, Product Growth | Formerly Superhuman, RD Station, IBM, Bosch • Jun 4

    I'll answer both honestly. The roadmap process for a growth team looks meaningfully different from a core product team, and I'm not sure any version "works well" in the absolute — but here's the version I find least broken: Quarterly themes, not quarterly features: Core teams can roadmap features 6 months out. Growth can't — by the time you ship a quarter-out feature, the experiments you ran in week 1 have changed what you thought was important. So we set a quarterly theme (e.g., "improve activa ...Read More

    374 Views
  2. Ojus Padston
    Ojus Padston

    Vanta Staff Product Manager • 3y

    Focus Area > Problem > Hypothesis First, the focus area for the team must be defined. This starts by mapping out the possible areas the team could focus. My recommendation is to assess the opportunity size using the product of "What's the business value if [x] area was improved?" times "What's the likelihood of that happening?" Next, you want to align on what problem you are tackling. For example, when I first started at ezCater we decided to improve initial landing experiences for visitor ...Read More

    1,757 Views
  3. Sreenath Kizhakkedath
    Sreenath Kizhakkedath

    Uber Uber Head of Growth Programs, Riders • 4y

    The roadmap process is no different from any other product manager. They work closely with marketing, engineering, design, and data science to create the roadmap. There are sprints & prioritization processes for all features. They are focused on continuous experimentation and learning - which is an input into the prioritization process. 

    1,425 Views
  4. Ruchi Aggarwal
    Ruchi Aggarwal

    Former BILL Director, Product Management - Payments • 3mo

    Growth product teams typically operate with a hypothesis-driven roadmap, focused on two things: increasing adoption of existing product capabilities and informing future product direction. The process usually looks like this: Gather signals from quantitative data (usage metrics, funnel drop-offs) and qualitative data (user feedback, support tickets) to understand where opportunities exist Generate hypotheses about what changes could improve growth outcomes, whether that's activation, retention, ...Read More

    387 Views
  5. Nicolas Liatti
    Nicolas Liatti

    Adobe Senior Director of Product Management, 3D Category • 2y

    I think a roadmap is just a tool to get alignment with stakeholders, it should not be used as a commitment on what's coming, and definitely not like a plan to just follow.

    So any roadmap for product growth would actually map out the outcome and then the different initiatives to reach it, and adjusted any time necessary.

    489 Views

Related Ask Me Anything Sessions

Bruno Gobbis

Nuvemshop Director, Product Growth, Bruno Gobbis on Growth Product Management

June 4 @ 10:00AM PT

View Answers
Ruchi Aggarwal

Former BILL Director, Product Management - Payments, Ruchi Aggarwal on Growth Product Management

March 17 @ 10:00AM PT

View Answers
Deepti Pradeep

Adobe Director of Product Management, Growth, Deepti Pradeep on Growth Product Management

February 19, 2025 @ 10:00AM PT

View Answers
See All Upcoming AMA's

Top Product Management Mentors