Back to resources

Advocating for Your Product

Product
Convincing

14 April, 2021

Sophia Broomfield
Sophia Broomfield

Product Management Coach at Coaching PM Leaders

Sophia Broomfield, Product Management coach and leader, speaks of her successful advocacy efforts that convinced senior executives to include her product in the first release of the next-generation platform.

Problem

I was working at a large company that was launching its next-generation applications. The product that I managed was not scheduled to be included in the first release, which presented a few challenges:

  • Our product would lose resources and investment, as some of the team would be allocated to other projects or products;
  • The team would be demotivated and potentially start leaving the company;
  • We would lose traction in the marketplace which would undermine all the hard work we had put in to gain a leadership position.

 

I was afraid that all of this would happen if we continued along the trajectory that had come down from the top.

 

Actions taken

At that time, I was Senior Director of Product Management for the product line. I could simply accept the executive decision and continue to maintain the product by doing small enhancement for customers. Or I could fight for my product and team by presenting a case of why it was important to include this product in the first release.

Before scheduling a meeting with the Executive VP, I went up my management chain to ensure they would be supportive of my advocacy efforts. They greenlighted my plan and I headed to a meeting with the Executive VP. The approach I took when talking to him was threefold:

 

a. Because this was a multi-billion dollar company, this executive may not have been familiar with all aspects of all the products. So I provided him with a high-level background, including the number of customers, the revenue growth and key recent wins against competitors in the market. I also provided two case studies of strategic customers who had used our product to make a significant impact towards their KPIs including cost reduction and employee satisfaction. I left him with powerful quotes from executives at these companies that described the tangible benefits that they achieved by leveraging our solution.

b. I also put myself in his shoes. From his perspective, he may not be as interested in the success of a single product, as he would be in the success of the entire suite of applications. We were competing with another key industry player that was doing extremely well in the market. We were trying to go head to head with them, but we were struggling. I presented a vision of an adjacent market that was growing, one in which my product played an integral part. I explained how our product was a competitive differentiator in this space, and that our sales team was excited about it because it was unique and something our competitor did not have.

c. I also needed to convince him that by adding our product to the first release that we would not negatively impact the release schedule or slow anyone else down. In fact, I explained to him that because our product was independent and smaller in scope than many of the others, we could operate autonomously and serve as a control example for the other teams. Even more importantly our product could be deployed standalone. So customers who were risk-averse or hesitant to move their entire suite of applications to a new technology platform could test the waters with a single product. If that worked well for them, they could then roll out the entire suite. This last argument is what I think closed the executive VP -- there really wasn’t much of a downside for allowing us in to the 1st release but could be a potential hook to persuade customers to explore the next generation technology once it was released.

 

When he responded with those magic words “Ok, go ahead, I will let the SVP of Applications know to add you to the 1st release,” I was elated. The entire team was excited, relieved and inspired to show the rest of the organization what we were capable of.

Lessons learned

  • Ask for what you want. Don’t just blindly accept the directives that come down from upper management as sometimes you may have an important viewpoint that they are not aware of. If you strongly believe in something and are passionate about it, ask for it! Do your research, build your case, and advocate for what you believe is the best solution for the company and your team.
  • When you make a case to executives, make it simple, clear and powerful. Provide a quick background, but emphasize things that executives care about including customer counts, revenue, recent wins, competitive differentiators, market leadership and customer impact. Showcase strategic customer stories supported by quotes that are easy to grab on to and remember.
  • Understanding where executives are coming from in terms of internal strategy and goals is critical. Position what you are saying with respect to that. Don’t just talk about how great your product is but how it could help the larger company strategy. Be brave and go for it!

Discover Plato

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


Related stories

Scaling a Team in Two Parts: The Product and Manager

2 August

Viswa Mani Kiran Peddinti, Sr Engineering Manager at Instacart, walks through his experience scaling a team, product and his skills as a leader.

Managing Expectations
Product
Scaling Team
Leadership
Meetings
Viswa Mani Kiran Peddinti

Viswa Mani Kiran Peddinti

Sr Engineering Manager at Instacart

How Product Management Chose Me

23 June

My accidental journey into product management

Product
Personal Growth
New PM
Career Path
Michael Castro

Michael Castro

Sr. Manager, Product Management at Capital One

How Product Marketing Can (and Should) Help Product Development

20 June

Pavel Safarik, Head of Product at ROI Hunter, discusses the frequently overlooked role of product marketing in getting high user adoption rates for your product.

Goal Setting
Product Team
Product
Different Skillsets
Cross-Functional Collaboration
Pavel Safarik

Pavel Safarik

Head of Product at ROI Hunter

How to Successfully Rebuild Your Product

6 June

Adir Nashawi, Senior Product Manager at Hibob, shares his insight and experience from rebuilding a product to handle many feature requests and offerings.

Customers
Product
Dev Processes
Users
Prioritization
Adir Nashawi

Adir Nashawi

Senior Product Manager at Hibob

How to Empower Teams to Build Out a Product Portfolio During Company Growth

6 June

Ivo Minjauw, Global Product Director at OTA Insight, discusses the importance of structuring your teams when undergoing company growth.

Alignment
Goal Setting
Product
Ownership
Performance
Ivo Minjauw

Ivo Minjauw

Global Product Director at OTA Insight