There's No Recipe

You open the chat and type the thing everyone types. Build me an app that does X. And it does. Out comes a screen, a button, a thing that clicks when you click it. Looks like the future. Took about ninety seconds.

Here's what the thirty-second clip leaves out. It built you something, but you never told it what you were making. You reached for a recipe. There's no recipe for the thing that's actually yours, though. There never is. There's only the question you skipped. Not how. What. What are you trying to cook?

That question is this whole piece. Not how to build it, not which tool or which model, not even what shape the thing takes. One move, the one that comes before all of those: working out what you're actually making, and who for. Get that wrong and the fastest builder alive just gets you to the wrong place quicker.

I should own something up front. I'm the last guy who should preach about slowing down. I reach for the tool before I read the manual. I build before I understand it, ask for directions on the second lap, read the instructions once I've already broken the thing. That's how I learn, hands on the thing and wrong a few times first. I'm not going to pretend otherwise.

One exception. Before any of that, I stop and find the problem. It's the single thing I don't wing, and it took me a few different trades to learn why: kitchens, a design studio, a print shop, now apps I build with AI.

Building starts with the problem, not the tool. True of anything: a business, a kitchen, a Saturday night. With AI that old line stops being a nice-to-have and turns load-bearing, because the tool will build you the wrong thing fast and look pretty fucking pleased about it. No pushback. No "are you sure." A confident, finished, wrong answer, handed to you warm.

So before the chat, two things, held apart. The outcome — what actually gets solved, and who for. And the form — how it shows up in the world. An app. An automation that runs while you sleep. A small tool, a script, a new habit. Most people open at the form. I want to build an app. That's picking the plating before you know the dish.

Turn it around. Outcome first, form dead last, decided so late that by the time you get there the shape is obvious. The wide net everyone casts is "what does it do, how do I use it." Decent questions, wrong order. The real one sitting under them: what do I want this for, and who am I in it. Those aren't two questions. They're one. The dish and the diner. Building it for someone else, the diner's them, not you, and the work is knowing them well enough to order for them.

A cook doesn't start the night by announcing beef wellington. A good one starts with the table. Who's eating, the in-laws or a four-year-old or the vegetarian you forgot was coming. The occasion, a flat Tuesday or an anniversary. What came in fresh that morning. What the room is actually hungry for. The dish is the last thing decided, and by the time you decide it, it's mostly decided itself. Lead with the recipe instead and you'll plate something technically perfect that nobody at the table wanted.

I've known that for years, in an actual kitchen. Didn't save me the first time it counted.

That first time was Job Studio, one of mine. I'd left a job and needed the next one, and anyone who's done that knows the hunt is a second job stacked on your day. So I reached for the obvious fix and decided to put mine on autopilot. Point an AI at the listings, let it fire off applications while I got on with my life. That was the idea. The form, grabbed first, the way everyone grabs it.

Then I lived in it, and it taught me what the idea had skipped. The pain was never the sending. It was not knowing which of forty openings was worth an hour before I'd already sunk the hour, then watching the few real applications I sent drown in a channel everyone was spraying into. More, faster, would have made my own problem worse. So I went hunting for the actual hurt under the thing I'd reached for, and there it was, the same one every serious seeker has.

The thing worth building flipped to the opposite of autopilot. Help you see what's worth your time before you spend it, help you sound like yourself, let you hit send by hand every time. Autopilot said automate the sending. The problem said never automate the sending. I'd grabbed the form, and the problem was hiding right under it the whole while.

That's the move worth more than all the rest: telling a real problem from a solution wearing a problem's clothes. They look identical head-on. I need to apply to more jobs, faster. Sounds like a problem. Walks like one. It's a solution that snuck in early and smuggled its own form along with it. The tell is dead simple. A real problem names a person and a hurt. A disguised one names a mechanism. "Apply faster" is a mechanism. "Good people can't tell what's worth their time and get buried when they try" is a person and a hurt. When you can't find the person in your own problem statement, you haven't found the problem yet. You've found a recipe.

Which is the good news: you don't need to know the shape yet. Maybe it's a snack, one automation that kills a single annoying task. Maybe it's prep, a workflow that hands you back an hour a week. Maybe it's the whole feast, a real product other people pay for. You can't tell this early, and forcing it this early is the mistake. Hold it open.

You'll know you've got it when you can say what you're solving and who for in one plain sentence, with no app or automation or tool anywhere inside it. The diner and the dish, no plating mentioned. That sentence is the thing worth making. Everything after it (what it is, what it isn't, how it gets built) hangs off that one line.

That's the first move, and it's the one nobody films, because "I sat down and worked out what I was actually making" doesn't rack up a million views. Once you've got the sentence, the next job is drawing its edges: what's in, what's out, what you're deliberately not building. That's scope, and that's where we go next.

For now, just the sentence. What are you making, and who for. Get that part honest and the tool finally has something true to build, instead of a fast road to the wrong place.

Grab a beer. Pull up a stool.

---

Further reading

• The Mom Test, Rob Fitzpatrick. The person-and-a-hurt move at book length: how to find a real problem by talking to people, without fishing for the answer you want to hear.
• Fall in Love with the Problem, Not the Solution, Uri Levine. Outcome before form, from the founder who built Waze and then did it again with Moovit.
• Jobs to Be Done: the milkshake, Christensen Institute. The diner and the dish in research form: what people actually hire a thing to do.