aAI Toolsat workFind my tool

PRACTICAL GUIDE

Write better prompts for real work

Give an assistant enough context to produce something useful, then improve the result through targeted feedback.

Start with the outcome

Describe the deliverable and what it needs to accomplish. “Write a customer email” leaves the most important choices unresolved. “Draft an email explaining a delayed delivery, preserving trust and asking the customer to confirm the new date” gives the task a direction. Include the audience’s knowledge and concerns. The aim is not to make the prompt long; it is to remove the uncertainty that would otherwise force the assistant to guess.

Supply the information it must respect

Provide the relevant facts, source text and constraints. Distinguish approved information from rough notes or possible ideas. If a price, deadline or commitment is undecided, say so explicitly. Ask the assistant to preserve missing details as questions or placeholders. When sharing examples of your style, explain what to copy: perhaps the sentence length, degree of formality or directness. Do not assume that one example communicates every preference you have.

Specify the shape of the answer

Choose a format that supports your next step: a table for comparing options, a short email for a customer or an outline before a long document. Set useful limits, such as three recommendations with evidence, rather than vague instructions to be comprehensive. For a complex task, ask for an outline or a list of questions first. This gives you an opportunity to correct the structure before the assistant spends effort developing the wrong answer.

Make uncertainty visible

Ask the assistant to separate facts, assumptions and suggestions. Tell it when to ask a question and when to use a clearly marked placeholder. If you provide source material, ask it to identify the passage supporting an important claim. These instructions help you review the output; they do not make it automatically correct. You still need to check facts and calculations. A request to “double-check everything” is less useful than naming the details that matter most.

Give specific feedback on the draft

Treat the first result as a draft. Instead of “make it better,” point to the problem: the introduction is too long, the recommendation lacks evidence, or the tone is too formal for the reader. Explain what should stay unchanged. You can ask for two alternative openings or a shorter version of one section without regenerating the entire document. Small, targeted revisions make it easier to understand whether the result is actually improving.

Save the structure that proved useful

Once a prompt works for a recurring task, turn it into a template with clearly named fields. Keep the quality checks beside it so future users know what to review. Include an example of an acceptable result and note the limits of the workflow. Reuse the structure, but update the context each time: yesterday’s audience, data or business objective may no longer apply. A useful prompt template is a working brief, not a magic phrase that guarantees the same quality everywhere. When you change a template, keep a short note about what improved and what did not. That makes the next iteration easier and helps colleagues understand why a constraint exists.

Keep this checklist

  • Outcome, audience and purpose are explicit.
  • Approved facts are separated from assumptions.
  • The output format matches the next step.
  • Missing information must be flagged rather than invented.
  • Feedback names a concrete problem and desired change.

Put it into practice