svpg
FREE newsletter

Subscribe via RSS

Subscribe

Tag Cloud

product discovery management product management company culture product portfolio planning product development process product strategy great products product owner innovation marketing user experience design scrum product marketing agile engineering prototype testing project management high-fidelity prototypes product development

Browse by Date

  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • February 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • August 2009
  • July 2009
  • June 2009
  • May 2009
  • April 2009
  • March 2009
  • February 2009
  • January 2009
  • December 2008
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008
  • March 2008
  • February 2008
  • January 2008
  • December 2007
  • November 2007
  • October 2007
  • September 2007
  • August 2007
  • July 2007
  • June 2007
  • May 2007
  • April 2007
  • March 2007
  • February 2007
  • January 2007
  • December 2006
  • November 2006
  • October 2006
  • September 2006
  • August 2006
  • July 2006
  • June 2006
  • May 2006
  • April 2006
  • March 2006
  • February 2006
  • January 2006
  • December 2005
  • November 2005
  • October 2005
  • September 2005
  • August 2005
  • July 2005
  • June 2005
  • May 2005
  • April 2005
  • March 2005
  • February 2005
  • January 2005
  • HOME
  • Services
    • Product Management
    • Product Marketing
    • Technology
    • User Experience
    • Public Workshops
  • Articles
    • Index
    • Blog
  • Clients
  • Resources
  • Company
    • Team
    • Manifesto
    • Contact Us

Product Management as a Service Organization

Posted by Marty Cagan on January 13, 2010

Tags: best practices

Probably one of the most common complaints I get from CEO's of mid- to large-sized companies is the lack of innovation and thought leadership from their product organization.   They see the money they spend on product managers, designers, engineers and QA, yet they often see only marginal improvements to the business.  Yet in most of these organizations, when I look at their roadmaps (these organizations rarely have product strategies), they’re littered with literally hundreds of specific features and incremental enhancements.

When a company is just starting out, it’s all about finding something that resonates with users and delivering real value to customers.  It’s why startups are such great places for innovation.   But for those skilled or fortunate enough to accomplish that, as the company starts to grow, very often the nature of the product organization changes into a group whose main purpose is to serve the needs of the many stakeholders across the business – business owners, sales, marketing, business development, legal, finance, operations, customer service, etc.  

The job of the product manager then devolves into one of documenting stakeholder requirements, mediating conflicting objectives, and allocating the limited developer resources to try to satisfy as many of the stakeholders as possible.

Is it really any surprise that innovation stops?  Is it really a surprise when your most talented and creative people leave for another startup, while the ones that remain are willing to spend their days running from stakeholder to stakeholder trying to negotiate some kind of agreement?

Now, of course there are always very legitimate business requirements that have to be addressed and accommodated.  Supporting contractual obligations, monetization opportunities, and addressing operational issues are all very real examples.

However, many product organizations become so overwhelmed with these urgent day-to-day stakeholder obligations that two even more important responsibilities are pushed aside.  The first is the focus on the actual customers and their needs; and the second is the future of the company and what it takes to provide sustained differentiation and ongoing sources of revenue and value.

Strong product organizations work to strike a balance between those things required to keep the business operating, and innovating on behalf of the customer.

Product organizations must achieve this balance otherwise they cease to provide the role that is needed.  In some companies, especially those with strong business owners or strong senior executives, others will feel they need to step in and try to fill this void, and it’s hard to fault them for that.

After years in this situation, the problem becomes cultural and institutionalized, and the product organization is not empowered, rarely even respected, and of course they are frustrated.

Fortunately, this situation can be corrected although it’s not a simple change, and it requires sustained and strong leadership.

It starts by having the product organization earn the respect of the company and its leaders, and this won’t happen until the product managers become the recognized expert on the company’s customers and users.  And this of course means reconnecting with your customers in a big way.

Once you’ve done this, and leaders from across the company seek you out because of your understanding of the customer, then you’ve earned that seat at the table, and now you can bring the opportunities that you have discovered during your intense customer interactions.

I don’t mean to oversimplify what it takes for a product organization to regain its mojo; I’ve got another article brewing on a set of steps to achieve that, but for those of you that feel trapped in a product organization that lives to serve the company stakeholders rather than your customers, and I know there are many of you, I hope you will take a look at your roadmaps and backlogs and ask yourself which of those items are actually serving the customer and have a chance at delivering real value for your company?


  • Product Management
  • Product Marketing
  • Technology
  • User Experience

© 2009 Silicon Valley Product Group. All rights reserved.