r/ProductOwner • u/Lucky_Mom1018 • May 03 '26
Help with a work thing Claude code
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?
4
u/pulsone21 May 03 '26 edited May 03 '26
For azure Devops you will need an enterprise app (at least that’s the way I know) which gets api permission for azure devops. Then you need to invite the service principle to the repo/s then happy days. The token will be the wither creds or cert from the enterprise app.
Then write a script run it on your maschine or even as pipeline regularly to pickup the stuff
2
u/Emergency_Nothing686 May 04 '26
the /superpowers plug-in is pretty useful for systematic debugging. I have a local copy of my repo and ask it why we're seeing certain bugs, then give that to our devs as a starting hypothesis.
2
u/_CaptRondo_ May 04 '26
Is just made a epic, feature, story writer this weekend. Just play around with it to learn the skills.
You don’t need Claude code for code generation alone.
How about building a stakeholder tracker?
Or Produxt strategy creator. Just play with it to learn
2
u/WaylundLG May 04 '26
Record/transcribe user and stakeholders interviews and us AI to help pick out common sentiment and needs - this is by far one of the most useful things I've seen AI do for a PO.
In some cases I've seen it do a good job building out gherkin-style acceptance tests, though it's been a mixed bag.
1
u/fraser_john May 06 '26
Write a Claude skill for business analysis and another for writing backlog items and acceptance criteria. The Claude context files are critical to make sure it does what you want otherwise it just starts coding. As a PO, you want business focus, and I direct my skill to only output stuff aligned with Microsoft writing style guideline.
12
u/cardboard-kansio May 03 '26
You need to run MCP connectors (or connect with the supplied ones) to have Claude use services like Jira, Confluence, GitHub, ADO, et al.
Once you have those arranged, I can highly recommend using Claude Code over Claude Desktop.
As for how to have Claude help you with user discovery... the closest I've come so far is to set up a multi-agentic ecosystem to evaluate my insights, and pipe everything into it (emails, Slack discussions, Teams meeting transcripts, screenshots, and such).
The short version:
Auto-load your CLAUDE.md every session, with a currently valid context covering product overview, north star, team context, decision principles. Uses @file to pull in supporting docs.
Supporting docs, in a context subfolder:
strategy.md covering vision, 12-month bets, explicit non-bets - this stops Claude from suggesting things that contradict your strategic context
personas.md, typical list of user personas, specific key individuals users, jobs to be done, language they use
metrics.md for your current targets and success criteria, to ground every recommendation
roadmap-context.md to cover what just shipped and what's next, in order to keep output relevant to this quarter (you can also automate release notes or other updates from this)
design.md to describe components and interaction patterns, and build prototypes specific to your system
Also there in a CLAUDE.local.md for personal overrides such as your individual tone, output format preferences, company style, etc.