CertainlyT: Product Lessons from a Controversial Game Designer

The Case for Friction

There's a dangerous trend in modern product design: our obsession with making everything "seamless" until it becomes invisible. We chase zero friction, but what we often get instead are products that fade into the background—forgettable, replaceable, unloved.

Bradford "CertainlyT" Wenban spent his career at Riot Games fighting exactly that kind of stagnation. He wasn't designing apps or interfaces. He was designing champions for League of Legends. But his philosophy on how humans engage with complex systems should matter to anyone building products today.

The Meaningful Burden

CertainlyT's most famous—and controversial—principle is simple: fun is learning. He didn't want players to pick up a character and master it in five minutes. He believed that if a champion felt too simple, it was essentially redundant.

So he introduced what he called a "burden of learning." He made players struggle. Whether it was Aphelios's intricate weapon cycling or Kalista's unconventional movement, he forced people to abandon their comfortable habits and think differently.

In product design, we experience this tension constantly. New patterns or paradigms feel heavy and unintuitive at first. But CertainlyT's "fruit of labor" principle shows us something crucial: when you give users a meaningful challenge, you're not just handing them a tool. You're offering them a path to mastery. That moment when they finally "get it" creates a depth of loyalty that no frictionless experience can match.

Systems Over Features

As a fellow Political Science graduate, I recognize a specific pattern in how Wenban approached design. We're trained to think about long arcs and systemic dynamics rather than isolated events. When Wenban designed a character, he wasn't just adding another option to the roster. He was reshaping the entire competitive ecosystem.

He was willing to be the villain in the short term. Players initially hated his designs—they felt overloaded and oppressive to play against. But he wasn't designing for day-one Reddit threads. He was designing for how the game would evolve over years. His reworks of champions like Caitlyn and Warwick became benchmarks precisely because they prioritized the long-term health and depth of the system over immediate comfort.

Bridging the Gap

One of CertainlyT's most valuable skills was bridging high-level concepts with concrete implementation. For those of us who work between strategy and execution, this is the essence of the job.

He took abstract ideas about human psychology and pattern recognition and translated them into specific mechanics. He didn't play it safe. He understood that a product everyone merely tolerates is a failure. He'd rather have half his users love the depth and half hate the complexity than have everyone feel nothing at all.

A Final Reflection

It's easy to build a "safe" product that follows every guideline to the letter and never upsets anyone. But that's how you end up with experiences that feel like promotional material rather than something people actually live with.

CertainlyT taught me that frustration isn't always a bug—sometimes it's a feature. If we want to build things that truly stand out or change how people work, we need to push boundaries. We need to trust our users enough to challenge them.

After all, as PolSci graduates know: the most enduring systems are the ones that demand the most from their participants.