How to Write a Brag Document (and Actually Use It)

Brag document template

Copy this near the top of your document so the next entry is easy to write.

Date:
Project / area:

What happened:

What I did:

Why it mattered:

Evidence:

- Metric:
- Stakeholder:
- Link:

Where I might reuse this:

- Performance review:
- Resume / CV:
- Interview story:

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.

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.

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:

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.

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, four different outputs:

1. Raw brag doc entry

   Redesigned onboarding flow. Activation went from 23% to 41% over 6 months. 3 engineers + product designer. VP sponsored.

2. Resume bullet

   Led cross-functional redesign of user onboarding, increasing activation rate from 23% to 41% within 6 months.

3. 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.

4. Review evidence

   This became one of the clearest examples of cross-functional leadership, measurable impact, and product judgment from the review period.

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:

Brag document vs. career journal

If a brag document in a spreadsheet is working for you, keep going. The habit matters more than the tool.

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.

Examples by role

Engineer: "Reworked the retry path for payment webhooks after two customer-impacting failures. Error rate dropped from 1.8% to 0.2% over the next release cycle."

Product manager: "Cut two low-confidence onboarding features from the launch scope and moved the team toward the activation step with the strongest support-ticket evidence."

Marketer: "Rebuilt the webinar follow-up sequence around three audience segments. Reply quality improved, and sales reused the copy for outbound."

Manager: "Changed weekly planning from status updates to blocker review. Two quieter team members started raising risks earlier, which helped us catch a release dependency before it slipped."

FAQ

How long should a brag document be?

Long enough to contain the evidence. A good document may be messy during the year and tighter before a review. Do not edit too early; capture first, shape later.

Should I include small wins?

Yes, if they show judgment, consistency, or useful impact. Small entries often become patterns when you review several months at once.

Is a brag document private?

Usually, yes. Treat it as your working file. Share selected examples with a manager, recruiter, or interviewer only when they are relevant.

How is this different from a career journal?