Making is no longer the hard part
For most of my career, the bottleneck in product work was making things. Design produced the screens, engineering built them, and a long queue sat in between.
That queue is shrinking fast. Designers are vibe coding working apps, turning prototypes into products and shipping without waiting for a sprint. I’ve seen it in my own work: a site quoted at £300k and six months was rebuilt by two people in two months.
When making gets cheap, the expensive question moves upstream. Not “can we build it?” but “should we, for whom, and how will we know it worked?” That has always been the product owner’s question. Increasingly, it’s the designer’s.
Most designers have a vague picture of product ownership
I’ve led design teams of 125 and 300 in two FTSE 100 banks. The designers I worked with were brilliant at understanding users and framing problems. Ask most of them what a product owner actually does and you’d get a shrug, a Jira board, or “the person who writes the tickets”.
The gaps are predictable. Designers anchor on the solution they can already picture. They want to keep every user group in play. They treat five good interviews as proof. They design the whole end state and resist shipping anything partial. And they rarely know how the money gets decided.
None of this is a talent problem. It’s an exposure problem. When I surveyed around 30 design leaders, 75% said getting design metrics was hard, and their main data source was team meetings. Designers bring anecdotes to rooms where Finance brings numbers.
If designers are going to own more of the product, they need the commercial muscles: outcome before output, a clear bet, kill criteria, and the confidence to say no.
What I’m building
There’s no shortage of product owner templates or AI tools that write user stories. Templates you can Google. What’s missing is the coaching: someone who knows how designers think, and where they go wrong, sitting beside them while they do the real work.
So I’m building two Claude skills.
A product owner coach. You share what you have: a prototype, a brief, design files, research. It shows you what your material already covers and what’s missing, then builds a product plan with you in five stages:
- Problem and outcome. What changes, for whom, and how we’ll measure it.
- Evidence. What we know, what we’re assuming, and what’s riskiest.
- The bet. The case for investing, and the points where we’d stop.
- The slices. Turning the design into releasable increments.
- The plan. Roadmap, metrics and who needs to sign off.
It drafts; you decide. Every challenge comes with a reason: who would push back, and what it would cost. It also asks how decisions get made where you work, because a case that suits a start-up founder looks flimsy to a bank’s investment committee, and the reverse.
A design-to-backlog skill. It turns a finished design into the thinnest slices that still deliver value, writes stories with edge cases taken from the design itself, and flags the gaps back to the designer rather than inventing answers.
Testing it on myself
The first test case is my own: Common Prints, a personalised typographic print shop. It’s live, it works, and it has never made a sale.
I went in thinking I needed a go-to-market strategy, a new homepage, a Google strategy and maybe a campaign. Within minutes the coach pointed out I’d listed four things to build before saying what had to be true for anyone to buy.
It got better. I picked gift buyers, it made the case against them, and I switched to interior designers on the spot. It called that out too: a product owner changes position because of evidence, not because of the last good argument. Fair.
It also had me commit to a number and a stop condition, which I’d quietly dodged twice. That’s the part designers skip, and apparently so do chief design officers.
The tests also showed where the skill fell short. It assumed what my site could do instead of asking. It jumped straight to action when the real first step was making the case to whoever holds the budget. Both are now fixed.
What’s next
I’m refining the skills with a collaborator and testing them on real work. The question I care about is whether a designer who has never owned a product can leave with a plan their sponsor would fund, and the judgement to defend it.
If you lead a design team where designers are being asked to own more of the product, or you’re a designer making that move yourself, I’d like to hear from you. I’m looking for a few people to try it on live work and tell me where it falls short.
The skills are on GitHub: github.com/noellyonsgit/product-owner-for-designers.