Skip to content
Module
Module 4 of 6Lesson 1 of 2~14 min

Handle requests from sales and other stakeholders

How to take in a feature request from sales or an executive without letting it rewrite your roadmap. You learn to trace it back to the real need, size what is at stake and keep each stakeholder informed at the right level, which preserves the trust of both the sales team and your own team.

Lesson objective

By the end of this lesson, you will be able to turn a feature request into a quantified problem (who, what, how many, what is at stake), record it in a single log, and organize how stakeholders are kept informed according to their role.

Questions this lesson answers

  • How do you respond to a feature request from the sales team?
  • What is a request log and how do you set one up?
  • How do you map the stakeholders of a product roadmap?

Topics covered

  • feature requests
  • stakeholder management
  • request log
  • stakeholder mapping
  • product and sales alignment

Where it fits

Stakeholders and requests

How do I handle requests from sales, support and leadership without losing either direction or trust?

Lessons in this module

  1. Handle requests from sales and other stakeholders (this lesson)
  2. Say no, or not now, without closing the door

What you will learn in this module

This lesson is part of the course Prioritize and build an outcome-based roadmap

  • Handle requests from sales, support and leadership starting from the problem behind them, and say no or not now with reasons.