The Prototype Is Not the Validation

A friend got an email from their CEO last week. Attached was a vibe-coded app. The ask: can we get this into production?

This is the new reality. The person with the idea no longer has to wait for the team. They can have a working prototype in an afternoon. It looks finished. It feels real. The conversation has already moved on before the team has even seen it.

The technical pushback is straightforward. Wrong language. Incompatible with the platform. Security issues. Those conversations are uncomfortable, but teams know how to have them. There's a shared vocabulary.

The harder conversation is the one nobody is trained for.

Just because it exists doesn't mean anyone needs it. Just because the CEO loves it doesn't mean it solves a real problem. The prototype is not the validation.

What natural friction used to do

Six months to build something meant weak ideas died quietly. The person with the idea had to convince someone to prioritise it, survive a planning cycle, watch it compete with other work. Most ideas didn't make it that far. Nobody had to say no. The timeline said it for you.

That protection is gone. The cost of creating a working prototype has collapsed to an afternoon and a subscription. The friction that used to do the organisational heavy lifting has been removed.

What hasn't changed is the work that actually matters: getting something in front of real users, measuring whether it changes their behaviour, deciding whether that change is worth sustaining. None of that got faster.

The muscle most teams haven't built

Technical pushback feels legitimate because it's objective. The language is wrong. The architecture won't scale. These are things you can point at.

Pushback grounded in user validation is harder. It requires saying: we don't yet know if anyone outside this room wants this. That's a different kind of conversation to have with a CEO who has already spent an afternoon building the thing and is excited about it.

Most teams haven't had to develop this muscle because the timeline used to do it for them. Now they do.

The question isn't whether the prototype works. It's whether it's solving something real. And the only way to answer that is the same as it always was: get it in front of actual users, not just enthusiastic colleagues, and be honest about what you see.

What the right pushback sounds like

It doesn't start with the technology. It starts with: who is this for, what are they doing today instead, and what would it take to find out whether this changes that?

That's not a no. It's a redirect from delivery to discovery. From "can we build it" to "should we."

The CEO's laptop just got a lot more powerful. The question of whether that power gets pointed at real problems is still a human judgement call. And right now, in most organisations, there's nobody trained to make it.