Brag Document

A running personal log of accomplishments, impact metrics, and wins maintained throughout the year — the single most practical tool for performance reviews, promotion packets, salary negotiations, and job searches.

A brag document (also called a hype doc, wins log, impact doc, or accomplishment tracker) is a private, ongoing record you maintain throughout your employment — capturing projects completed, problems solved, metrics improved, feedback received, and contributions made beyond your formal job description. The concept, popularized by engineering manager Julia Evans and widely adopted across industries, is simple: write things down as they happen rather than trying to reconstruct your contributions from memory six months later when a review cycle or promotion decision arrives.

The timing problem is the core reason brag documents matter. Performance reviews, promotion packets, and salary negotiation conversations all require you to articulate your impact — specifically, with numbers and context. Most people try to do this in the week before their review, relying on memory and whatever's still visible in Slack or their email. The result is a generic, underselling account that misses the projects from eight months ago, forgets the exact metric improvement, and omits the cross-functional help that didn't make it into any system. A brag document solves this by moving the recording to the moment the work happens, when details are precise and context is fresh.

What to include is broader than most people assume. The obvious entries are major project completions and measurable outcomes (reduced churn by 12%, shipped the redesign two weeks early, closed $340K in new pipeline). But equally important are: positive feedback from peers, managers, or customers (copy it verbatim — exact quotes carry more weight than paraphrases in a promotion packet); mentorship or onboarding help you provided that isn't in your job description; processes you improved that saved time for others; things you did that made your manager's job easier; and problems you prevented that no one will remember because they never became visible crises. The invisible wins are especially worth capturing because no one else will.

Beyond performance reviews, a brag document serves as the foundation for every career advancement conversation: it feeds your promotion packet directly, gives you concrete evidence for a salary increase request, provides the raw material for behavioral interview stories when you're job searching, and helps you evaluate whether your current role is actually advancing your career. Many practitioners suggest a weekly or bi-weekly cadence — a 10-minute Friday ritual to capture that week's contributions before the weekend wipes the details. Stored privately (not in company systems), the document stays with you across jobs and becomes a career-long record of your professional history.

What to Track

  • Projects shipped or milestones hit: scope, your specific role, the outcome, and any metric you can attach (revenue, time saved, error rate reduced, users affected).
  • Feedback received: copy exact quotes from Slack, email, or verbal comments you noted immediately after. 'Great job' is forgettable; 'your analysis is what unblocked the leadership decision' is promotable.
  • Cross-functional impact: work you did that helped another team, unblocked a dependency, or solved a problem outside your immediate scope — this is evidence of operating at a higher level.
  • Invisible wins: the bug you caught before it deployed, the customer call you de-escalated, the process change that saved hours per week. These disappear from organizational memory faster than any other category.
  • Growth and learning: new skills developed, courses completed, stretch assignments taken — context for 'demonstrating readiness for the next level' language in promotion conversations.

How to Use It

  • Before performance reviews: pull the document and identify your top 3–5 impact stories per review dimension. Don't just list everything — curate.
  • Before promotion conversations: map your entries to the specific competencies defined in your company's career ladder for the next level. Show your manager you're already operating there.
  • Before salary negotiations: quantify the ROI of your work. 'I contributed to $X in revenue and Y efficiency improvements' is a much stronger anchor than 'I worked really hard.'
  • Before job searching: these are your behavioral interview stories. Each entry is a potential STAR response already partially drafted.
  • Quarterly self-audit: read back three months of entries and ask whether the pattern of work reflects the career you want to build. If not, the document tells you what to change before someone else notices.

Example

A product designer starts a brag document on her first day at a new company, updating it every Friday afternoon. In month three, she notes: 'Redesigned the onboarding flow — reduced time-to-first-value from 8 minutes to 4.5 minutes (per Analytics, week of Mar 10). PM said in Slack: "this is the cleanest UX decision we've made in a year."' In month seven, she gets ready for her annual review. Without the document, she'd remember the redesign vaguely but forget the metric and lose the quote. With it, she pastes the exact data into her self-assessment and cites the PM's exact words in her peer review request. Her manager submits her for a promotion. The promotion packet's evidence section is built almost entirely from her brag document, and she's promoted in the next cycle.