An Australian bottlenose dolphin named Bubbles has developed a system for getting dinner.
He selects a bigeye trevally and pursues it until the fish regurgitates whatever it recently ate. Bubbles then collects the abandoned meal.
It’s not exactly table manners, but it is a system.
The method is inventive. It is repeatable. It saves Bubbles the trouble of finding the original prey himself. Judged strictly by the result—Bubbles wanted food and ended up with food—the process works.
Researchers describe the behavior as kleptoparasitism, which is a scientific word for acquiring lunch through somebody else’s terrible afternoon.
Bubbles isn’t evil. Bubbles is a dolphin.
Human beings, unfortunately, have meetings, dashboards, spreadsheets, and the ability to ask who pays for our efficiency.
“It works” is one of the most dangerous compliments we give a system because it usually ends the evaluation too early. Once a process produces the number we wanted, we stop asking what else it produced.
A dealership can increase deliveries by pushing every customer through faster. The units show up on the board. The month looks healthy. Somebody may even send an email congratulating everyone on “executing the process,” which is corporate language for placing a trophy on the table before checking whether the table is on fire.
But speed can hide its bill.
A salesperson skips a step, and finance has to explain something the customer should have understood earlier. A promise gets made during the sale, and service inherits it afterward. Missing documents become somebody else’s urgent problem. One employee keeps staying late because that person is dependable enough to absorb what the system refuses to fix.
The process works—as long as the only measurement is the sale.
Second-order thinking asks what happens after the first result.
The first-order question is simple: Did we close the deal?
The second-order questions take longer. What did the shortcut teach the employee? What expectation did it create for the customer? Which department inherited the unfinished work? Can we repeat this method for a year without grinding down the people responsible for making it appear successful?
The short game counts what it gains.
The long game also counts what the gain consumes.
This distinction reaches far beyond business. A family arrangement may keep the peace because one person has learned to swallow every objection. A manager may appear decisive because employees stopped bringing him bad news. A parent may produce obedient children by making honesty more dangerous than silence.
Those systems can look remarkably efficient.
There are fewer arguments. Fewer questions. Fewer uncomfortable meetings.
There may also be fewer people willing to tell the truth.
Playing the long game does not mean abandoning results or designing a workplace where nobody is ever uncomfortable. Good systems require standards, accountability, and consequences. Sometimes the right process is difficult precisely because it refuses to move the burden somewhere less visible.
But leaders should become suspicious whenever a method works only because the same people keep paying its hidden costs.
That cost may appear as rework, resentment, turnover, damaged trust, exhausted employees, or customers who complete one transaction and never return. None of those consequences may appear on this month’s scoreboard. The future has always been generous about letting us borrow from it before sending the invoice.
Bubbles doesn’t have to consider any of this. He doesn’t conduct employee surveys, calculate customer retention, or worry about the moral development of the trevally.
He eats.
We are supposed to be capable of more.
A good system does not merely produce the desired result. It produces that result without quietly consuming the people who keep it operating.
Every leader should ask two questions before praising a process:
Does it work?
And what does it do to the people inside it?
