Hi everyone, I know probably most days are differe...
# product-management
e
Hi everyone, I know probably most days are different, but how would you describe your day to day life of as a platform product manager?
s
Great question and indeed there is no day that looks the same. Let me try to answer... in my ideal scenario my day would look like this: 1. Product discovery ( reading articles, researching on features and new releases for my IDP) 2. Couple of check-in with the engineering teams 3. Talking to customers to gather feedback and requirements 4. testing the features that the team is building
g
I would also add 1. monitoring support emails and other channels - looking for problems worth solving, very often it is poor documentation 2. creating backlog to capture work for team 3. deepening domain knowledge - IDP, CI, CD, learning about users (engineers) through various publicly available reports on aspect that is an area of exploration like for example time spent on development 4. data analysis from various metrics tools ie. Google Analytics Below are less daily more occasionally but still quite frequent 1. presenting and selling products to an internal audience 2. presenting project progress and research results to various audiences 3. teaching engineers about product management practices: vision, strategy, discovery, product risks, customer interviews/validations etc
u
When you look at the source of the features that you are building or have just delivered, where do they come from? What % are direct requests from your Developers( users of platform)? What % are directions from your engineering leadership?
Also what framework do you use to prioritize all the requests in your backlog? I think the standard framework used in consumer facing products wouldn’t work for platform. Right? I am wondering your backlog would include requests like: • feature requests from developers • Feature requests from security • Feature requests from FinOps • Technical improvement from within platform engineering teams • component upgrades to ensure all components are on supported and secure versions. • Leadership requests
e
Honestly, it's meant to be a merging of direction of the business and customer needs right? You collect customer needs and prioritize based on the needs of the business. I use a framework to estimate these things as engineering hours or approx $ figures to give people an understanding of how much impact work has, and what we're trying to prioritize it's much easier thinking about it that way
I also wouldn't say I have a set schedule, it depends on the company's needs on what my schedule looks like. I have periods of intense customer outreach, periods of mostly talking to upper management and periods where I'm mostly focused internally, but I have a lot of teams to manage.
ATM it's solidifying the 2025 roadmap, resourcing and getting buy in from upper management, and there's a bit of misalignment within some of the teams which needs to be resolved.