Post

Players don’t learn what you value from your patch notes. They learn it from your systems. Which scoreboard you ship, which numbers you hide, how much friction you keep, what you charge for queuing into a ranked match: every one of those is a statement about who you think the player is. And players read all of it. They’re the most thorough close-readers any medium has ever produced, and they’ll find the sentence you didn’t know you wrote.

I’ve spent a long time writing those sentences at scale. League of Legends at Riot starting in 2013: champion select, position-based matchmaking, the 10-ban draft, Honor 2.0, Hextech Crafting, match history. Black Ops 4 multiplayer at Treyarch in 2018: progression, clans, ranked, the competitive metagame. Then six years at Respawn, where I led Experience Design on Apex Legends from launch through Season 22. In games, I find the claim runs even narrower and harsher: the system is the message, and the system is the one part of the message you can’t spin.

This site is the manual I wish someone had handed me in 2013.

Whatever you write in the announcement post, the system underneath it makes its own announcement, and the system’s version wins.

A scoreboard that displays kills and damage tells the lobby what mattered tonight, whatever the mode’s objective claims. A ranked queue with an entry cost says losses are supposed to hurt here. A crafting system built on randomized drops says something too. On my portfolio page for Hextech Crafting I compressed it to one line: “agency of choice is given up for a reduction in cost.” I still think that sentence was the real design, and everything else we built was just the UI for it.

Designers like to believe the rhetoric lives in the writing (the lore, the tooltips, the dev blog), but it doesn’t. It lives in the incentives, the visibility decisions, and the prices. You’re making rhetorical moves with every system you ship whether you intend them or not, so you might as well make them on purpose.