Then Why Am I Paying You?

"Then why am I paying you?"

My CEO had just thanked me for the work of the last five months. The reply came out of my mouth before I'd thought about it. I said the team had done it all. The hires had carried the load. The engineers had built the thing. I hadn't really done that much.

Half a smile from across the table. Then the question. He wasn't being cruel — he was being diagnostic. If I hadn't done anything, what was he paying for?

I went home, opened a document I keep, and started reading.

The deflection reflex

The instinct to push credit to the team isn't entirely wrong. The team did the work. The engineers shipped. The hires onboarded. The roadmap moved because dozens of people moved it.

But there's a tell in how senior people answer the "what did you do" question, and I'd just walked right into it. You can be genuinely humble and still owe yourself an honest accounting. The two aren't in opposition. Erasing yourself from the story isn't the same as crediting the team.

Why this matters more the higher you go is structural. Engineers ship code. Engineering managers are the glue that connects the steering wheel to the wheels. VPs and CTOs ship decisions. Direction. Which doors get closed. Which bets get made. Which people get the room and which don't. The feedback loop is long. The artifacts are quiet. And the work, by the time anyone can see it, is wearing someone else's name.

If you can't tell yourself what you did, you can't tell anyone else either.

The brag log

I'd been keeping what I half-jokingly call a brag log. It's a PowerPoint deck, one slide a month. What the team and I achieved. Decisions made. Responsibilities I took on, and ones I handed off. Things shipped. Projects started. Plans laid. An hour at the end of every month, and that's it.

It's not a journal. It's not a CV. It's closer to a captain's log — a running record of which way I turned the wheel and what I was looking at when I turned it.

I started keeping one years ago because I'd noticed something embarrassing about myself. By the time the annual review came around, I couldn't remember January. I couldn't remember which fires I'd put out in March, which architectural argument had taken a week in May, which hire had taken three months of effort to land. The brain doesn't hold this stuff well, and the things that feel obvious in the moment evaporate fast. Especially the wins. We remember failures with awful clarity and forget the steers. They say it takes five wins to balance a single failure. I believe it.

For an IC, a brag log is useful. For a senior leader, it's essential. Your output is decisions. Decisions are invisible until their consequences arrive — sometimes quarters or even years later, often attached to someone else's work. If you don't write them down at the moment of decision, you'll never reconstruct the chain.

What five months actually looked like

I went back through the log. Here's the unsettling part: it wasn't a long list. There were maybe five or six decisions in five months that I could point to and say, that one mattered. That one moved the boat.

Pushing the team to automate testing where we'd been getting by without. Clearing the road for a team by making their backlog and direction unambiguous. Naming the must-win battles to ship a product. Deciding to let someone go — yes, I do that too sometimes. Deciding to hire someone else. Deciding a project was worth starting at all.

Most of the work, day to day, hadn't felt like work. It felt like meetings. It felt like nudging. It felt like writing the same thing in three different Slack channels. Most days I went home thinking I hadn't done much. The log told a different story.

The boat moves because of the wheel. But the rowers do the rowing.

This is the thing my CEO was getting at, even if he was teasing.

The team really did do the work. None of those decisions would have produced anything without the people who executed against them. That's true. It's also true that the same team, pointed in different directions, would have produced different outcomes. The wheel matters. The rowers matter. They're not in competition. They work together.

There's something else here that's easy to miss. The higher up you sit, the longer the lever. A nail's worth of motion at the top is a mile of motion at the bottom.

When Satya Nadella decided Microsoft was an AI company now, that probably felt — from where he was sitting — like a single decision. A sentence. A direction. From everywhere else, it was billions of dollars of investment shifting overnight, entire org charts being rewritten, a thousand PhDs being hired, products being killed, products being launched. He did none of that. Not personally. He put the wheels in motion, and once those wheels are turning, they turn with everything Microsoft has.

None of us is Satya — closer to the MVP of our local Sunday league than the MVP of the NBA ten years running. But the physics is the same at every scale. A VP who decides their team is going to stop chasing parity and start chasing differentiation has just moved months of roadmap, dozens of careers, and a budget line. They didn't write the code. They moved the org by an inch, which is a mile by the time it reaches the ground.

Which is the thing nobody quite explains when you get promoted: management is fundamentally a leverage game. As an IC, you move a few hundred lines of code, or run a marketing campaign, or close a deal. Real output, hands on it. As you go up, the output stops being what you do and starts being what you cause. Your decisions don't ship the product. They ship the conditions other people ship the product in. Satya didn't write a line of GPT-4 plumbing. Microsoft is now the AI distribution king. Those two sentences sound contradictory until you realise they're the same sentence, observed from different altitudes.

The mistake I was making, and that I see senior leaders making constantly, is confusing "the team did the work" with "I didn't do anything." Those are different sentences. They sound similar in the moment. One is generous. The other is just sloppy. And given the leverage, the sloppy one isn't just a mis-statement — it's a mis-statement at scale.

How to actually keep one

Mine is a PowerPoint deck, one slide a month. It could be a Notion page, a notebook, a text file, a recurring calendar entry. The format doesn't matter. The discipline is:

Reserve an hour at the end of every month and write down what mattered. Memory rots fast and selectively.

Focus on results, not activities. Focus on decisions, not doings. Focus on the big picture, not the details.

And — this is the whole point — brag. It's a brag log. Don't fill it with the things you'd rather forget. People already remember those. What they forget is what you want them to remember.

Read it back every quarter, or every six months. This is the part most people skip, and it's the part that does the work. You will be quietly shocked at how much you did, and how little of it you remembered.

Back to the question

I sent my CEO the report I built from the log. You bet I did. The question was half a joke and half a real question. The joke half landed on its own. The real half I wanted to make sure he got right.

Because what he was really asking was: can you tell me what you actually do? If you can't, neither can I, and that's a problem for both of us.

If you're in a role where your work is decisions — VP, SVP, CTO, CPO — start writing them down. For the brag, yes. And for the honesty. For yourself first, and for the day someone asks why they're paying you. You should be able to answer without inventing the answer on the spot.

The team did the work. You decided which work. Both of you got paid for a reason.