You don't need to code. You need to give orders.

The site handled ten users in testing. Fifteen thousand showed up on Black Friday. It crashed.

Everyone blamed vibe coding.

They blamed the wrong thing.

The AI built exactly what it was asked to build — a system tested for ten users. “Must support 15,000 concurrent users” was never in the brief. So the AI never built for it.

Give that same incomplete requirement to a developer writing code by hand and you get the same crash. This wasn’t a vibe coding failure. It was a requirements failure.

The AI executed the order it was given — perfectly. The order was incomplete.

Here’s what nobody in that conversation said: I manage a software product with two professional developers. I write the requirements. I review the output. I’m accountable for what ships. I don’t write a line of code.

How is that different from directing Claude?

It isn’t. The only thing that changed is the speed and the cost. I’ve been doing this for years — non-technical director, technical team, accountable for the outcome. Vibe coding didn’t change the model. It changed who’s on the other end of the brief.

Which means the crash wasn’t an AI problem. It was a leadership problem. The requirement didn’t exist because nobody defined it. Nobody defined it because nobody knew to ask.

That’s the gap. And it has nothing to do with whether you can code. I wrote last month about knowing what assumptions to shape before you prompt — sketching the experience, defining what done looks like, before you type a single message. That’s the foundation.

The process is what separates a site that handles fifteen thousand users from one that crashes under the weight of its own success.

You don’t need to know how to code. You need to know how to give orders.

In the next note, I’ll give you the order format I use — borrowed from forty years of military doctrine — that catches these gaps before you build, not after the site crashes.

Building something with AI right now? Start a conversation for a gut check on your brief before you go further.