Development Skill
Iterate
Data-driven refinement cycles
Iteration means nothing without a clear goal. Good iteration starts by knowing what you are looking for, what the player should feel, and what success looks like before you begin making changes. Without that, you are just changing things.
Targeted Testing
I structure playtests around open questions, without guiding the player. Not "was that fun?" but "what did you feel during that encounter?" Trying to find the true reason behind a feeling.
I observe before I ask. Player behavior during a session tells you things they will never mention afterwards. Where they hesitate, what they ignore, where they died in ways I did not expect: that is the real data.
Data in Practice
In Oh, Bugger!, tracking enemy pathfinding call frequency revealed a 90% redundancy that was cut to 1.2ms per frame through targeted optimization. The problem was invisible until the numbers surfaced it.
In Rivertale, step-count tracking after introducing the anchor mechanic showed player movement doubling across sessions. The system was driving physical engagement rather than passive play, which confirmed the design intent was landing correctly.
The difference
Profiling and observation are not the same discipline. Profiling catches what the design is doing. Observation catches what the player is doing. Both are required. Trusting only one produces half a picture.
Knowing When to Stop
A system can be over-tuned into something that works technically but loses its character. Perfect and done rarely coincide, and chasing perfect often destroys what made something interesting in the first place.
I stop iterating when player behavior consistently matches the design intent, not when everything feels optimal. Consistent beats perfect. Shipping matters.