Brain Dump to Memo
Release mode Alpha
- Level
- Beginner
- Format
- individual or pairs
Convert rough thinking into a memo while keeping uncertainty, disagreement, and emotional context visible where they matter. You will separate observation from interpretation and proposal, locate unsupported claims, and decide what a human must restore or verify.
Improve usability without laundering uncertainty
What you will make
Convert rough thinking into a memo while keeping uncertainty, disagreement, and emotional context visible where they matter. You will separate observation from interpretation and proposal, locate unsupported claims, and decide what a human must restore or verify.
Lab materials
Use during the lab
-
- Lab Notebook Interactive · An optional place to record the work and download a local copy.
-
- Learner guide Markdown
Go deeper
- Related articles
-
- Facilitator guide Markdown
Before you start
Level and format: Beginner; individual or pairs
You need: a non-sensitive brain dump, a writing surface, and optionally an AI chat tool. Never paste confidential, regulated, personal, or identifiable material into a tool that is not approved for it. Invent or redact a scenario when unsure.
The core idea
Structure can clarify thought, but it can also make a suspicion sound like a fact or turn urgency into bland certainty. A memo is decision support, not an excuse to erase the conditions under which a decision is being made.
Turn rough notes into a reviewable memo
Complete the activity here. Open the optional Lab Notebook beside this page when you want a place to record your work.
-
Start safely
Write or select 150–300 words of raw notes. Mark facts you can support, impressions, feelings, unresolved disagreement, and next-step ideas.
-
Name purpose and reader
Complete: “This memo helps ___ decide/understand ___.”
-
Request organization, not invention
Example prompt: “Organize these notes into a memo for [reader]. Preserve uncertainty and disagreements. Do not add facts. Label observations, interpretations, proposals, and open questions when appropriate.”
-
Inspect the first memo
Highlight any stronger claim, missing disagreement, flattened urgency, or invented transition.
-
Repair it
Use a structure that fits: purpose, background, observations, interpretation, risks or concerns, proposed actions, open questions, and next steps. You may change the headings.
-
Validate
Mark every claim that needs a source, owner, or confirmation. Add the open questions and a concrete next step.
Check your result
-
Can a reader tell what happened versus what someone thinks it means? Has a concern been turned into a factual conclusion? Did the final memo preserve a disagreement that affects the decision? Is the tone appropriate without hiding urgency?
-
AI cannot independently verify source material, consent, legal requirements, or whether a workplace claim is fair. Ask an appropriate human to review consequential memos. For an extension, have a partner annotate claims without seeing the brain dump, then compare what the structure made clear or hidden.
-
A polished result is not proof that it is accurate, complete, safe, or appropriate. Keep unresolved questions visible and verify consequential claims outside the tool.
You are done when
Reflect: What did organization improve? What had to be put back? What should the recipient not infer? Save a redacted brain dump, a structure map, first memo, correction notes, final memo, and privacy statement. Done means a reader can identify observations, interpretations, unresolved questions, and a next step. Offer plain-text source files and flexible pacing; redact names before sharing.
Try another version
These are optional extensions, not additional completion requirements.
Learner Map
Tracks
Modules
Help us improve this Activity
Tell us what helped, what slowed you down, or what you needed but could not find.