I used to think the most important career document was your resume.

Turns out, I was wrong.

There's a document that will quietly do more heavy lifting for your career than your resume ever will.

It's called a brag sheet and once you start one, you're never going back.

So what exactly is a brag sheet?

It's a living document that tracks all the work you've done and the value you've delivered.

Think of it as your resume's more detailed, always-up-to-date cousin.

Here's Why You Should Have One

A brag sheet sounds a little self-aggrandizing at first but it's one of the most powerful tools in your career toolkit. Here's why:

New manager? No problem. When you get re-orged or land a new manager (which, if you work in tech, happens more often than we'd like), you can hand them your brag sheet and boom, they instantly know the caliber of work you've been doing. No need to re-prove yourself from scratch.

Promotion time. When you're gunning for a promotion, your manager needs evidence to make the case. Your brag sheet is literally that evidence handed to them on a silver platter.

Performance reviews become way less stressful. Instead of racking your brain trying to remember what you did six months ago (we've all been there), everything is already documented and ready to go.

A gut check on your own growth. You can look back at your brag sheet and ask yourself: am I doing the right type of work? Is the impact where it should be? Sometimes it's the nudge you need to shift gears.

Job searching. When it's time to update your resume or prep for behavioral interviews, your brag sheet is basically a goldmine. All your stories, all your impact — already in one place.

Here's What I Put In Mine

Okay, so you're sold. But what does this thing actually look like? Here's exactly how I structure each entry in mine:

1. A clear header — just the name of the project or work item.
2. Context — this is the meat of it. I go into detail on why the work mattered. What was the problem? How were things being done before I stepped in? Who else was involved — how many teams were we coordinating with? What was at stake if it didn’t get done? The more detail here, the better. I also note the process and steps I used to solve the problem as well as any challenges or road blocks.
3. Artifacts — anything tangible that came out of the work. Design docs, diagrams, presentations, meetings and meeting notes. If I made it, it goes here.
4. Code pull requests — links to the actual code changes, if applicable. Receipts matter.
5. Impact — the measurable outcome. Screenshots of kudos, shoutouts from teammates, metrics — all of it. Sometimes I wait a few weeks before filling this section out, because impact doesn't always show up right away.

How I Keep It Organized

You can structure your brag sheet however feels natural to you, but here's what works for me: I organize it by year and quarter. So it looks something like this:

2025

• Q1
• Q2
• Q3
• Q4

2026

• Q1
• Q2 ...

Clean, simple, and easy to navigate when you need to pull something up fast.

When Should You Fill It Out?

This is the question that trips most people up.

Here's my take: don't wait until the end of the year and try to remember everything.

What I do is add the title of the work or any relevant documentable entry as they come in, even if it's just a quick note.

Then, at the end of each quarter, I go back and flesh out the details.

Writing deep, thoughtful entries takes mental energy, so I give myself that dedicated time to do it properly.

Some people prefer to fill it out right after they finish a piece of work. That works too.

The main take away is don't wait too long.

The details fade faster than you think, and trust me, future-you will not remember as much as you think present-you will.

That's it for this one.

See you next time.

Uma!

P.S. Currently in week 8/24 weeks of my marathon training plan. Here's a picture from my 12 mile progressive run over the weekend.