Our product is undergoing a massive change in direction. I have 50 feature requests and only 3 developers. What analytical scoring models do you recommend to ensure we are building the "Right" things to support this change without wasting resources on legacy baggage?
3 answers
The most logical framework for this is the RICE scoring model (Reach, Impact, Confidence, and Effort). For a major pivot, you should heavily weight "Impact" toward how much the feature supports the new direction versus the old one. Calculate a score: (Reach x Impact x Confidence) / Effort. This gives you an analytical rank that removes emotional attachment to "legacy" features that the founders might still love. Additionally, use a "Kano Model" analysis to categorize features into 'Must-be,' 'Performance,' and 'Delighters.' If your pivot lacks the 'Must-be' features for the new target audience, no amount of 'Delighters' will save the software from failing.
When calculating the "Effort" score, how do you handle the analytical uncertainty of "Unknown Unknowns" in a codebase that wasn't designed for this new direction?
We use "Cost of Delay Divided by Duration" (CD3). It’s the most mathematically sound way to maximize the value delivered over time during a high-stakes transition.
CD3 is excellent for pivots, Elizabeth. It prioritizes the "Quick Wins" that provide the most immediate feedback, which is exactly what a team needs when navigating a major change.
William, that’s where the "Confidence" score in RICE is vital. If the dev team is unsure about the technical debt impact, the Confidence score should be low (e.g., 50%). This mathematically penalizes the feature, pushing it down the list until more research (a "Spike") is done. It’s an analytical way to prevent "Hope-based Planning" from ruining your pivot’s timeline.