r/ProductOwner • • Jan 27 '26

General question Am I the only PM recording *every* conversation now?

73 Upvotes

I've been recording all my meetings for the last few months - customer calls, stakeholder syncs, 1:1s with my manager - and feeding the transcriptions into a Claude project.
It's become a weird superpower.

When marketing needs customer quotes for a one-pager, I don't dig through notes. I prompt: "Find buying signals from conversations with Acme Corp tagged #customer." Its great for context engineering and the results have transformed my day to day work. It's like having a second memory. Months of context, instantly searchable, and an AI that actually knows my specific customers and stakeholders - not generic advice.

Curious if anyone else is doing this or if I've gone off the nerdy deep end or if this is something people are doing a lot. And if its the latter, any advice on what techniques you are using!


r/ProductOwner • • Feb 03 '26

Help with a work thing My boss thinks AI made us faster. Actually it just exposed that he has no idea what Product does

61 Upvotes

My boss (who's our CEO and a sales guy) won't shut up about "velocity." And here's the annoying part: engineering is actually moving fast now with things like Cursor, Claude Code, etc. They can ship entire features with a prompt and a quick review cycle.

So guess who looks slow? Me.

I'm the one turning messy customer calls, scattered Slack threads, edge cases, and vague asks into actual buildable tickets that won't blow up in prod. But while engineers are cranking output, I'm spending hours doing translation work, alignment, and ticket-writing. and my boss is getting frustrated that engineers are "waiting on product."

I'm using tools like Telos to auto-draft tickets now, which helps. But even with that, it feels like product work has become the harder job when engineering is increasingly "one prompt away."

Anyone else feeling this shift? What actually helped you scale: ruthless scope cuts, pushing back on alignment theater, hiring a BA, or something else?


r/ProductOwner • • Jul 17 '26

Fun Most POs I’ve worked with aren’t Product Owners. They’re backlog administrators. Change my mind.

58 Upvotes

10+ years in logistics IT, currently leading product teams. Hot take that’s been building for a while:

The Product Owner role has quietly degraded into a ticket secretary job, and almost nobody talks about it.

The pattern I keep seeing: PO spends 80%+ of the week inside Jira. Writing stories nobody asked for, for users they’ve never met. Refinements, plannings, more refinements. Then they wonder why the team ships features that technically match the acceptance criteria and still solve nothing.

I work in transport/logistics IT. The single most valuable thing I do as a PO is standing at a loading dock at 5am watching people actually use (or work around) our software. Two hours there beats two weeks of stakeholder meetings. Every time. Features that looked perfect in the backlog died within minutes of watching a forklift driver try to use them.

My rule of thumb: the role should be 80% outside – with customers, in operations, feeling the pulse – and 20% inside doing the necessary admin. Most orgs have it exactly inverted, and then they blame “agile not working”.

Am I off here? Genuinely curious whether this is a industry thing or whether the “backlog administrator PO” is the norm everywhere?!


r/ProductOwner • • Jul 29 '24

Fun Anyone use this backlog method? :)

Post image
37 Upvotes

r/ProductOwner • • Jun 02 '25

Fun How to know if you're 1000% a perfect fit for being a Product Owner

33 Upvotes

This made me chuckle.


r/ProductOwner • • May 08 '26

Career advice Always bored as a PO

29 Upvotes

I've been a Product Owner for 8 years now across 3 different jobs/companies/sectors. After the initial rush of "what the heck am I doing?" at a new job, I quickly figure things out and get BORED. Big time bored! I can't figure out whether I'm only doing half my job or I'm super smart. PO roles are just a formula to apply to a product in my eyes. And the wait times are driving me up the wall. I like delivering, quick decisions, producing, seeing quick wins. I keep applying for senior positions but I don't know if that will make a difference because it will be even less hands-on. Is anyone else bored as a PO? Everyone else is saying how much they have on their plate but I don't think my time was ever maxed out! It's actually NOT a nice position to be in. Trust me. Thanks!


r/ProductOwner • • Jul 25 '24

General question Admins - Do better !

28 Upvotes

This is supposed to be a community for Product people, not a marketplace to get sold the next miracle tech that will save us time and effort.

Rule number 1 is literally no spam, but 80% of the posts currently seem to meet this criteria.


r/ProductOwner • • Jun 06 '26

Career advice Vent about Claude Code and the AI boom

24 Upvotes

I work as a PM at a Brazilian tech company.

I have a pretty technical background for a PM. I can read documentation, write detailed specs, test APIs, read logs, and have meaningful conversations with engineers. I also program in Java. I don't use it in my day-to-day work anymore, but it helps me understand what the engineering team is talking about.

I took over a project about 6 months ago that was completely fucked. Bad architecture, no request queues, terrible code quality, almost no infrastructure standards, and we didn't even have database backups.

Since then, I've been trying to put everything in order. We've been creating new microservices, moving toward an event-driven architecture, implementing observability tools, fixing infrastructure issues, and paying down years of technical debt. As a result, support tickets have dropped significantly.

I haven't been able to deliver as many new features as I would like, but little by little we're finally getting features out while building something that won't collapse later.

We're a very lean team. It's me as the PM (with nobody above me except the CEO) and 3 senior full-stack developers.

My frustration is that with the AI boom, my CEO constantly pressures me about feature delivery. I explain that there are major architectural issues that need to be addressed, but every Monday the conversation is basically: "Was everything planned for last week delivered?" and "What will be delivered this week?"

I've basically become the guy who spends his time micromanaging developers and pushing for more output.

My team is exhausted. I have a great relationship with them and I know exactly which technical debts need to be addressed. But my CEO doesn't understand anything about tech. His view is: "You need to deliver more. Your developers need to use AI. They're not working hard enough. I built a system in Lovable in one day."

At this point, I genuinely don't know what to do. I've been working in product for 6 years and I've never worked with a CEO this clueless.

What makes it worse is that he doesn't accept my perspective, even though I have technical knowledge, understand the system, and know that if we don't prioritize these things now, we're going to pay for it later.

Honestly, I've started slipping architecture tasks into the roadmap without explicitly calling them out, because if I tell him what they are, he'll block them and demand more feature delivery instead.

The AI boom has made a lot of people who know nothing about software think they suddenly understand software. Because they built a prototype with Claude Code, Cursor, Lovable, or whatever tool is trending this week, they think they can challenge engineering decisions and tell technical teams what's right.

I feel like the respect and influence I used to have as a PM doesn't exist anymore. I'm not a product manager anymore. I'm just a task messenger whose job is to pressure developers.

Has anyone else been dealing with this?


r/ProductOwner • • Apr 23 '24

MOD Announcement Lets get this r/ProductOwner sub revived!

23 Upvotes

New Mod, new approach.

Same topic - everything and anything about Product Ownership - that's useful!

This sub is now public so have at it!


r/ProductOwner • • Oct 13 '25

Career advice Burnt out of ambiguity and meetings

22 Upvotes

I'm a few years into my product owner career. I liked it at first, but I'm starting to get so burnt out of both the ambiguity of the job (not sure if that's the right word - I miss having a job where I have XYZ tasks to complete in a week), and the CONSTANT meetings, both scheduled and as needed. I just want to sit down and work 😮‍💨 anyone else feel the same, or better yet, have a suggestion on something I could pivot to?


r/ProductOwner • • Jan 19 '23

Career advice Software Developer to PO

22 Upvotes

I have been working as a software developer for last 4years and now I’m thinking about switching from software dev to Product Owner! Anyone who made the similar switch here ? What should I do at first to get started on it ? What approach is the best so that I can have knowledge about PO without any real world PO experience? How can I make use of my software dev skills to make this switch ?

I would really appreciate if anyone could guide me.

Hope you’ll have a great day/year ahead!

Thank you!


r/ProductOwner • • Jan 06 '26

General question what's on your evaluation list for the best product analytics tools in 2026?

21 Upvotes

Fellow product people, I'm leading our Q4 initiative to future-proof our product analytics stack for the next 2-3 years. As we all know, the tooling we choose directly impacts how well we can understand user behavior, prove value, and guide the roadmap.

Our current setup is a patchwork of a major platform (for core analytics) and several point solutions for session replay and experiment analysis. It's becoming costly and fragmented.

My key evaluation criteria for 2026 center on PM/PO empowerment (how self-serve is it for product teams vs. requiring constant data or engineering support?), strategic insight (moving beyond "what" happened to actionable "why" and "what next" insights), and integration & cost (clean fit with Jira/Linear, Figma, and our data warehouse without insane per-seat or event-volume pricing).

I have Amplitude, Mixpanel, Pendo, and Heap on the standard list. I'm also curious about newer entrants like PostHog, June, or niche tools that excel at specific PM workflows.

For those doing 2026 planning: which tool has most effectively reduced your dependency on data teams for ad-hoc queries? Are you leaning towards an all-in-one platform or a best-of-breed combo in this new budget cycle? Any tool that particularly shines at connecting user behavior to business outcomes for stakeholder reporting?

Looking for perspectives from other product leaders who are balancing depth of insight with operational practicality.


r/ProductOwner • • Jul 14 '25

Knowledgebase Is Product Owner a glorified server at a restaurant?

21 Upvotes

Hi all,

The more I think about it, the more it feels like that product owner is a glorified server at a restaurant.

Users come for food and the server asks what they would like to have, share about speciality, etc.

Then PO places the order with the chef & cooking team (devs)

Then once order is ready, PO delivers to the customer and collects feedback.

I think that's all there is apart from the domain specific knowledge that a PO has. What kind of customers come to the restaurant? How to quickly deliver the food? How to ensure cooking ensures with temp, dietary requirements are specific and well tailored for cooking staff to understand and deliver?

What are your thoughts?


r/ProductOwner • • Mar 03 '20

Help! What did you do in your first 30, 60 and 90 days as a Product Owner?

21 Upvotes

Hello,

I'm currently applying for my first role as a product owner. So I'm trying every trick in the book to standout from the crowd.

One idea I've read on a blog is to write some goals for your first 30, 60 and 90 days in the job and include them in cover letters.

The problem is most job posts are quite secretive about the exact product that they are recruiting a PO for so it's tricky to be able to say how you would directly affect the product itself. That said I was wondering if there were more generic things that you could recommend for me to include.

Below is the generic example given in the blog.

Thanks so much in advance for any help.

Pete

30 Days: In my first 30 days, I will focus on listening, learning and studying the company. By day 30, I should be proficient in the company's internal processes and systems, and getting familiar with the cultural elements that are relevant to my role. I also intent to invest time in getting to know my teammates and team leader, in order to establish trust and learn from their experience.

60 Days: By day 60 I intend to have mapped my internal and external stakeholders, gathering feedback and aligning expectations with each of them for the coming month. I would also like to have established clear milestones and goals, by studying the best practices in the industry, the company success history and the margin for innovation.

90 Days: By day 90 I expect to have accomplished x, y and z metrics of the role, at which point I will seek the feedback of the relevant stakeholders in order to evaluate the impact of existing processes, as well as innovative ones.


r/ProductOwner • • May 03 '26

Help with a work thing Claude code

20 Upvotes

My company is 100% on board with Claude code nd mandating that everyone is it for absolutely everything they can. The managers are all technical devs. They use it for code. I don’t code as part of my job (but I can). They expect me up to use Claude code a significant part of my day, but at the same time not take over QA or dev’s jobs.

My job is mostly talking to stakeholders holders and solving problems with features. I don’t see how Claude can do that? Am I wrong?

I also do all BA work, writing acceptance criteria nd wire framing. I know how to have Claude help with that.

Lastly, documentation and release notes. Would love to have Claude take over, but I can’t figure out how to have Cowork connect to azure devops to do them for me.

Any hints or help? How else are you using Claude for your daily work?


r/ProductOwner • • Feb 12 '26

Career advice PM Mock Interviews

20 Upvotes

Hi everyone,

I’m a Big Tech PM and have recently gone through multiple MAANG PM interview loops successfully. Have some availability to run a few product sense, analytical thinking, or behavioral mocks and provide direct feedback. This is not a paid coaching; just paying it forward.

Feel free to connect with me on LinkedIn or DM
https://www.linkedin.com/in/johnnymai-global/


r/ProductOwner • • Jan 12 '26

Career advice New boss doesn't believe in product owners because they are "bottlenecks

20 Upvotes

Any recommendations how to approach this are welcome!!

We are an internal team. One PO two dev teams.

We develop internal apps either simple processes / frontend or data analytics pipelines etc.

In the past, PO and tech lead were the only real contacts to the head of the department. And it was me, the PO, who was the main organizer of work. I discussed with the head and then executed together with the tech lead. I was the main contacts for all stakeholders (even technical ones). I saw myself as a technical PO since lots of clients are technical too and I was a crucial part of the solution design discussion.

New boss (who has a technical background) doesn't want to have "bottlenecks". He basically wants (and already started) to re-hire the dev team with very senior engineers. And then he wants to assign entire projects to 1-2 people teams. And they do everything end-to-end (from talking to stakeholders, researching specifications / requirements, development, maintenance etc).

He agrees that there should be some overarching "team" structure since projects might need to be handed over or maintained by other people. However, he doesn't give any instructions in using agile, scrum, sprints etc. We as a department should self organize. But there is no hierarchy anymore since also the tech lead got demoted. It's basically lots of senior people and opinions. And now we have to negotiate and agree.

I don't really know what to do anymore. Since he approachs devs directly I am losing information. Devs don't really listen to me anymore because they got tasks directly from our boss and thus they can decide on priority themselves.

I have become an assistant in plannings where I ask about the projects and create the minimum amount of tickets (most devs wouldn't create tickets for themselves). But this way I can have at least some tracking of the projects. So I feel ultimately useless.

I have no authority. Which I probably never really had, but I was the main organizer and had information monopoly. I tried to shield everyone from the project work or politics and only gave high level roadmap / vision, but a lot of details for the next 1-2 sprints.

I am a senior PO and also have such a salary. I really think I need to move or get fired soon.


r/ProductOwner • • Jun 19 '26

Knowledgebase Switched from spec-first to prototype-first as a Product Owner. ~6 months in — the good and the annoying

19 Upvotes

For years my flow was: write requirements → align with design in meetings → design → dev. Standard stuff.

The thing that finally broke it for me:
I once defended a 12-page spec, the whole team nodded along, and two weeks later we shipped something noticeably different from what I'd meant. Nobody was at fault. Everyone just read the same doc slightly differently.

So I flipped it. Now I build a rough clickable prototype first — usually a few prompts in Claude or Lovable — and design, discussion, and dev happen around that artifact instead of around a document. (not affiliated with either tool, they're just what I reach for.)

What actually improved:

  • The "wait, how is this supposed to work?" meetings basically disappeared. The answer is something people can click, not interpret.

  • Alignment is faster because we argue about a concrete thing, not an abstraction.

  • Stakeholders give better feedback when they can see it.

Where it bites :

  • Stakeholders mistake the prototype for the final product. "Why isn't this done, it works?" Managing that expectation is now part of the job.

  • It quietly skips edge cases, error states, and accessibility — the prototype looks 90% done while being 40% done.

  • Falls apart for backend-heavy / complex-logic features where there's nothing to "click."

  • The prototype can become throwaway debt if devs feel pressured to build on top of it instead of rebuilding properly.

Net for me it's still a big win, but it's a process change with real tradeoffs, not a magic fix.

Question for people already doing this: how do you stop a prototype from being read as a spec by stakeholders and engineers? That's the part I still haven't fully solved.


r/ProductOwner • • Jul 14 '25

Help with a work thing New POs & Career Transitions: What I Wish I Knew Day One

19 Upvotes

Calling all seasoned Product Owners! We see many new faces and career changers here (from Scrum Master, QA, Dev, etc.) often feeling a bit lost. If you could go back to your first day as a PO, or your transition into the role, what's ONE crucial piece of advice you'd give yourself? What foundational understanding or skill would have made the biggest difference? Your insights could really help someone find their footing!


r/ProductOwner • • Oct 01 '26

Career advice Please stop me from quitting

18 Upvotes

About to hit 5 years working as a Product Manager at an agency and feeling absolutely burnt out. Dropping everything for the clients, context switching, and just working for clients I cannot stand anymore.

My mental health has been deteriorating but I know if I quit now, the job market sounds horrendous. I’ve been applying since August - 56 applications (tailored resume for each posting) so I know I need more volume - had 2 rounds of interviews at a company but got passed on.

But all the posts I see on here and Linkedin about people who have been laid off and struggling to find a job for months to years is very scary.

I’m starting to work less and care less to help with the stress and honestly am hoping for them to fire me so that I can at least collect unemployment.

I’m also thinking of maybe just leaving Product in general. What are some adjacent roles to look into? I’ve applied to a few Program Manager roles.


r/ProductOwner • • Nov 16 '25

Help with a work thing User stories & others!!

18 Upvotes

How user stories are written ?

      1. Based on a functionality ? 
      2. Based on scenarios?
      3. When a functionality behaves differently in different conditions

Who writes user stories? PO or Dev or PO with the help of Dev ?

If PO authors it solely, how we can identify dev feasibility before the story goes into grooming? What ever PO thinks to be solutionised , it will be solutionised logically by dev ?

Should there be a feasibilty call with dev team before actual grooming ?

Btw , apols if these are stupid questions but more questions to follow......

Again i know ,in most organisations PO's core job is not writing user stories. But in my org , PO along with BA draft the stories interchangeably ...


r/ProductOwner • • Aug 05 '25

Career advice Is pivoting into a Product Owner role at 34 realistic?

18 Upvotes

Hi, I’m a graphic/web designer with some UX knowledge. I’m 34 and was recently diagnosed with ADHD. I’m fed up with this execution-heavy role and want to move into strategy, which led me to consider a Product Owner position. My understanding of the PO role comes mainly from YouTube and ChatGPT, so it’s still very basic.

My big concern is whether it’s practical to pivot at 34 with no formal education. I’ve started a few online courses and trying to reach out to POs for mentorship. I even did a SWOT analysis with a career counselor, and I’m genuinely excited about this decision. I love design, but I’ve never been this enthusiastic about the actual execution. I usually give up on design courses halfway through. By contrast, I’m fully engaged in my (basic) PO courses because they teach how to think rather than which tool to use.

My questions:

  • So am I being overly ambitious? Is it realistic for me to start as an intern at my age and with no technical background?

  • How steep is the learning curve ahead of me? Right now, being a PO feels liberating compared to being stuck at my desk churning out designs. But what are the real pitfalls of being a PO?

  • Also, I don’t see many PO vacancies on LinkedIn. Is demand really that low?

  • And is the role AI-proof, or should I worry about automation down the line?

Any advice is appreciated. Thank you!


r/ProductOwner • • Mar 04 '26

Career advice I want to be a PO

17 Upvotes

Hi guys!

I’m feeling a bit lost in life at the moment… I have around 7 years of experience in web development and design, and I also have a Master’s in Customer Experience. My current role is quite hybrid — it’s a fairly large e-commerce company, but I kind of do a bit of everything and nothing at the same time. I don’t know if that makes sense.

I do some web development, fairly light (I’m not super passionate about coding and there’s another frontend developer), I manage some website improvement projects by coordinating with different stakeholders, following up, testing, and handling the launch/communication of new features. I also analyze the performance of some functionalities, review the data provided by the data team, and we assess whether improvements can be made, etc.

I do a few other things too, but I think they’re not that relevant.

So, since last year I’ve been considering learning more to become a Product Owner. I took a Coursera course to understand what the role involves and see if I liked it. I’ve sent out a few CVs for PO roles, but I’ve never been considered. I’m not sure whether, with my experience, getting a Scrum certification would improve my chances? Or how would you approach it? Or should I just get it out of my head and slowly rot at this company? Thanks!!


r/ProductOwner • • Oct 17 '25

Help with a work thing The Workflow That Made My Life as a PO Easier

17 Upvotes

Hey everyone, I’m Ozay.

After 4 years as a full-stack developer, I moved into a technical PM role (or PO for small teams).

Since I’ve been on both sides, I wanted to share the workflow that made my life much easier.

Let’s start from the dev side.

When I was a developer, the first thing I’d do to understand a product was visualize the interface, then build the backend around it.

My PO at that time used to share low-fi wireframes based on client feedback, and they made everything crystal clear. I could instantly understand the structure and UX behind each page.

That was a huge relief, because during my internship, there was no wireframe culture at all.

Every new task required a chat with someone just to figure out what screen we were talking about.

Later, in my second job, I started as a developer again.

After about a year, I switched to the PM side because I was comfortable communicating with both devs and clients, and I understood the product deeply.

But this time, there were no wireframes.

And it was painful.

Understanding what PMs meant took forever, because everyone had a slightly different image of the same feature in their head.

That’s actually why I decided to become a PM.

I thought, “If I were the one explaining this, I could make things flow way smoother.”

Once I became a PM, though, I realized it wasn’t that simple.

Explaining client requirements to developers and planning the phases clearly was harder than I expected.

I often caught myself thinking like a dev again, being too technical and not giving enough clarity.

So I went back to what worked for me before: wireframes.

I started documenting everything visually.

But soon I found myself uploading the same wireframes again and again for every new task, re-explaining the same elements.

Eventually, I convinced the team to switch to a wireframe-based task management workflow.

It changed everything.

Each element had its own context, documentation, and linked tasks.

The wireframe basically became a living doc.

I no longer had to repeat explanations, and the dev team could instantly see where and what needed to be done.

The best part?

I can now see which parts of the product are being worked on and what their status is directly from the wireframe.

It’s much easier to report progress to clients or management without constantly checking in with the dev team.

I know this might not be an issue in bigger, well-structured companies.

But for small teams and startups, where everyone wears multiple hats, this kind of confusion happens all the time.

This workflow helped me a lot, and maybe it’ll help someone else too.

Happy to answer any questions if you’re curious!