I have watched this happen enough times that the pattern is obvious now. A couple of years into the job, great salary, benefits, FAANG level impact (maango, whatever). You do good work and you get raises, but something doesn't feel right. You don't feel burned out, yet. But when you try to point to something and say, "that happened because of me," you don't have anything to show up to. When you see your family, your friends and they ask what you do it's vague and you can't really tell. The project had eighteen stakeholders. The decision went through four approval layers, often in circles and god knows who exactly is the one that influenced it. The outcome sits on a dashboard you can read and not really affect. Your contribution is probably real, but whether it mattered, and how much, is genuinely unclear.
That feeling is not a personality problem, big companies make everyone feel the same. It's not just you. What is missing, at least this is the name I would give it, is win density. Getting successes attributable to you, frequently. A win is: 1) bounded, attributable, and legible; 2) it ends and you got something done; 3) you can trace it back to what you did. You can point to the mark it left. Large companies suppress all three at once. Work stretches across quarters. Ownership gets spread across enough people that nobody can see their own outline in it. The feedback loop arrives late, filtered through dashboards, layers, and review cycles. It is how large organizations coordinate work at scale.
The startup trade is the inverse. Lower salary, higher win density. You get something done every day, and it's addictive. The problem is that the startups often fail and you end up burning out, with few savings.
Mental health
What low win density does to people is not dramatic, it doesn't get you to storm out, often you just get used to it. But it does make you eager to get something done, something new. Engineers start overengineering because made up milestones are better than no milestones. If the work will not give you a clean finish line, you invent one: another refactor, another re-architecture doc for a service that works just fine, a cleanup project that exists mainly because it can be completed, some new solution for testing... Other people just go gray and die inside. They just do exactly what they're told. They still show up. They still look fine in status meetings. But part of the salary starts to feel like payment for not getting to watch the work land.
This is mostly a white-collar complaint. Plenty of people have low pay AND low win density. This piece is about the white-collar version of the trade. Yes, often our salaries are great and quality of life is great. But we do spend 8+ hours a day at work, often more than that. And we need to make it work with the way our drive and our brains work. Yes, the work is comfortable and, often, we get paid a lot. And yes, you can make white collar jobs extremely pleasant and enjoyable. The point I'm making is that win density is needed for that. You need successes that are your own, frequently, so you can feel like winning.
To managers
That is also why the problem matters to managers, even if they cannot fix the underlying scale problem completely. Some work is slow by nature, not everything can ship in a one-week loop. But teams do better when work closes, attribution is real, and people can still see what moved because of them. can still feel that they owned it end to end and they got it done. Higher shipping frequency often correlates with better organizational performance and stronger engagement1 The practical point is simpler than the research argument: if nobody can tell what finished, who owned it, or what changed, ambition starts curdling into maintenance.
You don't need to pay people more to make them happier (wtf did i just say???). You often just need to "gamify" the job. Give dopamine hits to your engineers often and frequently. Some people will take that trade on purpose. I have taken it on purpose before. But ideally, give them money too.
DORA's State of DevOps literature consistently finds that higher deployment frequency correlates with stronger organizational performance and often with higher engagement, though the causal direction remains contested.