Why I'm Writing This

After more than a decade in mobile games, I’ve built features, games, live ops calendars, and full product organizations. I’ve seen what happens when PMs have to do it all — scope, design, coordinate, analyze — often without clear ownership or support. I’ve had to prioritize between retention and revenue with too little data and too many opinions. I’ve been the IC trying to influence without authority, and the Director trying to scale a team without burning people out.

And through it all, I’ve noticed something:

Most content about game development isn’t written for the people building mobile games at scale.

It’s written for indie devs. For console producers. For generalist tech PMs. But not for the mobile game PM trying to run an event while planning next quarter’s feature roadmap. Not for the product leaders trying to level their team, define KPIs, and stop being the human Jira board. Not for the people quietly holding together $100M games from the inside out.

So I’m writing the thing I wish I’d had: A clear, unapologetic guide to what product leadership in mobile actually looks like.

Because most teams don’t have a toolkit of best practices. They’re figuring it out under pressure — making hard calls between player experience, revenue targets, and org dynamics. I want to make that process easier, more structured, and less isolating.

And because I believe in the democratization of information — not gate-keeping expertise behind senior titles or secret decks. Everyone deserves access to the tactics, templates, and mindsets that have actually worked.

Who This Is For:

• Aspiring PMs who don’t want vague “break into games” advice — they want a path to success
• PMs working on mobile free-to-play games with a live services business model 
• Senior ICs trying to move into team leadership or more strategic function
• Product leaders figuring out scope, team structure, and performance ownership

Why Now?

Because after years in the trenches, I’m ready to codify the systems that worked — and the ones that didn’t.

Because too many PMs are still flying blind, thinking it’s just them.

Because no one teaches you how to manage tradeoffs between creative, data, and business — you have to learn the hard way.

Because most teams are navigating pressure without a blueprint — and it doesn’t have to be that way.

And maybe because I’m ready to stop just building quietly — and start sharing what I’ve learned to help others build better.

What You’ll Find Here:

• Monthly insights from inside mobile PM teams: org design, prioritization, KPI ownership, monetization
• Templates, frameworks, and systems I’ve used across teams and studios
• A growing library of content for product people in mobile games — from feature specs to team design to leadership transitions

No fluff. No hustle talk. No LinkedIn broetry. Just best practices, clarity, and honest lessons from the people behind the build.

Welcome to Modes of Play.