Same Territory, Shared Map: ITIL (Version 5) and the Cynefin Framework

# ITIL

# Service Management

How ITIL (Version 5)'s adoption of Complexity Thinking connects to Dave Snowden's Cynefin framework — and why service management professionals need to understand both.

July 2, 2026

Robert Edward Pinnington

Same Territory, Shared Map: ITIL (Version 5) and the Cynefin Framework

How ITIL (Version 5)'s adoption of Complexity Thinking connects to Dave Snowden's Cynefin framework — and why service management professionals need to understand both.

A Framework That Finally Admits the World is Complicated

For most of its life, ITIL operated on an implicit assumption: that if you defined the right processes, trained the right people, and measured the right things, service management would become predictable. Repeatability was the goal. Process compliance was the measure of maturity. The right answer existed — you just needed to find it and apply it consistently.

That assumption worked reasonably well in a world of stable, bounded IT environments. It works considerably less well in 2026, when organisations are managing AI-enabled services, dynamic digital products, distributed cloud infrastructure, and customer expectations that change faster than any change advisory board can reasonably govern.

ITIL (Version 5), launched in February 2026, acknowledges this directly. One of its defining new pillars is the explicit adoption of Complexity Thinking — a structured recognition that not every service management challenge is the same kind of problem, and that applying rigid procedural responses to inherently unpredictable situations is not a governance strategy, it is a recipe for failure.

For anyone familiar with Dave Snowden's Cynefin framework, the intellectual heritage is immediately recognisable. And that's not an accident.

Cynefin: The Original Sense-Making Map

Cynefin — pronounced 'kuh-NEV-in', a Welsh word meaning habitat or place of belonging — was developed by Dave Snowden at IBM in 1999 and has been refined considerably since. It is not a process model or a management methodology. It is a sense-making framework: a tool for understanding what kind of situation you are actually in, so that you can choose an appropriate response rather than defaulting to whatever you're most comfortable with.

Cynefin defines five domains, each requiring a fundamentally different mode of thinking and acting.

Cynefin Domain	Nature of the Problem	Appropriate Response	Failure Mode
Clear	Cause and effect are obvious and predictable	Sense, categorise, respond — apply best practice	Over-simplification; ignoring signals of change
Complicated	Cause and effect exist but require expertise to identify	Sense, analyse, respond — apply good practice	Analysis paralysis; over-reliance on experts
Complex	Cause and effect only understood in retrospect	Probe, sense, respond — run safe-to-fail experiments	Imposing order; treating emergence as failure
Chaotic	No perceivable cause and effect relationship	Act, sense, respond — stabilise first	Waiting to understand before acting
Confused (centre)	You don't know which domain you're in	Get out of confusion — gather information to reorient	Defaulting to your comfort zone regardless of context

The framework's central insight — and its most practically useful contribution — is that the most dangerous place to be is not Chaos. It is Confusion: the state of not knowing which domain you are operating in. An organisation that believes it is in Clear when it is actually in Complex will apply best practice to an emergent, unpredictable situation and wonder why it keeps producing the same failures.

Sound familiar? It should. Most major IT service failures happen not because the organisation lacked process, but because it applied the wrong kind of process to the wrong kind of problem.

The most dangerous assumption in service management is that every problem has a known solution. Cynefin tells you when that assumption is valid — and when it will get you into serious trouble.

ITIL (Version 5)'s Adapted Complexity Model

ITIL (Version 5) does not adopt Cynefin verbatim. It takes the underlying intellectual architecture — the recognition that organisations operate in fundamentally different problem contexts that demand different responses — and translates it into a service management lens with four complexity domains.

ITIL (Version 5) Complexity Domain	Characteristics	ITIL (Version 5) Response Approach	Cynefin Equivalent
Ordered	Cause and effect are known; linear processes work reliably	Apply defined practices and procedures; automate where possible	Clear + Complicated
Complex	Cause and effect understood only in retrospect; outcomes emerge	Experiment, iterate, observe; use safe-to-fail approaches	Complex
Chaotic	No stable cause-effect relationship; immediate stabilisation required	Act first to restore order; sense and respond once stable	Chaotic
Confused	The nature of the situation is not yet understood	Investigate deeply before acting; gather signal before choosing a domain	Confused / Disorder

The most significant structural difference is that ITIL (Version 5) consolidates Cynefin's Clear and Complicated domains into a single Ordered domain. This is a deliberate simplification for a service management audience. From an ITIL perspective, the distinction between 'apply best practice' and 'apply expert good practice' is less critical than the broader distinction between situations where established approaches work (Ordered) and situations where they don't (everything else). The consolidation makes the model more immediately actionable in operational contexts without losing its essential value.

The result is a four-domain complexity model that retains Cynefin's core intellectual contribution — you need to know what kind of problem you have before you can know how to respond to it — while being directly integrated into a service management framework that millions of practitioners already use.

ITIL (Version 5) doesn't just borrow from Cynefin — it operationalises it. For the first time, complexity thinking is embedded in mainstream service management practice rather than sitting alongside it as an interesting theory.

Where the Intersection Matters Most in Practice

The intellectual connection between ITIL (Version 5) and Cynefin is interesting. The practical implications are more so. Here are four service management contexts where understanding both frameworks simultaneously produces significantly better outcomes.

Major Incident Management

A P1 major incident begins in Chaos. The immediate priority is stabilisation — act, then sense. The classic mistake, observed in countless post-incident reviews, is the organisation that stops to convene a problem-solving group and conduct structured root cause analysis while the service is still down. That is Complicated-domain thinking applied to a Chaotic situation. ITIL (Version 5)'s Complexity Thinking explicitly validates the 'act first' response in chaotic contexts. Cynefin provides the theoretical foundation for why this is not recklessness — it is correct domain-appropriate behaviour.

As the incident stabilises, the domain shifts. What appeared chaotic becomes complex — cause and effect are not yet clear, but the system is no longer in freefall. Probe-sense-respond replaces act-sense-respond. Only once the situation is sufficiently understood does it enter the Complicated domain, where expert root cause analysis and the formal ITIL Problem Management practice become appropriate.

Applying the right response in the right sequence — rather than a single rigid process throughout — is what separates organisations that recover well from those that do not.

Change Enablement

ITIL's Change Enablement practice has always categorised changes by risk and complexity. Standard changes are pre-authorised and repeatable — Ordered domain. Normal changes require assessment and approval — still largely ordered, but with more analysis. Emergency changes require immediate action under time pressure — this is where Chaotic domain thinking applies: stabilise first, document and review after.

The gap that neither ITIL 4 nor traditional change management fully addressed is the Complex domain change, where the outcome cannot be reliably predicted in advance because the organisational system will respond to the change in ways that are not fully knowable before the change is made. Digital transformation programmes, cultural change initiatives, and the introduction of AI-enabled services almost always fall into this category. ITIL (Version 5)'s Complexity Thinking provides the conceptual framework for why these changes cannot be governed the same way as a server migration.

Continual Improvement

ITIL's Continual Improvement practice has traditionally operated in the Ordered domain — measure, analyse, improve, repeat. This works well for operational metrics with clear cause-and-effect relationships: reduce ticket volume by improving self-service, reduce mean time to restore by improving runbooks.

It works considerably less well for improvements in Complex domain areas — customer experience, organisational capability, cultural adoption of new practices. Here, the correct Cynefin approach is probe-sense-respond: run small, safe-to-fail experiments, observe what happens, amplify what works and dampen what doesn't. ITIL (Version 5)'s integration of Complexity Thinking makes this distinction explicit for the first time, providing practitioners with the conceptual permission to use different improvement approaches for different types of problems.

AI Governance — The New Frontier

ITIL (Version 5) introduces a dedicated AI Governance module — and this is perhaps where the Cynefin connection becomes most urgent. AI-enabled services operate almost entirely in the Complex domain. The behaviour of large language models in production is emergent and context-dependent. The interaction between AI capabilities and human behaviour produces outcomes that are not fully predictable in advance. The risks are not fully knowable until the service is live.

Applying Ordered-domain governance — define the policy, implement the control, audit for compliance — to AI services that behave in inherently Complex ways is a category error. ITIL (Version 5)'s Complexity Thinking, informed by Cynefin, provides the foundation for a more appropriate governance model: one that monitors for emergence, creates feedback loops, runs controlled experiments, and treats unexpected outcomes as signals to learn from rather than exceptions to suppress.

What This Means for ITSM Professionals

The practical implication of ITIL (Version 5)'s adoption of Complexity Thinking is this: domain diagnosis is now a first-class service management skill. Before selecting a practice, applying a process, or designing a governance model, the competent ITIL (Version 5) practitioner asks: What kind of situation is this?

That question — deceptively simple, genuinely difficult — is what Cynefin has been training people to ask for twenty-five years. ITIL (Version 5) has now made it a mainstream requirement rather than an advanced practitioner's optional extra.

For practitioners already familiar with Cynefin, Version 5 provides the institutional framework and professional vocabulary to apply complexity thinking within service management without having to first explain the intellectual background to every stakeholder. For practitioners new to Cynefin, Version 5 is the on-ramp — and the full Cynefin framework rewards the deeper study that Version 5 inevitably invites.

The two frameworks are not identical. ITIL (Version 5)'s four-domain model is a pragmatic simplification of Cynefin's five, and Cynefin's broader philosophical apparatus — SenseMaker, narrative research, safe-to-fail experimentation design — goes considerably further than anything in ITIL. But they share the same foundational conviction: that the world is not uniformly predictable, that different kinds of problems require fundamentally different responses, and that the greatest risk in any complex organisation is the confident application of the wrong tool to the wrong kind of problem.

In that conviction, ITIL (Version 5) and Cynefin are not just compatible. They are, finally, speaking the same language.

Enjoyed this post? Join the conversation by leaving a comment or sharing your thoughts below, we’d love to hear your experiences and perspectives. Don’t forget to explore our upcoming events for more opportunities to learn and connect, and visit the forum to continue the discussion.