Got asked about prioritizing features in a pm interview. I described a framework where I measure features against engineering complexity, user experience and impact on biz. But it’s hard to forecast the biz impact or estimate it always. What is a good way to answer prioritization of features question?
Do it based on how you really prioritize. All frameworks go out the door when a CEO wants a feature. Write down how you’ve really prioritized in the last 6 months, which features proved most valuable for you to prioritize and how you chose them. Make this answer your own. No point spilling out frameworks you don’t use. Hiring managers can see through that pretty easily.
Money baby! Features ain't worth shit if they don't bring home the bacon! Embrace the tap dance between the silly things that engineering wants to do and the things that actually make the money.
How did u become a pm without knowing this? Two things remember when prioritizing features 1) what customer wants 2) estimate how much the feature deliver.
Generally agree w this, with caveat - can’t always just ship what customers want. Has to also align with future of your business. Customers ask for a ton of crap sometimes.
Think about overall mission and objective. There are cool features, sometimes features users want, even easier to build, but you should stay focused on the ones that advance the mission and objective you see for your product and company in the future. Your framework adds context, but could also mean you end up shipping the least important features to drive your product forward simply bc they’re easier to build or have some short term business impact.
A few generic things to consider while prioritizing the features 1. Customer impact 2. Revenue impact 3. Product/feature strategic alignment 4. Dev capacity Again, always case to case
Prioritization comes down to 1. Customer benefit 2. Revenue($$) 3. Effort
Serious answers please.
So many wiseasses