Same Object, Different Deliverable

I've been making prototypes for twenty years. Someone sent me one this week and I couldn't figure out where to click.

Not because it was complicated. Because there was no path. No flow. No sense of what I was supposed to look at, or what I was supposed to think when I got there. Just an HTML file and an implied shrug. Tell me what you think.

The prototype wasn't missing a story. It was telling a different one.

The prototype was never the deliverable. It was the transport layer for a story: the clean path, the one or two branches, the walkthrough that lets the thing land when you're not in the room to narrate it. Take the story out and you don't have a smaller prototype. You have a surface that responds.

The file I opened responded to everything and led nowhere. It was built to move a stakeholder, not to walk a user, or so I assumed. A business case wearing the costume of a user flow. I was looking for the user in it, and the user was never the point.

The artifact got cheap. AI can generate a working, clickable prototype from a paragraph of description, and what used to take days of craft is a prompt now. And because it got cheap, everyone mistook the artifact for the skill. They saw the surface and decided the surface was the job. So they make the surface and ship it. It looks identical from the outside.

It isn't. A designer hands you a prototype and a path through it. Product hands you an HTML file and a shrug. Same object. Opposite deliverable. The difference is the entire job, and it just went invisible, because the part that was always the work was never the part you could see.

I've lived in these tools, and here's the tell. In the one I've used for years, a screen can't click to the next until you decide it should. The path is something you author. Get lost, and you can ask the tool to show you the way: it lights up every place the designer decided you could go. The wayfinding works because someone made those decisions.

The AI file has none of that. Everything clicks, because it's a web page and web pages click. I press anything, something happens. That feels like more. It's less. I wasn't lost because the signposts were missing. I was lost because nobody had chosen a destination.

I want to be careful here, because the easy version of this post is a designer complaining that product is doing design badly. That's not the post. That's the turf war, and I've been in it, and I'll cop to the pull.

The truth cuts both ways. Designers have spent years learning the business, sitting in the strategy conversations, building the case. We've been doing a version of product's job and calling it maturity. So when product picks up the tool and starts making artifacts, the honest read isn't "they're in our lane." It's that the lane between speaking for the user and speaking for the business is collapsing for everyone, and the tool poured gasoline on it.

Designers speak for the user. Product speaks for the business. That difference is real, and it's why the prototypes come out so different. But the difference was never a wall. It's a seam, and the seam is dissolving.

So here's the thing I can't stop thinking about.

While everyone fights over who gets to make the artifact now that the artifact is free, the user is the one quietly leaving the room.

Nobody's being malicious. We're all just trying to figure out the damn tool. But the fight has a casualty, and it isn't product and it isn't design. It's the person on the other end of the thing we're all so busy making. The one who was never in the room to begin with. The one whose only representation was whoever showed up accountable for them.

A prototype with a path through it is making a promise. It's saying someone walked this, on behalf of someone who couldn't be here, and here's what they need. The prototype with a shrug isn't making that promise. Not because the person who made it is careless. Because carrying the user was never their job, and now that the artifact is free, it's at risk of being nobody's.

I don't think the answer is designers drawing a line around the tool. The tool isn't going back in the box, and the line wouldn't hold.

And it isn't asking the tool for the signposts either. You can generate the wayfinding the same way you generated the screens, and it would look more navigable while deciding nothing. You can't prompt your way to a destination. A signpost points at a path. It doesn't make one.

The answer is smaller and harder. When the artifact is free, the only thing left worth anything is whether someone in the room is accountable for the person who isn't. That used to be design's job by default, because we were the ones who could make the artifact. The default is gone. The job isn't.

So the question I'd leave you with isn't who gets to make the prototype. Everyone does now. It's who, in the room, is still answering for the user when the file gets passed around and everyone nods.

If that's nobody, it doesn't matter how good the prototype is. The user already left.