Replace vague instructions with a job
“Write something professional” leaves the assistant guessing about the audience and purpose. Explain who will read the result, what they need to know and what action should follow. For a supplier email, specify the missing information and the deadline you have actually agreed, rather than asking the model to invent urgency.
Use a short prompt structure
Provide context, task, constraints and format. For example: “Draft a follow-up to a supplier about quotation Q-104. Ask for lead time and warranty terms. Do not invent prices or promise an order. Use a courteous tone and keep it under 150 words.” The structure matters more than finding a magical phrase.
Give examples carefully
An approved sample can show the tone or level of detail you want. Remove private names and commercial details if they are not needed. Explain which qualities to copy: brevity, structure or terminology. Otherwise, the assistant may reproduce facts from the example that do not belong in the new situation.
Ask for visible uncertainty
For a comparison or summary, request a separate list of missing information. Tell the assistant to distinguish supplied facts from assumptions. If the answer depends on current information, verify it against an appropriate source. A well-written prompt improves direction but does not make every statement correct.
Review against the original task
Before sending the output, check names, numbers, dates and commitments. Ask whether the recipient can understand the next action. Keep prompts that repeatedly work, along with examples of mistakes to avoid. Over time, a small collection of task-specific prompts is more useful than a huge list of generic productivity tricks.
Published by DevMania with AI assistance. Examples illustrate planning approaches and do not claim client results. Check current provider documentation before implementing product-specific features.