Every event started with a reason to exist. I'd define the target metric, the audience, and the constraints — budget, timeline, art capacity — before touching any theme or mechanic. From there I'd develop the concept and work out what made this event different from the last one on the same seasonal beat.

This is where most of the design happened. I built the core loop and progression path a player follows from first task to final reward. On top of that sat the economy and monetization layer: event passes and time-limited offers that gave players who wanted to go deeper a way to do it, without walling off the players who didn't spend. Content planning — assets, light narrative framing, quest structure — came out of this phase too.

Once the design was solid I'd get it into a playable build and refine the UX against how it actually felt rather than how it read on paper. Playtesting and balancing used internal testing alongside data modeling to find where the difficulty or pacing was off. I also set up the tracking and KPI instrumentation so each event reported the data I needed, and ran A/B tests to validate the choices I was unsure about before full release.

Before launch I'd do the final polish pass, tighten the UX, and align with marketing so the event went out with the right support behind it. After it went live I monitored performance and made real-time adjustments — a live event rarely behaves exactly the way the model predicted. When it wrapped, I ran a post-mortem on what worked and what didn't, and documented the learnings so the next event started from a better place.

The part of this work I'm proudest of isn't any single event — it's what I changed about how we built them. I turned the repeated pieces into reusable frameworks: templated event loops, progression structures, and economy setups that could be reskinned and retuned for a new season instead of rebuilt. Each new event cost less to produce than the one before, the development cycle got shorter, and every event shipped fed both content and learnings back into the frameworks the next one used.

I started by defining the cast-and-catch interaction — the single repeatable moment the whole feature rests on. It had to be satisfying on the first try for a casual player and still feel skilled enough that repeat plays didn't feel mechanical. That meant keeping the input simple but giving feedback that made each catch feel earned.

Around the core loop I built a milestone-based progression system with catch targets, rare species, and tiered rewards. The goal was to give players enough to chase across the event window without requiring constant play — each session should feel like meaningful progress, not a grind.

Most of my iteration time went into holding the right tone. I tuned catch rates, difficulty curves, and session pacing through repeated playtesting until the loop stayed relaxing rather than fiddly. The target was a player who finishes a session and wants to come back tomorrow — not one who finishes frustrated or one who finishes without feeling anything.

I designed the monetization layer around optional convenience — bait, retries, and progression accelerators — so spenders got a better experience without non-spenders hitting a wall. Spend points were positioned at moments where a player had already engaged enough to feel invested, which is when the decision to spend feels natural rather than forced.