How do I get better answers from AI

Tell the assistant what you want to produce and give it the information that changes the answer. A useful prompt is often a clear brief, followed by specific feedback when the first result misses something.

You do not need to tell it that it is the world’s greatest expert. It has heard that before.

Ask for a result you can recognise

“Make this better” gives little direction. If you want a client email, say who will read it and what the email needs to achieve.

You might ask for a polite request to confirm a meeting date, kept under 150 words. Supply the proposed dates and make clear whether they are confirmed options or suggestions.

OpenAI’s prompting guide recommends relevant context and a clear goal without requiring a rigid formula. Use enough detail to define success, then inspect the response.

Supply the information that matters

For a project update, include the current decisions and deadlines. Identify the version the assistant should use if your notes contain older information.

You do not necessarily need to upload an entire meeting archive. A short authorised extract can preserve the meaning without exposing unrelated material. If the task needs a condition or exception, keep it in the extract.

Tell the assistant what to do with missing information. Asking it to flag a gap is more useful than encouraging it to produce a complete-looking answer at any cost. Still check that it followed the instruction.

Show an example when words leave room for doubt

A short example can demonstrate a format more clearly than “use my usual structure”. Show a fictional update with a decision at the top, then explain that the order is what you want copied.

If missing deadlines are common in your notes, include an example that labels one as unknown. Otherwise the assistant may imitate only the tidy cases and fill gaps you wanted left open.

Claude’s prompting documentation discusses using relevant examples to guide outputs. You do not need its technical syntax for an ordinary request. The example should make your intention easier to understand, not make the prompt more elaborate for its own sake.

Try a complete brief

Here is a prompt for turning notes into an internal update.

Draft an update for our project team from the notes below. Put decisions needed before routine progress. Preserve conditions and distinguish proposals from approved decisions. Use only the supplied notes for factual claims. Put missing information under Questions. Do not send the update.

If the notes say testing happens Thursday only if a sample arrives Wednesday, the update needs that condition. If a budget increase is proposed, it must not describe the increase as approved.

Check those details before judging the writing style. A well-written error is still an error.

Correct the specific mismatch

Instead of “too generic”, ask it to include the supplied deadlines and identify where an owner is missing. Instead of “too long”, set a length that still allows the essential condition to remain.

Tell it what should stay unchanged when revising. Then read the revised result. An apology does not establish that the correction actually happened.

If repeated changes become tangled, restate the current brief and governing facts. A fresh, clear version is often easier to inspect than a long conversation containing several superseded instructions.

Reuse preferences with AI Passport

AI Passport holds selected personal context that connected assistants can use with your permission. It can help when you keep repeating the same writing preference in different tools.

Ask a supported connected assistant to propose a preference such as using British spelling and putting decisions needed first in routine project updates. Review it in Passport before approval. Keep the scope narrow enough that it does not force every kind of writing into the same structure.

A permitted assistant can retrieve that preference for a later task. It still needs the current facts in your brief. A style preference cannot supply the project’s latest deadline.

Approval of the memory and permission for an app to read it are separate decisions. If you copy the preference into another service manually, that service receives a separate copy. Passport does not automatically merge the tools’ conversation histories.

Say whether you want a draft or an action

For an assistant with tools, make the intended stage explicit. Preparing a message is different from sending it.

Use the available permission and review controls as well as instructions. Before an external action, check the exact recipient and content. A better prompt makes the work easier to evaluate, but it does not replace the decision about what the assistant is allowed to do.