Simplifying Complex Decision Interfaces : 17 Systems Shipped, Zero Redesigns Required

The Challenge

The Division 2 is a complex beast. Deep customization, gear optimization, talent trees, mod systems, seasonal content — the kind of product where users make dozens of meaningful decisions per session. Here's the problem: some of those decisions took way too long. Core tasks needed 5-6 steps across multiple screens. Users made mistakes. They got frustrated. They asked the same questions over and over in community forums. My job? Make it simpler without dumbing it down. Our power users wanted control. Our casual users wanted clarity. Both needed the same interface. Not easy. But that's the fun part, eh?

My Role

• Led feature needs analysis for 17+ systems over 5 years
• Designed user flows, UI mockups, and interactive prototypes
• Created tutorial systems — steps, flows, instructional text
• Shipped everything end-to-end, from concept to live release

Discovery

The Complexity Problem

Our users range from "I play 2 hours on weekends" to "I have spreadsheets optimizing my builds." The existing interfaces? Built for the spreadsheet crowd. Deep, powerful — and overwhelming for everyone else.

The symptoms were clear:

• Core optimization task: 5-6 steps across 3+ screens
• Same questions popping up constantly: "How do I do X?"
• Errors on complex tasks
• Power users tolerated the friction. Casual users just... left.

The Personas

We had 4 core user types from earlier research:

The challenge: serve all four with ONE interface. No "casual mode" cop-out.

Design Principles

After analyzing pain points across dozens of features, I landed on a few rules:

1. 3 steps or less — Any core task. No exceptions.
2. Progressive disclosure — Simple first, depth on demand.
3. No dead ends — Every screen has a clear "what's next."
4. Immediate feedback — User always knows what happened.

These became my north star for everything that followed.

Solution

Case Example: "Tinkering on the Go”

Here's a concrete one.

The problem: Users wanted to optimize their gear — recalibrate stats, improve equipment. The old way? Navigate to a specific location in the game world, access a dedicated workbench, go through multiple menus. 5-6 steps. Every time.

The insight: Users don't want "optimization" as a destination. They want to optimize in context — while checking their inventory, while prepping for a mission, while comparing items. Right there, right then.

The solution: One screen. All optimization actions. Accessible from anywhere.

What changed:

• Single screen for everything
• Clear visual hierarchy: what can improve, what's maxed
• Contextual access: inventory, loadout, gear inspection — all entry points work
• Exactly 3 steps: Select item → Choose optimization → Confirm

Done. No location required. No menu diving.

Some other Systems

Tutorials That Don't Suck

Complex systems need onboarding. But here's my philosophy: if your tutorial has to explain the UI, your UI is wrong.

Tutorials should teach concepts. The interface should be self-evident.

For each feature, I designed:

• Tutorial steps and flow
• Instructional text (clear, concise, action-oriented)
• Progressive reveal (teach as they encounter complexity)
• Skip option (respect the veterans)

Results

The "Zero Redesign" Thing

Let me explain why this matters.

In a live product with millions of users, shipping something that needs immediate fixes is expensive. Patches, hotfixes, community drama, trust erosion. It adds up fast.

17 systems. Zero UX redesigns post-launch.

That's not luck. That's process:

• Feature needs analysis before design
• User flows before UI
• Interactive prototypes before development
• Clear documentation for implementation

Front-load the thinking, avoid the rework.

Community Validation

Here's how I know it worked: when users DO ask questions about these features, the community response is usually something like "Oh that's easy, you just..."

The opinion shifted from common knowledge to self-explanatory. That's the goal.

What I Learned

1. Simplicity is achieved, not started with.

Every feature started complex. Simplicity came from iteration — removing steps, consolidating screens, questioning every element. K.I.S.S. is easy to say, brutal to execute.

2. Design for the extremes, win the middle.

If it works for The Master (power user) AND The Easygoer (casual), it works for everyone. Progressive disclosure is the cheat code. Simple by default, depth on demand.

3. Zero redesign is the real metric.

Speed-to-ship means nothing if you ship twice. The upfront investment in flows, prototypes, and documentation? Pays for itself every time.

How This Applies Beyond Gaming

Look, I know "video game UX" sounds niche. But look at the following things:

The methodology transfers. Complexity is complexity & users are users.