What Is a Complicated/Complex/Wicked Problem

Learn how to solve problems more effectively by distinguishing different categories of complex problems and starting from their unique characteristics.

A complex problem is made up of many interrelated elements that can behave adaptively. Each element can be clearly identified and understood with regards to their own characteristics and local rules but when considering the relationship between them, there is a high level of dynamic, non-linear interactivity. This means that you cannot predict the overall outcome of the system by looking at the interaction between small parts. The system is more than the sum of its parts as the main patterns within the problem can only be identified and analysed after the fact.

To fully understand what a complex problem is, you need to consider what it is in relation to a complicated problem (easier than complex) and a wicked problem (more complex than complex).

If you found the formal definitions confusing, then here is a simple version:

Ultimately, problems range from simple to complex. Complex problems fall exactly in the middle of the scale. Complicated problems fall below them and wicked problems fall above them. However, there is also varying levels of complexity within each category.

When I say varying levels of complexity, I mean each category has a minimum and maximum value which will never cross over.

I don’t rely on theory when understanding how these problems play out in practice. Below is how I understand each:

When faced with a complicated problem you can break down a large problem into individual sub-problems. This means you have a ‘whole is equal to sum’ situation. The end goal is very clear and there’s no compromise in value judgement.

Based on my experience, a complicated problem often depends on your knowledge in the particular domain and if you’ve had experience solving this type of problem previously. If you have you’ll find it much easier, however if there’s a guide or playbook you can follow, even someone with no knowledge will be able to solve the problem with ease compared to someone who hasn’t.

This is similar to having a large Lego set to build with. With a guide you can build up individual parts and then snap them together. Or even build the whole thing at once. As each part can be broken down into individual sub-problems, you can give individuals different pieces to work on to speed up the process. This reduces the complexity. For example in manufacturing, the car won’t be built from scratch by the car manufacturer. They outsource certain parts to specialist factories and then assemble the car. This reduces R&D costs massively.

When dealing with a complex problem you cannot break down a large problem into individual sub-problems.

The only way to solve a complex problem is to simulate a scenario and keep adding variables to run mini-experiments. Once you have a simulated system, you start to add variables to test how it reacts. You keep altering your approach until you find a solution. This makes solving them quite complex due to the amount of variables and links between them. However there is a definite end goal.

This is like trying to untangle a messy ball of yarn. If you pull one loose piece of yarn on the left you may cause the yarn on the right to become a tight ball. You can’t just force a solution and have to try gently pulling on a piece of yarn. The solution is very clear: either you untangle all the yarn or knit it into a jumper.

You can’t break down a complex problem into smaller pieces. For example if you took a pair of scissors and cut the yarn ball in half to make it easier to untangle. Whilst you could untangle each half, the yarn ball you have just solved is no longer the yarn ball you started with. The length of yarn has changed so you have altered the sub-elements.

There is an objective problem in a wicked problem. In fact it has already been defined. As there are many possible causes, jurisdictions, stakeholders and regulators involved it’s actually very easy to identify causes or authorities involved. Plus there are many possible solutions to the problem. Each solution has obvious trade-offs.

However there can never be agreement with the different parties.

This seems to me like a group of people trying to pull on a large object. As the object is so large they can’t see the whole thing. Everyone is using their full strength to pull the object towards them. The large object doesn’t move at all. The solutions are very clear but no-one will agree to them.

No. Unlike a complicated problem where the whole equals the sum of its parts, cutting a complex problem into isolated pieces alters the underlying sub-elements and severes their dynamic interactions—meaning you end up solving a completely different problem than the one you started with.

Because you cannot predict the outcome of a complex problem using a static blueprint, you must rely on simulation and iterative probing—testing small variables within a controlled environment, observing system feedback, and adapting your approach. (Note: Once you publish your Pillar page, link “problem solving strategies” right here).

DarkLight

Further Reading

Logical Compilation: Collapsing Linear Prose into Explicit Proposition TreesWhy does natural language need an AST? Exploring computable environments, decoding costs, and collapsing linear prose into explicit proposition trees.

An architectural comparison of Obsidian Canvas and Heptabase: how file-centric vs. card-centric data models shape spatial thinking, graph indexing, and data portability.