Development Skill
Prototype
Rapid proof-of-concept builds
Prototyping is how I think, how I communicate, and how I solve problems. You can debate a design decision for hours. A twenty-minute build will tell you more than any document ever could. Where an artist sketches, I build interactions.
Build First
The fastest path to a real answer is a playable thing that people can experience. Arguments about whether a mechanic will be fun are almost always resolved the moment someone plays it. I reach for a build before I reach for a spec.
I draw a hard line between prototyping and production. Prototyping is about learning: what works, what does not, and what the player actually does versus what the design assumes they will do. I move fast, build rough, and play often.
Kill Fast, Learn Faster
If a mechanic does not create something worth keeping in a prototype, production polish will not save it. I cut ideas quickly and without sentiment. Efficiency means everything in my design process.
The hardest part is cutting what almost works. "Almost" is not good enough. That said, some ideas come back sharper after being cut. The time away reveals the missing piece.
Prototypes as Communication
A working prototype communicates intent across disciplines in a way no document can. Programmers understand scope. Artists understand feel. Producers understand risk. All from a single playable build.
In practice
Rivertale anchor mechanic: First version was a single button hold. Playtested immediately, then got replaced with a rotary encoder after a session revealed players wanted physical effort to match the immersive experience.
Mowdown boost system: Prototyped as a simple speed multiplier. Iterated to a resource-based system within a week once playtesting showed the multiplier had no meaningful decision behind it.
Oh, Bugger! group management: Built and tested in two days before any art complimented it. Proved the core tension loop before committing production time.