The brag doc everyone recommends and nobody keeps.
Your brag doc didn't die because you're undisciplined. It died from friction, formlessness, and no reason to return. Why "journal daily" is the wrong fix — and the habit design that actually survives a busy month.
The doc you started and stopped
A lot of us got the brag-doc idea from the same place — Julia Evans' post about writing one so your work gets recognized. It's good advice. You read it, you nodded, you made a doc titled something like "Wins 2026," you wrote three bullets, and you have not opened it since. It's sitting in your Drive right now, three weeks stale, quietly making you feel slightly guilty.
We've done this more than once. And for a while we assumed the problem was discipline — that other people kept theirs and we just weren't organized enough. That's the wrong diagnosis. The brag doc doesn't fail because it's a bad idea. It's a great idea. It fails because a plain doc is easy to start and easy to abandon, and almost nothing about it is designed to survive contact with a busy month.
If you want the habit to stick, it helps to be specific about why the last one died. In our experience there are three failure modes, and they're all fixable.
Failure one: friction
The cost of a single entry is too high. A blank doc gives you no help, so every time you go to log something, you're also deciding how to phrase it, whether it's "big enough" to count, and how to format it next to the others. That's a lot of small decisions for a thirty-second task, and small decisions are exactly what a tired brain skips. The entry doesn't get written, and after that happens a few times, the doc is dead.
The fix is to make one entry nearly free. Let it be messy. "Onboarding drop-off was bad, dug in, shipped a fix" is a perfectly good entry — a seed you can grow later, not a bullet you have to perfect now. The moment capturing costs real effort, you've built something you'll abandon.
Failure two: formlessness
A blank doc gives you infinite freedom, which sounds nice and is actually the problem. With no shape at all, entries drift — some are one word, some are paragraphs, some are just a pasted Slack link with no context. Six months later you open it and half the entries don't mean anything to you anymore, because past-you didn't leave enough to reconstruct them.
The fix isn't a rigid template — that swings back into friction. It's just enough shape that an entry is never a blank page: what happened, what you did, a number if you've got one, a link. Light structure does two jobs at once — it lowers friction (you're filling slots, not facing a void) and it keeps entries useful later. That's the balance a good brag-doc habit needs and a raw doc never gives you.
Failure three: recall — the one nobody solves
This is the failure that actually kills it, and it's the one the standard advice ignores. Even a low-friction, well-shaped doc dies if nothing ever brings you back to it. Out of sight, out of mind — you remember the doc exists at exactly one moment: the night before your review, which is the whole problem you were trying to avoid.
And here's where the usual fix makes it worse. The common advice is "journal daily" or "do a weekly review." Turning your work log into a daily habit feels rigorous, but it's how you guarantee abandonment. Most meaningful work doesn't arrive on a daily schedule. You'll have a quiet Tuesday with nothing worth logging, then a two-week stretch where three real things happen. A daily cadence taxes you on the empty days and trains you to feel behind — and a habit that makes you feel behind is a habit you'll drop and not return to.
The bet: match the cadence to the work, not the calendar
When we built a tool for this, the central decision was contrarian for a productivity product: it does not want your daily attention. Most apps fight to become a daily habit because daily engagement is the metric they're graded on. We decided that's the wrong target for a career record, and made "come back after a week, or a few weeks, whenever something meaningful actually happened" the intended rhythm — not a streak to protect.
That changes how you solve recall, too. If the cadence is irregular, a streak counter is exactly wrong — miss two weeks because nothing happened and it punishes you for it. So the recall mechanism is a gentle nudge rather than a guilt meter: a quiet "want to log the last couple of weeks?" you can ignore without consequence, not a broken chain you'll abandon in shame.
The honest tension
We'll name the obvious risk, because it's real and we're still testing it: a tool you're allowed to ignore for weeks is also a tool you can forget entirely. Low-cadence habits trade the tyranny of the daily streak for the danger of drifting away completely. The nudge is our hedge against that, but we don't yet know if it's enough — this is an early product, and "does the low-cadence bet actually hold?" is a question we have on ourselves before we'd claim it for anyone else. We'd rather tell you that than pretend we've solved it.
What we're more confident about is the diagnosis, because we've lived every part of it. If your last brag doc died, it almost certainly wasn't your discipline. It was friction, formlessness, and no reason to come back — and all three are design problems, not character flaws. You can fix them in a plain text file: keep entries messy and cheap, give yourself four little slots so a new entry is never a void, and pick a rhythm that matches when your work actually happens instead of one a productivity app wishes it did.
“The best work log isn't the one with the most entries. It's the one you still have going when the review lands.”