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

🔥

Back to resources

Bringing a New Product to Market

Product

5 February, 2021

Glenn Block
Glenn Block

VP of Product at Uplevel

Glenn Block, Principal PM Lead at Microsoft, discusses the importance of understanding the target market and why the strategy of bringing a product to market should be determined by what the market is asking for.

Problem

I joined a startup to help launch a new business and bring a new product to market. The “big” startup was a hot technology company and on a path to IPO. They had a strong offering in the market and were looking to create a second product. I was hired for that purpose. The new product would be born out of the first. We were getting a good signal from prospective customers that they wanted us to create a new stand alone product based on capabilities in the first. The company had done amazingly well in the market with the first product. Their goto market strategy was to get developers within an organization to play with their freemium product and then over time it would grow into a paid purchase. Our particular new product was very different though we had assumed we would gain similar traction with a similar strategy.

Actions taken

Initially we tried to use a similar strategy to bring our new product to market, but that did not work. It became clear that the market demands were different and we ended up pivoting to target enterprises from the get-go. We invested a lot of time to talk to and iterate with our prospective customers and understand their needs. We learned that addressing this market required a very different strategy and we had underestimated the work that would be needed. We had allowed ourselves to be lulled by our reputation and thought that based on the company’s prior success, that we would be able to land the business. Everyone would love our product too right? We made a lot of assumptions that ultimately hurt us.

For example, we thought that the company’s brand would help us, and the rest of our senior leadership supported this idea. It actually ended up hurting us. The reason is because our products were very different. The existing product was in a completely different domain, which ended up causing a lot of confusion. Customers were perplexed if our product was related to a similar domain. We found on calls that we had to repeatedly explain that although we were part of the same company, our product targeted a different domain.

Another challenge we ran into was underestimating the effort it would take to create a new market. Our product was breaking new ground providing a new way to solve an old problem. Creating a new market can take a long time and require a lot of investment in education. We thought based on signing our first few 5 figure deals that the market was there. We learned over time that this was a false sense of reality. We had landed the early adopters and there was a lot more work necessary to create the market demand. We needed to educate the market, which would take time and money.

Ultimately we ended up shutting down the business. Although it was bringing in revenue, the path to its success and the required investment was much greater than our company was prepared to give.

The overall lesson here is that we did not do enough diligence early on. We did not question enough of our assumptions. We should have consulted with founders and advisors who had tread this path so that we would have reasonable expectations. They could have helped us see much earlier the challenges that were ahead and how to navigate them.

Lessons learned

  • Be very careful about taking your assumptions for granted. We tried to apply the playbook for a different kind of product and different kind of market. When bringing a new product to market, you have to understand the needs of that market and its customers.
  • Pick your advisors wisely. We needed to have advisors outside the company and outside our echo chamber. What I learned much later, talking to external consultants, was that our strategy was not suitable from the start. If I had talked to them earlier, that could have helped us formulate our strategy more realistically and come up with more reasonable expectations.
  • We were caught up in the excitement, and that blurred some of our vision. While enthusiasm and believing in your product and brand is always great to have, don’t let it cloud your judgment. Trusted advisors can often help clear the haze.

Discover Plato

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


Related stories

How to Pivot a Product Idea at the Right Time

23 November

Adi Purwanto Sujarwadi, VP of Product at Evermos, shares how he diligently managed a product in one of the biggest eCommerce companies by being an individual contributor.

Innovation / Experiment
Product Team
Product
Embracing Failures
Adi Purwanto Sujarwadi

Adi Purwanto Sujarwadi

VP of Product at Evermos

Overcoming imposter syndrome through focusing on your strengths

19 November

James Engelbert, Head of Product at BT, recalls when he had to battle imposter syndrome when managing a new team.

Product Team
Product
Health / Stress / Burn-Out
James Engelbert

James Engelbert

Head of Product at BT

The Right Way to Ship Features in a Startup

11 November

Matt Anger, Senior Staff Engineer at DoorDash, shares how he took the risk and shipped features in a startup.

Alignment
Product
Dev Processes
Matt Anger

Matt Anger

Senior Staff Engineer at DoorDash

How Data-Driven Products Help Customers and Increase Sales

11 November

Richard Maraschi, VP of Data Products & Insights at WarnerMedia, shares his insight on incorporating data science, AI, and product management to overcome slowing growth of the company.

Product
Conflict Solving
Users
Data Team
Performance
Richard Maraschi

Richard Maraschi

VP Data Product Management at WarnerMedia

How to Scale Product Teams for Empowerment & Impact?

5 November

Prasad Gupte, Director of Product at Babbel, shares his insights into the challenges behind successfully growing a team.

Customers
Product
Scaling Team
Strategy
Users
Prasad Gupte

Prasad Gupte

Director of Product at Babbel

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.