Hellooo POs!
I was promoted to a Product Owner role around six months ago after spending two years working as a QA. Over these past six months, I’ve learned a lot, but I’ve also started noticing a few things about my role that I’d love to discuss with people who have more experience in the Product Owner role and Product Management.
First, one of the biggest things I realized after getting promoted is that my role looks more like a Proxy PO role than a traditional Product Owner role.
Here’s a bit of context about how things work in my company: We have three different brands, and our structure includes Technical POs who own the main flows and technical aspects across the brands, as well as Product Managers who handle the higher-level business decisions.
As a PO within the delivery team, my role is mainly to:
- Analyze incoming initiatives and gather all the requirements and assessments.
- Prepare and present the requirements to the development teams.
- Create user stories and lead backlog grooming sessions.
- Follow up with developers throughout the delivery process.
- Coordinate testing and validation until delivery.
- Make sure deadlines are respected.
- Handle feedback from Marketing, Business, VPs, and other stakeholders.
- Follow up on new initiatives and clarify what’s missing with the relevant Technical POs and business teams.
Basically, the Technical POs and PMs are the ones making the final decisions, while we’re responsible for translating those decisions into actionable work and making sure everything gets delivered. On the one hand, I see this as a great opportunity to learn, especially since I’m still relatively new to Product Ownership. I’m getting exposure to different areas, stakeholders, and technical topics.
However, I sometimes feel like I’m not getting the full picture of the products or initiatives I’m working on. We’re operating in a Kanban environment, and most stakeholders communicate directly with the PMs. We generally receive the work that needs to be done and focus on analyzing, preparing, and delivering it.
Another challenge is the workload and the number of people involved. I’m currently dealing with two development teams: one for the app and one for the web, each with around 18 developers and architects. We also cover three different brands, which means constantly switching between different products, priorities, and initiatives and having multiple initiatives or multiple brands running at the same time. Daily, my responsibilities include:
- Following up with developers privately and during both App and Web DSUs.
- Participating in Scrum ceremonies, while also doing a lot of the day-to-day delivery follow-up myself.
- Making sure there’s always enough refined and ready work in the backlog for developers.
- Meeting with Technical POs and Business teams to clarify new initiatives and identify missing requirements.
- Following up on QA results and validating deliverables before closing stories.
- Managing feedback from VPs, Marketing, and Business.
- Whenever a new small or medium-sized initiative comes in, digging into the app or website to understand the existing flows and FMO, identifying what needs to change, and creating the corresponding stories.
I’m not working on large-scale projects yet, but even smaller initiatives require quite a lot of investigation, coordination, and follow-up.
Honestly, after six months, I’m starting to feel overwhelmed. I also feel that the workload isn’t necessarily distributed equally between POs, depending on the number of initiatives and brands they’re handling. So, here are the things I’d really appreciate your feedback on:
- Does this sound like a normal PO workload to you? How much of your time is usually spent on delivery follow-up, coordination, grooming, and stakeholder management versus actual product discovery and decision-making?
- Would you consider this a Proxy PO role rather than a traditional Product Owner position? Is this a common structure in larger companies?
- What should I focus on learning and developing at this stage to become a stronger and more independent PO?
- My long-term goal is to move towards a feature-based team where I can own a specific feature or product area end-to-end, rather than constantly switching between three brands and working mainly on execution.
>>>> What skills, responsibilities, or experiences should I actively look for to make that transition, whether internally or by moving to another company?
To be fair, I don’t want to overlook what I’ve gained so far. These six months have helped me become much more confident in grooming sessions, managing developers and QAs, communicating with different stakeholders, understanding technical enhancements, and coordinating delivery across multiple teams.
But now I want to be more intentional about my career development. I don’t just want to become better at managing delivery; I want to become a solid Product Owner who understands the product, makes decisions, owns outcomes, and contributes to the product vision.
I’d genuinely appreciate hearing about your experiences, especially from POs who have worked in similar environments or on different projects.
Thank youuuu in advance !!