Asking a Question vs Delegating a Job

You are using a colleague as an encyclopedia

Here is what most people do with AI. They open ChatGPT, type "tips for writing a good performance review", read eleven bullet points they mostly already knew, close the tab, and then write the performance review themselves.

That is asking. You got information. You still have all the work.

Now here is the same person on a good day. They type "write the performance review for a mid-level designer, second year, strong on craft, weak on speaking up in meetings, using our five-point scale, three paragraphs, honest but not brutal". Ninety seconds later there is a draft on the screen and they are editing rather than writing.

That is delegating. Same tool. Roughly the same amount of typing. Completely different amount of work left on your desk.

The tell: what is left on your plate

There is a simple test for whether you asked or delegated. When the answer appears, look at what you have to do next.

If the next step is "now I go and write it", you asked. If the next step is "now I read this and fix two things", you delegated.

Most people never make the switch because the asking habit came from search engines. Twenty years of typing keywords into a box that returns links has trained everyone to expect pointers rather than products. AI will happily play along. Ask it for tips and it gives you tips forever.

The verb does most of the work

You do not need a course in prompt engineering to make this switch. You need to start your instruction with a verb that produces a thing.

Weak openers: tell me about, what are some, how do I, give me tips on, explain.

Strong openers: write, produce, draft, build, rewrite, summarise into, turn this into, fill in.

Instead of: How do I write a good project update?
Produce the project update email for my client.
Project: [name]. Status: [on track / slipping / blocked].
What happened since last time: [two or three facts].
What happens next and by when: [dates].
Tone: calm and factual. Under 150 words. One subject line.

You just gave me general advice. I do not need advice, I need the thing.
Using what you said, produce the actual [document type] for this situation:
[paste your real details]
Give me the finished version, not an outline of it.

Ask for the finished shape too

Delegating is not only about the verb. It is about naming the shape. A colleague told to "write something about the budget" hands back something unusable. A colleague told "one page, three sections, numbers in a table, no jargon" hands back something you can forward.

Produce: [a one-page summary / a table / a five-slide outline / a customer email].
Audience: [who reads it and what they already know].
Length: [word count or number of items].
Structure: [the sections you want, in order].
Anything I must not include: [internal names, prices, guesses].

I am handing you a job, not a question.
The finished thing I need: [name it exactly].
Who it is for: [audience].
What good looks like: [one sentence].
Constraints: [length, tone, format, deadline, things to avoid].
If something is missing, list your questions at the end rather than inventing details.

That last line is worth more than the rest combined, and the next lesson is built around it.

What this does not mean

Delegating does not mean trusting blindly. It means the first draft stops being your job and reviewing becomes your job instead. Gemini, Claude and the rest will all state a wrong date with exactly the same confidence as a right one. You still read everything before it leaves your hands.

But you will read it in two minutes instead of writing it in forty. That is the whole trade, and it is a very good one.