Selfly

Build a brag document you’ll actually keep.

Add your wins as they happen and the document writes itself beside them. Five minutes on Fridays, and review season starts with everything written down.

  • Builds as you type
  • Saved in your browser
  • Copy to Notion or Google Docs
Brag document builderFree · saved in this browser · no sign up
1Your wins
Wins
2Your brag document

Brag document: [your name]

Update this every Friday. Five minutes now saves a whole evening at review time.

Goals for this period

  • [What you and your manager agreed you would focus on]

Wins

Shipped

  • [What you shipped] → [what changed because of it] ([link to the PR, ticket or doc])

Recognition

  • [Kind words from a teammate, customer or manager, with a link]
Guide

How to keep a brag document going.

A brag document only works if you keep it going. These four habits keep it to five minutes a week.

  1. 01

    Write it on Fridays

    Put a five minute reminder on your calendar. The week is still fresh, and a few lines a week add up to a full review by the end of the period.

  2. 02

    Link everything

    A link to the pull request, ticket or doc turns a claim into evidence, and helps you remember the details months later.

    Fixed the retry bug.

    Fixed the retry bug behind duplicate charges (github.com/acme/payments/pull/482).

  3. 03

    Write what changed, not just what you did

    If you don’t know the outcome yet, write the task now and add the result when you have it.

    Shipped the pricing cache.

    Shipped the pricing cache → checkout p95 from 900ms to 300ms.

  4. 04

    Count the invisible work

    Mentoring, interviews, incident calls and decisions rarely leave a trace in GitHub. Your brag document is where they stop being forgotten.

    Busy week, lots of meetings.

    Ran the incident bridge for the payments outage and wrote the review with 6 fixes.

FAQ

Questions, answered.

What is a brag document?

A running list of your accomplishments, kept as you go. When review season, a promotion conversation or a job search comes, you already have the record instead of trying to remember a year of work.

Is a brag document the same as bragging?

No. It is a private record of facts: what you did and what changed. Your manager has many people to keep track of, so giving them clear facts helps them argue for you.

Where should I keep it?

Anywhere you will actually open every week: a Markdown file, Notion or Google Docs. The template above pastes cleanly into all three.

Can this be automatic?

Mostly, yes. Selfly reads your pull requests and reviews, drafts each week’s record for you to confirm in about 90 seconds, and lets you add the work outside GitHub in one line.