Mature SaaS Companies Often Don’t Have an Engineering Problem, They Have a Product Management Problem

investor profile

July 04, 2024

by an investor from Harvard University - Harvard Business School in Toronto, ON, Canada

Based on my own experience as a software CEO, I feel strongly that Product Management is one of the most important - and one of the lest well understood - ingredients to building a successful software company. Many software businesses (particularly mature ones still led by their original Founders) don't have any product management function at all. While this may be tenable under the Founder's leadership, it is almost never tenable when the company is acquired and led by a CEO with minimal industry experience.

I also suspect that many problems that seem to be attributable to the engineering group (Technical Debt, high levels of customization, regularly missing deadlines, etc.) are actually product management problems masquerading as development problems. This episode, originally published in 2021, is as applicable today as it was then.

My guest today is ⁠Rich Mironov⁠, North America's preeminent Product Management thought leader. He has spent 40 years in the software industry in numerous capacities, and currently acts as a Coach, Consultant, and Interim Executive for CEOs and Heads of Product across Canada and the United States. Rich has led Product Management at six software companies, and has now consulted for more than 170 technology businesses of all sizes.

Among other topics, our conversation covers hiring a Product leader and Product team, how to think about prioritizing products/features/functions, how Product should interface with Sales and other internal departments, how involved CEOs should be in Product, and what fatal mistakes he’s seen Product Managers make.

Link to the show notes is below. Please enjoy!


Mature SaaS Companies Often Don’t Have an Engineering Problem, They Have a Product Management Problem

0
1
15
Replies
1
commentor profile
Reply by a searcher
from Colgate University in Charlottesville, VA, USA
Very interesting insights here. As a technical founder, I often find I can't imagine a non-technical CEO stepping into SaaS below a pretty decent team size. Any thoughts from your experience about general criteria for when a non-technical CEO could reasonably take the reigns of a SaaS company? Its seems like regardless you'd need a CTO with substantial equity to ensure somebody with skin in the game oversees the engineering.
Join the discussion