Farmville 3 | Zynga

Farmville 3 is a farming simulation game, the third in the Farmville franchise that helped define the casual mobile genre. I joined the team during softlaunch and stayed through full launch and into live operations, building player facing experiences across the product.

A game like Farmville ships a lot of systems over its lifetime. Events, progression tracks, seasonal content, tutorials, store layouts, social features. My work sat at the intersection different player journeys and how do players understand what’s available, what matters during that journey, and where the game goes from here?

The principle that guided most of my work on FV3 was a simple one: direction over pressure.

In games with deep feature sets, there’s a temptation to push players toward engagement through urgency — countdown timers, limited offers, fear of missing out. That works, but it erodes trust over time. We took a different approach: make the journey visible. If players can see where they are and where the game goes next, they’re more likely to stay because they want to, not because they feel they have to.

This philosophy shaped everything from how we surfaced progression to how we timed contextual tips to how we decided what not to show.

Progression systems were the backbone. These are the features that help players understand their current place in the game and what achieving the next milestone unlocks. Rather than a single linear track, we designed layered systems that could adapt to where a player was in their lifecycle.

For early players, the focus was on immediate clarity, short loops, visible rewards, guided next steps. For players deeper into the game, we shifted toward longer arcs and personal goals. The system needed to feel like it grew with the player, not like it was the same tutorial on repeat.

A game with as many systems as FV3 risks overwhelming players. New features appear over time, events rotate, and the map expands.

We designed a contextual guidance layer that surfaced tips and suggestions based on player state. A system that understood what the player had and hadnt engaged with, and offered direction without demanding attention.

The goal gradient effect shaped how we timed these interventions. People naturally accelerate toward a visible goal,so we made sure there was always a next goal in view, especially during the moments right after a big achievement when momentum is most fragile.

With dozens of features, the interface couldnt show everything at once. We relied on progressive disclosure heavily to reveal options and systems gradually as the player progressed, rather than front loading complexity.

We addressed this by tying feature reveals to natural progression points, unlocking a new area would introduce its associated systems in context, or when user check their curent level, they could see what features they could unlock as they evolve, or when they see something cool we show them how they could get them rather than dumping them into a settings menu.

None of this was designed in isolation. Game designers owned the system logic and content curves. I worked with them on the information hierarchy, interaction pattern, what gets surfaced, where, and at what priority.

Engineering flagged feasibility constraints early, which shaped how dynamic the contextual systems could be. PMs helped prioritize which systems to invest in and to set up experiements to test the metrics.

The work was iterative in the truest sense. Ship, observe, adjust.