How to justify resume points where you have not created any impact as a PM? You had no choice but to just build these features

Well, hopefully you've created some kind of impact. It may be that it's not obvious what that impact was, but hopefully the company, the product, and the market has done something in your tenure at this organization. Even if you've just executed off of a specific task list of features, hopefully some of them added some value to your community, to your users, and to the outcome of the business. And in that case, I'd highlight what happened to the product while you were there. Did you grow? Did yo ...Read More

Okay, you are not happy with your recent track record - good opportunity to flex your analysis, story telling and “marketer” muscle. Goals. These features didn’t seem to support your goal - but they likely supported someone else’s (even if you were unhappy about it)? Demonstrate how you supported supported those goals or how you thought outside of the scope of your immediate team, to support some fellow team. Learning. Did these features fail, though you knew this from the start? Focus your stor ...Read More

Impact as a PM extends beyond direct revenue or cost savings. Consider these aspects when justifying resume points: User growth or retention: Did the feature help sustain or expand your user base? Engagement: How did the feature affect user interaction with the product? Product value: Did it add foundational elements crucial for long-term success? Competitive parity: Was it necessary to keep pace with market standards? Future potential: Did it lay groundwork for upcoming strategic initiatives? F ...Read More

I'd always encourage you to think through impact and understand it before building a feature. Ask whoever is pushing you to build, ask your peers, validate with customers -- do whatever you can to understand and describe the problem your feature is solving for and how you'd measure impact. That said, especially earlier in your career, if you do have features that you think drive no impact, a couple of thoughts to help you think through - Uplevel your thinking to that of your boss or whoever gave ...Read More

I believe that even in situations where you "had to build the features" you can still show impact. Impact is not just about more users, more dollars for the business - impact can be about learning. If you have to ship features, use the time after you delivered them to learn and to bring that learning back to the organisation to impact the future roadmap. For example - you shipped feature x because you had to but you can still show whether feature x was impactful or not and why it was impactful o ...Read More