Managing Complexity

Design work gets harder when teams cannot hold the system together.

Managing Complexity looks at how well your team handles work that spans products, teams, channels, tools, constraints, and decisions. Strong design teams do not simplify by ignoring complexity. They create enough structure to move through it. This dimension shows whether complexity is helping the team make better decisions or slowing the work down.

Why Managing Complexity Matters

Most product and design work does not stay simple for long.

A small idea touches more screens. A flow connects to more systems. A decision affects more teams. What started as a clear problem becomes a larger set of dependencies, edge cases, tradeoffs, and stakeholder needs.

The problem is not that the work is complex, it’s that teams often do not have a shared way to manage it.

When that happens:

Teams lose sight of what matters most
Dependencies slow progress
Decisions get pushed across teams
Handoffs create confusion
Edge cases take over the conversation
The original user need gets buried
Leaders see activity but not clear movement

The work may be important, but the system around it becomes hard to follow. Managing Complexity helps teams keep direction clear as the work grows. It turns scattered dependencies into a clearer path forward.

What this dimension shows

Managing Complexity shows how well your team keeps work clear when it becomes larger, messier, or more connected.

It looks at whether your team can clearly answer:

What level of complexity are we dealing with?
What parts of the work are simple and repeatable?
What parts require coordination and expertise?
What parts are uncertain and need learning?
Where are the dependencies?
Who needs to stay aligned?
What structure will help the work move?

When this dimension is strong, teams can move through complexity without losing direction.

When it is weak, the work becomes harder to explain, harder to prioritize, and harder to finish.

Where momentum breaks

Momentum breaks when the team treats all work the same.

Some work needs a checklist. Some work needs coordination. Some work needs discovery. When teams use the same process for every kind of problem, the work either gets over-managed or under-managed.

This creates drag. Teams spend more time untangling the system than making progress.

You see it when:

Simple work gets slowed down by too much process
Complicated work lacks clear owners or handoffs
Complex work gets forced into fixed plans too early
Teams disagree on what kind of problem they are solving
Dependencies are discovered too late
Decisions stall because too many pieces are connected
The user need gets lost inside operational constraints

The issue is not that the team cannot handle complexity. It is that the complexity is not being named, structured, or managed clearly.

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><td colspan="1" rowspan="1"><h2>What strong looks like</h2>Strong Managing Complexity makes larger work easier to move.The team can tell the difference between simple, complicated, and complex work. It knows when to rely on known patterns, when to coordinate expertise, and when to create space for learning.Strong teams:<ul><li>name the type of complexity early</li><li>separate simple tasks from uncertain problems</li><li>clarify dependencies before they block progress</li><li>define ownership across teams</li><li>keep the user need visible as the work grows</li><li>use the right level of structure for the problem</li><li>adjust the plan as new signals appear</li><li>help stakeholders understand tradeoffs</li></ul>This does not mean removing complexity.It means making complexity easier to work with.</td><td colspan="1" rowspan="1"><h2>What weak looks like</h2>Weak Managing Complexity creates confusion and drag.The team may be working hard, but the work keeps getting tangled. Every decision creates another dependency. Every dependency creates another meeting. Progress depends on individual effort instead of a shared way to move through the system.Weak teams often:<ul><li>treat every problem as if it has the same level of uncertainty</li><li>over-process simple work</li><li>under-structure complicated work</li><li>lock complex work too early</li><li>miss dependencies until they become blockers</li><li>struggle to align product, design, engineering, and leadership</li><li>lose the user problem inside internal constraints</li><li>revisit decisions because the full system was not understood</li></ul>This makes design feel slow, even when the team is moving fast.</td></tr></tbody></table>

How Managing Complexity is evaluated

Managing Complexity is evaluated by looking at how well the team matches the work to the right level of structure.

Organizing Work uses the Decision Map to track how design knowledge moves from objectives to outputs. Managing Complexity uses a different lens: it looks at the type of problem the team is dealing with and whether the team is using the right approach for that level of complexity. The Organizing Work page already uses the Decision Map to show how teams connect inputs, decisions, evidence, and results across the work .

For Managing Complexity, the assessment focuses on three levels:

Simple
Complicated
Complex

These levels show whether the team can recognize what kind of work it is doing and apply the right amount of structure, coordination, and learning.

[Image]

The Three Levels of Managing Complexity

Managing Complexity is not about making everything simple. It is about knowing what kind of problem the team is facing.

A strong team can show:

What parts of the work are repeatable
What parts need expert coordination
What parts are uncertain or still emerging
What dependencies shape the work
What decisions need structure
What signals are needed before the team commits
How the team will adapt as the work changes

When these levels are clear, teams can move with more confidence. When they are blurred, teams either overbuild process, skip needed coordination, or force certainty where learning is still needed.

Simple

Simple work is stable, repeatable, and already understood.

This includes familiar patterns, known workflows, common interface changes, routine updates, and tasks where the team already knows what good looks like.

When simple work is strong, the team has clear standards and can move quickly without overthinking every step. When simple work is weak, small tasks become heavier than they need to be. Teams add meetings, reviews, and custom decisions to work that should be handled through shared patterns.

Simple work needs clarity, not complexity.

Complicated

Complicated work has many parts, but it can be managed with expertise and coordination.

This includes multi-step flows, cross-team handoffs, system dependencies, technical constraints, compliance needs, and larger initiatives where the path is knowable but requires alignment.

When complicated work is strong, the team identifies dependencies early, brings in the right expertise, and creates enough structure to keep teams moving together. When complicated work is weak, ownership gets blurry. Teams miss handoffs, discover constraints too late, or keep reopening decisions because the system was not fully considered.

Complicated work needs coordination, not guesswork.

Complex

Complex work is uncertain, adaptive, and hard to predict upfront.

This includes new product directions, unclear user behavior, emerging markets, AI-enabled workflows, major strategy shifts, and problems where the team does not yet know what will work.

When complex work is strong, the team creates space to learn. It uses signals to reduce uncertainty, tests assumptions early, and adapts as new patterns appear. When complex work is weak, the team pretends it has certainty too soon. Plans get locked before the problem is understood. Teams push toward delivery without enough evidence, then struggle when reality does not match the plan.

Complex work needs learning, not premature certainty.

How to Strengthen Managing Complexity

Start by naming the kind of complexity you are dealing with. You do not need a new process for every project. You need a clearer way to decide what kind of work it is and what level of structure it needs.

The goal is to create a clearer path:

Simple → Complicated → Complex

That path should show what can move quickly, what needs coordination, and what needs more learning before the team commits.

Useful moves:

Separate repeatable tasks from uncertain problems
Name the dependencies early
Identify which teams need to stay aligned
Clarify where expertise is needed
Define what decisions can be made now
Define what still needs a signal
Keep the user need visible as constraints grow
Use lighter process for simple work
Use stronger coordination for complicated work
Use testing and discovery for complex work

The goal is not to reduce everything to a simple plan, but to manage complexity without losing momentum.

Questions to ask

Use these questions to evaluate how well your team manages complexity:

Are we clear on what kind of problem this is?
What parts of the work are simple and repeatable?
What parts require coordination across teams?
What parts are still uncertain?
What dependencies could slow us down?
Who needs to be involved before decisions are made?
Are we forcing certainty too early?
What signal would help us move forward with more confidence?

What Improves When This is Strong

When Managing Complexity is strong, teams move through bigger work with less confusion. Simple work moves faster. Complicated work gets clearer ownership. Complex work gets the learning it needs before teams overcommit.

Strong Managing Complexity helps teams:

Reduce unnecessary process
Clarify dependencies sooner
Align teams around the right level of effort
Avoid premature decisions
Keep user needs visible through constraints
Make tradeoffs easier to explain
Move large initiatives forward with less drag

This is where design maturity becomes easier to sustain as the work grows

How This Connects to Results

Managing Complexity is one dimension in the Design Assessment. This page explains what the dimension means and what strong or weak behavior looks like. The Results Guide explains how to interpret your score after you complete the assessment survey.

Use the Managing Complexity Results page to review:

Your overall dimension score
Your layer scores across Simple, Complicated, and Complex
Where complexity is being handled well or creating drag
What strengths and gaps show up in the results
What action to take next

The goal is to move from understanding the dimension to improving how your team handles work as it grows.

Go deeper:

Related dimensions

Managing Complexity supports the other four dimensions in the Design Assessment.

When complexity is easier to name and structure, teams can:

Organize work with clearer context
Build proof from better-scoped problems
Guide decisions with fewer hidden dependencies
Scale influence because leaders can see how the work fits together

Use the other dimension pages to see where design impact may be breaking beyond how complexity is managed.

Next step

Review one current initiative and name the level of complexity:

Simple → Complicated → Complex

Look for the mismatch.

Is the team over-processing simple work, under-coordinating complicated work, or pretending complex work is more certain than it is?

That is where Managing Complexity should improve first. Then use the scoring section to evaluate the pattern more clearly and decide what to strengthen next.

Identify where decision quality breaks down

The Glare Design Assessment helps teams spot weak validation, stakeholder friction, alignment gaps, and assumptions that scale without measurable learning—so you have a clearer starting point for improvement.

About 5 minutes · Team-based · Diagnostic snapshot you can act on

Take the Design Assessment