Resources > Articles

Ask the Experts: How Do You Manage the Tension Between Strategy and Execution in Product Management?

Author
  • Paul Young

    Paul Young oversees the strategic development of Pragmatic Institute’s portfolio of products and leads the executive team in the evaluation of new product opportunities. He also manages the instructor team. Paul began his career as a software developer and has worked in startups and large companies across B2B and B2C industries, including telecommunications and networking, IT and professional services, consumer electronics and enterprise software. He has managed P&L lines for products with hundreds of millions in revenue, and faced difficult choices about which products in the portfolio to retain and which to kill. Reach him at [email protected].

Ask the Experts: How Do You Manage the Tension Between Strategy and Execution in Product Management?

Balancing strategic and tactical work is one of the hardest challenges for a product team. Execution-focused activities are extremely noisy, generating a lot of day-to-day phone calls, emails, meetings and hot escalations to other line-of-business executives. You and your product team feel a pressure to respond to the noise, lest you be perceived as unresponsive by your peers. We’ve all been there.

But it’s really a lose-lose situation. If you always respond to day-to-day firefighting, the longer-term strategic work gets put off indefinitely, eventually forgotten as the team loses that muscle memory and turns into professional firefighters. But the truly insidious thing about responding to the fires is that the team starts to turn away from the market (no time to do outside-in research when you’re so busy being inside-out) and make decisions based on little or no market data. This will result in poor product decisions and lead to failure.

You must strike a balance. And although there is no perfect balance, the following techniques will help you get started.

Gap Analysis and Prioritization

Perform a gap analysis using the activities listed in the Pragmatic Institute Framework to determine where the team spends time today, compared to which activities are truly most important. Once you visualize the gaps, you and your team can see where you are allocating too many resources and where you aren’t allocating enough. Then you can use this information to prioritize and focus your work.

Role Definition

One way to take on the issue of firefighting is to redefine the roles on your product team. Make sure you have someone dedicated to focusing outside-in, scheduling NIHITO visits, setting product and portfolio strategy, business planning and pricing. Next, dedicate other people to focus on go-to-market activities, enabling the sales and marketing channels to understand the buyer and develop the tools and training to make the product fly off the shelf. It doesn’t matter as much who does what, as long as it’s clearly defined.

Negotiate with Other Departments

If firefighting takes up a lot of your team’s time, perhaps there’s a resourcing gap in another department. For example, if sales doesn’t have enough help in technical sales support, they may lean on the product team. If technical support lacks resourcing, the product team may become the de facto tier 3 escalation. When the product team fills these gaps for other groups, the rest of the business is rarely aware that a gap exists because the gap has been papered over.

To find a solution, host an executive-level conversation about the appropriate role of product management and the other teams. If the executives recognize the true role of the product team, and they recognize the work that their teams should be able to take on, you can negotiate where to put the right resources to fill the gap. Alternately, they may approve an additional resource with which you can fill the gap.

Testing these techniques will help you find the balance between strategy and execution that works best for your team.

Author
  • Paul Young

    Paul Young oversees the strategic development of Pragmatic Institute’s portfolio of products and leads the executive team in the evaluation of new product opportunities. He also manages the instructor team. Paul began his career as a software developer and has worked in startups and large companies across B2B and B2C industries, including telecommunications and networking, IT and professional services, consumer electronics and enterprise software. He has managed P&L lines for products with hundreds of millions in revenue, and faced difficult choices about which products in the portfolio to retain and which to kill. Reach him at [email protected].

Author:

Other Resources in this Series

Most Recent

Article

Four Methodologies for Prioritizing Roadmaps 

In this blog, we'll explore four common approaches to roadmap prioritization and discover the practical tools and frameworks that can propel your product to new heights.
Prism photo: Product management Lessons from Pink Floyd
Article

Product Management Lessons from Pink Floyd: a Lighthearted Look into Their Epic Music and Unlikely Product Expertise

Few people (actually, no one!) spontaneously associate product management with Pink Floyd, but if you look closely, you can find good examples of best product management practices in their journey, as I hope to reveal...
Creating a product roadmap: what should you include
Article

A Guide to Product Roadmaps: How to Build One That Works

A product roadmap is a frequent request from the sales force and others in the company. ‘What’s coming in the next release and the ones after that?’ Long buying cycles common with strategic products often...
Dry erase board with product roadmap drawn on it
Article

How to Build a Brilliant Visual Product Roadmap

Building roadmaps is a crucial part of a product manager’s job. Yet most product managers still use outdated tools for roadmapping—Excel, PowerPoint, wikis, etc. The good news is that there’s a better way. Executives have...
Product Datasheet
Article

How to Write a Kick-Butt Product Datasheet

If your datasheet passes the all-important skimming test, it's more likely that buyers will read it in detail. Here are 10 tips to help you write a datasheet that buyers actually read.

OTHER ArticleS

Article

Four Methodologies for Prioritizing Roadmaps 

In this blog, we'll explore four common approaches to roadmap prioritization and discover the practical tools and frameworks that can propel your product to new heights.
Prism photo: Product management Lessons from Pink Floyd
Article

Product Management Lessons from Pink Floyd: a Lighthearted Look into Their Epic Music and Unlikely Product Expertise

Few people (actually, no one!) spontaneously associate product management with Pink Floyd, but if you look closely, you can find good examples of best product management practices in their journey, as I hope to reveal...

Sign up to stay up to date on the latest industry best practices.

Sign up to received invites to upcoming webinars, updates on our recent podcast episodes and the latest on industry best practices.

Training on Your Schedule

Fill out the form today and our sales team will help you schedule your private Pragmatic training today.

Subscribe

Subscribe