A compensation case I worked through in my HR course. Rather than walk through the whole analysis, I want to keep the few things it taught me — because they changed how I read pay everywhere, including in jobs I’ve held.
The firm in the case had a bonus system that had worked well for years. If you sold the work and delivered it, you got full internal credit for both, and the bonuses were steep — enough to double or triple your base pay. For a business built on individual rainmakers, that isn’t a flaw. It’s a well-tuned engine, with every dollar of reward sitting right next to the person who earned it.
Then the strategy changed. The firm moved into higher-end advisory work — the kind that runs for years and depends on teams coordinating across offices. No one person could sell and deliver it alone. But the pay system still rewarded people as if they could. The clearest moment in the whole case: a top performer chasing a big new-market pitch declined to bring in the local team that would have had to execute it, because sharing the work meant sharing the credit. The firm lost the pitch.
That one story taught me most of what I took away.
How a company pays is what it actually wants
You can write any strategy you like on a slide. The bonus formula is the version people actually believe, because it’s the one with money attached. This firm’s leadership genuinely wanted collaboration — and genuinely paid for solo heroics. When those two disagree, pay wins quietly and every time. So the first thing I do now, looking at any organization, is ignore the mission statement and read how it pays. That tells you what it’s really asking for.
A pay system is a spec, and people build to it
This is the idea I keep, because it fits how I already think. In my work I treat requirements as a specification: if the spec is wrong, people will build the wrong thing correctly, on time, and be able to defend every step. The lost pitch was exactly that. The consultant wasn’t being greedy or stupid — he was behaving rationally inside a system that priced collaboration as a personal cost. The failure traced straight back to what the firm had asked for, not to a bad person.
That reframe matters because it changes where you look when behavior goes wrong. The instinct is to fix the people. Usually the honest fix is upstream, in what you decided to reward.
Money is a weaker lever than it looks
The part that genuinely surprised me came from the research the course put in front of me — the argument that individual incentives don’t reliably improve performance, and that money is not the main motivator we assume it is. Lean too hard on individual bonuses and you don’t just fail to buy performance; you manufacture rivalry and eat up everyone’s attention arguing about who gets credit.
It’s sharpest on retention. Paying your best people more to keep them feels obvious, but it’s the easiest move in the world for a competitor to match — they can always add a zero. What’s hard to copy is the whole package: growth, real mentoring, a sense of belonging, work that means something. The framing I took away is that you keep people with material reward and development and community and purpose, and that a strategy resting on money alone is a weak one precisely because it’s so easy to imitate. You still pay well. You just stop pretending the check is the reason anyone stays.
Who shares the reward decides who counts
The redesign that made sense was to pay at the team or regional level, so that when a group hit its goals, everyone who contributed shared in it — not only the person who first shook the client’s hand. On paper that’s a mechanism. What struck me is that it’s also a decision about who counts. The old model made the downstream people — the ones who do the work, often in another office, often with less power — into a cost to be minimized. Deciding they share the reward changes who is visible.
I’ve been the downstream contributor on work that someone else got the credit for, so this one didn’t read as theory. A pay system quietly announces whose contribution is real, and most of them announce it in favor of whoever was closest to the sale.
The usual objection here is the free rider — that team pay lets weaker people coast on stronger ones. The case’s answer, which I found convincing, is that it doesn’t remove accountability so much as move it: when your reward depends on the group, your colleagues stop tolerating a passenger. You trade one manager watching everyone for a room of peers watching each other.
I went into the case thinking compensation was a math problem — set the numbers right and behavior follows. I came out thinking of it as one of the most honest documents a company writes about itself. If you want to know what a place values, don’t read what it says. Read what it pays for.
So here’s the question it left me with: the last time your pay and your employer’s stated goals asked for two different things, which one did you actually do? I know which one I did.
Comments