Skip to main content

Enable Your Product Manager to Be Strategic

Pragmatic Marketing's Steve Johnson has written an e-book, The Strategic Role of Product Management. In it, Steve argues that strong product management is key to the success of a company when it is strategic and focuses on identifying and solving market problems.

A key graph from the book is:
Increasingly we see companies creating a VP of Product Management, a department at the same level in the company as the other major departments. This VP focuses the product management group on the business of the product. The product management group interviews existing and potential customers, articulates and quantifies market problems in the business case and market requirements, defines standard procedures for product delivery and launch, supports the creation of collateral and sales tools by Marketing Communications, and trains the sales teams on the market and product. Product Management looks at the needs of the entire business and the entire market.
What can you, as a corporate executive, do to enable the strategic product management that will contribute to your company's success?
  1. Create a product management department in your company.
  2. Ask your product managers to lead the company's positioning efforts.
  3. Hire interaction designers and user interface designers that free your product managers to focus on documenting market requirements.
  4. Support your product managers' efforts to call and visit both prospective and existing customers.
  5. Make sure your QA team tests not just against technical specifications, but also tests that your products solve the problems your product managers identify in the market.
  6. Make sure your product managers are experts in the principles governing positioning, pricing, and naming.
Above all, stand up for the strategic recommendations of your product managers. In the face of interdepartmental paralysis, effective product management requires strong executive support.

Comments

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio