In partnership with
Your most reliable engineer is going to quit, and the reason is that he was good at his job in a way your company has no way to see.
He runs your infrastructure. For nine months nothing has gone down. No 2 a.m. pages, no status-page incidents, no furious email from your biggest account about an outage during their demo. The integrations hold. The deployments land. When a competitor's site fell over during a traffic spike in March, yours stayed up; three of your customers even mentioned it on calls that week.
He's the reason. You have never once had to think about the thing he thinks about all day, which is the entire point of having him.
Here's the problem sitting underneath that calm. Walk through your last company all-hands in your head. You celebrated the feature that shipped. You celebrated the logo that closed. You celebrated the redesign everyone could see on the screen. Every win you named was a thing somebody could point at. The nine months of nothing-went-wrong got named by no one, because an absence of disasters doesn't demo. Your reward system runs on visible output, and the most load-bearing work in your building leaves no mark on a screen.
That engineer feels it. He shipped a database migration four days early last week, the kind of move that takes down a less careful team for a weekend. He woke up the next morning to a task list flooded with new tickets, all in the clipped tone of someone who's behind, every one of them asking him to add estimates and pick up slack on a feature running late.
Not one line about the migration.
He sat with his coffee and ran the math that every overlooked person eventually runs. The work holding this place together is the work nobody here can see.
“So why am I killing myself to do it well?”
That's the piece this week. The reward system you built can only count what it can see, and the people doing your most load-bearing work are invisible to it.
