Complexity-Based Decision Making
The ITIL v5 Complexity Framework
ITIL v5 establishes that different contexts require fundamentally different management approaches. The framework defines four types of complexity context.
Four Types of Complexity Context
| Context | Cause and Effect | Approach | Analogy |
|---|---|---|---|
| Ordered | Known or knowable | Apply known solutions; follow established procedures | "Baking a cake: follow the recipe correctly, and the outcome is predictable." |
| Complex | Understood only in retrospect | Experiment, observe, adapt; emergent practices | "Raising a child: the same parenting approach might work differently with different children." |
| Chaotic | No discernible relationship | Act immediately, stabilize, then assess | "A fire in a building: the priority is getting people to safety immediately." |
| Confused | Unknown which context applies | Gather information to determine the true context | The situation has not been assessed yet; you do not know what type of problem you face. |
⚠️
The most dangerous mistake: treating a complex problem as if it were ordered creates an illusion of control while missing actual dynamics.
Why ITIL v5 Uses Four Contexts (Not Five)
The original Cynefin framework uses five domains. ITIL v5 adapts this into four contexts:
| Cynefin Domain | ITIL v5 Context | Notes |
|---|---|---|
| Clear (Simple) | Ordered | Combines "Clear" and "Complicated" where cause-and-effect is known or knowable |
| Complicated | Ordered | Expert analysis can determine the answer |
| Complex | Complex | Identical concept: emergent, probe-sense-respond |
| Chaotic | Chaotic | Identical concept: act-sense-respond |
| Confusion/Disorder | Confused | The state of not knowing which context applies |
Applying Complexity Contexts to ITIL Practices
Incident Management
| Context | Example Scenario | Decision Approach |
|---|---|---|
| Ordered | Known error: "printer offline." Documented fix exists. | Apply the known fix from the knowledge base. Standard response. |
| Complex | Intermittent database latency affecting some users unpredictably. No clear pattern in logs. | Form a cross-functional investigation team. Deploy additional monitoring. Test hypotheses incrementally. |
| Chaotic | Major security breach: customer data exposure. Situation evolving rapidly. | Invoke Major Incident Management immediately. Contain first, investigate second. Centralized command. |
| Confused | Users report "the system feels slow" but metrics show normal performance. | Gather more information. Is this a technical issue (ordered), an emergent pattern (complex), or a perception issue? Do not assume. |
Change Enablement
| Context | Change Type | Governance Approach |
|---|---|---|
| Ordered | Standard change (pre-approved): OS patch, configuration update | Automated deployment through CI/CD. No manual approval needed. Post-deployment verification. |
| Complex | Introducing a new AI-based service into production | Incremental deployment. Canary releases. Feature flags. Continuous feedback. Governance through observability. |
| Chaotic | Emergency change during a major outage | Expedited approval (single authorizer). Deploy the fix. Document and review after stability is restored. |
| Confused | A proposed change with unclear scope and unknown dependencies | Stop. Conduct impact analysis. Determine whether this is an ordered change with knowable effects or a complex change requiring experimentation. |
Problem Management
| Context | Approach |
|---|---|
| Ordered | Root cause analysis works well. Use techniques like Ishikawa diagrams, fault tree analysis, the "5 Whys." Cause-and-effect is traceable. |
| Complex | "Root cause" may not exist as a single factor. Use systemic analysis: contributing factors, feedback loops, emergent interactions. Blameless post-mortems reveal more than single-cause investigation. |
| Chaotic | No time for analysis during chaos. Focus on stabilization. Conduct post-mortem only after the situation moves from chaotic to ordered or complex. |
| Confused | Before investing in analysis, determine: is this a known type of problem (ordered) or an emergent phenomenon (complex)? The analysis method must match the context. |
Strategic Decisions by Complexity Context
Governance
| Context | Governance Pattern |
|---|---|
| Ordered | Directive or Compliance-based governance works well. Clear rules, defined approval processes, standard procedures. |
| Complex | Guided or Federated governance is more effective. Set boundaries and principles, but let teams decide how to operate within them. |
| Chaotic | Centralized, rapid-response governance. A single authority makes decisions quickly. Consensus-seeking during chaos creates paralysis. |
| Confused | Assessment-first governance. Invest in understanding the situation before choosing a governance approach. |
Team Structure
| Context | Team Approach |
|---|---|
| Ordered | Functional (specialized) teams work efficiently. Handoffs are manageable because processes are predictable. |
| Complex | Cross-functional (product) teams are essential. The team needs diverse skills to probe, sense, and respond to emergent circumstances. |
| Chaotic | Crisis response team (war room). Bring together the most experienced people regardless of organizational structure. |
| Confused | Assessment team with diverse perspectives. Avoid premature commitment to a team structure before understanding the context. |
PESTLE Analysis: Understanding External Complexity
ITIL v5 uses the PESTLE framework (Political, Economic, Social, Technological, Legal, Environmental) to systematically scan the external environment.
PESTLE Applied to ITIL v5
| Factor | Questions for IT Leaders | Impact on Complexity |
|---|---|---|
| Political | How do government policies, trade regulations, or geopolitical tensions affect our IT supply chain and data residency? | Can shift an ordered environment to complex/chaotic overnight (e.g., sanctions, data sovereignty laws) |
| Economic | How do economic cycles, inflation, and budget pressures affect IT investment? | Budget cuts force prioritization; economic uncertainty increases complexity |
| Social | How do changing workforce expectations, remote work trends, and diversity requirements affect our operating model? | Social shifts create complex adaptive challenges (not ordered problems) |
| Technological | How do emerging technologies (AI, quantum computing, edge computing) disrupt our current architecture? | New technology introduction is inherently complex (emergent, unpredictable effects) |
| Legal | How do regulations (GDPR, DORA, NIS2, AI Act) constrain or direct our technology decisions? | Regulatory changes can shift a flexible environment to heavily ordered/constrained |
| Environmental | How do sustainability requirements, carbon reporting, and green IT mandates affect our infrastructure and operations? | Industry 5.0 context: sustainability is no longer optional |
How to Conduct a PESTLE Analysis
- Assemble a cross-functional team (IT, legal, finance, HR, business stakeholders)
- Scan each factor systematically (use the questions above as starting points)
- Assess impact and uncertainty for each factor
- Map to the four dimensions (how does each factor affect Organizations and People, Information and Technology, Partners and Suppliers, Value Streams and Processes)
- Determine complexity context (does this factor create ordered, complex, or chaotic conditions?)
- Update quarterly (external factors change; your analysis must be current)
Common Leadership Mistakes with Complexity
| Mistake | Consequence | Correction |
|---|---|---|
| Treating every problem as ordered | Complex and chaotic problems get "best practice" solutions that do not work | Assess complexity context first, then choose approach |
| Skipping directly to complex approaches for ordered problems | Over-engineering solutions; unnecessary experimentation on solved problems | If the solution is known and documented, use it |
| Staying in chaos management mode after stabilization | Organization remains in crisis mode; people burn out; no learning occurs | When stability is restored, transition to post-incident analysis (ordered or complex) |
| Assuming the context never changes | A once-ordered environment (stable technology) becomes complex (AI disruption) | Reassess complexity regularly; external factors (PESTLE) shift contexts |
| Ignoring the "confused" state | People act based on false assumptions about the context | When uncertain, invest in assessment before action |
Related Pages
- Decision Framework (adoption decision models)
- Executive Summary (five strategic shifts including complexity)
- Governance (four governance patterns)
- AI Governance (complexity in AI-enabled environments)
- Four Dimensions (the four dimensions affected by PESTLE)
Last updated on April 2, 2026
ITIL® is a registered trademark of PeopleCert. © 2026 ITIL v5 Compass