Oct 6, 2026 · Lissette Arias

Designers Should Own Product Outcomes

A new product ownership model for the AI era: the designer closest to the user leads the bet, from framing through launch and measurement.

For too long, designers have been kept in an execution box. We're the ones who make things "usable and delightful," while product owns the strategy, the metrics, and the outcomes. But let's be real:

Design is strategy. Design is revenue. Design is growth.

And no, that's not just me being a designer about it. McKinsey's study followed 300 public companies for five years, and the top quartile of design performers grew revenue 32 percentage points faster than their peers. It's a correlation, not proof that design caused it (I know, I know). But the companies that pulled ahead had one thing in common: their leaders tracked design as seriously as revenue and cost.

Last year I wrote that designers need to step into product leadership and own the metrics, not just the experience. I still believe every word. But a lot has changed since then, and I think the ask is bigger now.

Here's what I keep seeing. A designer ships the onboarding flow that lifts activation, and someone else presents the win. Another spots the friction that's been quietly bleeding customers for months, and it gets logged as "UX polish" and pushed to next quarter. (If you've ever watched your insight show up in someone else's slide deck, you know exactly what I mean.)

And yes, some of that is on us. McKinsey said it too: designers have been partly to blame for not embracing design metrics or connecting our work to business goals. Ouch. But fair.

Ownership Should Follow the Problem

So here's what I'm proposing: product ownership should follow the problem, not the org chart.

When a designer is closest to the user behavior that will make or break a product, that designer should lead the bet, from framing through launch and measurement. The designer stays accountable for whether the experience actually works, not just for handing off screens.

What Owning It Looks Like

  • 01

    You define success before you design. What behavior are we changing? How will we know? What's it worth? "Users can finish setup without help" becomes "setup completion goes from 60% to 80%, and week-one support tickets drop by half." With AI features, this matters even more. The output can look perfect and still fail. What you really need to know is whether people trust it, how often they override it, and whether it actually saves them time.

  • 02

    You go back and check. Shipping is the halfway point, not the finish line. When a number moves the wrong way, you're the one who can explain why, because you know what the user was trying to do. Is that uncomfortable? Sometimes. It's also how you stop arguing about taste.

  • 03

    You make the business case. Designers see where a product earns trust and where it loses people. Say it in the language the business listens to: if we fix this step, here's what we recover. Baymard's research estimates the average large e-commerce site could lift conversion by up to 35% just by improving checkout. Results will vary. But there's almost always money hiding in the experience.

The New Design Stack

The tools designers use have changed more in the last two years than in the decade before. Designers can now go from a prompt to a working product without waiting on a handoff.

Figma's design agent works directly on the canvas, generating and editing screens using a team's own components and design system.

This is where you’ll find me when I am in focused design mode.

Figma Make, Google Stitch, and Claude Design turn prompts into high-fidelity UI concepts and clickable prototypes.

Claude Code, Codex, and Cursor let designers build and ship real software alongside engineers.

This is where you’ll find me most days.

The gap between imagining a product or feature and shipping one has never been smaller.

AI Raises the Stakes

AI is collapsing the distance between idea and shipped product. A designer can prototype a working flow and test it with real users in a matter of hours, and push it to Github by the end of the week. When execution gets this cheap, the bottleneck moves upstream to judgment: knowing which problem matters, which bet to make, and how to tell if it paid off.

AI can summarize a thousand interviews in seconds. But some of the most important things I've ever learned about users never showed up in a transcript. The designer’s empathy and curiosity are how we find them, and no model can do that part for us.

AI products also need designers to own outcomes more than ever. When a feature is non-deterministic, "does it look right?" is meaningless. Success becomes: Do people trust the output? How often do they edit or override it? Does it actually save them time, or just move the work around? Those are behavioral questions, and designers are best positioned to define and measure them.

The designer who can say what the AI should do, how we'll know it's working, and what it's worth to the business isn't just staying relevant. They're the person every product team wants in the room. Leading AI strategy is the opening, and it's ours to take.

Jump in now!

When a feature is non-deterministic, "does it look right?" is meaningless.

Start Here

You don't need permission or a new title. Take ownership on your next project:

Write the success metric at the top of your brief. Before a single frame.

1

Pull your own numbers. AI makes the queries easy now. No more waiting on an analyst.

2

Build it yourself. Get a working version in front of users before the debate starts.

3

Report results in impact terms. "Trial-to-paid went up 12%" gets a very different reaction than "we redesigned pricing."

4

Time to Own It

I didn't wait for permission to build Pawsitive Foster. I designed it, built it, and shipped it, and I own whether it works. That's not because I'm special. It's because the tools finally let one designer close the whole loop. That door is open to every one of us now. The only question is who walks through it.