Optimizing the Point Away<br>Nothing in Minecraft tells you to punch the tree.

Nothing warns you that night is coming, or what the crafting table does, or that the green thing walking toward you is about to explode. The game was, for practical purposes, unplayable without another kid who already knew. Everything you needed lived outside the game, in the schoolyard, the computer lab, the wiki, the older brother, passed hand to hand like it was contraband. And it became the best-selling game in the history of the medium.

Measured against the last forty years of playtests, funnels, retention curves, and postmortems, Minecraft is a catalog of errors: a brutal, unexplained first night with no tutorial, no goals, and no help coming. The most successful product the medium ever produced fails the entire accumulated curriculum, and it isn't a miracle, so the curriculum is wrong. The tempting save is that Minecraft's core loop was simply so good it could pay friction's tax. But the friction wasn't a tax on the loop; it was in the loop. The withheld knowledge is what made another kid necessary, and the other kid is what made it spread.

I want to argue something stronger than the curriculum being wrong, though: the industry, tech and games both, has been forgetting how to build great things while believing it's been learning to build them better, and the learning machinery is the mechanism behind the forgetting.

Forgetting at n=1: what happened to Viva Piñata

You can watch it happen inside a single studio, four years, one franchise. I recently replayed the original Viva Piñata and its sequel on the same day.

The first thing you do in Viva Piñata is walk down a beautiful hill into a ruined garden and talk to a crying girl standing in the rubble. She hands you a shovel and asks for help cleaning up the mess. You start by beating cracked ground into dirt. Effort, violence against the decay. Then a small worm appears, colorless, because the dirt you just made is its habitat. It moves in as you keep working, and then it blooms into gorgeous technicolor. In twenty minutes the game has taught its entire thesis without a single rail or forced action: life in this world is downstream of your work.

The sequel throws you into a pretty garden decorated with grass, flowers, and stepping stones. A creature lies penned in a fence. The first new one appears before you've done anything (yes, in an unskippable cutscene before your first action; I wish this point were harder to make), and within seconds the game assigns you a forced task. Life in this world is content to click through.

Nobody at the studio experienced these changes as mistakes. They were "improvements", by every measurement the studio could make. The empty start almost certainly playtested as friction: players took too long to reach their first piñata. So the garden got pre-filled. Nobody in the room knew what the empty garden was for, nobody had the will to defend it, and no one came to save the whole point of the game from optimization.

Metrics kill games by making fun inadmissible

The industry has what it sees as a learning system: playtests, A/B tests, dashboards, postmortems, conference talks, retention funnels, churn. But the system only ever learns what it can measure, so whatever it can't measure eventually just stops counting as an argument at all.

Most friction really is just bad UX, to be clear, and it should die. The disease is that the instruments can't tell one from the other: confusion that is the game and confusion that's a broken door report identically, and both get removed.

Everyone at the table can see the costs of friction:

churn

funnel drop-off

retention as a percentage

The benefits stay invisible right up until they're everything:

ownership

folklore

a sense of wonder

the story someone tells in ten years

the friend who teaches you the secret

These are all long-term properties. None of them can be seen inside a playtest or a quarter, and up front they cost you slower adoption. So every optimization-driven decision removes them, and the door only swings one way, because few producers ever green-light restoring confusion, though the good ones do. Each removal the data forces is locally correct, and the sum is a game nobody loves.

The filter runs on the people too. Defending illegible value is a career risk. A producer who restores confusion has nothing to show for it at review season, so a professional can't keep making bets their own instruments call insane. The only ones who can keep it up are people building out of love for the thing. Carmack and Notch never asked a dashboard for permission; the conviction was the company. Everyone else forms their taste inside the previous generation's already-smoothed games, until the tooltip layer stops being a choice and becomes what games are. Between broken-up teams, only the articulable transmits: systems, content cadence, retention tricks. The tacit part dies in every handoff, and four...