Which stakeholders have input into your roadmap, and how to balance giving them influence vs control?

The short answer: everyone gets influence; (almost) no one gets control. It is important to assume the role to smartly synthesize the inputs, and not to take the requests...

There are several stakeholders that have input into our roadmap, a few main partners and collaborators are listed below:Other Product & Design TeamsSales/CS teamsMark...

If I could reframe the question slightly, I’d say this: our roadmap is a living, evolving artifact. We’re operating in a high-growth environment with an AI-first product ...

I appreciate this question! Generally speaking, we get inputs mostly from sales, customers and product/engineering. I’ve used the approach of building partnerships with s...

As a general rule, everyone should have input into the product roadmap. In fact, at GitLab our mission is to make it so that everyone can contribute and we apply the same...

Prioritization is more art than science. My goal is to actively listen to all stakeholders and help communicate how I make tradeoffs and how that impacts timeline to deli...

This is possibly a good application of the RACI framework to determine which of your stakeholders have influence vs ControlResponsible: Think of your product, engineering...

In my mind, several groups of stakeholders often influence the roadmap. They include your customers (both internal and external), your product team (e.g., engineering, de...

The stakeholders who typically have input into a roadmap can be:Customers and Users:Product Managers on other teams (that have a dependency)Development TeamExecutives and...

It varies. Mostly the stakeholders fall in four categoriesCustomers especially in B2B larger enterprise products (there is sometimes more control here)Partners like engin...

The main stakeholders that have input into my roadmaps are (1) Customers, (2) Sales, (3) Customer Service, (4) Leadership / Executive Team, (5) Other teams dependent on m...

At GitLab, we say that everyone can contribute. This is true even when it comes to input into the roadmap. Our product managers know that the best ideas can come from ver...

It depends on the role and problem space, but I try to invite (1) virtually everyone I collaborate with on a regular basis, (2) their management/leadership, and (3) fell...

Prioritizing is one of the hardest tasks for a PM. Balancing the needs of stakeholders, with customer needs, and business priorities. However, only your manager (and the...

Your key stakeholders to shape a roadmap are: Customers/Users: Capture direct feedback and use data to gain insights into user needs, pain points, and feature requests.Sa...

Everyone can contribute to the roadmap—sales, marketing, developers, leadership, the board, customers, executives, and even random people on the street with great ideas. ...

Typically, several key stakeholders generally contribute to the roadmap, each bringing unique insights based on their functions, goals, and customer interactions. Broadly...