Skip to main content

Understanding Complexity

June 29, 2017

One of the most important things to understand in modern business (and quite possibly life in general) is the concept of complexity. While we use the words complicated and complex almost interchangeable in everyday language, they mean very different things. Let’s explore my favourite model on complexity called Cynefin.

There are already a number of introduction to Cynefin articles or videos, including Dave Snowden’s own one, but many are still not very approachable. Let’s try explaining it with games. Richard Shy has created an amazing visualisation of Cynefin in one of my courses.

 

Cynefin

Four domains of Cynefin

Cynefin talks about four different types of problems or domains. Obvious, Complicated, Complex and Chaos. We will tackle those first and cover Disorder later.

Cynefin is a way to figure out what type a given problem is and talks about a high level strategy for solving those types of problems.

Obvious

The gaming analogy for Obvious is Tic-Tac-Toe, also called Naughts & Crosses. Like Tic-Tac-Toe, Obvious problems have a clear, predictable cause & effect.

The high level strategy for solving Obvious problems is ‘Sense – Categorise – Respond’. Sense is nothing more complex in this case than looking at the board. Categorise means that we can reduce all possible variations into a much smaller, manageable subset. And Respond is making a move. Tic-Tac-Toe has 255,168 possible games, but we need only a few rules to play the best possible game. Take the starting piece, it should be placed in a corner, any corner will do.

We respond to Obvious problems by picking the appropriate Best Practicse. We have looked at all possible game and have figured out the best possible way. They are called Best, because there is always exactly one best response.

The obvious problem with obvious problems is that we don’t have much of those left IRL. This is the stuff that is easily automated. Computers are extremely suited for this type of work.

Complicated

Now Tic-Tac-Toe is a very boring game exactly because we have figured it out. Following best practices will make you play a perfect game. If both players play a perfect game it is a draw.

Chess is very different. And our high level strategy for Obvious problems won’t help us playing chess. A few moves into a game of chess and the board is in a position you have never seen it in before. And more importantly a tiny difference in the board makes a massive difference in the game.

In complicated problems the relationship between cause and effect is predictable, but (very) hard to predict. Complicated problems are the domain of expert, who are better able to predict what is likely going to happen. Which is exactly what top chess players do. They need to predict what the likely moves of their opponents are going to be. Experts can simultaneously consider more possible options, but also reduce it to a smaller set of scenarios that require more analysis.

So the strategy becomes Sense – Analyse – Respond. And because it is impossible figure out if a move is the best move (except check-mate obviously) there are no best practices in the complicated domain.

But there are good practices. Practices that are considered useful in certain contexts. In chess an example is the value of your pieces. Every piece in chess has a value associated with it. And you always want the total value of your pieces to be higher than your opponents. Unless you don’t want that, because you want to sacrifice a piece for board position.

Complex

Complex problems are completely different again. What sets them apart is that the relationship between cause & effect is only obvious in hindsight. The gaming metaphor for complexity is poker. Unlike chess, which is a game about predicting, poker is game about learning. Learning what cards your opponents have and how they compare to yours. And the high level strategy for chess doesn’t work for poker.

If you play my favourite game of poker, Texas Hold’em, you can look at your own cards until you are blue in the face, but the only thing you are going to learn is your opponents do not have the exact same cards as you do. So Sense – Analyse – Respond is out as a way to deal with complexity.

What we need instead is Probe – Sense – Respond. A Probe is a safe-to-fail experiment. Depending on the outcome of that experiment (Sense) we respond by amplifying the good and/or dampening the bad (Response).

Again, taking the poker example that probe can be in the form of betting. If you make a bet you force opponents to respond to it, by folding, calling or raising. This can give you information about their hand. But other probes can be calling out opponents, sensing can be just looking at their demeanours for example.

So the most important thing about Complexity is that there is no way to learn (and thus solving the problem) without doing. Just thinking about it isn’t going to solve it. In Complex problems our practices are always evolving based on what we learn. In poker, even if we would play a game with the exact players with the exact same cards would turn out differently, because we learned things not just about the game, but certainly about our opponents.

Chaos

Chaos happens when there is no relationship between cause and effect or they change very quickly. In this case there is no point in probing because any learning does not help us get better.

The gaming analogy here is children playing. Anyone who has ever played with kids know that the rules are continuously changing. And there is no point in trying to learn the rules before starting to play. You have to get in and play with them (Act), while making sure are having fun (Sense) and change accordingly if not (Respond).

But most often we end up in Chaos because of some crisis. When that happens we need to very quickly stabilise the situation and get back out of Chaos. This happens all the time in business, where we are frequently relying on hero leaders and task forces to get us out of trouble.

The practices here are Novel.

Disorder

Disorder isn’t a separate domain, but instead means that we are using the set of strategies that we are comfortable with instead of the appropriate ones for the problem at hand.

And the unfortunate reality is that most people are spending most of their time there.

Conclusion

I am not even remotely kidding or exaggerating when I say that understanding Cynefin has changed my life. Whenever I find myself (or people around me) spending too much time thinking, my first instinct is to take a step back to make sure the problem at hand is Complicated. When organisations keep insisting on Best Practices I check whether the problem at hand is indeed Obvious. If it is Complicated (which is very likely) we should be looking at a myriad of good practices and figure out which practices is applicable in what circumstances.

But the most important learning is that a whole lot of our circumstances are complex. And thus inherently unpredictable. And no amount of thinking is going to solve that.


What did you think about this post?

Comments (8)


Chuck Suscheck
01:30 pm June 29, 2017

One of the things that piqued my interest in Cynefin is that companies that organizations believing they are in the obvious domain often move to chaos when a non-standard problem becomes apparent.


Jim Gilliece
01:00 am June 30, 2017

I wish there had been a moment spent on Occam' s Razor - as, so often, simple solutions win; once we are finished with the over thinking.


evanderkoogh
06:31 am July 3, 2017

Hey @chucksuscheck:disqus. That is indeed the case. Prolonged exposure to Disorder indeed leads to Chaos. But especially the Obvious/Chaos cliff is insidious..


evanderkoogh
06:34 am July 3, 2017

@jimgilliece:disqus Interestingly enough Occam's Razor is not at all about solutions, but about hypotheses. "Among competing hypotheses, the one with the fewest assumptions should be selected."

Which fits is very well with dealing with Complex problems. Pick the hypothesis with the fewest assumptions, test them, learn and repeat.


Andrew Webster
04:21 pm July 3, 2017

Very good introduction to Cynefin, thank you. I'm _so_ stealing the games metaphor! As an Agile coach and trainer, I now include Cynefin as an essential component in setting the context for Agile in a large business environment.
It's a generalization, I know, but I've found than in many larger businesses, people are under such "pressure" that introducing Agile is experienced as causing more overhead, not less, and so it tends to be rejected, or becomes ScrumBut or similar as people go through the motions without understanding how it's going to benefit them.
However, introducing Cynefin can be a game changer, as it allows people to start asking questions like "If Best practices are actually irrelevant or dangerous to this work in this situation, how can we identify Good practices? Or even Emergent...?"
Bingo!
"We are uncovering better ways of developing software by doing it and helping others do it" - welcome to Agile.


Carlos Arturo Quiroga
07:08 pm January 9, 2018

The context could affect the classification of a kind of project? for example a two machines (algorithms) running chess could make it "Obvious"? The context and point on view could affect the nature of problems?


evanderkoogh
02:58 am January 16, 2018

The context influences everything. It is all about the relationship between cause and effect. Is it obvious, hard to predict, only obvious in hindsight or non-existing?


Carlos Arturo Quiroga
08:38 pm January 16, 2018

@evanderkoogh:disqus could you refine your question? I'm totally agree with your answer about the context. I will invite you put on your trainees about "Understand Complexity oriented by context" because the classification of problems or projects must be done based on the context, and for the same problem or project could have different classification on different context