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...

Building Better Products Using Quantitative & Qualitative Data

Disclosure: This was an internal post I wrote and shared with my colleagues back in 2015. While cleaning out my Confluence space, I came across it and thought that I'd share it with everyone. There is a much more recent and polished post by my good friend Glenn Block on Mind the Product that you can read here:  https://www.mindtheproduct.com/2018/01/need-quantitative-qualitative-data/ What Data Is/Not Data cannot  compensate for bad design or replace good design, but it can inform designers. Data cannot compensate for listening to actual users, but it can inform the kind of user research we conduct. Data cannot tell us what to build, but it can inform what we should investigate. Example If you can visualize a funnel report where visitors are leaving a buying process during various stages of the journey, quantitative data can give you information about where you may have a problem. In the above example, the quantitative data ( QT ) informs you that 36 pe...

Luck Is Not The Answer

As the 2011 season of the National Football League approaches, so does the rabid anticipation of its parasitic counterpart; fantasy football. Anyone who knows me knows that I love football (not fĂștbol); particularly the NFL . I grew up a dedicated Patriots fan and have since become more of a fan of the game itself rather than just a New England loyalist. I tend to keep up with NFL news throughout the year, and regularly download the Rich Eisen Podcast for listening during my morning commute. Rich's guest on the most recent episode was Michael Fabiano, the resident fantasy football expert at NFL.com. At one point during the podcast, Rich and Mike were exchanging viewpoints on what constitutes being an expert and how no matter how much of an expert you are, you need to be lucky to win a fantasy league. A similar sentiment was expressed during a 2010 podcast by one of the guests (I forget whom); that it's all luck and you can't really predict anything. I take exception t...