Getting Better Answers — Light Prompting Basics

A few small habits that make a big difference in the answers you get

You don’t need to learn a new language

“Prompting” just means the way you ask Claude for something. It sounds technical, but it isn’t. You’re already good at explaining things to people — the same instinct works here. This lesson covers a few small habits that noticeably improve your results.

Habit 1: Say what you’re trying to accomplish

Instead of just handing over raw material, say what you want done with it. Compare these two:

  • Less helpful: “Here are some notes.” (with notes pasted in, nothing else)
  • More helpful: “Here are my notes from today’s meeting. Turn them into a short summary with action items.”

The second version tells Claude exactly what “done” looks like, so it doesn’t have to guess.

Habit 2: Give context Claude can’t guess

Claude doesn’t know who the email is going to, how formal your office is, or how long you want the answer, unless you say so. A little context goes a long way:

Without context With context
“Write an email about the delay” “Write an email to a client explaining a 2-day shipping delay, apologetic but confident tone”
“Summarize this” “Summarize this for my manager, focused on what decisions she needs to make”

Tip: Picture describing the task to a smart new coworker on their first day. What would you tell them so they don’t have to guess? Tell Claude the same things.

Habit 3: Say the format you want

By default, Claude often uses bullet points and headers because that’s a safe general-purpose format. If you want plain paragraphs, a table, a short list, or a specific length, just ask.

  • “Write this as a plain paragraph, no bullet points.”
  • “Keep it under 100 words.”
  • “Put this in a table with two columns.”

Habit 4: Treat it like a conversation, not a single shot

You rarely need to get it perfect in one try. If the first answer is close but not quite right, just respond with what to change. This is normal and expected — not a sign you did something wrong.

Key idea: Good results come from a short back-and-forth, not from crafting one perfect sentence. Ask, look at the result, then adjust.

Putting it together

A strong request usually has three simple ingredients: the situation, the goal, and any details Claude wouldn’t otherwise know (audience, tone, length, format). You don’t need all three every time — but reaching for them when an answer misses the mark will fix most problems.

Try it: Take a request you’d normally type in one short sentence. Rewrite it adding the situation, the goal, and one detail about audience or format. Compare the two results.