Skip to main content

Why Have a Product Strategy?

About two weeks ago, I attended my first event hosted by the Silicon Valley Product Manager's Association (SVMPA). The main speaker was Barbara Nelson, a consultant for Pragmatic Marketing who gave a presentation entitled "Why Have a Strategy?" What follows are some takeaways from that presentation.

One would think that by now, most organizations would know precisely why a strategy is necessary. When I say organization, I don't just mean high-tech companies, as many in the valley naturally assume. This applies to all organizations; large, small, corporate, non-profit, etc.

Think about it for a moment. Think of all the activities that your organization is engaged in. Are they strategically aligned to accomplish a goal? What is the strategy? Is there even a goal or a vision in place?

A 2006 study titled "Making Strategy Execution a Competitive Advantage" showed that only just over half (54%) of companies surveyed have a strategic execution process in place. Of those, only 5% of the companies communicate that strategy to their employees. That means that 95% of the employees at companies with strategies in place are working in the dark. When you factor in the employees at companies without a strategy in place, the over-all percentage of employees without a strategic reference climbs to nearly 100%. It's a wonder that anything gets accomplished at all.

During my Software Project Management sequence at UC Berkeley Extension, one of my teachers shared the following anecdote. During the 1960's, a national news crew was interviewing a machinist of sorts in Maine. When asked what he was working on, he replied that he was working on the Space Program; the initiative set by President John F. Kennedy to put a man on the Moon. The important thing is that the man did not say he was fabricating metal tubing, or he was working for the local plant. He understood exactly what he was working on. He understood the vision; the ultimate goal towards which his efforts were contributing in a strategic, systematic manner. Therefore, he was highly motivated and proud of his work.

Having a stated strategy is good for morale. It's also essential for maintaining efficiency. Strategies do not merely help you determine what are going to do, but sometimes more importantly, what you are not going to do.

Without a strategy in place, organizations waste valuable time and resources grasping at straws and get sucked into diversions that often undermine the original goal. I once worked with an organization that had seven major initiatives on a limited budget. During a strategic planning session, we examined each initiative and asked ourselves, does this fit in with the stated goal? As it turned out, very few of them did. The lack of a strategy cost this organization many hundreds of thousands (perhaps millions?) of dollars and several person-years of wasted work.

Product managers play the pivotal role of bridging strategy with execution. Without a clear understanding of both the goal and the strategy for accomplishing that goal, a product manager cannot move a product or a company forward.

If you are a product manager, ask yourself: Do you know what the goal is? Do you know what the strategy is for achieving that goal? If the answers to these questions are "no", then stop reading this blog, get up, and go find out now. Ask your boss. Ask your CEO or Executive Director. Ask your Board of Directors.

It's entirely possible (although frightening) that perhaps even they don't know the answer to those questions. If so, then you've got to stress the importance of having a strategy. Perhaps you are the person to help lead that discussion.

With a clear understanding of your goal and strategy, a product manager is effectively the "Product President". Without this understanding, you are merely the "Product Janitor".

Comments

Popular posts from this blog

Social CRM: Putting Customers First

Last night I attended Social CRM: Putting Customers First , hosted by the San Francisco chapter of the Social Media Club .  It was a great event, and I'll briefly recap some of the discussion and my observations. The panelists were first asked why Social CRM (SCRM) was relevant.  Their answers were as follows: Vendors need to know who their customers are out there on the social web. Vendors need to be able to identify customer pain points from conversations on the social web.  Vendors need to know what to do with these conversations on the social web.  These discussions are the center of business today; their importance cannot be understated. The social web grows too fast for vendor solutions to keep up.  Therefore, vendor solutions must embrace the social web, and learn how to crowdsource.  There is no way that you can scale communities and community managers that fast. Customers don't care about your organization structure, they just want answers a...

Product Parenthood

It has been a long time since I've been able to sit down and write a lucid blog post.  This one will not be one of them. I've come to realize that my full-time job as a Product Manager, my other full-time job as a husband, and my newest (and most demanding) full-time job as a parent (to a delightful son) consume roughly 100% of my time; leaving precious few moments in the day in which to gather and synthesize my thoughts.  Thus, I've been using Twitter more often and blogging less. " Blogging less?  What?  You only have 3 prior entries! " I used to blog quite a bit under a different moniker.  However, as a parent, I have come to the realization that composing longer, thoughtful essays are a luxury that I generally cannot afford. With that, I've added my Twitter feed to the left, and will make an effort to write "larger-than-micro" blogs here on at least a weekly basis, if not more frequently. And now it's back to full-time job #1, follo...

Improving Win Rates

Still here at the Gartner Local Briefing. In a session with Richard Fouts about customer win rates. Sharing Win/Loss Data Sales teams tend to advertise their wins, yet contain their losses. Why is this so? Q:  How many global IT companies conduct win/loss on an enterprise scale? Less than 5%? About 10%? About 20%? A: Less than 5% Why? CEOs and Sales people say "I know why we win/lose".  Some politics are touchy; people don't want you to expose what they did well/not (especially in competitive environments).  "I clicked the won/loss checkbox in Salesforce.com" One company evaluated their win/loss data. They looked at 140 wins, and 55 losses. Looking at this data, they noticed a correlation between the wins and the fact that they beat their competition to market with compelling announcements in over a third of the scenarios. An IT services firm attempted to sell a more sophisticated solution. Upon evaluation of the win/loss data, they fo...