I Make Games Work in Production

I work as a Game Producer focused on live systems, player behavior and long-term retention.
I align teams, systems and priorities to make sure what gets designed is actually built, shipped and sustainable over time.

My Approach

Most systems break when they go live.

Combat, progression, economy and live ops are often designed in isolation…
and only connected later, when it’s already too late.

My job is to make sure that doesn’t happen. That means aligning design, product and development before problems hit production.

Every system is part of a live environment:

it drives player behavior
it impacts retention
it affects long-term scalability

Design decisions are not only about “what feels good”.

They are about what works over time.

Systems Are Not Features

As a producer, I don’t think in features.
I work on systems that generate player behavior.

Creates player choices

Adapts over time

Reduces the need for constant content production

This is especially critical in live service environments, where sustainability matters more than novelty.

The goal is not to create more content.

The goal is to create systems that make content last longer and making sure they can be implemented without breaking production.

Designing for Behavior

In live environments, every system drives behavior.

Daily missions, progression loops, reward structures. All shape how players interact with the game.

My focus is to align systems with natural player behavior, not force artificial actions.

That means:

rewarding what players already do
reducing friction instead of adding tasks
building habits without creating pressure

The best retention systems don’t feel like systems.

They feel like the game and they work within production constraints, not against them.

Designing with Measurable Outcomes

In live ops, every decision needs to be measurable.

Even when working on conceptual systems, I design with clear validation metrics in mind:

Retention (D1, D7, D30)
Session length and frequency
Progression depth
System usage distribution
Economy stability (inflation / sinks / flow)

These metrics are not post-launch tools. They drive priorities, trade-offs and decisions during production.

Sustainable Live Service Design

Most live service systems fail for the same reason: they rely on content volume.

More events. More rewards. More pressure.

This approach is not sustainable.

I focus on systems that:

evolve without resetting player progress
introduce variation without breaking balance
maintain long-term engagement without power creep

Retention should come from depth, not from obligation. If a system requires constant content to survive, it becomes a production bottleneck, not a scalable solution.

Designing Means Choosing

Protect what matters

Every system involves trade-offs.

Engagement vs fatigue
Progression speed vs long-term value
Flexibility vs clarity
Monetization vs trust

As a producer, making trade-offs explicit is critical to avoid misalignment across teams.

Good game systems are not about maximizing everything. It’s about choosing what matters and protecting it.

What This Means in Practice

What I Drive in production:

drive player behavior without forcing it
scale systems without constant content dependency
align gameplay, progression and economy across teams
support long-term retention without breaking player trust
ensure systems move from concept to shipped features

Games are not just systems. They are coordinated efforts across teams, timelines and constraints and my role is to make sure they hold together in production.