We hit the revenue target on a Wednesday. Someone posted the dashboard screenshot in chat. There were congratulations, a few celebration emojis, and then — nothing. The thread went quiet faster than any I can remember.
That silence told me more than the number did.
The goal had been public for months. We talked about it in all-hands meetings. It sat on a shared scoreboard. Everyone knew the figure, knew the timeline, and knew where we stood relative to both. By any standard measure of goal-setting, we did it right: clear target, visible progress, shared ownership.
And the team delivered. They hit the number with two weeks to spare.
From the outside, this looked like a well-run quarter. Inside, it felt like surviving a car accident and being told to admire the paint job.
I noticed small things first. An engineer who always reviewed pull requests within hours stopped responding for days. A support lead who once volunteered for weekend coverage started declining every optional meeting. Two people took sick days in the same week — not coordinated, just simultaneous exhaustion.
Then came the conversations. One-on-ones turned confessional. People weren't angry. They were tired. Not the productive kind that follows a sprint with a finish line. The accumulated kind — the kind that builds when you sustain effort without anyone acknowledging the weight of it.
What had happened, in plain terms: to close the revenue gap, the team absorbed work that should have required more people, more time, or both. They made trade-offs — shipping faster by skipping internal documentation, handling support volume manually instead of investing in better tooling, staying online later because time zones demanded it. Each trade-off was small. Together, they compounded.
Nobody raised a flag because the scoreboard only showed one thing: revenue. And revenue was going up.
Most founders I know, myself included, learned to run a company by setting targets and rallying people toward them. Nothing wrong with this. Goals focus effort. Milestones mark progress. The problem is not the milestone. The problem is treating the milestone as the whole picture.
Think of it like a long-distance drive. You can track miles covered and time elapsed. But if you never check the fuel gauge, the engine temperature, or whether the driver slept last night, you're optimizing for arrival while ignoring the vehicle. Eventually something gives. Usually not where you expect it.
Revenue milestones are miles covered. Team capacity is the fuel gauge. We were running on fumes and calling it a win.
I started calling this "achievement debt." Same logic as technical debt: you take a shortcut now, pay for it later, and the interest is always higher than you expect.
Achievement debt accumulates when a team consistently over-delivers against targets without adjusting for the human cost. The repayment comes as turnover, declining quality, slower future velocity, and — hardest to quantify — eroded trust. People stop believing that leadership sees the full picture, because the full picture was never measured.
The worst part: achievement debt is invisible to the people who set the goals. Revenue went up. Churn stayed flat. From the leadership dashboard, everything looked healthy. The debt lived in individual calendars, in skipped lunches, in the growing lag between "I'll handle it" and the moment someone actually could.
We didn't stop setting revenue targets. We added a second lens.
Every revenue goal now comes paired with what we call a cost-of-achievement check. Before a quarter starts, we ask: what has to be true for the team to hit this number without borrowing from their own reserves? If the honest answer is "people will have to work in ways that aren't sustainable," the target is wrong — or the plan to reach it is.
We started tracking leading indicators of strain alongside trailing indicators of success. Not surveillance. Just better questions: Are people taking their days off? Is the backlog of internal improvements growing or shrinking? Are one-on-ones surfacing energy or exhaustion?
None of this is complicated. It just requires admitting that the number on the wall is not the only number that matters.
If your team just hit a milestone and the room feels flat, pay attention. That flatness is data. It might mean the goal was reached at a cost you didn't price in.
Pair every revenue target with a capacity check. Ask what it will actually take — not in pipeline terms, but in human terms. When you celebrate a win, look around the room. If the people who made it happen can't muster enthusiasm, the win is incomplete.
The milestone is not the point. The team that can hit the next one is.
Be the first to comment.
0 comments
Loading comments...