How to ask well: the four-part request
Learn the simple recipe that turns vague answers into useful ones, every time.
Most disappointing AI answers come from short, vague requests. The fix is a simple four-part recipe:
- Who: who should it act as? "You're a friendly personal trainer."
- What: what do you want it to do? "Make me a weekly exercise plan."
- Background: what does it need to know? "I'm 52, I haven't exercised in years, I have a dodgy knee and 30 minutes a day."
- Format: what should the answer look like? "A simple table, Monday to Sunday, with one line per day."
Put together:
You're a friendly personal trainer. Make me a weekly exercise plan. I'm 52, haven't exercised in years, have a dodgy knee and 30 minutes a day. Give it as a simple table, Monday to Sunday.
Compare that with "exercise plan please". The difference in the answer is huge.
You don't need all four every time. But when an answer disappoints, ask yourself which one you left out. It's usually background.
Why short requests disappoint
An assistant can only work with what you give it. "Write a speech" could mean a wedding toast or a retirement speech, two minutes or twenty, funny or heartfelt. With nothing to go on, it picks the middle of the road and you get something bland.
The four-part request
| Part | Question it answers | Example |
|---|---|---|
| Who | Who should the assistant be? | "You're an experienced primary school teacher." |
| What | What's the task? | "Explain fractions to my 8-year-old." |
| Background | What should it know? | "She likes baking and gets frustrated with abstract numbers." |
| Format | What should the answer look like? | "Three short steps, using a cake as the example, then a fun question to check she's got it." |
Examples, before and after
Before: "Help me with my CV." After: "You're a recruiter in retail. Review my CV for a store manager role. I've been an assistant manager for 4 years and led a team of 12. Give me the 5 most important changes as bullet points. [paste CV with contact details removed]"
Before: "Ideas for dinner." After: "Suggest 5 weeknight dinners that take under 30 minutes. We're a family of four, one of us is vegetarian, and I've got chicken, peppers, rice and a tin of chickpeas. Give the name, time and a one-line description for each."
Handy extras
- Give an example of what you like: "Write it in the style of this message: [paste]".
- Set limits: "under 150 words", "no jargon", "UK English".
- Ask it to ask you: "Before you start, ask me any questions you need answered." This is one of the most useful tricks there is.
- Say what to avoid: "Don't suggest anything with nuts."
You don't need to be formal
You can write the four parts as one natural paragraph, with typos. The recipe is a checklist in your head, not a form to fill in.
What's going on under the hood
The text you send is called a prompt. The assistant uses everything in the conversation as its working context and produces the response that best fits. Detail narrows the range of plausible answers towards the one you actually want. That's why the same assistant can seem brilliant to one person and mediocre to another: the difference is often the .
Each part of the recipe does a specific job:
- Who (role) sets expectations for expertise, vocabulary and tone. "You're a GP explaining to a worried patient" produces different language from "you're a medical researcher".
- What (task) should use a clear verb: summarise, compare, draft, critique, plan, explain, list.
- Background (context) supplies the facts that make the answer specific to you. It's the most powerful and most neglected part.
- Format controls the shape: length, structure (bullets, table, steps), reading level and language variety (UK English).
Techniques experienced users rely on
Ask for questions first. "Before answering, ask me up to five questions that would help you do this well." The assistant identifies the gaps in your context for you.
Show, don't just tell. Paste an example of the output you like, or one you dislike and say why. Examples are often clearer than descriptions.
Break big jobs into steps. For a report: first ask for an outline, agree it, then ask for each section. You stay in control and catch problems early.
Ask for alternatives. "Give me three different approaches and the pros and cons of each." It's a quick way to see the range of options.
Ask it to think it through. For decisions or tricky problems: "Work through this step by step and explain your reasoning before you give a recommendation." Many assistants now do this automatically with a "thinking" or "reasoning" mode, which you can usually switch on.
Ask for a critique. After a draft: "Act as a sceptical reader. What's weak or unclear here?" Then ask it to fix those points.
Things that don't matter as much as people think
You'll see online "prompt hacks": magic phrases, offering the AI a tip, or very long templates. Modern assistants are good at understanding plain requests, so these tricks matter much less than they did in 2023. Clear context and a clear goal beat clever wording.
Saving your best requests
When a request works well, save it. A note on your phone with your best "recipes" (meal planning, email replies, explaining letters) saves time and gets consistent results. Lesson 15 covers this, and lesson 14 shows how to give your assistant standing instructions so you don't repeat yourself.
Try this prompt
You are [who it should act as]. I need [the task]. Background: [the situation and any details]. Please give me [the format: a list, a table, under 100 words, three options].
Replace the [brackets] with your own details
On haystak
Quick check · 1 of 3
Which part of a request is most often missing?
Next step
Talk, don't search: following up and improving an answer
Get from "not quite right" to "exactly right" by having a conversation instead of starting again.