Perfect Dark – Case study
Spykata: From cinematic idea to systemic, player-driven combat (in first-person)
Project Role
Strike Team Design Lead (Player Abilities & Close Quarters Combat)
Studio Title
Senior Systems Designer / Design Manager
​
Studio
Crystal Dynamics | 2024
Feature Summary
Gun-Fu (internally dubbed Spykata) became the defining combat mechanic of the Perfect Dark reboot: a fluid, cinematic system blending gunplay, parkour traversal, and close-quarters combat into a single expressive player fantasy.
The Problem
When I took ownership of the feature, Perfect Dark had already been in development for several years. While the game technically had guns and CQC mechanics, the core combat loop lacked cohesion, clarity, and player agency
Key challenges:
-
Combat was overly animation-driven, limiting responsiveness
-
Success relied heavily on NPC positioning and setup
-
Player inputs often felt out of sync with outcomes
-
Multiple teams had strong, sometimes conflicting, ideas of what “Gun-Fu” should be
​
This was not a blank-slate problem. It was a leadership problem inside a live, complex production.
​
Vision and Creative Alignment
The creative north star was intentionally broad but emotionally clear:
“Imagine if John Wick, Max Payne, and Lara Croft had a super-spy baby.”
​
To ground that fantasy, I aligned the team around shared touchpoints:
-
Film: Equilibrium, John Wick, The Matrix
-
Games: Max Payne 3, Mirrors Edge
-
Franchise DNA: The original Perfect Dark
​
The goal was not to recreate those references literally, but to extract feel:
-
Momentum over memorization
-
Player intent over canned sequences
-
Style emerging from systems, not scripts
Leadership Approach
Rather than incremental tweaks, I proposed a strike-team level reset of the feature.
​
Key leadership actions:
-
Established a clear design owner for Gun-Fu to reduce fragmentation
-
Framed Spykata as a systemic prototype first, not a polish pass
-
Coordinated across Weapons, Traversal, CQC, AI/NPC, Animation, and Camera teams
-
Authored and maintained the core documentation to keep alignment tight
-
Represented my team in weekly director reviews to build trust and unblock decisions early
​
This was as much about confidence and morale as it was about mechanics.
Execution and Iteration
Execution centered on speed, clarity, and daily feedback.
​
What we did:
-
Rebuilt the feature as a systemic combat layer, not a collection of moves
-
Reduced reliance on bespoke animations in favor of player-driven logic
-
Played the build daily, iterating continuously
-
Shipped and reviewed multiple internal iterations quickly
-
Allowed for switching between iterations at runtime to compare delta
​
The third major iteration proved to be the turning point, where the system finally clicked for both players and developers.
Outcomes and Impact
​
While details are NDA-restricted, I can share the following outcomes:
-
Gun-Fu evolved from a situational, fragile mechanic into the core combat identity of Perfect Dark
-
Animation budget for the feature was reduced by approximately 85 percent
-
Combat became more readable, responsive, and extensible
-
Team morale improved significantly across partner studios as clarity returned
-
Alignment replaced debate. Momentum replaced hesitation.
​
Most importantly, the feature went from “cool idea” to game-defining pillar.
What this demonstrates
​
This feature highlights my ability to:
-
Take ownership of high-risk, high-visibility systems mid-production
-
Align multiple teams around a shared player fantasy
-
Balance creative ambition with production realities
-
Lead through ambiguity without burning teams out
-
Turn systemic design into something players immediately feel
​
And, as always, none of this happened alone. The outcome was the result of focused, empowered teams doing their best work once the path forward was clear.