Don't Bury the Question in Backstory

A common mistake of writing a long run-up — background, history, caveats, feelings about the problem — and only at the very end, almost as an afterthought, stating what you actually want. The real request gets lost in the preamble, and the answer misses the point.

When the ask is buried under paragraphs of backstory, two things go wrong. Claude weights the abundant context heavily and the single-line request lightly, so it responds to the story rather than the question; and a request tucked at the end of a wall of text is easy to under-serve. Leading with a clear statement of what you want — then following with the context that supports it — makes the target unmistakable. The backstory still helps, but it's now in service of an ask Claude can see, not a substitute for one it has to hunt for.

Recognise this whenever your prompt starts with 'So, some background…' and runs several paragraphs before the actual question. Also when an answer addresses your situation eloquently but doesn't do the thing you needed — that's usually a buried ask.

This is a mistake to avoid, not a technique to apply. The one nuance: some context genuinely must come first to make the ask intelligible — in that case, still signpost the request clearly ('Here's my question, then the background') rather than hiding it at the end.

What I need: <the specific ask, stated first and plainly>.

Context that matters for it:
- <relevant background 1>
- <relevant background 2>

Given that, <restate the ask as an instruction with the output format you want>.

A prompt opens with five sentences about a stalled project, team frustration, and a looming deadline, ending with '…anyway, thoughts?' Claude returns empathetic commentary on the situation. Rewritten to lead with 'Give me a three-step plan to unblock this project by Friday,' followed by the same context, it returns the actionable plan that was wanted all along.

Use a two-part shape for anything complex: a one-line 'ASK:' at the top and a 'CONTEXT:' block beneath. The label forces you to articulate the request as a single clear sentence before you pour out the backstory — which is often where you realise you hadn't actually decided what you were asking for.

• Ending a long message with a vague 'thoughts?' instead of a specific instruction — the buried ask and the vague ask compound.
• Assuming Claude will infer the real question from the emotional weight of the story; it answers what's stated, not what's implied.
• Front-loading caveats and disclaimers so heavily that the request reads as optional.