A brag document fails when you start it the week you need it, because recall under pressure is poor and favors whatever happened most recently. This order builds the evidence first, adds an outside voice you cannot generate yourself, and only then rehearses the ask. Facts, then proof, then delivery.
Step 1: Create the file before you feel ready
Naming the file comes first because the blank page is the only part of this process that has to be decided in advance; everything after it is recall. Open Drive, create a new Doc, title it exactly 'My Wins,' and star it so it sits at the top of your Drive list. Add one line at the top: 'Updated [month year].' Then stop. Do not build a table, a tag system, or a color scheme. A plain list of dated bullets is what you will actually keep using. The common way this stalls is treating the setup as the project: an hour in Notion building a database with categories, then never typing a single win into it. The doc exists to be ugly and additive, not organized.
Step 2: Pull three wins out of memory
Three is the number because it is small enough to finish in one sitting and large enough to prove the doc is worth returning to. Do not try to remember from scratch. Open your calendar, sent mail, and any project tracker, and walk backward month by month; whatever you click on with a small 'oh right, that' is a candidate. Write each win as a change, not a duty: 'cut invoice reconciliation from five days to two' beats 'responsible for invoicing.' If you have a number, put it in. If you don't, write who noticed the difference. What usually goes wrong here is that people write their job description, which is what they were hired to do and therefore proves nothing. A win is a delta, something that was one way before you and another way after.
Step 3: Record the praise while you still can
By now the doc holds facts; this step adds the one thing you cannot generate yourself, an outside opinion. Pull the exact wording, not a summary. If a client emailed 'you're the reason we renewed,' paste that sentence with their name and the date. If it was said out loud, write it the same week in quotes and tag it '(verbal, 12 Mar).' Precision matters because a manager repeating your own accomplishments to a budget committee hears self-assessment, while a client's sentence is evidence. Paraphrasing it into 'the team was happy with my work' drains it of everything that made it useful. If no compliment comes to mind, search your inbox for 'thank' and 'appreciate' — most people have three and remember none.
Step 4: Reread right before the ask
The document only earns its keep in the twenty minutes before the conversation, which is why this comes last. Read it top to bottom, then pick the three entries that map to whatever the company said mattered this year, usually revenue, retention, or a stated priority, and say them out loud once, in order, so the phrasing is already in your mouth. A workable shape: one number from step 2, one quoted line from step 3, then the ask, all inside ninety seconds, then stop talking. Chronology is the usual trap; people walk through the year in the order it happened and bury the strongest item fifth. Keep the doc closed during the meeting. It is rehearsal material, not a script.
A reminder typed into a phone app disappears the instant you tap it done, leaving no trace you ever planned anything. A paper strip behaves differently: it stays where you taped it until the last line is cut, and it visibly gets shorter as you work.