Turns out, the easiest way to multiply a problem is to start paying people to solve it.

British colonial rulers in India faced a major problem in Delhi. Venomous cobras were everywhere, putting residents at risk. To fix the issue quickly, the government introduced a straightforward economic solution. They offered a cash bounty for every dead cobra brought to them. At first, the policy worked brilliantly. Locals hunted the snakes, turned them in, and the wild cobra population dropped.

But as wild cobras became harder to find, people realized a flaw in the system. The British weren't paying for hunting cobras. They were paying for dead ones. To keep the cash flowing, enterprising locals set up breeding programs in their homes. They raised thousands of venomous snakes strictly to kill them and collect the reward.

Eventually, administrators noticed something strange. The number of dead snakes coming in stayed massive, even though the wild population was clearly depleted. Realizing they were funding a thriving snake breeding industry, the government canceled the bounty program overnight.

The breeders were suddenly stuck with thousands of worthless, dangerous snakes. Unwilling to pay to feed them, they released the cobras into the wild. The city ended up with a much worse snake problem than when the whole thing started.

Known as the Cobra Effect, it perfectly illustrates a perverse incentive. When you tie a reward to a specific metric, people will optimize for that metric rather than the actual goal.

The British measured success by dead snakes, assuming it meant a safer city. By paying for the output instead of the outcome, they accidentally incentivized the exact opposite of what they wanted. Systems always prioritize what gets measured and rewarded, no matter how disconnected it gets from reality.

This same dynamic plays out in business and software development all the time.

Take software bug bounties. If a company pays developers a cash bonus for every bug they find and fix, they often get a sudden surge in reported bugs. Why? Because developers quickly realize they control both the creation and the fix. Some start writing sloppy code on purpose, slipping in trivial errors they can easily log and resolve to collect extra cash. The software ends up more unstable, while the company bleeds money fixing manufactured problems.

Or look at customer support metrics. If management wants to reduce customer wait times, they track average handle time and penalize agents who stay on the phone too long. Agents figure out the fastest way to close a ticket isn't to solve the problem. They start transferring angry customers, giving rushed answers, or hanging up before they even finish a sentence. Call times drop, but customer satisfaction tanks and repeat callers skyrocket.

When you design an incentive structure, you have to look past the surface level metric. Ask yourself what shortcuts people can take to game the system. If there's an easier path to the reward that doesn't actually solve the underlying problem, people will take it every single time. Stop rewarding the output. Focus on the outcome, and build systems that make it impossible to profit from the problem.

In his landmark book Influence, psychologist Robert Cialdini highlights the Rule of Reciprocation: humans possess an evolutionary drive to repay favors, gifts, and concessions.

It is the glue that built cooperative human societies. But in modern social dynamics, it can also create subtle friction when a small gesture carries an unstated expectation.

Consider the familiar dynamic of picking up the tab on a first date.

Often, it's simply a genuine gesture of hospitality. But occasionally, a hidden expectation creeps in: the giver views the meal as an informal down payment, while the recipient realizes an unwritten obligation has been created. Whether the gesture was innocent or measured, the presence of an unwritten invoice changes the rules of the interaction.

This is the Asymmetric Reciprocation Trap. It occurs when a low-cost, low-risk courtesy is silently leveraged to invite high-value access, compliance, or emotional debt.


Why this dynamic creates friction:

• Unspoken Contracts: Genuine reciprocation relies on mutual, voluntary goodwill. Friction arises when one person assumes a transactional agreement that the other party never agreed to sign.

• Proportion Disconnect: The brain naturally resists transactional leverage when the perceived cost of a gesture ($50 dinner) feels wildly out of balance with the return being sought (time, loyalty, intimacy, or access).

• The Perception Shift: The moment a gift or favor feels like it comes with an invisible invoice, the interaction shifts from connection to calculation.

The next time you offer a favor, a gift, or buy a meal, whether in dating, networking, or business, it's worth asking a simple question:

Is this a clean gesture with zero expectations, or an invisible invoice?

If you're keeping score, it isn't generosity. It's a transaction, and people always spot the bill before they finish the meal.

Mentioned in this piece:
Influence: The Psychology of Persuasion by Robert Cialdini

Think about the phrases you repeat with your partner or closest friends. To yourself.

"I always run late."
"We just enable each other."
"I'm terrible with money."

We think we're just making harmless observations. In reality, we're building a mythology.

The semiotician Roland Barthes argued that myths aren't just ancient fables. They're active systems of communication. They're the messages we construct to give meaning to our world. In our own lives, a myth is simply a story we choose to repeat until it becomes our reality.

When you tell a story about yourself enough times, it hardens into fact. If your personal mythology is built on friction or failure, you'll unconsciously look for ways to prove it true. You'll pick a fight or sabotage an opportunity right on schedule because that's what your story dictates.

But you hold the pen. You can build a different myth.

It starts with deliberate observation. Catch yourself the next time you lean on a lazy, default narrative. Stop saying you're the person who always folds under stress. Decide that you're the individual who handles chaos better than anyone else.

Find one small moment of grace and turn it into your new anchor. It could be a time you navigated a massive crisis perfectly or a moment you laughed off a complete personal disaster.

Repeat that story. Bring it up in conversations. Remind yourself of it when the pressure gets heavy. Use it to overwrite the old script.

Mythologies become true because we repeat them.

Stop adopting broken stories. Start writing your own.

Near the end of the 1998 film Elizabeth, there's a brilliant scene where Cate Blanchett’s character makes a deliberate choice. Her reign is under relentless threat, her advisors are spiraling into panic, and her life is in danger. Instead of breaking under the weight, she cuts her hair, paints her face stark white, and steps out in absolute royal armor.

She stops being a vulnerable individual and actively becomes an untouchable symbol. She tells her court she is married to England.

You probably aren't painting your face white to deal with a sudden family crisis or a community dispute. But the dynamic Elizabeth uses here is exactly what leadership requires when things get chaotic.

When life goes sideways, the people around you don't just look to you for a logical plan. They look to you to figure out how they're supposed to feel.

We constantly scan the steady figures in our lives to calibrate our own responses. If you show up panicked or frustrated, your family or friends will mirror that anxiety. If you show up steady, the room settles down. In these moments, leadership is partly a performance. It's the deliberate act of putting aside your internal stress to project exactly what the situation requires. You have to step out of your personal anxiety and inhabit the role of the anchor.

This doesn't mean lying to your people or hiding bad news. It means recognizing that your reactions set the baseline for everyone else. When a major hurdle pops up and you're internally screaming, your job is to pause. You lower your voice. You ask clear questions. You project absolute stability.

You aren't just managing the logistics. You're managing the social mirror for the people around you.

Think about the last time a stressful situation unraveled around you. Did you amplify the chaos or did you absorb it? The next time the pressure spikes and everyone looks to you, remember they're searching for a steady presence. Give them a symbol they can rely on.

When a master forger wants to move a fake painting, they don’t try to convince a buyer it’s real. That’s a losing game. Instead, they drop a hint to a renowned art expert. They leave breadcrumbs in a dusty attic or a forgotten estate.

They let the expert "discover" the lost masterpiece.

Once the expert authenticates the fake, the forger’s work is done. The expert’s ego is now permanently tied to the painting’s legitimacy. If anyone questions the artwork, the expert will fight tooth and nail to defend it. They aren't protecting the forger; they are protecting their own reputation as a genius.

We are heavily wired to protect our own discoveries. When someone hands us a fully formed idea and tells us to agree, our natural defense mechanisms flare up. We look for flaws. We play devil's advocate. We push back.

But when we connect the dots ourselves, the resulting idea becomes ours. We rarely scrutinize our own brilliance; we champion it. The art forger exploits this cognitive blind spot. They weaponize the expert’s ego to do the heavy lifting.

You waste immense energy trying to force people to see your perspective. Whether you are pitching a new direction to a skeptical team, negotiating a deal, or navigating a stubborn disagreement, brute-force persuasion is highly inefficient.

Stop handing people the finished painting. Hand them the brush.

Present the raw data. Frame the problem clearly. Lay out the exact constraints. Then, step back and let them connect the final dots. Let them arrive at your intended conclusion entirely on their own.

When they inevitably "discover" the solution you engineered, they won't just agree with it, they will take ownership of it. They will defend your idea with the exact same ferocity as an art critic defending a counterfeit masterpiece. Because to them, it isn't your idea anymore. It's theirs.