Personal tools
Document Actions
Home / Strategic Role of Product Management
Document Actions

The Strategic Role of Product Management

How a market-driven focus leads companies to build products people want to buy.

Who is focused on next year and the one after, the next product, the next market?

The Strategic Role of Product Management

 

Does product management matter?

The Strategic Role of Product Management explains why product management is a critical, strategic role in a technology company. One which guides products to be created based on a market need, not because someone thinks it is a good idea. 


Download The Strategic Role of Product Management


Kindle Version of Strategic Role of Product ManagementKindle Edition ($0.99)



Development knows what can be built;
product management knows what should be built.

 

Marketing knows how to communicate;
product management knows what to communicate.

 

Sales knows what one customer wants to buy;
product management knows what a market full of customers want to buy.







 

Commentary on the Strategic Role of Product Management

 

 

Jeff Lash at How to be a Good Product Manager

Delegate Tactical Responsibilities

If you want to be a bad product manager, do everything yourself. You’re the product manager, after all, so you should be the final authority on everything related to the product. You should be the one answering questions from salespeople, drafting press releases for marketing, defining all of the processes for suppliers, and poring over every detail with engineering. Sure it takes a lot of your time, but that’s what a product manager should be spending time on. What other more important things are there to do?

If you want to be a good product manager,delegate tactical activities to allow you to spend time on the strategic aspects of the job. Effective product managers pass on product knowledge and responsibility for tactical decision-making as much as possible to others on the product development team. By leveraging the rest of the team, the product manager can focus on the strategic role of product management.

It is difficult for many product managers — especially new product managers — to effectively balance the strategic and tactical priorities of product management. With so many competing priorities, the minutia and day-to-day tends to take over. To extend a common metaphor, it’s not just that product managers sometimes focus on the trees instead of the forest — they go so far as to end up focusing on a specific piece of bark.

While it is easy to say that product managers should be more strategic and less tactical (see Spend your time in the right places, for example), actually accomplishing that is a significant challenge. Pragmatic Marketing recently released the free ebook “The Strategic Role of Product Management,” by Steve Johnson, which describes why product management is a strategic role and why product managers need to think and act strategically. Buried in the “Final thoughts” section is this beautiful nugget of wisdom (emphasis added):

Product management is a strategic role. Yet as experts in the product and the market, product managers are often pulled into tactical activities. Developers want product managers to prioritize requirements; marketing people want product managers to write copy; sales people want product managers for demo after demo. Product managers are so busy supporting the other departments they have no time remaining for actual product management. But just because the product manager is an expert in the product doesn’t mean no one else needs product expertise.

Product managers should take heed of this last sentence. Think about all of the tactical activities in which you engage — documenting details, answering questions, describing functionality, responding to feedback, tracking down responses, and the like. How much of your time is taken up by these activities? Why are you engaged in them? Is it because

  1. you are the only person in the company who knows how?
  2. everyone else is busy and you are the only one who has free time?
  3. they are so important that they must be done by you and only you?

The answer to these questions is probably an emphatic NO in most cases. The real reason that product managers are engaged in these activities is because they have done them in the past, so others assume they will do them in the future. Every time a product manager writes copy for marketing, or conducts a demo for sales, or investigates some technical issues for development, the product manager creates the expectation that he or she will do that in the future. Obviously, there are some occasions where this may be appropriate, However, the vast majority of the time, the product manager can and should be giving the necessary direction, context, and guidance to allow other people to accomplish these tasks themselves.

Most product managers do not have staff reporting to them, so it is not necessarily as easy as delegating tasks to a direct report. Instead, product managers need to leverage others and teach them to be self-sufficient. This is not to say that product managers should ignore requests or haphazardly push off their responsibilities, of course. Instead, product managers should look to make those around them more effective by providing them with the tools, information, or resources they need.

Every time you as a product manager are presented with a task, ask yourself these questions:

  • Is this helping to advance the product strategy?
  • Does this support one of the high-level goals for my product?
  • Is there anyone else within the company besides me who can accomplish this task (e.g. answer this question, investigate this problem)?
  • Is this something that has come up before or is likely to come up again?
  • Is this a valuable use of my time?

It’s never easy saying “no,” though it may be easier to look at it this way — every time a product manager says “yes” to something that is tactical and routine, they are saying “no” to something that is forward-looking and strategic. Which would you feel more comfortable telling your boss — or the CEO — that you said “no” to?

So what do you do with the tactical activities — those requests for copy writing, operational meetings, responses to customers, and discussions of detailed product minutia? Ask yourself — and others — whether they are really necessary, or at least whether it is really necessary for you to be included. Going back to the three questions posed earlier, look at why you are engaged in tactical activities:

  1. If you are the only one who knows some vital piece of information, figure out some way to rectify that. Document it, communicate it, teach it to others, pick someone to transfer knowledge — find some way to make sure that someone else has the information. Beyond just providing better use of your time, this can be vital for business continuity and succession planning.
  2. If everyone else is claiming to be busy and is offloading responsibilities, the same can be doubly true for a product manager. Help create ways for people to answer questions or streamline tasks on their own, rather than passing on their additional work for you.
  3. If there really are activities that appear to be vital enough to be performed by you and only by you, analyze those activities closely. Some may seem critical at first glance, though upon review you may notice that they are not as important as originally thought. Also, other people may be turning to you because they think you want to be involved, or because they think you would be offended if you were not consulted. Just because someone else thinks a task is crucial enough that it must only be done by you does not mean that you have to agree with them.

Lastly, if you are involved in these activities only because you have always been — well, then make it a resolution to stop today! The more product managers can think about their role as being strategic and market-focused, the more they can add value to the organization and to customers. Effective product managers help create more product expertise within the company. This gives the product manager as much time as possible to focus on the reason the company created the position — to add value by creating and improving market-focused products.


Michael Ray Hopkin at Lead on Purpose

Though the role of product manager differs from one company to the next, most product managers I know believe they drive the strategy for their products. I suppose in most cases they do. Strategic product managers spend time understanding the market and directing product activities toward meeting those activities. CEOs and other executives don’t always (or often) understand this. Therefore, part of the product manager’s job becomes educating executives on the strategic importance of understanding the market.

I found a great new resource for educating people on the strategic role of product management. Yesterday Steve Johnson released an ebook called The Strategic Role of Product Management. He answers several questions such as who needs product management, what is marketing, and where does product management belong in an organization. It’s written in an easy-to-read format, in Steve’s unique and witty style, with stories that drive home key points. It’s replete with facts and statistics based on the many years of research carried out by Pragmatic Marketing. One of the key takeaways for me is the focus on helping people in other roles understand why product management is strategic. The following quote provides some insight on this:

Instead of talking about the company and its products, the successful product manager talks about customers and their problems. A product manager is the voice of the market full of customers.

One last thought about the importance of leadership. I found a quote by Dee Hock (founder of Visa) that provides good advice for product managers who need help convincing executives of their strategic role:

Control is not leadership; management is not leadership; leadership is leadership. If you seek to lead, invest at least 50% of your time in leading yourself—your own purpose, ethics, principles, motivation, conduct. Invest at least 20% leading those with authority over you and 15% leading your peers.


Roger Cauvin at Cauvin

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.


Great e-book!

Posted by Karen Milton at 2008-04-17 11:42 PM
Hi Steve,

This is a great e-book and one I will pass around to our Executives. Do you know what percentage of companies use product managers in a strategic role vs. a tactical role?

PM in a strategic role

Posted by Steve Johnson at 2008-04-18 12:23 PM
Go to http://www.pragmaticmarketing.com/publications/survey/2007/product-management-activity to see how people spend their time. The tactical activities seem to dominate of course but many product managers are spending significant time on the strategic items. Another indication is where the job reports. Years ago, it was frequently in development or marketing, and now it increasingly reports to the CEO or VP of product management.

Research

Posted by Danielle Eide at 2008-05-01 02:14 PM
Have you done research on the role of product management from other countries and how does that fit with pragmatic's approach?

Our Research

Posted by Steve Johnson at 2008-05-01 02:17 PM
Different implementations of product management occur not so much by the country but how the office is focused. In offices with development labs, product management tends to be development-focused. When the offices market products (but do not develop them), the role tends to become marketing-focused.
We have found in all cases that product managers can change the way products are developed, marketed, and sold by focusing on the problems of the market rather than the features of the product. Our research is consistent around the world. Successful products come from the companies that know the market and its problems. Check the Pragmatic Marketer’s article on “Products and services that resonate” at http://www.pragmaticmarketing.com/publications/magazine/6/2/why-didnt-we-think-of-that

SAAS

Posted by Larry Concannon at 2008-05-02 06:37 PM
How does a SAAS business model change product management?

SaaS Business Model

Posted by Steve Johnson at 2008-05-02 06:54 PM
One way of looking at a SaaS business model is to ask how product delivery affects product management. It certainly affects the way the business recognizes revenue but the challenge of identifying the market problems is basically unchanged. What’s great about SaaS is the customers tend to have a more intimate a more vocal, relationship with their vendors. In my experience, on-premise customers complain to internal IT who largely ignore them. On-demand customers are more likely to complain to the SaaS vendor—and expect an answer!
The big impact SaaS has on product management is that it tends to pull product managers into more urgent operational and individual customer issues. SaaS packaging seems to involve more daily and weekly decision-making. That’s why many SaaS companies supplement the product manager (who should be monitoring the future market and potential offerings over months and years) with an operations manager (who monitors the daily health of the current customers and existing products over days and weeks).

Saas Business Model

Posted by Donna Reed at 2009-06-05 04:28 PM
Yes, Steve says it so well. Having worked in delivering SaaS products to clients I have also found that many more product feature requests (FR's) are received by Product Managers....and hence the need to not only manage those requests in a prioritized backlog and roadmap will be critical....but dealing with the expectation of "I expect an answer fast".

Steve's webinar on this topic "Roadmaps, Requirements, ..." is a must to listen to to help you organize this barage of FR's.

Communication out becomes very critical the the influx of communication "in" when working with SaaS solutions.

How ave you dealt with these issues?

Critera

Posted by Mike Volpe at 2008-05-02 06:37 PM
What are the most important criteria to look for when hiring a product manager?

Qualities of a Product Manager

Posted by Steve Johnson at 2008-05-02 06:54 PM
The most important quality of the best product managers is the ability to sublimate personal opinions to the market facts. In so many cases, the good product manager knows the answerbut the great product manager supplements his intuition with market facts—and invariably finds another facet or another problem that he hadn’t anticipated.

Agile Environment

Posted by Amy Bourne at 2008-05-02 06:37 PM
How have you seen this framework applied in agile environments?

Agile Environment

Posted by Steve Johnson at 2008-05-02 06:54 PM
Yes, absolutely. We have been advocates of agile methods, particularly Scrum and XP, since 2000. Agile developers realize, perhaps more than traditional developers, the role customer input plays in defining product requirements. Customer input is in fact critical to the agile development process.
The challenge for many product managers is that they are getting pulled into (or are imposing themselves onto) development management. Effective product managers focus on product managementand leave development to the developers. Learn more about product management in agile at http://www.pragmaticmarketing.com/publications/topics/06/0606sj/ and at Stacey Weber’s blog at http://theagileproductmanager.blogspot.com/

MARCOM

Posted by Gary Barush at 2008-05-02 06:37 PM
Which of the boxes would you suggest fall under the duties of MARCOM.

Marcom

Posted by Steve Johnson at 2008-05-02 06:54 PM
It depends on the role marketing communications plays in your company. In most companies, marcom is focused on campaigns and not products. Marcom people do not know the product or the market; instead they specialize in specific communication techniques such as PR, events, direct mail, graphics, and so on. Without product knowledge, you cannot do any of these boxes. In this case, marcom serves as an internal agency to product management or product marketing. This means that product management owns the content of the boxes and marcom owns the execution of them. For instance, a product manager or product marketing manager might determine that an ebook is a key part of your thought leadership; marcom would define and manage the campaign around the ebook.

Tactical to Strategic

Posted by Chris Streight at 2008-05-02 06:37 PM
Where on the website is the PDF showing Tactical to Strategic

On the Framework

Posted by Steve Johnson at 2008-05-02 07:04 PM
Go to http://www.pragmaticmarketing.com/pragmatic-marketing-framework

The CEO

Posted by Michael Kasloff at 2008-05-02 06:37 PM
Where does the big-ego CEO who has all the right ideas fit into the framework?

Use the Framework

Posted by Steve Johnson at 2008-05-02 07:04 PM
The framework works best with people who believe, as we do, that they market should be consulted about its problems. Some companies have a CEO (or CTO or product manager) who believes instead that customers are stupid; they believe that they know more about the market’s problems than the market does. In this scenario, use the framework to articulate and organize the facts you know: the requirements, the positioning, the sales process, and others. And if you see that your market facts are out of sync with your leader’s plan, you can wonder if you’re perhaps in the wrong place.

Software PM's

Posted by John Slauson at 2008-05-02 06:37 PM
Do most successful software PMs come from a programming background?

Product Managers

Posted by Steve Johnson at 2008-05-02 07:12 PM
The two most common sources of product managers are development and sales, specifically sales engineering. Many developers want to spend more time on defining product strategy, having tired of managing people or developing products. Their struggle, as you might imagine, is that they know too much about the technical bits of the product and tend to dabble too much in development management and product design. It’s natural.
Product managers from the sales ranks know the market, know the product, know how to demonstrate and close and answer technical questions. They’re great! Their biggest challenge is to step away from their sales orientation—the issues of today’s big deal, the urgent client problem—and focus on market full of clients.
Here’s the best source of product managers: hire your competitor’s top sales engineer. He or she cannot be promoted because they are so good. Your competitor’s best SE already knows your market, they know their product (and yours), they know how to travel but they are ready to travel less than 110%.

Buyer Personas

Posted by Martin Johnson at 2008-05-02 06:37 PM
Do you have the questions (in a document or link) that would help us to figure out our Buyer Persona's. who should I contact for a quotation on Consulting.

Buyer Personas

Posted by Steve Johnson at 2008-05-02 07:12 PM
What do you want to know? From user personas, we want to know about problems that prevent them from being successful in their jobs. From buyer personas, we want to know how to participate in their thought leadership community. What conferences do they attend? Do they sit in on webinars? Or do they prefer to read? Are they reading blogs? How can we have a meaningful interaction with them?
The more time you spend with clients, the more obvious your personas become. Creating a persona is not a creative writing exercise (although it certainly helps to be creative). Instead, persona development is grounded in research.
We at Pragmatic Marketing know product managers: we visit dozens of them weekly; we survey hundreds in our annual survey; I can review their technical stats in my website logs. I can tell you everything about Robin, the product manager and Alan, the director of Strategy.
Do you know your customers? Are they fictional characters? Or are they archetypes grounded in research? Personas give us a programming and marketing target. Make sure that everyone in the company has clarity on our customer so we can deliver product that meet their needs and marketing collateral that answers their questions.
Read more in http://www.pragmaticmarketing.com/publications/magazine/1/4/0310sj and http://www.pragmaticmarketing.com/blogs/productmarketing/archive/2007/08/28/knowing-your-personas/

The Role of Product Management

Posted by Mohammad Ramezan at 2008-05-02 06:37 PM
How do you see the role of Product Management in the companies which have internal IT shops, i.e. they product products for the use of their own business not to sell softwares to the market? I am hearing from business that "We are building Business Systems rather than Software Products." OR "Our business is not in the software market and is not a product company, so the Product Management role like software companies does not apply here." OR "Product Managers are perceived as Product Owners, but in here the Business Groups are the owner of products not IT." How would you deal with that in these types of companies?

Customers with requirements...

Posted by Steve Johnson at 2008-05-02 07:12 PM
Hmmm, I’m not sure I disagree. Ask what results we hope to achieve from having product management. In the vendor world, product management is about understanding clients and potential clients, and delivering a solution that can be sold to more than one of them. Do you need this in your company?
One of my favorite clients is a church headquarters. They have dozens of product managers supporting their internal infrastructure. They want to run their IT like a business including formalized product requirements, clear market positioning, and sales tools that help their distributed churches “buy” the right solutions.
Yet I’ve had this discussion with some organizations that just stare at me blankly. “What’s a customer?” they ask. One government agency thinks of us as taxpayers, not customers—which says a lot, doesn’t it?
Whether a church, an internal IT group, or a vendor, we all have customers with requirements.

Understanding the Market

Posted by Guhan Vaidyanathan at 2008-05-02 06:37 PM
What is the best way to understand the market?

Be part of it.

Posted by Steve Johnson at 2008-05-02 07:12 PM
The best way to understand a market is to be a part of it.
Many product managers come from the client world so we already know more about the technology and domain than an outsider. But we have to keep that information current. If you’ve been a product manager for more than a couple of years, you areout of date; you no longer understand the realities of the job. The best way to understand the problems in a market is to observe them. Go visit to customers and resist the temptation to talk. Watch with your eyes open and your mouth closed.
For more on conducting research, see Barb Nelson’s series on understanding the market at http://www.pragmaticmarketing.com/publications/magazine/1/2/07bn

Buy In

Posted by Mary Caplice at 2008-05-02 06:37 PM
How difficult is it to get Engineering to buy into this in most cases?

Getting Buy In

Posted by Steve Johnson at 2008-05-02 07:16 PM
For me it’s always been an easy sale. Developers and engineers want to be market-driven; they just do not want to be driven by marketing people. Sadly, too many product managers and marketers think that their opinions matter. And to make the pill especially hard to swallow, they say, “I don’t have to understand technology. Just explain it to me like I was a five-year-old.” Engineers typically take a wonderfully passive-aggressive approach to this by just ignoring the incompetent product manager.
We have consistently heard that developers embrace our problem-oriented approach to writing requirements as explained in our Requirements That Work seminar and our “Writing the Market Requirements Document” article at http://www.pragmaticmarketing.com/publications/topics/01/0104sj/

Question

Posted by Deepesh Nayanar at 2008-05-02 06:37 PM
Steve: What do you say to a PM who says I have been in this job for so long, I know exactly what the customer would say if I went looking for Market Problems?

Prove It!

Posted by Steve Johnson at 2008-05-02 07:16 PM
I’d say, “Prove it!” That product manager should go visit some customers with someone else taking notes. I’ve never had a case where I didn’t learn something new when talking to customers. Oh, and when I said “customers” I include those people who haven’t yet bought from us. Who knows what they need? Someone needs to ask.

Survive to fight another day

Posted by Ken Friesen at 2008-05-02 06:37 PM
Sometimes software companies will go through hard times - and management will pressure Product Managers to only to Tactical in order to survive to fight another day. How do you defend the long term and tactical in this scenario?

Emergency Mode

Posted by Steve Johnson at 2008-05-02 07:23 PM
I think the real question is how long a company can stay in emergency mode. It’s true; there are times when cash flow becomes critical and everybody is in sales. But employees cannot forever be! At some point, the emergency should pass and we can all take a breath. And even while in emergency state, who is thinking about future products? Who is taking care of existing customers?
A company that is always in a state of emergency will quickly find that its best people are leaving for a company that is being run by adults.

Lost Prospects

Posted by Tim Smith at 2008-05-02 06:37 PM
How do you get lost prospects to take calls from PMs for loss analysis? In our experience, it is very difficult to avoid them assuming it's an attempt to salvage the sale.

Win/loss analysis

Posted by Steve Johnson at 2008-05-02 07:31 PM
Well, that’s the trick, isn’t it? One way to convince them is to actually not be attempting to salvage the sale.
Win/loss analysis tells us what we do right and wrong in selling. For product management purposes, you may need to visit only one or two each month to learn what you need to know about problems in selling. But I suggest that you look at your list of questions—and then look at them again from the customer’s point of view. Are you asking sales questions (focused on‘how I can sell you better next time’) or are you asking product management questions (focused on ‘how we can create a better product in the future’)?
Product managers tell me repeatedly that they visit lost customers quite easily. One said that he had a 100% success rate. I suspect he starts by saying, “I’m not selling.” Another product manager told me that she did a dozen win/loss calls, wrote it up, and gave it to her VP. A few days later, the VP told her that the win/loss was the only fact-based document in the entire company. Kudos!
Read more about win/loss analysis in http://www.pragmaticmarketing.com/publications/magazine/1/3/08bn

Tools

Posted by Mark Roberts at 2008-05-02 06:37 PM
Are there any tools to help us understand finding needs? what do you offer to help my culture embrace this from the ceo down?

Embracing from the CEO Down

Posted by Steve Johnson at 2008-05-02 07:31 PM
The Strategic Role of Product Management is focused specifically on product management in a technology products company but our “Tuned In” series is focused on helping executives re-connect with their customers and markets. Go to http://www.pragmaticmarketing.com/secrets for links to the ebook briefing as well as to the paper book and blog.

Research Tools

Posted by Steve Johnson at 2008-05-02 07:31 PM
Our two favorite research tools are onsite interviews and web-based surveys. We discuss these (and four others) at length in Practical Product Management. If you’ve already attended the seminar (or need something to tide you over until you do), read Barb Nelson’s excellent series on understanding customers, potential customers, and recent evaluators; for the first article in the series, go to http://www.pragmaticmarketing.com/publications/magazine/1/2/07bn

Recommendations?

Posted by Joyce Yan at 2008-05-02 06:37 PM
What would you recommend as the best technique or strategy to convince the rest of my organization to adopt this framework?

Prove the framework by living it

Posted by Steve Johnson at 2008-05-02 07:42 PM
My free ebook is a first step towards convincing your colleagues and executives of the strategic value of product management. But nothing convinces as much as success. Prove the framework by living it. For your next meeting, come prepared with market facts. Everyone else will have opinions—we have plenty of those of course—but you will be able to say, “interesting opinion but here’s what the market is telling me.” Download the ebook at www.pragmaticmarketing.com/srpm

The Triangle

Posted by John Gromberg at 2008-05-02 06:37 PM
From a model persepctive, where does the triangle (Dev + Marcom + Sales) relate to the master PM grid? Does the grid, in theory, fit in the middle of the triangle?

The Center of the Triangle is the Grid

Posted by Steve Johnson at 2008-05-02 07:42 PM
The Pragmatic Marketing Framework (“the grid”) covers all of the activities that successful companies typically associate with product management. So yes, the center triangle is the grid.However, the typical product managers knowledge of business, products, and markets often pulls him into product design, product marketing, and sales engineering. The trick is to enable those groups so you can focus on product management. You can read more about the product management triad at http://www.pragmaticmarketing.com/publications/magazine/1/2/07sj

Getting Strategic

Posted by Don Rokusek at 2008-05-02 06:37 PM
Do you see more organizations using Sales Engineers - or Technical Consultants - for some of the tactical boxes (channel support)? to allow PMs to get more strategic???

Getting Strategic

Posted by Steve Johnson at 2008-05-02 07:42 PM
Absolutely. In most companies, the right-most column, Channel Support, isn’t product management at all; it’s sales engineering. When organizations realize that product management is doing what sales engineering could (or should) do, I find myself recommending they hire more sales engineers instead of more product managers. Sales engineers support individual deals so that product management can focus on markets full of deals.
I have long been an advocate for the role of sales engineering. Read more at http://www.pragmaticmarketing.com/publications/magazine/2/5/0410sj/

Lead Generation

Posted by John Brandt at 2008-05-02 06:37 PM
Why is lead generation so far separated from Customer Aquisition in the chart?

Lead Generation

Posted by Steve Johnson at 2008-05-02 07:42 PM
We wanted to separate lead generation a little from the marketing plan. The marketing plan should include how to acquire customers and how to retain them—lead generation is only one technique towards achieving the goals of our marketing plan. A much stronger program for the typical marketing plan is thought leadership and we put that on the lower, more-technical part of the grid.
For more on marketing programs, learn about our Effective Product Marketing session at www.pragmaticmarketing.com/epm.

Career paths

Posted by Raji Narayanan at 2008-05-02 06:37 PM
You described "technical product manager " vs "director, product strategy". Is the latter the only career path for the former ?

Career paths

Posted by Steve Johnson at 2008-05-02 07:42 PM
Yes, it seems logical for a technical product manager to become a director of strategy and then VP of product management or marketing. But if there’s a typical career path in product management, I don’t know about it. For some product managers, the next step isn’t up the latter but sideways. One former product manager friend is now VP of Customer Support; another is a sales guy;many are nowrunning their own businesses. This job gives exposure to every aspect of a technology company and some product managers learn they prefer other jobs that are tangential to product management.
But for many, product management is the ideal job. It was for me! The great thing about product management is that you touch every part of the company: you work with development, marcom, sales, support, services, finance, operations, production, and more. You work with everyone in the company. Only one other role has the same holistic view of the company… CEO.

Career paths

Posted by Sundar at 2009-06-18 01:44 PM
Well said. Normally, they call a Product Manager as the "CEO of a product"

Career path

Posted by Aware IT guy at 2009-08-21 07:41 PM
With that being said, what obstacles do you see for someone with a background in systems administration and support in getting in to such a role? Part of my current job as an IT Manager requires that I work with HR, Finance, business units, services, etc. I am currently redefining part of my role as the Product Manager for internal systems in order to get better insights and understanding our clients needs. Do you think this would be a good steps towards developing a career in PM? Should my next step be sales engineer once I've mastered this portion of my professional development?

think activities, not titles

Posted by Steve Johnson at 2009-08-24 11:08 AM
Look at the chart of product management activities. Which are you doing? Which should you be? Use this chart to describe your current job and the job you'd like to have. As you say, for internal systems, you may already be a product manager.

It's always good to spend some time in sales, either as a rep or a sales engineer. In your current role, you may not have the sales experiences that you'd like but I suggest that you sit down with a hiring manager and ask what skills you need to fulfill the job. Use the Pragmatic Marketing Framework at http://www.pragmaticmarketing.com/pragmatic-marketing-framework to focus your conversation.

Tools and Templates

Posted by Dana Cole at 2008-05-02 06:37 PM
Is the a place on the pragmatic site for tools, templates, etc?

Tools and Templates

Posted by Steve Johnson at 2008-05-02 07:48 PM
We offer templates and tools to our seminar attendees. Come to a class and get a complete set.

Teams Attending Seminars

Posted by David Guinther at 2008-05-02 06:37 PM
How often do product teams (development, support, marketing) attend seminars jointly ?

Bring the Whole Team!

Posted by Steve Johnson at 2008-05-02 07:48 PM
Great question and the answer is “Not often enough.” Definitely bring your team! Every time you feel yourself saying, “hmmm, maybe that won’t work for us” you can turn to your development, marketing, or support people and ask! In particular, our problem-oriented approach for market requirements is embraced by developers and our persona-oriented approach for positioning is embraced by marketers. Do you want to build a team? Then bring your whole team!

Educating Executives

Posted by Michael Hopkin at 2008-05-02 06:37 PM
What are practical things we can do to educate executives about the pragmatic framework?

Educating Executives

Posted by Steve Johnson at 2008-05-02 07:48 PM
Read my ebook at www.pragmaticmarketing.com/srpm. Print off some articles from http://www.pragmaticmarketing.com/resources/articles/. Forward specific blog posts from www.productmarketing.com. Attend a seminar. Listen to this (and other) webinars with your team.

Newbie Product Manager

Posted by Manoranjan Sahu at 2008-05-02 06:37 PM
My organization is too development focused. What would you recommend for a newbie product manager to pursuade folks to market focused

Newbie Product Manager

Posted by Steve Johnson at 2008-05-02 07:48 PM
First read and distribute my ebook at www.pragmaticmarketing.com/srpm. I wrote it as a tool to show that product managers can be more than secretaries to developers and the best source of demos for sales people. Most of all the book attempts to show that the best products are grounded in the reality of the market.
In the end, your team has to ask: where do requirements come from? If you don’t answer “the market” then this will be an uphill battle. While it is true that people don’t know what features they need, people do know what problems they have. Or can recognize them when problems are shown to them.
Or here’s another approach. Just do it. Interview 10 customers this month and start being a name-dropper. At your next development meeting, say “really? Is that what you think? Because Jim Brunke at J P Morgan Chase told me something else entirely. He said, …”
Don’t try to show them with your words; show them with results.

Question

Posted by Shawna Kelly at 2008-05-02 06:37 PM
What would you say when our ceo is also playing the role of director of product strategy? Is that fairly common?

CEO Playing Director of Product Stategy

Posted by Steve Johnson at 2008-05-02 07:48 PM
In a small or new organization, it’s natural for the founder or CEO to define product strategy. But at some point, running the company becomes a full-time job and defining strategy takes a back seat. Who is spending hours each week understanding the market?
The one who owns these activities is the one who writes them down and keeps them current. Is that your CEO (or president, head of business development, director of strategy, product manager)?
Ask your CEO,
• How many customer visits have you documented this month?
• When was the last time you watched a client doing the job?
• When was the last time you interviewed a client without demoing the product
• How many win/loss interviews did you complete this month?
• What are the top three product issues according to customer support?
• What are the top three buying issues according to the sales channel?
(Oh, and if you’re a product manager, ask yourself the same questions.)

New Position

Posted by susan kahler at 2008-05-02 06:37 PM
I am just starting to transition to a product management role from another background. What's the number one piece of advice that you can give me?

New Position

Posted by Steve Johnson at 2008-05-02 07:54 PM
Often, a new product manager tries to lead with opinions while the developers and others on the team are anxious for some market facts. You’ll quickly learn that your opinion, while interesting, is irrelevant. So start your new job by interviewing customers (to understand what your product does well) and then do win/loss analysis (to discover what your product doesn’t do well).
And of course, the best way to start a new job is to make sure you have current skills, so you’ll definitely want to attend Practical Product Management to get grounded in best practices—andpractical ones—forproduct management.

The Triad

Posted by Somayaji Manikantan at 2008-05-02 06:37 PM
How do you modify the coloring of the traid for an "internal" product where the customer is in the same company and not external?

The Triad

Posted by Steve Johnson at 2008-05-02 07:54 PM
Whether an inside customer or an outside customer, product management is responsible in most companies for writing requirements. Where do these requirements come from? The people who use the product are the ones with requirements. So if your product is only used internally, then you still need someone to interview the market full of internal customers.
The way I have organized the triad may not work for everybody. Feel free to change the coloration to better fit your environment. However be cautious of adding or removing activities. We often find that companies have added non-product management activities, such as beta test and writing RFPs, because product managers have the skills to do them—not because it has anything to do with product management. In these two specific cases, beta testing should be run by QA and RFPs should be written by sales and sales engineering. Just because a product manager can do it, doesn’t mean he should.

comments

Posted by Rashid minhas at 2009-05-20 03:57 PM
dear,
i read this column its so great and in line of job responsibilities of product manager. i happy to read it.

share it

Posted by Steve Johnson at 2009-05-22 02:24 PM
I'm glad that you found it helpful. Please share it with your colleagues.

hello

Posted by mikko at 2009-06-22 12:27 PM
can i ask you something?

what roles do consumer and supplier play in new product definition and production?..

you need both

Posted by Steve Johnson at 2009-08-24 11:08 AM
In order to create a great product that people want to buy, you need to understand the entire value chain from supplier to vendor to sales channel to consumer. Many companies focus only on the needs of their sales channel and miss the bigger opportunities. I love (good) sales people but they are usually focused on requests from their clients--which is what we want--but they often miss the revolutionary opportunities that create breakthrough products. In the end, create a satisfied customer and the value chain will usually take care of itself.

Two Questions

Posted by John Dueckman at 2009-09-18 06:03 PM
Where would a task such as a special sales campaign fall in terms of the framework? Is it in one of the boxes?

What advice would you give to help a company or division to move from being, in essence, run by the engineers (i.e. deciding strategy, requirements, etc) to being handled by product managers? How do you get the company or division to recognize it cannot continue having engineers "assume they know the market" when really they're focussed on their own technical area (i.e. they can't see the forest for the trees)?

on sales programs and engineering orientation

Posted by Steve Johnson at 2009-10-04 09:26 PM
Ideally, sales programs are the domain of marketing execution and are articulated in the marketing plan. product management is best as a strategic role, defining and analyzing, rather than an operations or execution role. So look for patterns in your sales numbers; once you identify a problem, work with marketing communications to determine the right approach for addressing the problem.

As for being engineering driven, we've all been there too. Engineers and developers know more about their technology than anyone and truly think they know what customers want. Yet by defining buyer and user personas and then quantifying their requirements, we can show that what engineers think will sell isn't the same as what the market data tells us.

My advice, don't try to persuade developers with opinions; use market facts. Then after each release, do a retrospective to see which features were adopted and which were not. If you're doing product management right, your market-driven features will win the day.

Question

Posted by Tony Goulding at 2009-09-18 06:03 PM
What if you're in the position of establishing a market and so, the pains/needs of the market is not yet so obvious?

market driven starts with markets

Posted by Steve Johnson at 2009-10-04 09:26 PM
Some companies can be successful by inventing cool things and then finding people who want them. Most companies find that understanding market requirements BEFORE building a product works better. In fact, these companies are 31% more profitable because you know the market will want the product.

Regardless, if you're working on a new product, go find some candidates who are likely to be the target and understand their challenges. You'll likely find that they want some features you haven't anticipated and won't want some that you have planned. And in this scenario, shipping a product early with plans for LOTS of quick revisions and continuous market feedback will help you create a product that resonates in the market.

Location

Posted by Todd Rodgers at 2009-09-18 06:03 PM
Is there any reason that Product Marketing Managers need to be located at corporate headquarters or are remote managers common given current technology?

virtual product management

Posted by Steve Johnson at 2009-10-04 09:26 PM
With today's technology, it's easy to be a remote product manager. You can schedule calls and webinars to connect with your colleagues. That said, never doubt that a face-to-face meeting is better than a phone call or an email. I suggest t hat product managers schedule face time with developers, marketing, finance, executives, and sales people. And I strongly recommend face time with clients.

Ideally, product managers should have virtual tools to connect with colleagues around the world but they also need face-to-face time to make personal connections that last.

Question

Posted by Andy Fuller at 2009-09-18 06:03 PM
If you're a product manager in a company that's almost entirely focused on tactical activities, how do you suggest approaching "selling up" a process as described by the Pragmatic framework?

selling the idea

Posted by Steve Johnson at 2009-10-04 09:26 PM
Use the Pragmatic Marketing Framework to show your executives the rest of the job. In my experience, the execs woul like product management to be more focused on strategic activities than tactical- and operations-related ones. Ask how important the strategic activities are to the business and who, if anyone, has responsibility for them.

Meanwhile, start doing them anyway. Soon you'll be the only one in the room using market facts to make your point--and you'll find that people listen much more to facts than they do to opinions.

Defining roles

Posted by Barbara D'Antonio at 2009-09-18 06:03 PM
If an organization has a product management role, product marketing management roll (and a separate Marcom dept)... how would you really define the difference between the product manager and product marketing manager?

product manager and product marketing manager

Posted by Steve Johnson at 2009-10-04 09:26 PM
Titles are a mess but I think of product management as defining the product and product marketing as delivering the product. Or if you prefer, product management listens to the market and product marketing talks to the market. In order to do this, both product managers and product marketing managers need to know the market and how the product solves the market problems. Marketing communications (marcom) are typically experts in communication, not experts in the product, so their role is to develop programs that achieve the product goals. Just as we deliver requirements to development that results in products, we deliver requirements to marcom so that they can development marketing programs to address the communication problem.

See http://www.pragmaticmarketing.com/publications/survey/2007/product-management-activity for more on this.

Framework Question

Posted by Anuradha Sridharan at 2009-09-18 06:03 PM
Hi Steve, this is Anuradha from India. In the framework, could you elaborate more on innovation under the business section? thanks!

on Innovation

Posted by Steve Johnson at 2009-10-04 09:26 PM
Many firms allocate time for innovation and research. Product management's role in innovation is focusing it on markets and their problems, defining boundaries that keep us from going away from products that will drive business success.

Suggestions?

Posted by Theresa Smay at 2009-09-18 06:03 PM
Do you have any suggestions on convincing executive staff to focus on strategic tasks for internal enterprise software product.

The Strategic Role of Product Management

Posted by Steve Johnson at 2009-10-04 09:26 PM
I suggest that you share this webinar plus the The Strategic Role of Product Management ebook to get the ball rolling. Also, Tuned In, on the Amazon bestseller list last year, was written by our leadership as a tool for convincing management that listening to the market results in better products faster.

Use the Pragmatic Marketing Grameowrk to define the activities for product management in your organization. Ask the execs which activities are most important and they'll quickly see that product management can be the business advocates at the product level.

Prod Mgmt for geographically separated Teams

Posted by Guru at 2009-10-02 02:22 PM
How do you think Product Management changes if the main customer base and the executive team are based in a different country than PM and the dev and operations team? Is second hand (through the internet and feedback from people in the main market)information good enough as a source of Market demand / requirements ?

co-located teams

Posted by Steve Johnson at 2009-10-04 09:26 PM
The first question is always, what do you want from product management? If it's market knowledge, then the product manager should be near the market. If it's really development hand-holding, you'll need to be near the developers. Look at the activities on the Pragmatic Marketing Framework and define which are the most critial activities. Most teams realize that they need better market intelligence so product management should be near the market.

There's a school of thought however that product management is also a political job, which means working closely with all departments and all executives. So regardless of where you sit at work, you should schedule time to be in corporate headquarters.

I suggest that product managers plan no more than 20% of their time with development, 20% with marketing and finance, 20% with sales, and the rest of their time doing the strategic activities of product management.

Where does configuration fit within the organization

Posted by David Pesante at 2009-12-03 11:06 AM
First of all.. great eBook.

I have a question around the role of product configuration. We have a product that is highly configurable. We use configuration to create what we call our "base template" on how we feel clients should be "defaulted" when they sign up to use our product. One of the qualities of configuration is that it can be done via the application (does not require a developer to write code) but given the power of what we can do in configuration from the end users point of view, changes done via configuration (e.g. adding a dashboard of information, etc.) can be viewed as product enhancements. So, we are unsure as to where does it belong...

Should configuration roll up to Product Management or Development?

yes, a little of both

Posted by Steve Johnson at 2009-12-04 12:03 PM
The fact that you have a platform that must be adapted to many different client profiles means that the market requirement is to be highly customizable. Configuration options is the ideal approach. Making it customizable is the what--the job of product management; how to make it so is the job of development. The market needs a dashboard of information (is what); we will use these switches to drive data to this UI (is how).

Obviously, we want to collaborate. But let's keep product management focused on what the market needs and let development focus on how to get it.

Just to confirm...

Posted by David Pesante at 2009-12-05 10:58 PM
Thanks for the reply... just to make sure I understand the what vs how distinction as if refer to configuration (or even other things that are easy to do via the app).

Given the fact that development has built a framework that enables us to do things easily via configuration such as building dashboards (e.g. by picking parts from a library of predefined reports similar to how you do with yahoo, google, etc.) or just adding additional reports using our adhoc tool.... We use a team of configuration specialist to make this type of changes today (during new client implementations, ongoing account management support, and as part of our standard base configuration)... should that team roll up to product management or development.

collaboration is key

Posted by Steve Johnson at 2009-12-08 12:20 AM
Should it be product management or development? As you've described it, it sounds to me that the configurations, particularly dashboards, are more about what the market needs than how the market needs it. If it's 'what', then it's product management; if it's implementation of 'how' then it's development.

The real answer is that it doesn't really matter as long as the work is being done and is meeting the needs of the market.

This is old world

Posted by Navid Sadikali at 2011-06-10 06:11 PM
Your process does not conform to where industry is moving and how true innovation works.

Virtually all product managers need to hire skilled designers, who know how to go from observational research to what product concepts and requirements that will work for the business and the users. You need to tie the observation to the ideation - that is Design 101, taught at any design school. You need to have the synthetic right-brained people involved empathically with people and then the ideas will flow (trust me, not the ideas people told you). Typically (please let's not talk about exceptions, as I've worked with tens of product managers), the product manager is an analytical person who when he hears what people says takes it quite literally. The "magic" all happens in one persons mind to go from an observation to a drawing, or a system process that would solve all of the constraints (ie that is what design is).

For some things, such as say a technical constraint (can it be windows or should it be on Mac) customers have market requirements. However, for virtually all other things users have needs and goals but rarely requirements (did Apple mine iPhone requirements from people? Where was the list? You're kidding yourself on how innovation works).

So what you are proposing is having an analytical person, untrained in design research create a nugget of a requirement and bring it back to the company as gold. This is how all problems start. This is why most product managers are chasing the herd in their industry, and believe it or not the users are part of the herd (and will echo competitors assertions about what they need) The first thing that any qualified designer would be go right back in the field and do design research. Design research is so involved, that some companies now hire user researchers.

In summary, I don't believe your process would stand up to any scrutiny with any company that is using the power of design and synthetic thinking to innovate (Apple, Pixar, Proctor and Gamble). Go look at how they do it, their requirements process is a design process.

Design is a skill

Posted by Steve Johnson at 2011-06-13 04:09 PM
Market Requirements is a term that all product managers are familiar with but we’re just as happy to call them use scenarios, user stories, or anything else that communicates problems. Our focus is to get product managers OUT of the design and return them to reporting market problems. We believe strongly in the value of design and designers--both UX design and architecture--and we also agree that most product managers don’t have the skills to develop good designs.

What many designers miss is knowledge of the market. In so many ways, designers fall into the old trap of designing for themselves rather than for the market. One can look at the iPad and say “WOW! Good job!” but also look at Microsoft Office 2007 and say “Who was THIS designed for?”

You wrote: “The first thing that any qualified designer would be go right back in the field and do design research.” And I completely agree. Whether the product manager, the designer, or someone else, product teams need personal experience with customers--and also potential customers--to develop great products. Product managers should focus on problems; designers should focus on solutions.

There’s an old saw about Henry Ford who is supposed to have said, “If I asked customers what they wanted, they’d have asked for a faster horse.” But if he’d asked about their problems, they’d have said “I need to go faster.”

design is a 360 skill of future visualization and imagination

Posted by Navid Sadikali at 2011-07-01 03:50 PM
What many designers miss is knowledge of the market.

> Then they aren't very good.

In so many ways, designers fall into the old trap of designing for themselves rather than for the market.

> Designers should be a) designing for people, b) working with PMs to figure out the market implications and potential for a new product design c) knowledgeable in technology to ensure they can get their design built

One can look at the iPad and say “WOW! Good job!” but also look at Microsoft Office 2007 and say “Who was THIS designed for?”

> The fact that Microsoft flubbed a design in your opinion does not mean they lacked market knowledge. Most companies have tons of resources of people who go out and talk to people. They usually get right all of the market problems users can express, and miss any problems that require user experience considerations. They favor what people say, they don't favor using design methods to figure out market problems.

Whether the product manager, the designer, or someone else ...need personal experience

> The person choosing what the REAL PROBLEM is and WHAT POTENTIAL solutions exist should be one, or a very tight team led by design. The old axiom of WHAT (market problems) and HOW (design solutions) is absolutely false. Everything is a WHAT-HOW. Design when it is done right, looks like prototyping to imagine a future, evaluation (even by users) of that now created future to discover new needs, and then more iteration. It is messy and if you aren't versed in product design and user experience it is hard to talk about the HOW part, which feeds back to the WHAT part. Quite often WHAT problems aren't even apparent until you imagine the HOW of the future - I assure you that most cell phone companies in 2001 would have looked at their crappy built in web-browsers (I used mine once and never again), asked users if they want to surf the web on those (mass majority would have said hell no!), they could have watched people who use their cell phones only to discover that most problems are with voice mail systems....and never found the iPhone!

I encourage anyone to see how product innovation works at Pixar - they don't send someone off to write a story in some abstract form "People would like to see a story about a princess and a frog"...now let's write the market problem down and call the people who can sketch! Or at Apple, "people want to surf the web anywhere"...now let's document that and call the industrial designers to sketch out a solution. That is not how design-led companies work. They use design to figure out WHAT the problem is.

about product manager

Posted by safira islam at 2011-08-24 04:35 PM
agree with the above answer

Discuss the transition of purchasing from a tactical to a strategic activity.

Posted by Alvin Tee at 2011-12-02 07:29 PM
Discuss the transition of purchasing from a tactical to a strategic activity.