How Incentive Systems Shape Culture Faster Than Values Statements

The first time I understood the gap between stated culture and real culture, I was watching a recruiter get praised in a team meeting for a placement made at speed — a search that had been closed in under three weeks. The placement was wrong. The hiring manager knew it within sixty days. But in the meeting, the celebration was genuine. Volume was what got recognised.

Nobody had written down "we value speed over quality." Nobody believed that was true of the firm. But the incentive system — what got celebrated, what got visibility, what determined who had a good quarter — was saying something different. And the team was listening to the system, not the statement.

That is what incentive design actually is: the set of signals that tell people what is really valued, regardless of what is officially said to be valued.

The gap is not a communication problem

Most leadership teams who notice a gap between their stated culture and their actual culture diagnose it as a communication problem. The values aren't visible enough. The messaging isn't clear enough. The culture decks need updating. They commission better internal communications and are surprised when nothing changes.

The gap is not a communication problem. It is an incentive design problem.

Harvard Business School research on organisational culture found consistently that employees in every kind of organisation report understanding their company's stated values — and acting differently from those values when their actual work environment incentivises different behaviour. The problem is not that people don't hear the values. It is that they hear the incentives more clearly.

This is a feature, not a bug, of human behaviour in organisations. People are very good at reading the real signals — what gets noticed, what gets rewarded, what gets ignored — and behaving accordingly. The stated culture is what leadership says. The real culture is what the incentive system produces.

Every organisation has a stated culture and a real culture. The gap between them is not a communication problem. It is an incentive design problem. What you reward is what you get — regardless of what you say you value.

What counts as an incentive

Compensation is the most discussed incentive, but it is rarely the most powerful one in shaping day-to-day behaviour.

The incentives that shape culture most reliably are subtler:

Recognition patterns. What gets celebrated in team meetings, in company all-hands, in Slack channels. What kinds of wins get made visible. Whether the person who caught a problem quietly gets the same recognition as the person who delivered a headline number. Recognition signals what the organisation considers success.

Promotion patterns. The last ten promotions in any organisation are a precise description of what the organisation actually values. Not what it says it values — what it rewards with power and status. If every person promoted in the last three years shares the characteristic of being diplomatically agreeable rather than rigorously honest, the organisation has an incentive system that selects for diplomatic agreeableness, regardless of what the values statement says about candour.

Failure treatment. Whether the person who took a reasonable risk and failed is treated as a thoughtful operator who learned something, or quietly marginalised, is one of the most important cultural signals an organisation sends. It determines whether people take risks, surface problems early, and bring bad news directly. The organisations that say they have a culture of psychological safety and then quietly punish the people who bring bad news have created an incentive system for hiding bad news.

Problem-raising dynamics. Whether the person who identifies a real problem is thanked or treated as difficult is the test of whether an organisation can learn. Every organisation has problems. The question is whether the incentive system makes it safe to surface them.

The Majhi Group design problem

Building a retained executive search firm meant making a deliberate incentive design choice early: what do we reward, and what does that produce?

The contingency model — the dominant model in most recruiting — rewards placement speed. Close the search fast, move to the next one. The incentive is clear and it produces a clear culture: volume, speed, fill rate. It does not produce a culture of quality, of long-term fit, of honest assessment when a candidate is wrong for the role.

The retained model creates a different incentive structure. The fee is committed upfront. The firm's reputation is staked on the outcome, not the placement. The guarantee is 90 days — if the hire fails inside that window, we redo the search at no charge. Those structural choices are incentive design. They create a system where quality is not just stated as a value but built into the economics.

The culture that results is not the product of values statements. It is the product of a system where everyone involved — the search lead, the researcher, the person who makes the final recommendation — knows that their reputation rides on whether the hire works out, not on whether the hire happens.

That alignment between what we say we value (quality, long-term fit, honest assessment) and what the system rewards (all of the above, because the economics depend on it) is what makes the culture real rather than aspirational.

The Majhi OS parallel

Building Majhi OS — the operational infrastructure for hiring systems — required the same thinking applied to system design rather than firm design.

The recruiting tools most search teams use reward the wrong things. ATS platforms track fills and time-to-fill. Outreach tools track message volume and open rates. CRMs track pipeline stage movement. None of these are wrong metrics in isolation. But when they are the primary incentive signals — what recruiters see, what managers review, what determines whether a quarter looks good — they produce a culture that optimises for those numbers.

The system we built tracks different things: mandate health, funnel degradation, response decay, shortlist quality, offer acceptance rate, 90-day outcomes. The metrics are the incentive system. What the platform surfaces and rewards is what recruiters pay attention to.

This is not unique to recruiting operations. Every organisation that builds measurement infrastructure is making incentive design choices. The dashboard you build determines what people optimise for. The KPIs you choose determine what culture you produce.

The audit question

The fastest way to understand an organisation's actual incentive system is not to read its values statement. It is to answer four questions.

Who got promoted in the last two years, and what do they have in common? The pattern in those promotions is the most accurate description of what the organisation rewards with power.

Who left frustrated in the last year, and what did they have in common? The pattern in voluntary exits describes what the organisation's incentive system does not reward — and often, what it implicitly punishes.

The last significant failure: who was accountable, and what happened to them? This describes whether the organisation has a real accountability system or a symbolic one.

The last person who raised a serious problem that turned out to be correct: were they recognised for it, or treated as difficult? This describes whether the organisation can learn.

Research by Ethan Bernstein and colleagues at Harvard Business School found that in organisations with transparent performance environments, employees spent 33% less time on observable work — performing for an audience — and 33% more time on productive work. The measurement system changed the behaviour. The incentive structure shaped what people actually did.

Building the system before the culture

Most founders think about culture first and incentives later. The right order is the reverse.

Define what outcomes you actually need: quality over speed, honesty over comfort, long-term fit over short-term fill. Then design the incentive system that rewards those outcomes — in recognition, promotion, failure treatment, and measurement. Then, and only then, write the values statement. Because at that point it will be true.

In Odisha, where I built both businesses without the ecosystem shortcuts available in Bangalore or Delhi, the incentive design had to be explicit from the start. There was no informal community of practice that would transmit professional norms by proximity. There was no density of similar firms that would keep standards high by competition. The incentive system had to do the work that the environment wasn't doing.

That constraint produced a discipline I wouldn't trade. When the incentive system is designed deliberately, the culture that emerges is predictable. When it isn't, the culture that emerges is whoever's behaviour the system happened to reward — which is often not what anyone intended.

Values statements describe the culture you want. Incentive systems produce the culture you have. The gap between them is a design problem. And like all design problems, it is solvable — but only if you treat it as one.

Sources

Harvard Business School — Organizational Culture Is Not Just About Values

Ethan Bernstein, Harvard Business School — The Transparency Paradox

HBR — Incentives and Culture: How Reward Systems Shape Organisational Behaviour