When Product Managers Get Trapped…

How many of us product managers have been in this situation — trapped in an organization, an organization that does not understand the essence of product management.

An organization where:Trap

  • Product managers are responsible for clerical tasks and book keeping
  • Product managers are required to project manage
  • Product managers are made the scapegoats for engineering failures
  • Product managers are required to double up as functional managers to cover up for poor engineering managers

A few of us would certainly have some experiences to share.

If at all, we end up in such a trap, here are some tips (read as arsenal!) that could be used in times of need, so that organizations/leadership-folks understand the need for product management for product and overall business success.

  1. Data – make use of data and unearth insights about product usage patterns
    • This will make the leadership team feel the need to improve product design
  2. Competitive Landscape – research into your competitors’ products and identify gaps in your offering
    • This will surprise the leadership team
  3. Market Trends – research your target market segment and identify unmet needs
    • This will enable trust with the leadership team
  4. Feature Prioritization — effectively prioritize your features using a good tool
    • This will delight the leadership team
  5. Portfolio Analysis – do an analysis of your company’s product portfolio and let leadership know about products that need investment vs. the ones that need to be killed
    • This will give sleepless nights to the leadership team, for good:-)
  6. Product-Market Fit – constantly pursue the leadership team to understand achieving product-market fit sooner than later, because faster product-market fit will ensure the product will enjoy maximum differentiation for a longer period of time

Hope you liked the post. Would love to hear your insights too!


Feature Prioritization *New*

Back in 2011, I made this blog post on prioritization of product features, and the prioritization template looked like this.

Over the years, I have been updating the format and refining it to ensure it articulates the objective prioritization and shepherds the product towards product-market fit — the latest is here.

In general, features will have to be categorized into three backlogs. The backlogs have been named by lifting NBA terminology for self explanation.

  • Offensive Play — features that aid revenue generation and acquire new customers
  • Defensive Play — features that aid in delighting and retaining existing customers
  • Time out — features that aid cost cutting such as those that reduce product returns, reduce customer service costs, improve operational efficiency, tech deprioritizationbt, etc.

Product Managers will have to ensure appropriate ‘plays’ are adopted depending on business needs, including a mix of features from more than one backlog in a release, for creating customer value, generating competitive advantage, and delivering profitability.

Few takeaways:

  • Strike the right balance between offensive and defensive plays
  • Features that can be implemented in a shorter time are *not* always the ‘right thing’ to do
  • Always look at relative priority and the objective impact a feature will have on customer value, ROI, and overall purpose

Would love to hear what’s on your mind!