Claude prompt for data analysis: Decision Log (With Examples)
Claude · Data Analysis · With Examples
You are a exacting editor using Claude for data analysis, specifically decision log.
Job: what we chose and why.
Audience: ops. Constraint: revisit date.
Working style: practical. Optimize for few-shot samples and before/after pairs.
Process:
1. Restate the brief in one sentence and list missing facts as questions.
2. Draft the artifact.
3. Stress-test it against the constraint.
4. Return a final version plus 3 numbered improvements.
Output contract: use headings, short paragraphs, and concrete examples. No filler. No invented statistics.
If information is missing, make the smallest reasonable assumption and label it.Looking for a Claude prompt for decision log? Start here — the with examples angle focuses on few-shot samples and before/after pairs. Most failed runs trace back to missing audience or success criteria — this prompt adds both. The with examples version uses practical language and targets few-shot samples and before/after pairs.
When to use this prompt
For Anthropic models, data analysis prompts fail when they mix strategy and execution. This decision log brief separates the job so you can iterate once, not ten times. Swap only nouns when adapting — keep the process intact.
Why this prompt works
- Separates draft from critique so you can steal the structure later.
- Names a clear job so Claude does not wander into generic advice.
- The with examples angle adds few-shot samples and before/after pairs without extra fluff.
- Keeps data analysis vocabulary specific instead of buzzwords.
- Uses practical language that matches how practitioners actually brief work.
How to use it in Claude
Use practical follow-ups only — mixing tones mid-thread confuses Anthropic models. Name the success metric aloud: what we chose and why. If the draft cannot pass it, do not polish prose yet. This With Examples path is for ops who care about what we chose and why. Paste the prompt into Claude and replace bracketed details with your facts. If the first answer is vague, reply with the constraint again: revisit date.
Have Claude list assumptions about data analysis before drafting. Delete any you cannot defend. For decision log in data analysis, the failure mode is usually no example. This prompt blocks that by design — especially "revisit date". Expect two minutes customizing and two minutes editing for With Examples output. Anthropic models still need your facts for decision log; they cannot invent metrics or brand rules. analysts and operators teams bookmark slug decision-log-examples when few-shot samples and before/after pairs matters.
Step-by-step
- Open Claude and paste the prompt block unchanged.
- Replace placeholders with your project facts (ops, offer, timeline).
- Confirm the constraint is still visible: revisit date.
- Because this is the With Examples variant, prioritize few-shot samples and before/after pairs over length.
- Reply with one fix list, then regenerate the final version only.
Example output
Example output shape: H1 with Decision Log, 3 short sections, bullet list of recommendations, closing line that states revisit date. Facts you supply appear; nothing invented.
Common mistakes
- Accepting the first draft without checking what we chose and why.
- Asking for decision log plus three other jobs in one message.
- Using the With Examples prompt but editing it into a vague one-liner.
Expert notes
Slug decision-log-examples: a analysts and operators-oriented data analysis brief. Queries, insights, charts, and decision memos. Pair it with one real asset from your portfolio before the second run.
Refresh quarterly: Claude models change. Keep constraints; update examples. Mark the page stale if revisit date no longer matches policy.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a decision log piece. |
| This prompt | You need a usable draft | Role, constraint, steps, and output contract included. |
| Plus examples | Voice must match yours | Paste 120 words of your writing or a still you like, then rerun in Claude. |
Key takeaways
- The With Examples variant is for few-shot samples and before/after pairs.
- Ship a draft, then tighten. Do not chase a perfect first token.
- State the job (what we chose and why) in one line before any style talk.
- ops should recognize themselves in the first paragraph.
- Keep revisit date visible in the prompt, not only in your head.
FAQ
- What is a Claude prompt for decision log?
- It is a structured brief that tells Claude how to produce data analysis output for ops. This with examples version stresses few-shot samples and before/after pairs and keeps "revisit date" in the instructions.
- How do I customize this Claude data analysis prompt?
- Swap project nouns, paste one real example, and leave the process steps intact. The constraint "revisit date" should stay unless your brief truly changed.
- Why use the with examples angle for decision log?
- Different angles solve different failures. With Examples helps when ops need few-shot samples and before/after pairs. It is not longer for its own sake — each line has a job.
- Is this Claude prompt updated for 2026?
- Yes. Pages follow our SEO Bible, refresh on a rolling schedule, and include current best practices for Anthropic models. Always verify facts before client delivery.