Ever had to make a tough call that wasn’t popular? Learn how seasoned product leaders handle difficult prioritization decisions that are necessary but not always well-received.
In product management, making tough prioritization decisions is part of the job. These decisions often involve trade-offs that might not be popular but are essential for the product’s long-term success.
Here are some controversial techniques that I have found effective on the job:
1. Kill Your Darlings
What: Identify and eliminate beloved features or projects that no longer add value.
Why: Nostalgia and attachment can cloud judgment, wasting resources on outdated features.
How: Conduct a brutal audit of your product. Use metrics to identify underperforming areas, regardless of their past success. Communicate the decision transparently to stakeholders, emphasizing the need to allocate resources efficiently.
When: Perform this audit annually or when there is a significant shift in business strategy.
Example: Do you have a legacy feature that is a favorite among long-term users but has little use? Cut it. This frees up resources for innovative features, increasing new user engagement.
2. Introduce ‘No’ Weeks
What: Dedicate specific weeks where no new features or tasks are added to the pipeline.
Why: Constant additions can overwhelm the team and dilute the focus.
How: Schedule ‘No’ weeks quarterly. During these weeks, the team focuses solely on completing existing tasks and addressing technical debt. Communicate the purpose and benefits of this approach to the team and stakeholders.
When: Implement ‘No’ weeks during high stress or after major releases to consolidate gains and prevent burnout.
Example: After a major product launch, introduce a ‘No’ week where the team cannot start any new tasks. This allows them to focus on stabilizing the product and addressing technical debt. The result is a more stable product and a refreshed, less stressed team ready for the next sprint.
3. Radical Transparency
What: Make all prioritization decisions and their rationales public within the organization.
Why: Secrecy breeds mistrust and misunderstanding, while transparency fosters trust and alignment.
How: Use internal blogs, newsletters, or all-hands meetings to communicate the reasoning behind each prioritization decision. Encourage open discussion and feedback.
When: Implement radical transparency whenever a significant prioritization decision is made.
Example: If faced with a critical decision to delay a feature due to unforeseen technical challenges, openly share the technical reasons and potential risks while gaining the entire organization’s broader understanding and support. This transparency turns potential dissent into collaborative problem-solving.
Have you used these or any other strategies? Would love to learn about them.
#Leadership #Prioritization #Productivity #ProductManagement #ToughDecisions