Editing, Adapting, Refining, and Comparing Output
CoreEdit, adapt, refine, and compare Claude's output · Difficulty 1/5
Explanation
Raw Output Is Usually a Draft
Claude's first response to a request is rarely the final deliverable. Associates treat it as a draft and apply four standard moves before it goes anywhere:
| Move | What it means |
|---|---|
| Edit | Correct factual, logical, or structural errors |
| Adapt | Reframe the content for a different audience -- e.g., an engineer's answer rewritten for executives |
| Refine | Improve tone and structure without changing the underlying content |
| Compare | Generate alternative versions and pick the strongest |
Adapting for Audience
The same underlying content often needs different presentations: a detailed technical answer reframed for executives, a long explanation shortened for a Slack message, a casual draft formalized for a client. Adapting means changing the presentation to fit the reader, not changing the underlying facts.
Comparing Alternatives Is a Standard Move
Rather than accepting the first draft, asking Claude for two or three variations -- and choosing the best one, or asking it to rewrite for a different reader -- is a normal, expected technique, not an extra or unusual step. It costs little and often surfaces a stronger framing than the first attempt.
Why This Matters for Evaluation
Editing, adapting, refining, and comparing are downstream of evaluation: they are what an Associate does *after* checking accuracy, completeness, and hallucination risk, to turn a validated draft into a deliverable that fits its destination and reader.
Key Takeaways
- Treat Claude's first response as a draft, not a finished deliverable
- The four standard moves are editing for correctness, adapting for audience, refining tone/structure, and comparing alternatives
- Adapting changes presentation for the reader (executive vs. engineer, Slack vs. client email) without changing the underlying facts
- Requesting multiple variations and picking the strongest is a standard, expected technique, not an extra step
Related Concepts
Inline, Artifacts, and Structured Output as Distinct Surfaces
Inline suits short, conversational answers; Artifacts suit substantial, iterate-and-share deliverables; structured data suits output feeding another system
Code Execution: Computing Numbers Instead of Writing Them
When a number must be right, have Claude compute it via code execution rather than generate it in prose