I’m getting ready for senior PM interviews and need help showing strategic thinking in my product examples.
I have this story about removing an old feature that wasn’t working well:
- Usage data showed only a tiny percentage of users actually used this feature, and most were low-value accounts.
- The few important customers who did use it weren’t getting much value from it.
- User research backed this up - people said they only checked it occasionally but didn’t use it for important decisions.
- Removing it wouldn’t hurt our customer retention.
- The maintenance costs were way higher than any benefits.
- The whole problem area had changed over time, so I made a plan for how we might tackle it differently later.
My main question is: how do I tell stories like this to show strategic product leadership instead of just basic execution skills?
Should I focus on:
- How removing this feature let the team work on more important projects?
- The missed opportunities we avoided by not wasting time on outdated features?
- How this decision connected to our bigger product roadmap?
What do senior hiring managers really want to hear to see that someone thinks strategically about these choices?
your story sounds like cost-cutting, not strategy. interviewers want the “so what” - did cutting this feature free up budget for something that actually mattered? did you pivot the whole product category based on what you learned? skip the obvious stuff (low usage = bad feature, duh) and focus on how this fit your long-term vision. what did you learn about users that changed your future bets? the maintenance cost angle is basic - show them you were thinking three moves ahead.
The key difference between strategy and execution here is showing your decision-making process, not just the end result. Don’t frame this as a simple data-driven removal. Instead, highlight the frameworks you used and the bigger picture you considered. Talk about the strategic questions you asked yourself: Does this feature still fit our market position? What message does removing it send to stakeholders? Should we worry about how competitors might react to our timing? For L6 interviews, the most important part is proving you think beyond the immediate decision. Explain how you weighed short-term resource savings against potentially regretting it later. Show how you set things up so you could reverse course or adjust if the market shifted. Hiring managers want proof you can handle uncertainty and think through ripple effects. Structure your story around how you make decisions, not what you decided. That shows them your strategic thinking will work for whatever new problems they’re facing.
honestly the key thing missing from ur story is the why behind the why. yeah removing dead features is good but what was the bigger business context? maybe focus on how this decision freed up eng bandwidth for a critical initiative that moved key metrics. also think about competitive positioning - was this feature making you look dated compared to competitors? strategic pms connect tactical decisions to company vision and market dynamics, not just internal efficiency stuff
You’re burying the lede! The real story isn’t what you removed - it’s the vision behind solving that problem differently. Start with “I saw our [problem area] approach was fundamentally broken, so I killed the feature and built a new strategy that…” L6 thinking means tying this to market trends or competitive moves. Did axing that clunky feature let you pivot where the industry was going? That forward-thinking angle separates senior PMs from junior ones who just tweak existing features.