September 18, 2026
A blank text box is a strange thing. It looks like it wants one perfect sentence, so most people type one and hope for the best. The answer comes back flat and generic, and they decide the tool isn't much good. Something simpler happened: the request was thin, so the response had nowhere to go. Writing a good prompt is mostly about moving what's already in your head onto the page. Four things do most of that work — task, context, format and constraints. Here's how they fit together, using one ordinary request rewritten three times.
The Four Building Blocks
Treat a prompt like a short brief you'd hand a capable colleague who knows nothing about your situation. Four pieces carry the weight:
- Task — what you want done, phrased as an action.
- Context — the background nobody could guess.
- Format — the shape you want the answer in.
- Constraints — length, tone, and what to leave out.
You don't need all four every time. A quick factual question needs only a task. But the moment a request matters — an email a client will read, a plan your team will follow — the other three are what separate a finished answer from a draft you have to rewrite anyway.
Start With the Task
Open with a verb. Draft, summarise, compare, rewrite, list, explain, review. "Write a message to my landlord about the radiator" beats "something about my radiator" because it names the deliverable, not just the topic.
Keep it to one job per prompt. If you want a summary and a recommendation, either ask for both explicitly — "summarise this, then give me three recommendations" — or run them as two requests. Vague multitasking is the most common reason an answer feels scattered.
Add Context the Other Person Couldn't Know
This is where most beginner prompts lose their edge. Nothing on the other side can see your inbox, your audience or your history, so describe them:
- Who is this for, and what do they already know?
- What happened before this?
- What have you already tried or ruled out?
- What does a good result look like to you?
Paste the actual text rather than describing it. If the message is about a specific email thread, include the thread. And include the awkward detail — the thing that makes your situation different from the average one. That detail is usually the reason you're asking in the first place.
Decide the Format Before You Ask
If the answer has to fit somewhere, say where. A subject line and three short paragraphs. Five bullets, no more than ten words each. A two-column table. A numbered list of steps. Ten options, one line apiece.
When you genuinely don't care, saying so frees things up: "Any format, keep it short." When you do care, being specific saves an entire round of back-and-forth.
Use Constraints to Set the Edges
Constraints are the quiet part of a prompt, and they often change the answer more than the task does. Word counts. Tone — direct, warm, formal, plain. Reading level. Things to avoid: jargon, exclamation marks, filler openings. A spelling convention if you're writing for a particular audience.
Phrase them as what you want, not only as what you don't. "Plain language, no acronyms" is checkable. "Don't be boring" isn't. If one constraint matters a lot, repeat it near the end of the prompt, where it's hardest to miss.
One Request, Three Rewrites
Here's the same request at three levels. Notice that the task never changes.
Version 1: task only
Write a birthday message for a coworker.
You'll get something pleasant and completely anonymous — a card that could go to anyone, which means it lands with no one.
Version 2: task and context
Write a birthday message for a coworker. She's been on my team for four years and leaves next month. She likes hiking and terrible puns.
Much better. Now the answer has a person in it. What you still can't control is length and tone, so you may get four paragraphs where you needed three sentences.
Version 3: all four blocks
Write a short birthday message for a coworker. She's been on my team for four years and leaves next month. She likes hiking and terrible puns. Format: three sentences, under 60 words, ready to paste into a team card. Constraints: warm but not gushing, no exclamation marks, one light hiking reference, and skip the pun — someone else is using it.
The task is identical to version one. The difference is that the answer arrives finished. You read it, swap a word if you like, and send it.
When the Answer Misses, Adjust One Thing
Beginners usually scrap the whole prompt and start over. Keep what worked instead. "Shorter." "Less formal." "Same content, but lead with the problem." "Keep the second paragraph, cut the rest." The earlier turns are still in the conversation, so you're steering rather than re-explaining.
Two or three small corrections beat one giant rewrite nearly every time.
A Two-Minute Routine Before You Hit Send
Run through this and your prompts will improve immediately:
- What exactly do I want back? Name it with a verb.
- What wouldn't a stranger know? Add the audience, the history, the awkward detail.
- What shape should the answer take? Say it, or say you don't mind.
- What are the limits? Length, tone, what to skip.
- Read it once. If you'd be annoyed to receive it as a brief, tighten it.
Your first prompt doesn't have to be your best one. Write it plainly, see what comes back, then add the piece that was missing. Do that a few times and the habit carries over into ordinary requests — the ones you make to colleagues, and the ones you make to yourself.
Photo: StartupStockPhotos / Pixabay
