Plato Elevate Winter Summit has been announced (Dec 7th-8th)

🔥

Back to resources

Handling Frustrating Feature Requests

Roadmap
Stakeholders

27 January, 2021

Michael Smith
Michael Smith

VP of Innovation at Omnipresent

Michael Smith, VP of Innovation at Hadean Supercomputing, shares how he successfully reframed the dreaded feature requests into a stakeholder engagement exercise that helped him sell and test his roadmap.

Problem

While acting as a PM at Google, I was having an extremely stress-filled day. Then a very smart and influential salesperson stopped and said, "Hey, I have an idea for a product feature - can I pitch it to you?"

"Great," I thought to myself, "as if I didn't have enough to prioritize already, and now I have to manage this random idea for a feature. I'd love to tell them 'no,’ but perhaps they're going to escalate; I don't have time for this." My anxiety increased as I felt my backlog increasing, deadlines slipping or a huge amount of expectation management queueing up.

Since then, I have seen many PMs with this same problem: a stakeholder or even the CEO comes at them with a feature. Most of the time, this feature request is in the form of a proposed solution in light of a perceived customer problem.

I propose that this anxiety-inducing experience is an opportunity if you take the right actions.

Actions taken

I checked myself: why am I resistant to have people pitch ideas to me? Shouldn't I have space to listen?

I realized that fielding this request was my job. If a feature request hadn't come to me, then someone might have worked around me, either going to stakeholders or engineers directly. So I thanked the person who had the request, cementing my position as the gatekeeper in their mind. To myself, I celebrated that they were knocking on the "front door" of the team. Channeling the suggestions of Stephen Covey ([ https://en.wikipedia.org/wiki/The_7_Habits_of_Highly_Effective_People#5_-_Seek_first_to_understand,_then_to_be_understood]), I thought: "Seek first to understand, then be understood." So I "leaned in" to the request and said what would become a staple of my communications from then on: "That's an interesting hypothesis!" I asked the requestor to tell me more: why believe that would be useful? What user and/or business issue are you working to solve?"

I listened very closely. They explained the feature and what it did, but I pressed the requestor for the "why": what was the customer problem that they thought they were solving? Once I understood the "why", I could tell them how this customer needs fits currently into my mental model and roadmap. I had another solution queued up in the roadmap that I believed might more elegantly tackle the underlying customer issue: how might their suggestion be better than what I had proposed? Did they agree with the items that I had prioritized before then?

Once we discussed all that, the salesperson felt heard, and I had a thought partner to pragmatically test my roadmap. I only had minor changes to make, and they only significantly helped my roadmap! Win-win!

Lessons learned

  • Always engage with incoming feature requests, but do so by digging into the underlying customer need.
  • My experience me to a framework I have since built for handling feature requests:

a. Acknowledge. Thank them and tell them, "that's an interesting hypothesis.” Put yourself into an open mindset.

b. Understand. Ask them about the customer problem they're solving.

c. Respond. Explain how their proposed solution might or might not already be solved by your existing roadmap, your reasoning on this, and solicit their opinion.

  • But above all, embrace incoming feature requests as opportunities to learn more about users, build rapport and share information with your stakeholders.

Discover Plato

Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader


Related stories

Why Overloading Product Teams Never Work

23 November

Adi Purwanto Sujarwadi, VP of Product at Evermos, shares how he identified the symptoms of his overworked product team and worked towards defining conflicting priorities.

Managing Expectations
Product Team
Deadlines
Stakeholders
Adi Purwanto Sujarwadi

Adi Purwanto Sujarwadi

VP of Product at Evermos

The art of managing up

19 November

James Engelbert, Head of Product at BT, shares how managing up is all about being an excellent manager to bring the best out of a team.

Mission / Vision / Charter
Managing Up
Internal Communication
Strategy
Stakeholders
Cross-Functional Collaboration
James Engelbert

James Engelbert

Head of Product at BT

The Benefits of Stakeholder Communication

17 November

Piyush Dubey, Senior Software Engineer at Microsoft, shares how to understand the stakeholder communication process better and why it is essential.

Meetings
Internal Communication
Collaboration
Ownership
Stakeholders
Piyush Dubey

Piyush Dubey

Senior Software Engineer at Microsoft

How to Successfully Complete A Major Reorganization

4 November

Kirk Gray, VP of Engineering at McGraw-Hill, recalls his experiences performing major reorganizations of departments, including successful techniques to ensure a smooth transition.

Alignment
Convincing
Reorganization
Roadmap
Fairness
Kirk Gray

Kirk Gray

VP Engineering at McGraw Hill

Securing A Fluid Transition to an Established Organization

2 November

Priyanka Naik, AVP of Product and Technology at J.P. Morgan, describes her switch from a startup to a large company and how she created rapport with her new team.

Internal Communication
Coaching / Training / Mentorship
Stakeholders
Cross-Functional Collaboration
Priyanka Naik

Priyanka Naik

AVP - Product and Technology at JP Morgan

You're a great engineer.
Become a great engineering leader.

Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.