Embedded Files
Confidentiality Note: To comply with non-disclosure agreements and government classification standards, certain project details have been generalized or abstracted to ensure security and protection of sensitive information.
The Situation
The Situation
Midway through a development cycle, engagement metrics were not reaching expected targets. The team was working hard, but the data told a different story. Users were interacting with a fraction of what we had built. We were at risk of finishing a product that served our roadmap more than it served our users.
What I Did
What I Did
I ran a product analytics deep dive using our engagement dashboard and discovered a stark pattern: 80% of active user value was concentrated in just 20% of our features. Four of our six primary navigation tabs had near-zero engagement.
I applied the RICE framework (Reach, Impact, Confidence, Effort) to score every item in the backlog, then organized a leadership session to present the findings. Rather than burying the conclusion in data, I built a clear 'Perish List' — features I was recommending we formally kill — and walked leadership through the logic. The data removed the emotion from what would otherwise have been a contentious conversation about work the team had already invested in.
The Outcome
The Outcome
+25%
Core feature engagement
30 days
Delivered ahead of schedule
4 of 6
Low-use features cut
Page updated
Google Sites
Report abuse