stopaskingai
Lesson 1

Stop asking. Start delegating.

The difference isn't which AI you use. It's whether you ask for a small answer or hand over a well-defined piece of work.

You own the goal and the decision. AI organizes the problem and does the first pass.

Asking or delegating

Asking

"Can you write a follow-up email?"

You supply every detail and work out the next steps yourself.

Delegating

"Here's the call transcript and our history. Find the commitments, draft the follow-up, list the to-dos, and flag anything I need to decide. Don't send anything."

AI prepares the work. You approve what happens next.

Why this works

It can't read your mind, but it can read your material

Most bad AI answers aren't the model being dumb. They're the model guessing at everything you didn't say. Every fact you hand over is one less guess.

A small sample is cheap, a wrong batch is expensive

If the first draft is off, you've lost two minutes. If a hundred are off, you've lost the afternoon and maybe trust in the tool. Checking early is the cheapest quality control there is.

Drafts keep you in charge without doing the work

Reviewing a good draft takes a fraction of the time it takes to write it. You still decide what goes out, so a mistake costs you an edit, not a client.

A worked example, start to finish

A small business owner got a long email from a client asking three questions and complaining about a missed deadline. Here's how the conversation goes when you delegate instead of ask.

You

Write a reply to this client email.

AI

Dear client, thank you for reaching out. We apologize for any inconvenience and value your business. We will look into this and get back to you shortly.

You

That's useless, and it's my fault. Here's what you need. The client is a 10-year customer. The deadline slipped because their files arrived late, but we never told them that. Answer all three of their questions using the notes I'm pasting below. Own the communication miss, not the delay. Keep it under 150 words, in my voice: direct and friendly. Don't send it. Show me the draft.

AI

Hi Dana, you're right that we went quiet, and that's on me. Here's where things stand. 1) The new date is Thursday. 2) Yes, the price stays the same. 3) We'll send updates every Monday until it's done. The delay came from files arriving on the 14th, and I should have told you then instead of now. I'll call you tomorrow to walk through it. Sam

You

Good. Change Monday to Tuesday, that's when we meet. And add that the files are now complete so there's no further risk.

The second request took one minute longer to write and saved twenty minutes of rewriting. The AI didn't get smarter between the two answers. It got the facts.

This is an illustrative example. Names and details are made up.

Seven habits

1. Talk, don't write specifications

Explain what you want in your own words. Turning it into a plan is the AI's job.

"I'm going to ramble about this client call. Turn it into a clean summary and next steps."

2. Give it the whole problem

The people, the history, the constraints, and what good looks like.

"Here's the email thread, our quote template and the client's priorities. Ask only what's missing."

3. It drafts, you decide

Anything that leaves your hands stays under your control.

"Prepare the reply and show me the draft. Don't send it."

4. Turn repeat mistakes into rules

Correct the same thing twice, then make it standing.

"From now on, list assumptions and exclusions before the price in every quote."

5. Push back

Ask what it checked and what a skeptic would say.

"Show me the source for that number. Where could this be wrong?"

6. Give it real material

A recording or a thread beats a description. Share only what you're allowed to.

"Use this transcript and the current proposal, not what you remember."

7. Check the first sample

Answer its questions and look at ten before it does a hundred.

"Do ten first. I'll check them before you do the rest."

Common mistakes

Asking for the output without the inputs

Fix: Paste the thread, the notes or the file. Then say what you want.

Accepting the first answer

Fix: Treat it as a first draft. Say what's wrong and why. The second answer is usually much better.

Letting it act before you've seen a sample

Fix: Ask for one or ten before it does a hundred, and before anything is sent.

Never writing down what you keep correcting

Fix: When you fix the same thing twice, save it as a standing instruction in your AI's settings or project.

Check yourself

Pick the better request. You'll see why right away.

1. You need a follow-up after a sales call.

2. You want a list of 200 local businesses to contact.

Exercise

Rewrite this request so the AI can actually do it well: "Make me a social media post about our new service." Write yours first, then compare.

Show a strong answer
We just launched same-day laptop repair for small offices in Austin. Our customers are office managers who can't lose a day without a machine. Write three short LinkedIn post options, each under 80 words, in a friendly, plain voice. No hashtag walls, no exclamation points. Include that we pick up and drop off. Show me the three; I'll pick one and tell you what to change.

Notice what it adds: what the service is, who it's for, why they care, where it's going, how long, the tone, the one fact that must be in it, and a first step that's small enough to check.

What Jason actually did

I have AI watching two inboxes with different jobs. One gets the alerts and the noise: it labels, files and only brings me decisions. The other is client-facing: it drafts replies to customers and saves them as drafts. Nothing sends until I read it and click Send. Most of the drafts are right the first time.

Practice: turn a request into an assignment

Pick a kind of task, describe the situation, and get an assignment to paste into any AI. The coach checks it as you go. Nothing you type leaves this page.

Try it today

Private to you. Saved only in this browser, on this device. Nothing here is sent anywhere, and nobody else can see it. Clearing your browser data erases it.

0 of 5 done

Your saved prompts

Nothing saved yet. Use "Save this prompt" on any example above.

Go deeper

The sources worth your time if you want the reasoning behind this lesson.

Keep going

Back to the field guide