What is a brag document?
A brag document is a running record of your accomplishments at work, kept so that review season doesn't depend on your memory.
The name is unfortunate, because the practice isn't bragging. It's record-keeping for a fact everyone learns the hard way: nobody remembers your work, including you.
In short
- A brag document lists what you shipped, fixed, prevented and helped with, plus the impact, updated as it happens.
- It exists because performance reviews cover 6 to 12 months and human memory covers about 6 weeks of work honestly.
- There's one entry type that makes a brag document dramatically more persuasive, and almost everyone omits it. We'll get to it.
What is a brag document?
A brag document is a single running file where you record your work accomplishments and their impact, so you can draw on it for performance reviews, promotion cases and updated CVs. The term was popularized in engineering circles by Julia Evans, whose brag documents post is the standard reference.
The format is unglamorous on purpose: one document, dated entries, plain sentences. "Led the March migration; cut deploy time from 40 minutes to 12" is the genre at its best.
Why keep a brag document?
You keep a brag document because reviews ask you to summarize a year and memory can't do it. By November, February's work is gone; what survives is the last month and whatever went wrong.
Play the scene forward without one. The self-review form is due Friday. You stare at it and list what you can remember, which means recent things, which means you rate a year of work by how the last four weeks felt. Your manager, reviewing eight people, remembers even less than you do.
The same negativity bias that makes you forget personal wins runs your work memory too: the incident you caused stays vivid, the ten quiet successes evaporate.
What goes in a brag document?
Record anything you'd want a fair judge to know: projects shipped and their impact, problems prevented, people you helped, skills you grew, and the unglamorous glue work that kept things moving. Numbers when they exist, honest description when they don't.
And here's the entry type we promised, the one almost everyone omits: disasters that didn't happen. The launch that went smoothly because you insisted on the extra test pass. The client who stayed. Prevention is invisible by definition, which is exactly why it needs a written record; nobody else will ever log it for you.
How is a brag document different from a wins journal?
A brag document is work-facing and written to eventually be read by someone else; a wins journal is private and written for you. Same behaviour underneath, different audience, and they feed each other well.
The private version catches everything as it happens, including wins too raw or personal for a work document. Come review time, you mine it for the professional entries. We wrote a practical guide to keeping a brag document for review season if you want the workflow.
The honest trade-off: a brag document only works if you update it while things are fresh. Started in November, it's just homework with a deadline.
FAQ
Is keeping a brag document arrogant?
No. It's memory infrastructure, and your manager generally wants you to have one, because it makes writing your review easier and fairer. Bragging is inflating the record; this is keeping one.
What if my work doesn't produce numbers?
Describe the change honestly instead: what was hard, what you did, what's different now. "Support tickets about onboarding stopped after I rewrote the guide" is evidence without a single metric.
How often should I update a brag document?
Little and often: a few minutes at the end of each week beats an hour each quarter. The freshness of the entry is what protects you from writing the whole year from memory.
The habit is easier if the catching part is effortless. Cookie Jar, our free wins app, is where the raw material lands the moment it happens: one line per win, private, on your phone, ready to be mined when the review form opens.