How a Brag Doc Changed My Promo (and Comp) Outcome

You’ve probably already heard the general advice: keep a running log of your work so you’re not reconstructing a year of impact from memory when it actually matters. It’s good advice. It’s also not what this post is about: plenty has been written on the mechanics of keeping one, and I don’t have much to add to that genre. What I want to tell you instead is where the habit actually came from for me, because it wasn’t a productivity tip I read somewhere. It came from having no other choice.

Where I actually started

I didn’t start my career with an offer letter. I started as a contract developer, brought into a talent pool at a large organization where contractors interviewed around internally to find a team that would take them. My first assignment wasn’t even that. I was shadowing a team temporarily, with no guarantee it would turn into anything. Looking back, I don’t think I was meant to make it past that stage. Nobody tells you that outright, but you can feel it.

The part where I was bad at it

I want to be honest about the beginning, because it wasn’t a smooth ramp. It was genuinely painful: an immense flood of information, more of it than I could process, and I failed at a lot of it before I found any footing. But I decided early that my circumstances weren’t going to determine my output, even when the only thing I could contribute at first was showing up for the unglamorous work nobody else wanted.

When nobody else stepped up to be sprint champion, I took the role. When it came around again and people still didn’t step up, I took it again. I was presenting in demos some weeks barely understanding the details of what I was presenting, doing my best to represent the team well anyway. In parallel, I was reading the codebase, reading git history, working through every wiki page I could find, debugging my way into an understanding nobody was going to hand me. I took on defects nobody wanted, including defects that technically belonged to other teams, much to their surprise sometimes. Within a few months I’d resolved hundreds of them.

The hours were brutal. Late nights until the cleaning staff turned the lights off, home for a few hours of sleep, back the next day to do it again. I’m not holding that pace up as some kind of ideal. It’s not sustainable as a permanent operating mode, and I’d think harder now about the tradeoff than I did then. But it was working, and at the time I was addicted to watching it work.

The habit that actually changed the outcome

Here’s the part that actually matters. A mentor told me, early in that stretch, to track every task I accomplished, every day - memorable or forgettable. So I did. Not a polished record, not something built for an audience. Just a running account of what I did and got done, day after day, for months.

I didn’t fully appreciate what that habit was buying me until the end of the year, when it came time to discuss what I’d done. My dedication had been visible to people the whole time. You don’t resolve hundreds of defects and cover other people’s sprint-champion slots without someone noticing eventually, but visible isn’t the same as documented, and documented is what actually carries into a decision. When the conversation happened, I made sure none of it had been forgotten, because none of it had to be reconstructed from memory. It was already written down, task by task, months of it.

They didn’t just want to keep me on the team. They wanted to convert me to a full-time employee, with a promotion attached.

The part that’s actually about money

Here’s why this belongs on a site about money as much as career advice: going from a contractor with no guaranteed continued work to a full-time offer with a level attached isn’t an incremental raise. It’s closer to what I’ve written about elsewhere as a level change, in What “Good” Comp Actually Looks Like, where the whole shape of your comp resets rather than nudges: base, benefits you didn’t have as a contractor at all, equity if the offer included it, the works. A strong year of contract work might earn you a rate bump if you’re lucky and the client feels generous. What happened to me wasn’t that. It was a step function, and the mechanism behind it wasn’t luck: it was that the case for it already existed in writing before anyone had to build one from scratch.

I’m not going to attach a specific dollar figure to it here, partly because it would date the post and partly because the number isn’t really the point. The point is that the number traced directly back to a habit a mentor handed me that cost a few minutes a day. If you want a version of that number for your own situation, the Comp Delta Calculator gives you a rough one, compounded over a few years, using your own base and your own assumptions.

The practice, minimally

I’m deliberately not turning this into a full methodology post: that ground is well covered elsewhere, and this site’s angle is the outcome, not the system. But in the interest of not being coy about it: the version I actually kept up was daily during that stretch, out of necessity, and it’s settled into something closer to weekly now that the stakes of any single week are lower. What hasn’t changed is the instinct my mentor gave me: write it down before you need it, not after, and keep it private by default. It’s a record I keep for myself, not a document I’m shopping around for visibility.

If you want the actual system rather than the philosophy behind it, that’s what’s in the Brag Doc Kit: the fields I use, a worked example, and the process for turning the log into a promotion packet. And if you already have a draft and want to know how it actually scores, the Promotion Packet Scorecard is a free 2-minute version of the same rubric.

Documenting for yourself isn’t the same as broadcasting

That privacy is doing real work. A log you keep for your own reference, that surfaces when a conversation about your work is already happening, is a completely different thing from narrating your wins in Slack or turning every project into a LinkedIn post. The first is just good record-keeping for a decision that was going to get made regardless. The second is a much easier way to become the engineer everyone quietly resents. I’ve been asked more than once whether keeping a log like this eventually tips into that. It’s a fair question, because the line is real and not always obvious from the inside. That’s a big enough topic that it deserves its own post rather than a paragraph here.

Next in this series: building an internal reputation without becoming a self-promoter, where I get into that line properly.

The narrow point

I’d be skeptical of a post that told you a habit like this guarantees an outcome. It doesn’t, and the work still has to be real. Nobody converts a contractor who wasn’t actually delivering, no matter how good the log looks. What I can say is narrower and, I think, more honest: the work was real, but the work alone wasn’t what carried the conversation. What carried it was that none of it had to be remembered, because none of it had been left to memory in the first place.