Why Generic Summaries Miss What Matters
When you ask Claude to "summarize this document," it produces a balanced overview of all major points weighted roughly equally. Useful if you need general orientation. Not useful if you have a specific purpose -- a decision to make, a question to answer.
Generic summaries trade nuance for coverage. Targeted summaries trade coverage for relevance. For most professional use cases, relevance is more valuable.
The most useful addition to any summary request: tell Claude what you are going to use the summary for. "Summarize this contract with a focus on the termination clauses and any unusual obligations" produces a more useful output than "summarize this contract."
Summary Request Formats That Preserve Nuance
Decision-focused: "I am deciding whether to [X]. What does this document say most relevant to this decision? What nuances should I be aware of?"
Question-focused: "Answer these three specific questions using only the content of this document: [Q1, Q2, Q3]. Quote the relevant passages."
Action-focused: "What do I need to do based on this document? List specific actions required, by whom, and by when."
Tension-focused: "What are the most important tensions, trade-offs, or qualifications in this document? I already understand the main argument -- I want the nuance and caveats."