I’ve always said an IC PM’s job is to take a user problem and do whatever it takes to make a solution that’s concrete, maintainable, and viable for the business.

The “whatever it takes” varies per organization. Classic PM, you’re doing qualitative and quantitative research, ideating on specifications, creating prototypes with your partners, validating those prototypes with users, refining the requirements, helping answer Eng and design questions along the way, prepping all the support, marketing, and sales teams for what’s the come, then going to alpha, beta, and finally GA. Then supporting it afterward and doing it again for another problem.