
Battlefield 6:
Beyond Spectating
My Role:
UX Designer
Timeline:
Oct 2024
Skillset:
Rapid Iteration | Experience Design System Design | HUD Communications
Design for High-stress and Fast
Paced Environments
The Challenge:
Keeping players engaged beyond active gameplay
In Battlefield 6, players who were eliminated could face a period of downtime before returning to the match. This interruption created a potential point of frustration, particularly for players eager to return to the action.
I joined an ongoing initiative to explore how we could transform that downtime into an opportunity for strategic team participation.
The challenge was to introduce a new layer of tactical gameplay without overwhelming players, distracting them from the core experience, or discouraging them from redeploying.
The Solution:
Turning downtime into an opportunity for teamwork
We explored an interactive spectator system that allowed eliminated players to continue supporting their squad through surveillance, reconnaissance, and environmental interactions.
Using a tactical map, players could locate and hack network hubs, access connected cameras and devices, identify enemy positions, and communicate valuable information to teammates still in combat.
My focus was on making this complex system approachable through clear interaction patterns, contextual onboarding, and intuitive communication.
The experience needed to be engaging enough to make downtime meaningful while remaining secondary to the core gameplay.
Impact at a Glance
Improved Feature Engagement
Playtesting showed increased engagement after we introduced contextual onboarding that helped players understand the system and its capabilities.
Clarified complex interactions
Created detailed interaction flows covering multiple system states and edge cases, helping designers and engineers understand how the feature should behave.
Informed future design
Although the feature was ultimately cut before launch, the work contributed to broader design discussions and helped inform other features and communication patterns within Battlefield 6.
Understanding the Problem
Battlefield 4: Commander Mode Reference
Discovery & Alignment
I joined the project after initial design exploration had begun, taking ownership of the UX work during a period of rapid iteration.
The team had identified several challenges that could prevent the feature from succeeding:
-
Discoverability: Players might not realize the system was available after being eliminated.
-
Learnability: The feature introduced unfamiliar interactions and mechanics that players would need to understand quickly.
-
Engagement: Players might overlook the feature or choose not to participate if its value wasn't immediately clear.

Cyberpunk 2077: Security Camera Mode reference
Research
Given the project's accelerated timeline, I focused my research on existing game systems that could help us evaluate different approaches to interaction and navigation.
I explored Battlefield 4's Commander Mode for its strategic oversight and team-support mechanics, alongside Cyberpunk 2077's camera hacking system for its approach to navigating interconnected devices.
Rather than conducting a full heuristic analysis, I used these references to facilitate focused discussions with game designers about which patterns could translate effectively into our experience.
This helped us align on the core interaction model and move quickly into design exploration.
Designing Solutions
Feature Onboarding
One of the biggest challenges was helping players understand a completely unfamiliar feature without requiring a lengthy tutorial.Traditional onboarding could create additional friction for players already frustrated by being removed from active combat.
We designed a brief introduction, lasting less than 30 seconds, that combined cinematic storytelling, voiceover, and visual demonstrations to communicate the feature's core capabilities.
From there, players could explore the system and learn through interaction.
Design rationale: Prioritize immediate comprehension and player autonomy over exhaustive instruction. The goal was to provide just enough guidance for players to get started without making onboarding another obstacle to gameplay.
Hacking a Hub
The hacking system introduced multiple layers of interaction. Players needed to identify available network hubs, understand which devices were connected, and determine how those devices could support their squad.
I worked through the interaction flows and system states needed to communicate these relationships clearly.
Players could select hubs within their squad's operating area, access connected devices, and use those devices to gather intelligence or interact with the environment. The challenge was balancing the depth of the system with the speed at which players needed to understand and act on information.
Design rationale: Establish clear relationships between hubs, devices, and available actions so players could build a mental model of the system without relying on repeated instruction.
Accessing a Device
Once connected to a network hub, players could access multiple devices, each offering different tactical opportunities. Requiring players to repeatedly return to a menu or cycle through every available device would introduce unnecessary friction.
To support faster navigation, we explored allowing players to identify nearby connected devices directly within their current view and move between them.This created a more fluid interaction model that supported exploration while maintaining awareness of the surrounding environment.
Design rationale: Reduce unnecessary navigation steps and help players stay focused on the tactical information they were gathering.

Enemy Hack
The system also needed to account for situations where enemy players had already compromised a hub or were actively attempting to take control.
These scenarios introduced different levels of urgency and required distinct communication.
I designed interaction flows to distinguish between a network that was already compromised and one currently experiencing an attack.Both states needed to feel consistent within the broader system while communicating different risks and available actions.
Design rationale: Use consistent interaction patterns while making meaningful differences in system status immediately recognizable.
Redeploy
Although we wanted the spectator experience to feel engaging, returning to active gameplay remained the player's primary goal.
Players could choose to redeploy immediately, but their return sometimes depended on teammates reaching a respawn location. This created an additional communication challenge: helping players understand what was happening while they waited and when they could expect to return.The design needed to make this transition clear without creating confusion about whether players should continue interacting with the spectator system.
Design rationale: Support meaningful secondary interactions without allowing them to compete with the user's primary objective.
Validation
User Testing
Rather than relying solely on Figma prototypes, the team prioritized implementing the feature in-engine to evaluate it during gameplay.
This allowed us to observe how players interacted with the system in the context of an actual match, including how they transitioned from combat into the spectator experience.Playtesting revealed that players engaged with the system more frequently after we introduced the onboarding explanation.
Testing also exposed broader design concerns. In particular, allowing eliminated players to control offensive equipment raised questions about fairness and whether the feature could undermine the consequences of being eliminated.
These findings reinforced the importance of evaluating not only whether players could understand and use a system, but also how that system affected the larger experience.
Reflection & Takeaways
A video walkthrough of the feature I made for a studio-wide townhall
Although the feature was ultimately cut due to production constraints and concerns about its impact on core gameplay, the project offered valuable lessons about designing complex systems within an established product.
What worked well
One of my most meaningful contributions was translating a complicated gameplay concept into detailed, actionable interaction flows.
By documenting system states, edge cases, and interaction patterns, I helped establish a shared understanding across design and engineering disciplines.
The onboarding improvements also demonstrated how relatively small changes in communication could influence player engagement with an unfamiliar feature.
What I
Learned
This project reinforced that good UX isn't just about making a feature intuitive. It's also about helping determine whether the feature creates meaningful value within the broader product.
A system can be understandable and engaging while still introducing conflicts with other user goals or established product expectations.
What I'd explore next
If I continued working on this concept, I would focus on strengthening communication between spectators and active squad members so that both sides could better understand the value of their collaboration.
I would also explore clearer entry and exit points for the experience, ensuring that players felt motivated to participate without losing sight of their primary goal: returning to the match.




