Create effective prompts for business tasks
A good prompt gives Claude the context, task, constraints and examples a capable new colleague would need.
Whether you can spot what is missing from a weak prompt and pick the change that most improves the output. Most wrong answers add emphasis or vague adjectives instead of information.
Key ideas
- Context first
- Say who the output is for, why it is needed and what Claude should know about the situation. Generic output almost always means missing context, not a weak model.
- A specific task
- Use a clear verb and name the deliverable: “Draft a 150-word email inviting existing customers to the webinar” beats “Write something about the webinar”.
- Constraints that matter
- Length, tone, format, reading level, must-include facts and things to avoid. Concrete limits (“no more than 12 items”) work better than adjectives (“concise”).
- Examples of good output
- One or two approved examples transfer style and structure more reliably than any description of them.
- Separate instructions from material
- When you paste documents, label them clearly (headings or tags such as <policy>…</policy>) and state the task separately, so Claude doesn't mistake content for instructions.
- Say what to do when information is missing
- “If the documents don't cover it, say so” prevents confident guessing.
Worked example
A marketing manager needs a product launch email.
Write a launch email for our new product. Make it exciting.
Write a 150-word launch email for existing small-business customers announcing Invoicely Pro (details below). Goal: book a 15-minute demo. Tone: friendly, plain English, no hype words. Include the launch date and the demo link. Here is a past email that performed well: <example>…</example>
Why: The strong version adds audience, goal, facts, length, tone and a model to imitate. “Exciting” gives Claude nothing to work with.
Common traps
- Writing instructions in capitals or saying “this is very important” instead of adding information.
- Telling Claude to “be an expert” and expecting that alone to fix missing facts.
- Asking for things Claude can't guarantee, such as trademark availability or today's prices without web search.
When output is generic, add context and examples before you change anything else.