Your manager can’t remember what you did in March, and they’re the one writing your review. A brag document is how you stop losing credit for work you already did.
Quick answer: A brag document is a running list of your wins, the numbers behind them, and who noticed. Spend 10 minutes on it every Friday. Then, when a review, a raise conversation, or a job search shows up, you’re reading from notes instead of guessing from memory.
In my story brainstorm sessions, the most common problem isn’t a lack of accomplishments. It’s that people can’t remember them. They know they led a big migration two years ago, but they can’t tell me what it saved, who asked for it, or what would’ve broken without it. So we spend half the call doing archaeology instead of building stories.
Why a brag document beats your memory
Your memory is a bad record-keeper for your own career, for two reasons.
First, you forget the details that make a win count. You’ll remember “I fixed the onboarding flow.” However, you won’t remember that support tickets dropped the next month, or that a VP mentioned it in an all-hands. The details are the proof, and they fade first.
Second, your manager remembers even less. They’ve got eight direct reports, their own boss, and their own review to write. As a result, reviews tend to lean on the last month or two of work. That’s recency bias, and it means your best project from February is competing with whatever went sideways in November.
The idea isn’t new. Julia Evans made the case for it in her 2019 post on brag documents. Her core point stuck with me: you don’t need to make your work sound better than it was. You need it on the record. You’re not inflating anything. Instead, you’re refusing to let it disappear.
What to put in your brag document
Keep it simple. One doc, one running list, newest at the top. For each win, capture five things:
- What happened: One line, in plain language. “Rebuilt the renewal email sequence.”
- The problem it solved: What was broken, slow, or at risk before you touched it.
- The number: Dollars, percentages, time, tickets, churn. If you don’t have an exact figure, write the ballpark. Directionally truthful beats blank.
- Who noticed: The Slack message, the email, the shout-out. Paste the link or a screenshot.
- Your part: What you specifically did, versus what the team did. People skip this line, and it’s the one interviewers probe hardest.
Also capture the work that’s hard to measure: the new hire you got up to speed, the process doc everyone now uses, the fight you headed off by calling a meeting early. That work rarely shows up in a dashboard, so it only survives if you write it down.
The 10-minute Friday routine
Here’s the routine I give clients. Put a recurring 10-minute block on your calendar for Friday afternoon, and answer the same three prompts every week:
- What did I finish, ship, or unblock this week?
- What would’ve gone worse if I hadn’t been there?
- Did anyone thank me, cite my work, or ask for my help?
Most weeks you’ll write one or two lines. Some weeks you’ll write nothing, and that’s fine. The value comes from the weeks where something happened and you caught it while the numbers were still sitting in your inbox.
One more rule: keep a copy somewhere you control. Your work laptop isn’t your career’s filing cabinet. When people get laid off, their access usually disappears fast, which is why I tell anyone in the first week after a layoff that whatever they didn’t save is probably gone. Strip anything confidential, keep the wins and the numbers, and store them in a personal doc.
How to use your brag document for reviews, raises, and interviews
The payoff shows up in three places.
Performance reviews. Before your self-review, send your manager a one-page summary pulled from the doc: your top five wins, each with its number. You’re not doing their job for them. Rather, you’re making it easy for them to write the review you earned.
Raise and promotion conversations. “I think I deserve more” is a feeling. “Here are four results from this year, and here’s what each one was worth” is a case. The doc turns the first into the second. And if the answer is still no, you’ve got what you need to decide whether changing jobs for a raise makes more sense.
Job searches. Every strong resume line and every interview story starts as an entry in that doc. The problem, your part, and the number map straight onto a resume bullet point formula and onto the stories you’ll tell in the room. So instead of spending your first week of a search trying to rebuild three years of work from memory, you open the doc and start picking.
FAQ
Is a brag document the same as a resume?
No. A resume is a short, edited sales document. The brag doc is the raw log you pull from to write it.
How often should I update it?
Weekly works best for most people, because the details are still fresh. If weekly won’t stick, do it monthly, but don’t wait for review season.
Should I share it with my manager?
Share a summary, not the raw log. A one-page list of top wins with numbers, sent before your review, is enough.
What if my work is hard to quantify?
Write down what would’ve happened without you, and who relied on it. A ballpark number or a named stakeholder is still evidence.
Your next move
If your list of wins is thin and you’re starting to wonder whether it’s time to look elsewhere, run the job search cost assessment. It takes 90 seconds and shows what a search would cost you each month before you start one.
If you’ve already got the wins and want to turn them into answers that land, read Interview Stories: Build Five, Not Twenty Single-Use Ones next.
If you’d rather have someone go through your wins with you and tell you which ones are worth building into stories, book a free strategy call.