How to conduct feature prioritization audit without alienating important stakeholders

by•

Refusing to fulfill internal feature requests made by sales and engineering departments results in a lot of compromising meetings and too crowded product roadmaps. Last month during our quarter planning meeting each department tried to convince that theirs pet project should be prioritized.

We solved this problem using a strict customer-impact score matrix based on real ticket tag data and churn feedbacks. Each of the feature requests needed to demonstrate that it lowers churn or fixes at least thirty customer tickets to get a spot on our next sprint.

Cleaning up low-impact roadmap features gave us three weeks of extra engineering time to work on product stability. Important decisions are always appreciated better when they are data-based.

Never approve any new feature request without reaching certain threshold of support tickets.

Prioritize your product backlog based on customer retention impact only.

Data-based prioritization is the only way to keep your product aligned with user needs. What is your strategy for choosing which feature requests should be eliminated from the roadmap?

2 views

Add a comment

Replies

Be the first to reply

Have a question or a thought to share? Add a comment above to start the conversation.