Article URL: https://ianreppel.org/how-successful-companies-go-blind/ Comments URL: https://news.ycombinator.com/item?id=48859678 Points: 76 # Comments: 33

The Mexican cavefish kept its eye genes for over a million years after the eyes themselves disappeared. Something similar happens to companies once they achieve success. The Mexican cavefish (Astyanax mexicanus) exists in two forms only kilometres apart. In the rivers along the Sierra del Abra, the fish has eyes and behaves the way ordinary fish behave. In the limestone caves under the same mountains, members of the same species are blind, depigmented, and translucent. The genome is virtually identical. Within hours of fertilization in cave conditions, the lens-building programme triggers early apoptosis (i.e. programmed cell death), and the energy that would have gone to optic tissue is redirected to traits the cave actually rewards: better olfaction, deeper feeding, and fat reserves against the next lean year. Sight is no longer expressed. The same fish, hatched in the river, would see. Companies who have forgotten what it took to become successful are similar: they stop recognizing competence, because the environment has stopped expressing the trait in anyone the company hires. Call it competence blindness, which is different from incumbents who fail because they cling to the customers and margins of yesterday’s market. Firms with competence blindness do not disappear. In fact, they can survive for decades. When a startup hits rapid growth, it hires at speed. Headcount targets bend the bar until the bar disappears altogether. Engineers who have never worked elsewhere learn the house style, and within a year find themselves on hiring panels. They select for comfort with the prevailing mess, because they have no other frame of reference. After a few cycles the company has a population of well-meaning people who do not suspect anything is off. They have only ever known the cave, and life inside the cave is good. The view from outside is encouraging: strong brand, decent margins, headcount up. From within, the view is not so flattering. Build pipelines only the original author can run, deployments so fragile that they require a senior engineer to be on call at all times, and a wiki so out of date it might as well be written in hieroglyphics. Because the company’s numbers still look fine, leadership believes the foundations are sound. In this climate, careful engineering becomes a vestigial trait: the capacity exists, but the expression has been suppressed by an environment that does not return the energy spent on it. An engineer who insists on expressing the trait is investing in an organ the cave will not feed. After the first round of overruled proposals, the apoptosis begins. Arrive with sight and the problems are immediately visible. You propose something the wider industry has already moved past, and you are told the suggestion is over-engineered, academic, and not aligned with priorities. What you intended as overdue maintenance reads as an attack on the identity of the engineers who stapled together the existing infrastructure.