LearnAI home

Foundations · Lesson 3

Be Specific or Be Sorry

Why 'write email' gets you garbage and what to say instead.

The intern on day one

Imagine delegating to a brilliant new intern. Genuinely brilliant: top of their class, reads everything, types 200 words per minute. It's also their first day, and they know nothing about your company, your customers, or your feelings about the phrase "circling back."

You wouldn't say "handle the email thing" and walk away. You'd brief them: who it's for, what it needs to accomplish, what tone fits, what to avoid.

An AI model is that intern, forever. Every prompt is day one. Specificity is the briefing.

"Write email" vs. an actual brief

Here's what the difference looks like with a real workplace task.

❌ Weak prompt

Prompt

Write an email about the deadline

Output

Subject: Important Update Regarding the Deadline. Dear Team, I hope this message finds you well. I am writing to inform you about an important update regarding our upcoming deadline. Please ensure all necessary actions are completed in a timely manner. Best regards.

Which deadline? Moved earlier or later? Who's the audience? The model didn't know, so it generated the email equivalent of elevator music: 60 words that say nothing.

✅ Good prompt

Prompt

Write a short email to my project team (5 engineers, casual culture). The client moved the Phase 2 deadline from March 14 to March 7. I need everyone to flag blockers by Friday. Tone: calm, not panicked. Under 100 words. Subject line included.

Output

Subject: Phase 2 moved up to March 7, blockers due Friday. Hey team, quick heads-up: the client pulled the Phase 2 deadline in a week, to March 7. Totally doable, but I want zero surprises. Please drop any blockers in the thread by Friday EOD so we can sort them early. Thanks. We've got this.

Every question answered before it was asked: who, what changed, what action, what tone, how long. The output is send-ready. The prompt took 30 extra seconds; the output saved 15 minutes of rewriting.

What "specific" actually means

Specific doesn't mean long. It means the important decisions are made by you, not by the model's autocomplete instincts. The usual suspects to pin down:

  • Audience: your boss, a customer, five engineers, your HOA?
  • Goal: inform, persuade, apologize, get a reply by Friday?
  • Constraints: under 100 words, no jargon, must mention the refund policy
  • Tone: calm, playful, formal, firm-but-kind
  • The actual facts: names, dates, numbers. The model cannot invent your March 7 deadline; it can only invent a deadline, which is worse.

Every detail you leave out is a decision you're delegating to a random-ish process. The model doesn't leave blanks. It fills them with plausible guesses. "Plausible" and "correct" are different words for a reason.

Practice: brief the intern

Here's the same vague request, upgraded into a real brief. Notice how each line answers a question the model would otherwise have to guess.

❌ Weak prompt

Prompt

Write an email asking for time off

Output

Subject: Time Off Request. Dear Sir or Madam, I am writing to formally request some time off at some point for some duration. Thank you for your consideration.

No recipient, no dates, no tone, so the model defaulted to 'Victorian job applicant.' A time-off email without dates isn't a request; it's a vibe.

✅ Good prompt

Prompt

Write an email to my manager Dana (we're friendly but professional) requesting June 10-14 off for a family trip. Mention that Priya agreed to cover my on-call shift and that I'll finish the Q2 report before I leave. Keep it under 80 words.

Output

Subject: Time-off request: June 10-14. Hi Dana, I'd like to request June 10-14 off for a family trip. Priya has kindly agreed to cover my on-call shift that week, and I'll have the Q2 report wrapped up before I head out. Let me know if those dates work on your end. Happy to adjust if needed. Thanks!

Recipient, dates, coverage plan, tone, length: every decision made by you, not the dice. This one's ready to send.

Want a reusable version? Here's the brief-the-intern skeleton:

The delegation brief

Write [the thing] for [audience]. Goal: [what should happen after they read it]. Facts to include: [names, dates, numbers, and anything else only you know]. Tone: [pick one]. Length: [pick a limit]. Do not: [anything to avoid].

Checkpoint

Treat the model like a brilliant day-one intern: every unstated decision (audience, goal, facts, tone) gets filled with a guess, so state the ones that matter.

The 30-second rule

Before hitting enter, spend 30 seconds asking: what would a stranger need to ask me before doing this? Answer those questions in the prompt. Thirty seconds of briefing routinely saves thirty minutes of "no, not like that."

📝 Quiz

Question 1 of 3

Why does 'write an email about the deadline' produce a useless email?

Found this useful? Pass it on.