Module 2 · Lesson 2.1

Brain-Dump Before You Prompt

3 min read · Updated

Most people open an AI tool and type something like "write a blog post about remote work". The model has nothing to go on except the topic, so it writes the average post about remote work. You then spend twenty minutes trying to make it yours.

There's a faster way. Spend five minutes writing down what you know, badly, before you prompt. Then hand the mess to the model.

Why a messy brain-dump beats a clever prompt

Remember from lesson 1.1 that a model picks the most likely next word given what it's been told. If all it's been told is a topic, the likely words are generic. If it's been told that your team of six went remote in March, lost their Friday lunches and gained two hours a day, the likely words are suddenly about you.

Prompt tricks like "write in a human tone" or "be creative" don't add information. A brain-dump does.

How to do a brain-dump

Set a timer for five minutes. Type, or record a voice memo and transcribe it. Don't fix spelling. Don't write sentences if you don't feel like it. Answer these questions:

  1. Who is going to read this, and what do they already know? "My manager, who missed the meeting" is more useful than "a professional audience".
  2. What happened, or what's true? Dates, numbers, names, quotes. Anything you'd have to look up.
  3. What do you think about it? Your opinion, even if it's half-formed. "Honestly, the new process is slower but people like it more."
  4. What's one example or story? A specific moment beats a general claim every time.
  5. What should it not say? Things to avoid, sensitive topics, claims you can't back up.

That's it. You'll end up with somewhere between 100 and 300 words of rough notes. That's the raw material the model was missing.

A worked example

Say you need a short update for your company newsletter about a new returns policy. Here's a real-feeling brain-dump:

readers = our 40 store staff, not customers. they hate policy emails. new rule from nov 1: 60 days not 30 for returns. no receipt needed if it's in our system. why: complaints went up a lot in summer, Dana in Leeds store had 3 shouting customers in one week. i think it's good, staff won't have to say no as much. worry: people will think they have to accept anything, they don't, damaged stuff still no. keep it short, they read on their phones.

Then the prompt:

Write a short newsletter update for our store staff using only the notes below. Keep it under 150 words. They read on their phones and skim policy emails, so put the change in the first sentence. Use plain words and a friendly tone. Don't add facts that aren't in my notes. Notes: [paste your brain-dump here]

The draft you get back will mention November 1, 60 days, the Leeds store and damaged items. It'll still need an edit, but the hard part, the content, is already yours.

"Don't add facts that aren't in my notes"

Keep this line in every prompt built on a brain-dump. Models fill gaps with plausible details, and plausible isn't the same as true. A made-up statistic in your newsletter is worse than a generic sentence. If the draft needs a number you don't have, it should leave a gap you can see, not invent one.

A useful extra line: "If something important is missing from my notes, ask me instead of guessing." Many tools will then come back with two or three questions before drafting. Lesson 2.4 builds a whole method around this, using AI as an interviewer.

When you can skip it

You don't need a brain-dump to reformat a table or fix grammar. Skip it when the content already exists and you only want help with form. Use it whenever the writing should contain your knowledge, your experience or your opinion. That's most writing that matters.

Try this

Pick something you need to write this week. First, prompt an AI tool with just the topic and save the result. Then do a five-minute brain-dump and prompt again with the notes. Paste both drafts into the AI detector. Look at the "Specific details" signal in particular. The second draft usually scores much more human before you've edited a word.