How to Write a Brag Document (and Actually Use It)
A brag document is the simplest career habit that works: a running list of what you did and why it mattered. Most people start one and quit in three weeks. Here's how to not be most people.
A brag document is a running list of things you did at work that you'd want to cite later. The name comes from the tech world, but the practice is useful for anyone who has ever sat in a performance review and thought, "I know I did more than this."
When it happens
“Led vendor scoring redesign for 40 suppliers. Renegotiated 2 contracts using the data — saved EUR 85K/year. Finance adopted the framework org-wide.”
6 months later
“I think I did something with vendor contracts? We saved some money. Not sure how much.”
It's not a diary. It's not a task list. It's not a polished self-assessment. It's the raw material that those things come from. You write down what happened, what you did, and what changed as a result. Later, you turn those entries into resume bullets, review self-assessments, or interview stories.
The concept has been around for years. Julia Evans wrote about it. It gets shared on Reddit and HackerNews every few months. Plenty of people have started one.
Almost nobody keeps it going past three weeks.
What a brag document entry looks like
Each entry is a few fields. Date, what you did, impact, and enough context to jog your memory six months from now.
Engineering manager
Mar 2026 -- Redesigned onboarding flow. Activation rate went from 23% to 41% over six months. Worked with 3 engineers and a product designer. VP sponsored the initiative.
Operations lead
Jan 2026 -- Built vendor scoring system for top 40 suppliers. Renegotiated two contracts using the data, saving EUR 85K annually. Finance asked to adopt the framework for all procurement.
Marketing coordinator
Feb 2026 -- Ran first partner webinar series. 3 sessions, 1,200 total registrations, 34% attendance rate. Pipeline sourced from attendees: EUR 220K. Repeated quarterly after results.
HR business partner
Mar 2026 -- Designed manager feedback training after engagement survey flagged "quality of feedback" at 3.1/5. Ran 6 sessions across the org. Follow-up pulse survey: 4.0/5. Attrition in participating teams dropped 12% over the next quarter.
Notice the pattern. Short. Factual. Specific numbers where they exist. Enough context that you'll remember the story, but not so much that writing the entry takes more than two minutes.
Why most brag documents die
The typical lifecycle looks like this:
Week 1: Enthusiasm
You create a document. You write four entries. Some of them are even from past months. This feels productive.
Week 2-3: Drift
You forget on Friday. You tell yourself you'll catch up Monday. Monday has its own problems. The document sits untouched.
Week 4-6: Guilt
You open the document, see the gap, and feel like you've already failed. The blank space between your last entry and today feels insurmountable. You close the tab.
Week 7+: Abandoned
The document joins your other well-intentioned systems -- the reading list, the workout log, the budget spreadsheet. You'll start fresh next quarter. You won't.
There are two failure modes here, and they usually work together.
The fix is boring (and that's the point)
One recurring calendar reminder. Friday at 4pm works for most people -- the week is still fresh, you're winding down, and it takes less time than making coffee.
Three fields per entry: what you did, impact, context. No editing for quality. No going back to polish old entries. If the entry takes more than two minutes, you're overwriting.
What I did: One sentence. What happened this week that you'd want to cite later.
Impact: Numbers if you have them. "Reduced X by Y" or "Shipped Z to N users." If no numbers yet, describe the outcome in plain language.
Context: Who was involved, what constraints existed, why this mattered. One or two sentences.
After a month, you'll have four entries. After three months, twelve. After a year, fifty. None of them took more than two minutes.
What to do with it
This is where most brag document guides stop. "You'll have it for your review!" Great. But a list of raw entries isn't useful on its own. It needs to become something.
Here's the progression. Same achievement, three different outputs:
Raw brag doc entry
Redesigned onboarding flow. Activation went from 23% to 41% over 6 months. 3 engineers + product designer. VP sponsored.
Resume bullet
Led cross-functional redesign of user onboarding, increasing activation rate from 23% to 41% within 6 months.
STAR interview story
Situation: activation was stuck at 23%, and the VP of Product flagged it as a company priority. Task: redesign the onboarding experience without disrupting the existing user base. Action: assembled a 4-person team, ran a 2-week discovery sprint, shipped iterative changes over 3 months. Result: activation hit 41% at the 6-month mark. The framework we built became the template for all new feature launches.
The raw entry took two minutes to write. The resume bullet took thirty seconds to derive from it. The STAR story took five minutes because all the details were already there.
After three months of entries, the raw material starts compounding:
Interviews
Pull STAR stories without the night-before panic — the details are already there.
Resumes
Write bullets with real numbers instead of vague claims. No more staring at a blank page.
Reviews
Walk into your performance review with examples from every quarter, not just the last six weeks.
Patterns
Spot what kind of work you gravitate toward — and what you're quietly great at.
Promotions
Build a case grounded in evidence, not feelings. Managers respond to specifics.
Confidence
Stop second-guessing your impact. The record speaks for itself.
Brag document vs. career journal
A brag document captures wins. A career journal captures the full picture. Here's the difference:
Brag document
A list of what you did and why it mattered. Wins, impact, numbers. The evidence you need for reviews and resumes.
Career journal
Everything a brag doc captures, plus: challenges you navigated, decisions you made, feedback you received, things you learned. The context that makes the wins meaningful.
If a brag document in a spreadsheet is working for you, keep going. The habit matters more than the tool.
If you find yourself wanting the entries to turn into something -- polished resume bullets, tagged interview stories, patterns across months of work -- that's where a purpose-built career journal adds value. It takes the same two-minute Friday habit and connects the dots for you.
Either way, the starting point is the same. Open a document. Write down one thing you did this week that mattered. Do it again next Friday.