svpg
FREE newsletter

Subscribe via RSS

Subscribe

Tag Cloud

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

Browse by Date

  • 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

Where Should Product Management Live?

Posted by Marty Cagan on July 3, 2006

Tags: company culture, management, product management

The single most frequent question I get from product leaders in companies both large and small, is where should product management live? The choices are most often engineering or marketing. While if you have the right personalities, it can work in either place, I’m actually not a fan of it residing in either.

In this note I’d like to lay out the considerations and my views on where product management should live organizationally.

The most common situation I find is that product management lives within the marketing organization. The problem with this organizational design is based on the misconception that you get products from talking to your customers, and that it is marketing’s job to talk to customers. I won’t repeat all my arguments here, but suffice it to say that there are several key reasons why you won’t find successful products just by asking your customers, and further, what usually happens is that the product marketing role and the product management role get combined. These roles and the skills required are so different that what usually ends up happening is that one or the other (or both) gets poorly executed.

The next most common situation is that product management is put in the engineering organization. While this has the benefit of putting the people that invent and design the product next to the people that actually build the product, this can also be problematic because engineering organizations are really designed to focus on building a product right, rather than building the right product. It takes a different mindset and different skills to come up with the right product to build. Moreover, it’s easy for the product management team to be consumed in the details and pressures of producing the detailed specs rather than looking at the market opportunity and charting a winning product strategy and roadmap.

So if not the marketing organization, and if not the engineering organization, then where?

I am a believer in raising the level of the product organization to be on par with engineering and marketing. Ideally, the product organization includes the design team, because the interaction between product management and design needs to be absolutely as close as possible. Increasingly, you’ll see an organization with the name of “Product” or “Product Management” or “Product Management and Design” and often with a VP of Product or even a Chief Product Officer running it.

There are several benefits to this organizational design, but the biggest reason is that I believe that the head of product needs to have a seat at the table on the executive team. Companies are all about products, and marketing and engineering each have other considerations that typically supersede product. Additionally, this organizational structure makes it clear that the product is not being driven by the technology, and not being driven solely by the sales or marketing needs either.

One special case exists in many larger companies. Often large companies have a centralized engineering function and decentralized business units. This lets the company focus on multiple business lines, while potentially enjoying efficiencies in common engineering services. In such organizations, the product management and design function might be located in the centralized engineering/product development organization, or it might be in its own organization, or it might be a part of the business units themselves. Often in such an organization, the business unit managers must play a major product management role, so it can create problems if the product management team isn’t part of the business unit. In these situations, I usually prefer integrating product management and design into the business units.

While I’ve explained my reasons for the ideal locations, it can be very hard to implement organizational design change, and your company may not be willing or able to go this route. This does not necessarily mean that you’re destined for problems. It still boils down to the people involved and the skills they bring. If you can develop your product team’s skills and demonstrate their value across the company, any of these organizational structures will succeed.


  • Product Management
  • Product Marketing
  • Technology
  • User Experience

© 2009 Silicon Valley Product Group. All rights reserved.