The cursor blinks in an empty box and you've got nothing.

Not because you don't know what you want. You know exactly what you want. You want a winter shutdown procedure for a jobsite, the kind you've walked a hundred crews through verbally and never written down. But typing all that out feels like homework, and you've got a truck to get on the road. So you close the tab and do it the way you've always done it.

That blank box is where most people quit on AI, and the standard advice makes it worse.

Every AI tip you've read says the same thing: write better prompts. Be more detailed. Add context. Structure your request.

Fine advice for someone with a free afternoon. Useless for an operator between jobs. It puts the entire burden on you to anticipate everything the machine needs before it says a word, which is exactly the thing you don't have time for. And honestly can't do well, because you don't know what it needs.

So flip the whole thing around. You're not a prompt writer. You're the guy who knows the answers. Let it do the asking.

Add one line to the front of any request:

That's it. That's the whole technique. Everything below is just variations on it.

Take that winter shutdown procedure. The lazy version, "write an SOP for winter shutdown on a jobsite," gets you a generic document about a jobsite that doesn't exist, full of steps that don't apply and missing the two that matter.

Now add the line:

And it comes back with questions instead of a document. What kind of site. What equipment is staying versus coming back to the shop. Is there anything with water in it that can freeze. Who's responsible for the walk-through. Is this for the crew or for the client's file. How long is the shutdown.

Now look at what just happened. You didn't write a prompt. You answered six questions in fragments, the way you'd answer a foreman on the phone. Thirty seconds of typing, and the thing it produces is about your job.

And there's a bonus most people miss: it asked about something you'd forgotten. That happens constantly. The questions aren't just feeding the machine. They're a checklist you didn't have.

When you're in a hurry, have it list assumptions instead. Questions take a round trip. This doesn't:

You skim the list, fix numbers three, six, and nine, and it goes. Faster than a conversation, nearly as good.

When it already produced something mediocre, ask what you withheld.

This is the highest-value question in the whole toolkit and almost nobody asks it. The answer is a map of your own blind spots.

When you want the interview to stick, save it. Copy the questions and your answers into a plain text file. Next time you need anything about that site, hand it the file first. You just built your first context document by accident, which is the whole spine of everything we talk about here.

Cap the questions or you'll get thirty of them and lose the afternoon. "Up to eight" works. "Ask me the five most important things" works better when you're impatient.

Answer in fragments. Nobody's grading your grammar. "Two 500-gallon tanks, water, staying on site" is a complete answer.

And it's still a confident intern. It'll ask smart questions about the shape of the job and know nothing about your local code, your inspector, or the client who calls at 6am. When the answer touches safety or compliance, a human reads it before it goes anywhere. That rule doesn't bend.

The interview move scales further than it looks. It's how you get a usable scope out of a rambling client call. It's how you turn twenty years of "we just know to do it this way" into something a new hire can read. It's how you write the job descriptions, the training outlines, the estimate templates you've been meaning to write since 2019.

And once you've done a few interviews and saved the transcripts, something shifts. You stop starting from zero every time. The AI opens the file, already knows your sites and standards and how you talk, and the questions get sharper because it only asks about what's genuinely new.

That's the real destination. The blank box was never the problem. The problem was that nothing remembered the answers.

Don't get better at asking. Add one line, ask me what you need to know first, and let it pull the job out of your head.

Reply and tell me: what's the thing everybody at your company knows and nobody wrote down? That's the one worth interviewing out of you first.

Friday: how to put a real drawing in front of a customer without owning a single design tool.

New here? The fastest way to put all of this to work is the free Context Starter Pack — one folder, three files, one hour.