Ask Like a Real Human

Before diving in, complete Ask Claude to Remember Things so you arrive with persistent context already working and can focus on prompt structure instead of setup.

Most people type into Claude the same way they type into Google: short keywords, no context. That works for search engines because Google is looking for a matching page, not trying to understand your situation. Claude is doing something different. It is predicting the most useful response to everything you wrote. Give it keywords and it predicts a keyword-level answer. Give it a real situation and it predicts a real answer.

Here is the before and after: Someone types: 'Help me write a performance review.' Claude produces a generic template. The same person types: 'I manage a 4-person design team. I need to write a performance review for a senior designer who consistently does great work but misses deadlines. The review goes to HR and should be professional, honest, and constructive. Keep it under 300 words.' Claude now has role, context, the specific challenge, the audience, the tone, and the length. The second version takes about 45 extra seconds to write and produces something that is actually usable.

Think of Claude as a smart new colleague on their first day. They are capable, but they know nothing about your world. You would not hand a new colleague a sticky note that says 'email.' You would give them a two-minute brief. That brief is your prompt. Two to four specific sentences, covering what you need, who you are, and what a good result looks like, is usually enough to unlock a response that requires no rewriting.

The 'what good looks like' piece is the most commonly skipped. Without it, Claude guesses. It almost always guesses wrong about length, tone, or format.

I need help with [describe the actual task in one sentence]. Here's the context: I am [who you are or what role you're in]. The situation is [what's happening and why this task matters right now]. A good result for me would [describe what success looks like, even roughly]. Please keep your response [short and direct / detailed with examples / in bullet points, whichever fits].

Here's a performance review for your senior designer, Marcus, that is honest and constructive without being harsh:

'Marcus consistently delivers work that raises the bar for the team. His concepts are original, his execution is polished, and his instincts for what the client actually needs are sharper than anyone else on the design team. The one area that needs attention this year is delivery timing. On three of our six major projects, final assets arrived one to three days after the agreed date, which created downstream pressure on the development team. Marcus is aware of this and we have discussed it directly. The goal for next year is maintaining the same quality bar while hitting 90% of milestones on time. I am confident he can do both.'

This is 113 words. Want me to add a section on goals for next year or adjust the tone to be slightly more or less direct?

What good looks like

• You wrote a prompt with at least three pieces of context: what you need, who you are, and what a good result looks like
• The response felt tailored to your situation rather than generic
• You would actually use or share the response without major rewrites
• You included the 'what good looks like' piece, not just the task description
• You ran the same task with a short keyword version and a full-context version, and the difference was obvious