Complex vs Complicated: The Cynefin Framework

Overview

• What you’ll learn: The Cynefin Framework’s five domains, the critical difference between complex and complicated, and why Scrum is optimized for the complex domain.
• Prerequisites: Lesson 5 — The Five Scrum Values
• Estimated reading time: 13 minutes

Introduction

Not all problems are the same. Fixing a car engine is complicated — there are many parts, but an expert can analyze, diagnose, and predict the outcome. Raising a child is complex — there are many interacting factors, outcomes are unpredictable, and what worked for one child may not work for another.

Scrum is designed for complex problems. Using Scrum for simple problems is overkill. Using Waterfall for complex problems is a recipe for failure. The Cynefin Framework helps you understand which domain you’re operating in.

The Five Domains

Clear (formerly Obvious/Simple)

Cause and effect are obvious. Best practices exist. Sense → Categorize → Respond.

Example: Processing a standard invoice. Follow the procedure. No Scrum needed.

Complicated

Cause and effect can be determined through analysis. Expert knowledge is required. Sense → Analyze → Respond.

Example: Building a car engine. An expert can analyze and predict outcomes. Waterfall can work here.

Complex

Cause and effect can only be understood in retrospect. Emergent patterns appear through experimentation. Probe → Sense → Respond.

Example: Developing a new software product. You need to try things, get feedback, and adapt. This is where Scrum thrives.

Chaotic

No perceivable cause and effect. Immediate action is needed to stabilize. Act → Sense → Respond.

Example: A server is down and the company is losing money every minute. Act first, analyze later.

Confusion (the center)

You don’t know which domain you’re in. The priority is to gather information and move to a known domain.

Why This Matters for Scrum

Scrum’s empirical approach — probe (build an Increment), sense (inspect it with stakeholders), respond (adapt the plan) — is perfectly matched to the complex domain. In complex systems:

• You cannot predict the outcome of your actions in advance.
• The best approach emerges through short experiments and rapid feedback.
• Retrospectives and reviews are essential because you can only understand cause and effect after the fact.

Key Takeaways

• The Cynefin Framework identifies five domains: Clear, Complicated, Complex, Chaotic, and Confusion.
• Complex problems require empirical approaches (probe → sense → respond). Scrum is designed for this.
• Complicated problems can be solved with analysis and expertise. Waterfall may work.
• Using the wrong approach for the domain leads to failure — Scrum for simple problems is wasteful; Waterfall for complex problems is dangerous.

What’s Next

In Lesson 7, you will explore the difference between fixed and growth mindsets and how mindset shapes a team’s ability to adopt Agile practices.