# Managing Complexity

See how your team handles work as systems, teams, dependencies, and uncertainty grow.

As organizations grow, their systems, processes, and decisions multiply. What once felt clear and simple starts to feel heavy. Managing Complexity measures how well your team stays aligned and adaptive when conditions change. It captures how design structure evolves into flexibility — how teams keep learning, adjusting, and delivering clarity at scale.

When this score is strong, teams coordinate across multiple functions without losing focus. They maintain confidence even when priorities shift. When it’s lower, structure turns rigid, and work slows down under the weight of process and uncertainty.

Complexity isn’t something to remove. It’s something to lead through with confidence, structure, and shared visibility.

### **Where this fits**

Managing Complexity is one of five dimensions in the Design Assessment. Each dimension shows a different place where design impact can strengthen or break down:

1.  [Organizing Work](https://glare.helio.app/document-overview/design-assessment/results-guide/organizing-work): how well design knowledge is captured, connected, and reused.
    
2.  [Managing Complexity:](https://glare.helio.app/document-overview/design-assessment/results-guide/managing-complexity) how well teams handle work as systems, teams, dependencies, and uncertainty grow.
    
3.  [Building Proof:](https://glare.helio.app/document-overview/design-assessment/results-guide/building-proof) how well design work connects to user outcomes and business results.
    
4.  [Guiding Decisions:](https://glare.helio.app/document-overview/design-assessment/results-guide/guiding-decisions) how well signals turn into clear choices.
    
5.  [Scaling Influence:](https://glare.helio.app/document-overview/design-assessment/results-guide/scaling-influence) how well design proof travels beyond the immediate team.
    

Use this Results page to understand your Managing Complexity score, review the layer pattern, and choose what to improve next.

### **Why Managing Complexity Matters**

Every organization faces the same challenge: growth adds complexity faster than structure can adapt. Design maturity is measured by how effectively teams stay aligned through that change, how they simplify decisions without losing nuance, and how they adapt structure to fit new conditions.

Strong teams understand that complexity cannot be eliminated. It can only be managed through clarity, shared goals, and the confidence to adjust together.

The goal is not to make work simple. It’s to make it navigable.

## **How to Use This Page**

This Results page helps your team interpret your Managing Complexity score and turn the pattern into action. You can move through it section by section or jump to the parts that matter most.

Use this page to:

1.  **Overview & Score**: See how your score reflects your team’s ability to handle growing complexity with clarity.
    
2.  **How It’s Measured**: Understand how the three complexity modes (Simple, Complicated, Complex) shape your team’s adaptability.
    
3.  **Rubric Breakdown**: Compare your layer scores and see how teams mature from managing tasks to managing systems.
    
4.  **Strengths and Gaps**: Identify where coordination is strong and where alignment starts to break down.
    
5.  **Next Actions**: Turn insights into specific steps that strengthen adaptability and shared understanding.
    

The goal is to build structure that bends without breaking, systems that can handle change without losing direction.

**💡 First Step:** Review your results together. Identify where coordination feels natural and where it stalls. Those moments reveal where adaptability can grow next.

* * *

## **1\. OVERVIEW & SCORE**

### **Understanding Your Managing Complexity Score**

Your Managing Complexity score reflects how effectively your team balances structure and flexibility as work scales. It shows how well your organization adapts to uncertainty, coordinates across functions, and keeps clarity intact when systems, tools, or priorities grow more intricate.

High scores indicate a team that thrives under changing conditions. Roles, processes, and tools support collaboration without slowing it down. Lower scores reveal a system that struggles to adapt, where structure may be too rigid or visibility fades when new challenges arise.

This score helps you see how your organization:

-   Keeps clarity and alignment as more people and projects are added.
    
-   Adjusts systems and workflows when priorities shift.
    
-   Uses shared signals to reduce confusion and decision fatigue.
    
-   Balances process discipline with creative flexibility.
    

Strong performance here signals a mature organization that turns complexity into momentum rather than friction.

### **Score Interpretation**

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 589px;"><colgroup><col style="min-width: 25px;"><col style="width: 182px;"><col style="width: 382px;"></colgroup><tbody><tr><td colspan="1" rowspan="1"><p><strong>Score Range</strong></p></td><td colspan="1" rowspan="1" colwidth="182"><p><strong>Label</strong></p></td><td colspan="1" rowspan="1" colwidth="382"><p><strong>What It Means</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>90–100</strong></p></td><td colspan="1" rowspan="1" colwidth="182"><p><strong>Adaptive Larity</strong></p></td><td colspan="1" rowspan="1" colwidth="382"><p>The team handles simple, complicated, and complex work with the right level of structure and learning.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>70–89</strong></p></td><td colspan="1" rowspan="1" colwidth="182"><p><strong>Managed Complexity</strong></p></td><td colspan="1" rowspan="1" colwidth="382"><p>The team handles most complexity well, but some dependencies, handoffs, or uncertainty still create drag.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>60–69</strong></p></td><td colspan="1" rowspan="1" colwidth="182"><p><strong>Developing Structure</strong></p></td><td colspan="1" rowspan="1" colwidth="382"><p>The team has some ways to manage complexity, but work often depends on individual coordination or late problem-solving.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Below 60</strong></p></td><td colspan="1" rowspan="1" colwidth="182"><p><strong>Tangled Work</strong></p></td><td colspan="1" rowspan="1" colwidth="382"><p>Complexity slows progress. Dependencies are unclear, roles blur, and uncertain work gets forced into fixed plans too early.</p></td></tr></tbody></table>

  
Most organizations score between **75 and 85**, they manage routine complexity well but find it harder to adapt as interconnected systems expand.

### **Example: How a Team’s Score Reveals Strength and Gaps**

A team scoring **84 overall** shows solid coordination and reliable structure but limited adaptability under uncertainty.

-   **Simple (94)**: Tasks and operations are reliable and efficient.
    
-   **Complicated (80)**: Cross-functional coordination works well but takes extra effort to maintain.
    
-   **Complex (79)**: Adaptability drops when facing unknowns or rapid change. Learning and experimentation feel risky or slow.
    

This pattern is common in growing organizations: strong operational systems with limited agility when navigating uncharted situations.

**Focus:** Strengthen adaptive capacity in complex environments. Build faster feedback loops, increase transparency, and create safe spaces for testing new ideas before decisions solidify.

[Image]

**Focus:** Strengthen the “complicated layer.” Build repeatable frameworks that make multi-step work easier to manage and share. When coordination scales smoothly, complexity stops being a barrier and starts becoming a competitive strength.

### **Understanding the Model**

The Managing Complexity model measures how well your team matches the work to the right level of structure.

It looks across three layers:

1.  **Simple work** is stable, repeatable, and already understood.
    
2.  **Complicated work** has many parts and needs expertise, ownership, and coordination.
    
3.  **Complex work** is uncertain, adaptive, and needs learning before the team commits.
    

When these layers are understood, teams can move with the right level of effort. Simple work stays fast. Complicated work gets coordinated. Complex work gets the discovery it needs.

When one layer weakens, the team misreads the work. Simple tasks get over-processed. Complicated work lacks ownership. Complex work gets treated like the answer is already known.

Strong complexity management does not remove uncertainty. It helps the team move through it without losing clarity.

### **How It Works**

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 556px;"><colgroup><col style="min-width: 25px;"><col style="width: 113px;"><col style="width: 225px;"><col style="width: 193px;"></colgroup><tbody><tr><td colspan="1" rowspan="1"><p><strong>Layer</strong></p></td><td colspan="1" rowspan="1" colwidth="113"><p><strong>Primary Function</strong></p></td><td colspan="1" rowspan="1" colwidth="225"><p><strong>What It Does</strong></p></td><td colspan="1" rowspan="1" colwidth="193"><p><strong>When It Works</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p>Simple</p></td><td colspan="1" rowspan="1" colwidth="113"><p>Keep basics reliable</p></td><td colspan="1" rowspan="1" colwidth="225"><p>Handles stable, repeatable work with clear patterns and lightweight structure.</p></td><td colspan="1" rowspan="1" colwidth="193"><p>Routine work moves quickly without unnecessary process.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Complicated</p></td><td colspan="1" rowspan="1" colwidth="113"><p>Coordinate moving parts</p></td><td colspan="1" rowspan="1" colwidth="225"><p>Aligns teams, owners, systems, constraints, and handoffs.</p></td><td colspan="1" rowspan="1" colwidth="193"><p>Multi-step work stays clear because dependencies are visible.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Complex</p></td><td colspan="1" rowspan="1" colwidth="113"><p>Learn through uncertainty</p></td><td colspan="1" rowspan="1" colwidth="225"><p>Uses signals, discovery, and adaptation when outcomes are not fully predictable.</p></td><td colspan="1" rowspan="1" colwidth="193"><p>The team reduces risk before committing too early.</p></td></tr></tbody></table>

  
**Tip:** The healthiest teams shift fluidly across all three modes. They rely on simple systems to support day-to-day work, structured collaboration to manage scale, and adaptive habits to navigate change.

* * *

## **2\. HOW IT’S MEASURED**

### **See how your team adapts as complexity grows**

Your Managing Complexity score is built from three connected modes of work that describe how your team handles clarity, coordination, and change. Each mode reflects a different kind of challenge, from efficiency to collaboration to adaptability.

[Image]

The more balanced these modes are, the more confident and flexible your team becomes as systems grow in scale and uncertainty.

When one mode dominates, the organization starts to lose balance. Work may run smoothly in routine conditions but falter when new situations arise. Understanding these patterns helps teams build structure that adapts rather than resists.

### **How to Read Your Three Mode Scores**

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 532px;"><colgroup><col style="min-width: 25px;"><col style="width: 253px;"><col style="width: 254px;"></colgroup><tbody><tr><td colspan="1" rowspan="1"><p><strong>Layer</strong></p></td><td colspan="1" rowspan="1" colwidth="253"><p><strong>What It Represents</strong></p></td><td colspan="1" rowspan="1" colwidth="254"><p><strong>Complexity Strength</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p>Simple</p></td><td colspan="1" rowspan="1" colwidth="253"><p>Stable, repeatable work that should stay reliable.</p></td><td colspan="1" rowspan="1" colwidth="254"><p>Shows whether the team can move routine work without overcomplicating it.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Complicated</p></td><td colspan="1" rowspan="1" colwidth="253"><p>Multi-step work that needs expertise, coordination, and ownership.</p></td><td colspan="1" rowspan="1" colwidth="254"><p>Shows whether dependencies, handoffs, and constraints are managed clearly.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Complex</p></td><td colspan="1" rowspan="1" colwidth="253"><p>Uncertain work where the path is not fully known.</p></td><td colspan="1" rowspan="1" colwidth="254"><p>Shows whether the team creates enough learning before making larger commitments.</p></td></tr></tbody></table>

When your scores across these three modes stay within a 10-point range, your organization adapts easily between stability and change. A wider spread shows where rigidity or uncertainty creates drag.

### **Start with the Shape, Not the Score**

Your total score shows maturity, but the shape of your three mode scores tells you where adaptability breaks down. Balanced teams can move comfortably between predictable, coordinated, and adaptive work.

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 496px;"><colgroup><col style="min-width: 25px;"><col style="width: 230px;"><col style="width: 241px;"></colgroup><tbody><tr><td colspan="1" rowspan="1"><p><strong>Pattern</strong></p></td><td colspan="1" rowspan="1" colwidth="230"><p><strong>What It Means</strong></p></td><td colspan="1" rowspan="1" colwidth="241"><p><strong>Focus Area</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p>Balanced Flow</p></td><td colspan="1" rowspan="1" colwidth="230"><p>The team handles all three levels with the right amount of structure.</p></td><td colspan="1" rowspan="1" colwidth="241"><p>Keep the system clear and repeatable.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Simple Strong, Complex Weak</p></td><td colspan="1" rowspan="1" colwidth="230"><p>Routine work is reliable, but uncertain work gets forced into fixed plans.</p></td><td colspan="1" rowspan="1" colwidth="241"><p>Add more discovery, testing, and signal gathering before commitment.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Complex Strong, Simple Weak</p></td><td colspan="1" rowspan="1" colwidth="230"><p>The team handles ambiguity well, but everyday work feels heavier than it should.</p></td><td colspan="1" rowspan="1" colwidth="241"><p>Reduce process around repeatable work and clarify standard patterns.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Complicated Gap</p></td><td colspan="1" rowspan="1" colwidth="230"><p>Work breaks down in coordination, ownership, or handoffs.</p></td><td colspan="1" rowspan="1" colwidth="241"><p>Clarify dependencies, decision owners, and cross-team rhythms.</p></td></tr></tbody></table>

Complexity isn’t a problem to fix. It’s a landscape to navigate. Your shape shows how your team finds its balance between control and curiosity.

### **Score Patterns to Watch**

-   **Balanced within 10 points  
    **Complexity is being handled with the right level of structure. The team can move routine work, coordinate bigger efforts, and learn through uncertainty.
    
-   **Wide Spread, 15–20+ points  
    **The team is strong in one kind of work but struggles in another. Look for where the mismatch is slowing progress.
    
-   **Over-processed Simple Work  
    **Routine work is slowed by too many meetings, reviews, or custom decisions. Create lighter patterns for work the team already understands.
    
-   **Under-coordinated Complicated Work  
    **Dependencies, ownership, or handoffs are unclear. Strengthen alignment before the work becomes blocked.
    
-   **Premature Certainty in Complex Work  
    **The team treats uncertain work like the answer is already known. Use signals and discovery to reduce risk before committing.
    

**💡 Healthy complexity management means the team knows what kind of work it is doing before choosing how to manage it.**

* * *

## **3\. RUBRIC BREAKDOWN**

### **See how maturity develops across your three modes of work**

Design maturity under complexity is not about control,  it’s about connection. Each mode of work represents a different kind of balance between clarity and adaptability. Together, they show how structure and flexibility can reinforce one another rather than compete.

When teams flow smoothly between modes, complexity turns into confidence. When one mode dominates, the organization either over-optimizes for stability or struggles to adapt when conditions shift.

### **How Design Maturity Takes Shape**

The *Managing Complexity* model measures how well your systems evolve with scale. Mature organizations create clarity that travels across simple, complicated, and complex work.

They know when to follow process, when to collaborate across boundaries, and when to experiment and learn. When balance breaks, progress slows. Simple work feels efficient but uninspired. Complicated work turns bureaucratic. Complex work becomes chaotic.

[Image]

Use this section to see how maturity develops as your team learns to shift comfortably between stability and change.

### **Example Layer Scores**

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 538px;"><colgroup><col style="min-width: 25px;"><col style="width: 110px;"><col style="width: 403px;"></colgroup><tbody><tr><td colspan="1" rowspan="1"><p><strong>Layer</strong></p></td><td colspan="1" rowspan="1" colwidth="110"><p><strong>Score</strong></p></td><td colspan="1" rowspan="1" colwidth="403"><p><strong>Interpretation</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p>Simple</p></td><td colspan="1" rowspan="1" colwidth="110"><p>94</p></td><td colspan="1" rowspan="1" colwidth="403"><p>Operations are efficient and predictable. Teams excel at routine execution and process reliability.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Complicated</p></td><td colspan="1" rowspan="1" colwidth="110"><p>80</p></td><td colspan="1" rowspan="1" colwidth="403"><p>Coordination is solid, but visibility between teams requires extra effort. Systems work but need active maintenance.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Complex</p></td><td colspan="1" rowspan="1" colwidth="110"><p>79</p></td><td colspan="1" rowspan="1" colwidth="403"><p>Adaptation lags behind scale. Teams handle uncertainty but hesitate to test or shift direction quickly.</p></td></tr></tbody></table>

This pattern shows a team that runs efficiently but lacks adaptive rhythm. Processes work well for known problems but slow down when navigating ambiguity.

**Focus:** Encourage more real-time learning and feedback during complex work. Help teams test and adjust without waiting for full certainty.

### **Summary of the Three Modes**

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 549px;"><colgroup><col style="min-width: 25px;"><col style="width: 123px;"><col style="width: 130px;"><col style="width: 120px;"><col style="width: 151px;"></colgroup><tbody><tr><td colspan="1" rowspan="1"><p><strong>Layer</strong></p></td><td colspan="1" rowspan="1" colwidth="123"><p><strong>What It Represents</strong></p></td><td colspan="1" rowspan="1" colwidth="130"><p><strong>When It’s Strong</strong></p></td><td colspan="1" rowspan="1" colwidth="120"><p><strong>When It’s Weak</strong></p></td><td colspan="1" rowspan="1" colwidth="151"><p><strong>How to Strengthen</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p>Simple</p></td><td colspan="1" rowspan="1" colwidth="123"><p>Stable work that should move through known patterns.</p></td><td colspan="1" rowspan="1" colwidth="130"><p>Routine work is clear, fast, and reliable.</p></td><td colspan="1" rowspan="1" colwidth="120"><p>Simple tasks get slowed by too much process.</p></td><td colspan="1" rowspan="1" colwidth="151"><p>Create reusable checklists, standards, and lightweight review paths.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Complicated</p></td><td colspan="1" rowspan="1" colwidth="123"><p>Work with many parts that requires coordination.</p></td><td colspan="1" rowspan="1" colwidth="130"><p>Owners, dependencies, and handoffs are visible.</p></td><td colspan="1" rowspan="1" colwidth="120"><p>Teams discover constraints late or keep reopening decisions.</p></td><td colspan="1" rowspan="1" colwidth="151"><p>Map dependencies early and clarify who owns each decision.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Complex</p></td><td colspan="1" rowspan="1" colwidth="123"><p>Uncertain work that needs learning before commitment.</p></td><td colspan="1" rowspan="1" colwidth="130"><p>The team tests assumptions and adapts as signals appear.</p></td><td colspan="1" rowspan="1" colwidth="120"><p>Plans are locked too early and reality breaks the plan later.</p></td><td colspan="1" rowspan="1" colwidth="151"><p>Use discovery, experiments, and signal reviews before committing.</p></td></tr></tbody></table>

Balanced maturity comes from movement, knowing when to rely on structure and when to learn through uncertainty.

### **How to Read the Modes**

Each mode reflects a stage in how organizations manage complexity. The healthiest systems use all three with intention, structure to ground work, coordination to align effort, and adaptability to handle change.

**Simple → Where stability begins**  
Teams establish rhythm, reliability, and shared expectations.

-   When strong: Operations feel effortless. Teams stay consistent and dependable.
    
-   When weak: Routines harden into rules that resist change.
    

**Focus:** Keep systems simple enough to evolve as goals shift.  
  

**Complicated → Where coordination happens**  
Teams balance structure and alignment across systems and specialties.

-   When strong: Collaboration feels natural. Dependencies are visible and manageable.
    
-   When weak: Silos grow and communication breaks down.
    

**Focus:** Strengthen cross-team visibility and shared problem-solving habits.  
  

**Complex → Where adaptability grows**  
Teams face uncertainty and learn through experimentation.

-   When strong: Learning happens quickly. Teams adjust with confidence and stay connected to purpose.
    
-   When weak: People hesitate to act without full clarity. Progress stalls under ambiguity.
    

**Focus:** Create spaces for open reflection and safe-to-learn experimentation. Capture what’s learned and share it across teams.  
  

When these three modes reinforce each other, complexity becomes a source of strength. Your team can respond to change without losing rhythm, and evolve structure without losing direction.

* * *

## **4\. STRENGTHS AND GAPS**

### **See where structure supports clarity and where it resists change**

Your Managing Complexity results reveal how well your team keeps work clear as it grows. Some layers may already have strong structure. Others may show where work gets tangled, dependencies appear late, or uncertainty is handled too rigidly.

-   Strengths show where the team already matches the work to the right level of structure.
    
-   Gaps show where complexity creates drag, confusion, or premature decisions.
    

The goal is not to add more process. It is to use the right amount of structure for the kind of work in front of you.

### **Example: Strengths and Gaps**

For a team scoring 84 overall, stability is a clear strength. Routines and tools keep the work reliable, but complexity begins to outpace coordination as scale increases.

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 478px;"><colgroup><col style="min-width: 25px;"><col style="width: 148px;"><col style="width: 155px;"><col style="width: 150px;"></colgroup><tbody><tr><td colspan="1" rowspan="1"><p><strong>Layer</strong></p></td><td colspan="1" rowspan="1" colwidth="148"><p><strong>Strengths</strong></p></td><td colspan="1" rowspan="1" colwidth="155"><p><strong>Gaps</strong></p></td><td colspan="1" rowspan="1" colwidth="150"><p><strong>Opportunity</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p>Simple</p></td><td colspan="1" rowspan="1" colwidth="148"><p>Routine work is handled consistently.</p></td><td colspan="1" rowspan="1" colwidth="155"><p>Some simple tasks may still require too much discussion or review.</p></td><td colspan="1" rowspan="1" colwidth="150"><p>Create lighter paths for repeatable work.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Complicated</p></td><td colspan="1" rowspan="1" colwidth="148"><p>Teams can coordinate when dependencies are visible.</p></td><td colspan="1" rowspan="1" colwidth="155"><p>Ownership or handoffs may become unclear as more teams get involved.</p></td><td colspan="1" rowspan="1" colwidth="150"><p>Map dependencies and decision owners earlier.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Complex</p></td><td colspan="1" rowspan="1" colwidth="148"><p>The team can learn through uncertainty when given space.</p></td><td colspan="1" rowspan="1" colwidth="155"><p>Complex work may be forced into fixed plans before enough is known.</p></td><td colspan="1" rowspan="1" colwidth="150"><p>Use signals and discovery to reduce risk before commitment.</p></td></tr></tbody></table>

Your team operates efficiently and shares information well but loses speed when uncertainty rises. Improving adaptability and communication under pressure turns structural reliability into true resilience.

### **Team Reflection**

Use this section to turn your results into conversation. Discuss how your team manages transitions between simple, complicated, and complex work.

1.  Where does structure help us move faster?
    
2.  Where does process slow down creative or adaptive thinking?
    
3.  Which types of challenges energize our team, and which create friction?
    
4.  What one small change could help us shift between modes more easily?
    

**Tip:** The healthiest teams don’t simplify complexity — they build confidence in navigating it. Encourage open feedback, quick reflection, and regular review of where structure still supports growth.

* * *

## **5\. NEXT ACTIONS**

### **Turn complexity into confidence**

Your Managing Complexity results show how well your team adapts as systems grow. Complexity is not a sign of disorder,  it’s a natural result of success. The key is maintaining clarity and alignment even as work becomes more interconnected.

Teams that thrive under complexity don’t simplify everything. They learn to see patterns, coordinate faster, and stay confident when things change.

### **Implications & Recommendations**

If your scores are high in Simple and Complicated modes but lower in Complex, your team runs efficiently but hesitates under uncertainty.  Structure works well for predictable work, but adaptability depends on individual initiative.

[Image]

Focus on creating systems that learn as they scale:

-   Encourage fast feedback loops to help teams adjust without waiting for full clarity.
    
-   Simplify communication during change by focusing on shared outcomes rather than rigid plans.
    
-   Build regular reflection points where teams review what’s working and what’s not.
    
-   Treat experimentation as part of the process, not an exception to it.
    
-   Train leaders to model curiosity and openness, especially when direction is uncertain.
    

Clarity and adaptability are not opposites. The more openly your systems learn, the easier it becomes to coordinate through change.

### **30-Day Focus**

Start small. Complexity management improves when habits shift, not just processes.

1.  **Pick one process to stress-test.** Introduce a variable or “what if” scenario and see how the team adapts.
    
2.  **Add one learning checkpoint.**During ongoing work, pause briefly to identify what’s changing and how the team is responding.
    
3.  **Simplify one coordination channel.** Replace long update meetings with a shared dashboard or short written check-ins.
    
4.  **Reflect at the end of 30 days.** Ask what felt clear, what slowed down, and what made change easier to manage.
    

**Goal:** Strengthen your team’s ability to move between structure and adaptability. Confidence grows when teams can respond to uncertainty with shared clarity, not hesitation.

* * *

## **Next Step: Making Impact**

Once your team can guide decisions confidently with signals, the next step is turning that proof into influence.  
  
The Making Impact dimension focuses on how design outcomes connect to business results — how every signal, test, and validation translates into measurable success. Guiding Decisions builds the foundation for that shift. It turns intuition into evidence.  
  
Making Impact takes it further,  turning that evidence into outcomes people can see.

**💡Explore Next:** \[Making Impact →\] Learn how to tie your design work directly to KPIs, track results, and communicate value across your organization.