What Playing Games Taught Me About Being a Better Product Manager
Gaming has been a constant thread throughout my life, from grinding Ragnarok Online and Seal Online as a kid, to spending hundreds of hours in Dota 2 and CS:GO, and Mobile Legends today. For a long time, I kept these two parts of my life completely separate which are the player and the product manager.
Then I started noticing something.
Every time I opened Mobile Legends, I was unconsciously doing product analysis. Why does this limited bundle feel urgent? Why does this shop refresh feel satisfying? Why did I spend on that skin but ignore the other one? The more I paid attention, the more I realized that the games are the most honest product feedback loop in the world.
Here are the 3 things gaming has taught me about building better products.
1. Retention is an emotion, not a metric
The best games don't keep you coming back because of push notifications or streak mechanics. They keep you coming back because something feels unfinished. There's a next rank to reach, a mechanic you haven't mastered, a social moment you don't want to miss.
The practical example is when I have goals to increase on user retention for Edutech, I stopped asking "how do we increase DAU?" and started asking "what makes a student feel like they left something behind?" That question shift in framing changed how we prioritized features entirely and it moved the retention number.
2. Every system has a “meta”
In games, the meta is the dominant strategy that emerges when you combine all the rules. Experienced players don't just follow the meta, they tend to understand why it exists, and when to break it.
Product roadmaps work exactly the same way. There's always an organizational meta, the priorities that get full support, the stakeholders with the loudest voices, the frameworks everyone defaults to. The most effective PMs I've worked with understand the meta deeply enough to know exactly when to play against it. That's not politics, that's systems thinking.
3. Losing teaches you faster than winning
I've lost ranked games in Mobile Legends that taught me more than any MVP finish. Failure is information.
When a feature doesn't move a metric, that's not a failure, that's a data point. The problem is that most product teams treat a failed experiment as something to quietly bury rather than learn from publicly. Gaming culture already normalized post-mortems long before others’ did. We just call them "analyzing the replay and statistic”
Final Thought
I'm not saying every PM should be a gamer. But I am saying that the habits that make someone a great player are exactly the habits that make someone a great product manager, such as pattern recognition, systems thinking, fast iteration, and emotional intelligence about what users actually feel
The two parts of my life were never really separate. I just needed to notice.
