TrenchOps 🐎 
The Strategy That Never Won a Single Match - And Won Everything
What a 1980 computer tournament explains about your worst customer, your dumbest feud, and your exit interviews
Around 1980, a political scientist ran a tournament for computer programs playing the iterated Prisoner's Dilemma. Game theorists, mathematicians, economists, the whole intellectual heavyweight class, submitted strategies. Some were baroque: probabilistic betrayal, opponent profiling, deception layers built to squeeze a few extra points out of the naive.
The winner was a handful of lines of code, submitted by a mathematical psychologist. Cooperate on move one. After that, do whatever the other player just did. That's it. Tit For Tat. Shortest entry in the field. It won again in the second tournament, where everybody already knew it was coming and had specifically designed strategies to beat it.
Here is the detail people always skip: Tit For Tat never won a single individual match. It cannot. By construction it can never score more points than its opponent, because it only ever defects in response. The best possible outcome against any given opponent is a tie.
It won the tournament by being the strategy that everyone did well against, including itself.
Read that twice if you measure your quarter in individual wins.
The three losing strategies, in office dress
- Always defect. Takes credit upward, distributes blame downward. Wins spectacularly early. In tournaments it dies, because nasty strategies also meet each other, and then they starve together. In companies it survives longer than it should, because every reorg supplies fresh unmet victims. It's a strategy that only works with high player turnover, which explains a great deal about companies with high turnover.
- Always cooperate. The nicest engineer on the team. Absorbs every emergency, never says no, gets farmed by exactly the people you'd predict, and is quietly gone in eighteen months. Unconditional kindness is not a strategy. It's a resource for other people's strategies.
- Grim trigger. Cooperate until the first betrayal, then defect forever. The senior architect who was overruled once in a design review three years ago and has been passive-aggressively correct ever since. Locally satisfying. Globally catastrophic.
Tit For Tat wins because it is four things simultaneously:
- nice (never defects first)
- retaliating (defection costs something, immediately)
- forgiving (one clean move restores trust)
- clear (the opponent can figure out the rules in a single round).
Clarity is the underrated one. Complicated retaliation policies get read as mood swings instead of boundaries.
The customer everyone had labelled hostile
I once inherited an account that internal folklore described as hostile. The customer's technical lead had a reputation. Escalated everything. CC'd executives with the enthusiasm of a man who had discovered the address book. Called our service level agreement "creative fiction." Two account managers had quietly rotated off before me.
I spent an afternoon reading ticket history before my first call. What I found was not a difficult human. What I found was eighteen months of small defections from our side. A promised callback that never happened. A bug marked "fixed" in a release note where it demonstrably wasn't. A workaround that was really a distraction delivered with a straight face.
He wasn't hostile. He was mirroring. He had opened with trust roughly a year and a half earlier, got defected on, and was now running the algorithm exactly as specified. From where he sat, he was the cooperative player being perfectly reasonable about a pattern.
So I did the only thing the model permits. Cooperate first, visibly, and make it cheap to verify. One promise per week, small, kept. When we couldn't fix something, I said so and gave a date for the next honest update instead of a fake date for the fix. I stopped forwarding optimism upward, and stopped forwarding it downward too.
Six weeks. Not because he was stubborn, but because trust in an iterated game rebuilds at precisely the same rate it was destroyed: one move at a time. There is no bulk import.
By month four he was pre-filtering his own team's tickets before sending them to us, because he had concluded we were worth not wasting. That is what a cooperating opponent looks like. Free labor, volunteered, because the payoff matrix finally rewarded it.
The flaw that runs your company's oldest feud
Pure Tit For Tat has a fatal weakness, and it's the real reason this article exists.
Two Tit For Tat players in a noisy environment - where a move can be misread - lock into a death spiral. One accidental defection, one dropped ticket, one email that lands colder than intended, and the two of them alternate punishment forever. Both worse off. Both behaving correctly. Neither wrong about the last move.
Now look around your office. That is the entire mechanism behind every long-running war between two departments who no longer remember what started it. Engineering thinks support dumps garbage tickets. Support thinks engineering ignores them. Both are retaliating for something that happened in a previous fiscal year, and both are factually right about the most recent exchange.
Corporate life is a maximally noisy channel. Chat, timezones, translation layers, middle managers helpfully rephrasing things into their opposite. If your policy is strict reciprocity with zero slack, you will end up in feuds with people who were on your side. That isn't integrity. It's a signal processing failure.
The fix from the later research is almost insulting in its simplicity: forgive occasionally without being provoked into it. Not always, not never - a small, deliberate rate, something like one in ten. Cooperate even when the last move was a defection. That single modification breaks the spiral and beats strict mirroring wherever information is imperfect.
Information in your company is imperfect. Permanently. So the optimal human strategy is not an eye for an eye. It's an eye for an eye, with a budgeted error allowance for grace.
That budget is not softness. It's the maintenance cost of a system you intend to keep using.
Why everything goes wrong on the way out
The second thing the theory tells you, and nobody puts on a slide: if both players know the game is finite, the logic unravels backwards from the last round. No retaliation is possible after the final move, so defect there. Which makes the second to last move effectively final. And so on, all the way back.
This is why almost every unpleasant surprise in business happens at the exit. The vendor whose quality collapses in the last quarter of the contract. The employee who has already signed elsewhere and stops caring. The customer who suddenly disputes twelve months of invoices in week two of the notice period. The manager who becomes honest with you only in the exit interview, which is the corporate equivalent of confessing to an empty room.
Nobody became a worse person. The horizon just became visible.
Two consequences. Keep the game long and visibly repeated, because reputation only has value when there is a next round. And when the horizon genuinely is finite - offboarding, contract end, a vendor you're replacing - stop expecting reciprocity to carry the load and switch to structure. Milestones, retained payments, handover checklists signed before the final salary run. Not cynicism. Arithmetic.
The best hire I ever made came out of the opposite move. A power horse 🐎 who had been treated as always-cooperate by three previous employers, underpaid accordingly, visibly braced for the usual. I opened with trust I hadn't earned yet: real budget, real authority, no probation theater. Cooperation came back on the first round and compounded for years. Cost of the move: the risk of being wrong once.
👉 Open cooperative. Every time, with everyone. The downside of one betrayal is small; the upside of a compounding relationship isn't.
👉 Retaliate fast and proportionally, then stop. A defection you swallow silently teaches the other side that defection is free. Delayed punishment reads as mood, not consequence.
👉 Be legible. The strategy won because opponents could predict it. If people can't model you, they can't cooperate with you - they can only hedge against you.
👉 Budget forgiveness before you need it. Decide in advance that roughly every tenth insult is noise, not malice. You'll be right most of the time and you'll save relationships pure logic would have incinerated.
👉 Never play to win the individual round. The strategy that couldn't beat anybody beat everybody. Your quarterly hero metric is scoring the wrong game.
👉 Check who defected first before labelling someone difficult. Read the last eighteen months of history. It's usually your own company in the log.
👉 When the horizon becomes finite, replace trust with structure - before the last round, not during it.
The most sophisticated players in the room lost to four lines of logic, because complexity is what you build when you're trying to exploit someone. Simple, predictable, reciprocal is what you build when you plan to still be here next year.
👇 Which internal feud in your company is just two reasonable teams stuck in a retaliation loop that nobody started on purpose?
This article is also available in German.
0 comment(s)
No comments yet. Be the first to comment.
Leave a comment