A brag document is evidence, not bragging

What it is

A brag document is a personal file where you record outcomes and decisions from your own work, with dates. The practice comes from engineering organizations, and the idea is simple: instead of reconstructing six months the night before a performance review, accumulate as you go.

Despite the name, the content is not bragging. A well-kept brag document reads like a list of facts without adjectives: what you did, what changed, why you chose that path.

Why it matters

Your evaluator does not remember your work as well as you do. And you remember less than you think: a half-year review covers 26 weeks, and unrecorded memory overweights the last month while the first half of the period disappears.

With a record, the review conversation shifts from claims to evidence. The same material serves promotion cases, salary negotiations, and job changes.

What to write

Date every entry, and keep whichever of these five applies.

• Outcomes — numbers if you have them, before-and-after if you don't
• Judgment — why this approach; rejected alternatives are often the better material
• Scope — 40 screens, 12 stores, 3 markets: countable facts
• Feedback and adoption — was the proposal shipped, did other teams follow the standard
• Glue work — reviews, onboarding, documentation. It vanishes from evaluations, which is exactly why it belongs in the record

Remove the adjectives and it stops being bragging

"Successfully led the redesign" cannot be verified. "Shipped to 12 stores, and the new-store guide followed this standard afterward" can. Keep only verifiable sentences and the document becomes evidence rather than self-praise — and it holds up in reviews and interviews.

When to write it

Batch-writing turns memory into invention. The sustainable cadence is five minutes once a week, one entry at a time. Scan it quarterly and merge related entries, and the review material writes itself.