Skin in the Game
When one team gets the win and another team cleans up the mess, the decision-makers are missing the feedback they need.
The people making a decision need to feel enough of what it causes to learn from it and stop handing hidden damage to somebody else.
The decision and the cleanup belonged to different teams
A company wants customers to complete identity verification faster. The growth and product team owns the onboarding flow, and its main target is the percentage of people who activate an account.
The team removes a manual review from a difficult class of applications. Activation improves immediately.
The failure appears elsewhere. Risk analysts find more accounts that should have been reviewed, support receives complaints from legitimate customers caught in later restrictions, and operations begins reconciling cases the automated path can't explain. One support lead spends several late evenings reconstructing decisions from incomplete records while the launch dashboard remains green.
The people who made the decision receive its visible upside while other teams carry most of its downside.
Skin in the Game asks whether the people shaping a decision feel enough of its real consequences for those consequences to change what they choose next time.
When someone can make the call, enough of what happens later has to come back to them to change the next call. Making everyone suffer more does not make anyone wiser.
What exposure actually counts
Money is one form of exposure, but it's rarely the only useful one.
A decision-maker may have skin in the game through:
- Capital that rises or falls with the long-term result
- Reputation attached to the accuracy of the claim
- Time spent repairing predictable consequences
- Responsibility for the operating budget affected by the choice
- Customer contact that makes downstream harm visible
- A delayed reward that depends on whether the result lasts
- The authority to stop the experiment when its cost exceeds the agreed boundary
The consequence needs to be big enough to change the choice, connected to the harm being created and difficult to hand off after the reward has already arrived.
Someone who receives a small symbolic penalty while keeping all of the upside still has an asymmetric position. Someone who is punished for every honest failure may avoid useful risk or hide bad news.
Bring the consequence back into the decision
The company needs the problems that appear later to affect the next rollout decision without turning every bad outcome into punishment.
The company could change the rollout so that:
- The team judges faster sign-up beside later account restrictions, fraud losses, support requests and the time customers need to recover.
- The product owner joins the first operational reviews and sees representative cases rather than a summary count.
- The time and money spent fixing customer problems and handling unusual cases count as part of the experiment.
- Risk and support can pause the rollout when a named safety boundary is crossed.
- Rewards depend on whether people are still using the account successfully after thirty or sixty days, not only whether they finished signing up on day one.
- Honest failures inside the agreed test boundary are treated as learning, while concealed or repeatedly transferred harm has consequences.
Support cases now appear beside completed sign-ups before the rollout expands, so the product team sees the extra work while it can still change the rule. It learns sooner because the people changing the policy now see what happens later.
How the same mechanism appears elsewhere
Economics and finance. People can take bigger risks when somebody else absorbs the loss. Ownership, money held back until later and rules for returning bonuses can reconnect a decision-maker with what happens after the decision. For example, US listing standards require companies to have policies for recovering some incentive pay after certain accounting corrections. That ties part of an executive's earlier reward to the corrected result. The SEC explains the recovery rule here.
The useful question is whether the person keeps the reward while someone else absorbs the loss. If employees already depend on one company for salary, healthcare, reputation and career progression, forcing all their savings into the same company creates dangerous concentration and may weaken judgment.
Software and organisational design. When the people who build an online service also take turns keeping it running, slow responses, confusing warnings and difficult recovery stop being somebody else's problem. That direct feedback can improve the design because the people deciding how the parts fit together also see what happens when those choices fail. Google describes Site Reliability Engineering (SRE) as protecting the availability and performance of live systems while keeping operational reality close to engineering work. Google's SRE overview.
This fails when taking turns responding to problems becomes punishment. Exhausted engineers make worse decisions and start hiding incidents, so teams still need sustainable rotations, clear ways to ask for help and enough time to fix the underlying problems.
Law and institutional design. Duties, liability and legal remedies can make people answer for power they use on someone else's behalf. Law also shows the opposite need: a judge or referee often needs no personal stake in the result. US law requires judges to step aside in circumstances including certain financial interests. 28 U.S.C. §455.
The exception matters: people making and implementing policy often need exposure to the result, while judges, auditors and referees may need distance from it to remain independent.
Check where authority and consequence sit
Use Skin in the Game before setting policy, delegating authority, introducing an incentive, allocating risk or deciding who owns a system.
Trace six things:
- Who can make or materially shape the decision?
- Who receives the upside if it appears to work?
- Who handles the downside if it fails later?
- How long is the delay between decision and consequence?
- Can the decision-maker transfer the loss while keeping the reward?
- Which consequence should the decision-maker share without making useful risk-taking irrational?
The repair may involve sharing downside, but sometimes it should work in the other direction. Frontline workers often carry enormous operational, emotional and reputational exposure while having almost no decision authority. Giving them more skin would deepen the imbalance. Give them voice, stop authority or a share of the upside.
Where this can become crude
Risk pooling and limited liability exist for good reasons. Insurance lets people undertake useful actions that would be impossible if one accident could destroy them. Companies allow capital to fund experiments without making every investor personally liable for every loss.
The question is whether protection removes the feedback needed for good judgment. The answer is usually a bounded share of consequence, sensible deductibles, delayed rewards, oversight or enforceable duties rather than total personal exposure.
Outcome-based punishment creates another failure. A careful decision can produce a bad result, and a reckless decision can get lucky. If every loss is treated as proof of poor judgment, people avoid uncertainty, conceal incidents and optimise for defensible appearances.
Review the decision process, the information available at the time and whether the agreed risk boundary was respected. The goal is to bring real consequences into the decision without pretending every bad outcome proves the original choice was reckless. Hindsight blame makes people hide the evidence the system needs.
Nearby models
The Principal-Agent Problem diagnoses delegation where the person acting has different information or interests from the person bearing the result. Skin in the Game is one possible intervention: make the actor share a relevant consequence. Delegation may still require monitoring, contracts, transparency and the ability to replace the agent.
Mechanism Design works backwards from a desired system outcome and changes rules, information and incentives. Skin in the Game is one design principle within that larger discipline. A good mechanism may use consequence-sharing, or it may deliberately remove personal stakes where neutrality matters.
When the person choosing can keep the upside and hand off the downside, ask what that arrangement rewards them for doing.