How to ask an AI for something useful

People try these tools once, get something generic, and conclude they are overrated. Almost every time, the request was one line long and the output matched.

There is no secret phrasing. There is just being specific about five things.

The five parts

1. Role. Who should it be while answering. "You are an experienced operations manager reviewing a process document."
2. Task. The actual job, stated as an instruction. "Rewrite this update so a busy director reads it in thirty seconds."
3. Context. What it cannot know. The audience, the history, the constraint, the thing that went wrong last time.
4. Format. How you want it back. Five bullets, a table with three columns, an email under 120 words, no headings.
5. Standard. What good looks like, or what to avoid. "No marketing language. Do not invent numbers. If something is missing, ask me instead of guessing."

You will not always need all five. Context and format are the two that carry most of the improvement.

The same request, twice

Weak: "Write an email to a customer about a delay."

Better: "You are a customer success manager. Write an email to a customer whose onboarding is slipping by two weeks because our data import failed twice. They are already frustrated and have asked for updates before. Keep it under 120 words, one apology sentence, then what we are doing and when they hear next. No corporate language. Give me the plainest version you can."

Same tool, same second of effort. The second one is usable.

The habit that matters more than the prompt

Your first output is a draft to react to, not an answer to accept. The fastest quality gain available is one follow-up:

• "That is too formal. Say it like you would to a colleague you like."
• "Cut it by half. Keep the specifics, lose the throat-clearing."
• "What did you assume that I did not tell you?"
• "Give me three versions: cautious, direct, and warm."

I get more value from that second message than from any clever opening prompt.

Four mistakes worth naming

Asking for facts it cannot have. If it is not searching the web, do not ask about this quarter's pricing. Paste the page in instead.

Describing a document instead of pasting it. Paste the thing. Everything improves.

One chat for everything. A long thread drags old context into new work. Start a fresh chat when the topic changes.

Accepting good-sounding output. Confident prose is what these tools produce by default. Check names, numbers and dates every single time. This is the one rule I have never regretted.

Reusing what works

When a request works well, keep it. A note on your desktop with five or six of your own tested prompts, with a blank where the input goes, is worth more than any prompt library you can buy. Mine has six in it. It has been the same six for months.

Once the asking is comfortable, the next question is which tools deserve a place in your week. Your first three tools is the short answer.