Using Claude Day-to-Day
The core prompting principle
The biggest predictor of whether Claude gives you a useful output is how clearly you tell it what you want. Vague in, vague out. The formula that works in almost every situation:
Context + Task + Format
- Context: who you are, what the document is, what background matters
- Task: exactly what you want Claude to do
- Format: how you want the output structured
Without this formula:
"Summarise this contract."
Claude produces a generic summary. It may or may not highlight what matters to you.
With this formula:
"I am a procurement manager reviewing a supplier services agreement. Summarise the key payment terms and flag any clauses that deviate from standard 30-day net payment terms. Format as bullet points, with a separate 'flags for review' section at the end."
Claude produces a targeted, structured output that is immediately useful.
You do not need to write an essay. Two or three sentences of context is usually enough.
5 practical use cases for managers
1. Meeting notes → action items
Paste your meeting notes and ask:
"These are notes from a team meeting. Extract a clear list of action items, including who is responsible and any deadlines mentioned. If a deadline is not stated, note it as 'TBD'."
Result: a clean action log in under 30 seconds, ready to paste into your project tracker.
2. Email drafting
"I need to email a supplier to push back on a proposed price increase of 12%. Our position is that the increase is above the rate agreed in our contract and we expect them to honour the original terms. Tone should be firm but professional. Keep it under 200 words."
Claude drafts it. You adjust the one or two things it doesn't know (the supplier's name, a specific contract reference). Done in 2 minutes instead of 15.
3. Weekly report summarisation
Paste your team's updates and ask:
"These are individual updates from my team of 8. Write a one-page executive summary for my director. Lead with the three most significant achievements this week. Flag any risks or blockers. Avoid jargon."
This takes the cognitive load off synthesising 8 updates into 1 narrative — Claude does the first pass.
4. Performance review language
"I need to write a performance review comment for a team member who consistently meets deadlines and produces high-quality work but rarely offers ideas in meetings or contributes to team discussions. The tone should be constructive and forward-looking. The company uses a 'strengths / development areas / goals' structure."
Claude gives you draft language. You adjust it to match what you know about the individual. The blank-page problem disappears.
5. Briefing doc from bullet points
"Turn these rough bullet points into a structured two-page briefing document for senior stakeholders. Use plain English. Include an executive summary, background section, key considerations, and recommended next steps."
Then paste your bullets. Claude produces a coherent document structure; you refine the content.
The iteration principle
Claude's first answer is a draft, not a finished product. Treat every response as version one.
If the first output is 80% right, do not start over — refine it:
- "That's good, but make the tone more direct and cut it by half."
- "The third paragraph is too technical for a non-specialist audience — simplify it."
- "Add a section on the financial implications."
This back-and-forth is how professionals use Claude effectively. You get from rough to polished in 3-4 exchanges rather than rewriting from scratch.
What to do when output is wrong
If Claude gets something wrong, tell it what is wrong and ask again. Do not just accept incorrect output, and do not start a new conversation — correct it in the same one:
"That liability figure is wrong — it should be £50,000, not unlimited. Update the summary with the correct figure."
Or:
"The tone is too casual for a board communication. Rewrite it in a more formal register."
Claude remembers the context of the current conversation. Corrections in-context are faster than starting fresh.
What to tell your team
As a manager, your team will take their cue from you. A few things worth making explicit:
"Use Claude for first drafts, not final decisions." Set the expectation that Claude output gets reviewed before it goes anywhere significant.
"Tell me when you've used it." Visibility is not surveillance — it is sensible workflow awareness. If a team member tells you "I used Claude to draft this report," you know to review it with the same eye you would for any first draft.
"Ask Claude to explain things you do not understand." Claude is a patient explainer. If someone does not understand a contract clause, a financial concept, or a technical term, asking Claude is faster than searching Google and usually produces a clearer, more contextualised answer.
"Do not put sensitive data in." This is covered in the next lesson — make sure your team knows the data rules before they start.
Key takeaway
Context + Task + Format. Give Claude those three things and iterate. It handles the blank-page problem; you handle the judgement. The managers who get the most value from Claude are the ones who treat it as a capable first-draft partner, not a magic answer machine.
📖 Official Documentation See this in practice in Anthropic's live support docs: