Achievement Log
You might know it as a brag document, hype doc, or wins journal - a running record of your work, kept while it is still fresh. The Achievement Log is a brag document that keeps itself: log a line from Slack or in the app in seconds, and arrive at review season with a year of evidence instead of a blank page.
Your review is only as good as your memory in November
Most people walk into review season with a blank page and a recency-biased memory, then spend 2-6 hours per review digging through Slack, Jira, and old emails to reconstruct what actually happened. The wins from the first half of the year quietly vanish, and with them, the strength of your promotion or pay case.
A brag document that keeps itself
The Achievement Log is a structured brag document: short, timestamped entries categorised as achievements, tasks, or feedback. Log for yourself, and if you manage people, keep an "About Others" log for each direct report, so calibration conversations run on evidence rather than recall.
Capture from wherever you work
Add entries in the app in seconds, or straight from Slack: use the /log slash command or DM the Perform Review bot, and the entry lands in your log without switching tools. Optional reminders on your chosen cadence keep the habit alive during busy weeks.
It compounds at review time
When you sit down to write your review, your logged entries pre-fill the draft. The year you captured line by line becomes a polished self, peer, or manager assessment - written from your real work, in your voice.
Frequently asked questions
What is a brag document?
A brag document is a running record of your accomplishments, kept as you go rather than reconstructed at review time. High performers are known to keep them because memory is recency-biased: without one, the win from March disappears from the review you write in November. The Achievement Log is a structured brag document with categories, reminders, and Slack capture built in.
How is the Achievement Log different from a brag document in Google Docs?
A document depends entirely on you remembering to open it. The Achievement Log meets you where you work: log from Slack with a slash command or a DM to the bot, get reminders on your chosen cadence, and keep entries categorised as achievements, tasks, or feedback. At review time your log pre-fills your review draft instead of being copy-paste raw material.
What should I put in my Achievement Log?
Short, specific lines while the detail is fresh: things you shipped, problems you unblocked, feedback you received, and measurable outcomes. One sentence is enough - "Shipped the Q3 dashboard two weeks early" beats a paragraph you will never write. Aim for one or two entries a week.
Can I log achievements for my direct reports?
Yes. "About Others" lets managers keep a log per direct report. Wins you observed, feedback you received about them, growth moments. When review season arrives you have real evidence for every report instead of reconstructing eight people’s years from memory.
Can I log achievements for my peers?
Yes. "About Others" works for colleagues too, not just direct reports: note the moment a peer stood out so it is ready when you come to write their peer review, rather than trying to recall it from memory months later.
Is my Achievement Log private?
Yes. Your entries are visible only to you, and your inputs and reviews are never used to train AI models.
Explore the rest of the story: Write the review · Win the conversation
Start free - no credit card required