GPM Global · Project Context
Project Complexity, Explained
Why two projects with the same plan can need very different management. And how GPM rates the difference.
A short guide to what project complexity means, why it matters, and how to check your own project.
Every project happens in different conditions. Some projects are easy to plan and run. Others are full of moving parts that nobody can predict. The word "complexity" describes these conditions. This page explains what complexity means, why it matters, and how you can check the complexity of your own project in a few minutes.
Complexity is not good or bad. It is just a description of the conditions around your project. But knowing the complexity helps you plan in the right way, read your results correctly, and talk to investors and sponsors honestly about what your project really faces.
Why Complexity Matters
Two projects can look the same on paper. Same budget. Same plan. Same team. But one will finish on time, and the other will struggle for years. The reason is often complexity — the conditions around the project, not the project itself.
Here is a simple example. A company wants to build a new office. In one country, the rules are stable, the supply chain is local, and the team has built ten offices before. In another country, the rules change every year, materials must come from three different countries, and the team has never worked there. The plan looks the same. The complexity is very different. The second project needs a different way of working.
A high complexity rating is not a problem. A low rating is not a reward. Complexity tells you what kind of project management you need, what kind of risks you should plan for, and how often you should review your decisions. It also tells investors and sponsors what your team is really facing.
Three Things That Make a Project Complex
GPM looks at twelve indicators across three groups. Each group describes a different source of complexity.
|
1 · Internal Complexity — What is inside the project
This is about how the project is built and run. How many people need to agree on decisions. How clear the goals are. How well-known the methods are. Whether the team has done this kind of work before.
Example: A project led by one company, with one clear goal, using methods the team has used many times, has low Internal Complexity. A project with five partner companies, unclear goals that change each month, and new technology nobody has used before, has high Internal Complexity.
|
|
2 · External Complexity — What is around the project
This is about the conditions outside the project that you cannot control. The weather and climate where the project happens. The rules and laws that may change. The supply chain — where materials and services come from. Public attention and social acceptance. The pace of technology change.
Example: Renovating an office in a stable city, where the rules are clear and materials are local, has low External Complexity. Building a wind farm in a country where the energy rules are being rewritten, the storms are getting worse, and some materials come from one supplier in a different country, has high External Complexity.
|
|
3 · Coupling — How things in the project interact
This is about how risks and problems connect to each other. When one thing goes wrong, does it stay contained, or does it trigger many other things to go wrong? It is also about time — does the project run longer than anyone can predict the future?
Example: A short, simple project where each risk is separate from the others has low Coupling. A multi-year project where any small problem in one part of the work creates bigger problems in three other parts has high Coupling.
|
Four Levels of Complexity
We combine the three groups into one of four categories. Each category needs a different way to plan and run the project. The categories come from a well-known model called Cynefin, used widely in project management.
|
Simple — Everything is clear
The plan can be followed step by step. The methods are well-known. The risks are known and contained. You can predict the result.
Example: Replacing the windows in an office building. The team has done this many times. The materials are standard. There are no surprises.
How to manage it: A clear plan, regular check-ins, and a small team. Review once a year.
|
|
Complicated — It needs expertise
The work needs experts. The right answer exists, but you need analysis to find it. The methods are known to specialists. With the right people, the project can be planned well.
Example: Building a new hospital with several specialty wings. The construction is well-understood, but each wing needs different experts: surgery, imaging, emergency care, pharmacy. Coordination matters.
How to manage it: Bring in experts. Use proven methods. Build a clear plan with named change triggers, so the team knows when to review.
|
|
Complex — You learn as you go
Cause and effect are only clear in hindsight. A fixed plan will not survive contact with the conditions. The team must try things, see what happens, and adjust. Wave planning works better than one big plan.
Example: A multi-country infrastructure project where the regulations are still being written, the technology is new, and several partners have different interests. Nobody can fully predict what will happen in year three.
How to manage it: Plan in waves. Review every three months. Build flexibility into contracts and budgets. Expect to reframe the project as you learn.
|
|
Chaotic — The situation is changing fast
The conditions change too fast to plan in the normal way. The team must act now to create some stability, then look again. Any normal assessment is only true at the moment it is written.
Example: Setting up emergency hospitals during a pandemic. The disease is new. The rules change every week. Supplies are uncertain. The team must build, learn, and rebuild.
How to manage it: Act first to stabilise the situation. Set up a continuous watchlist. Treat every assessment as a snapshot, not a position. Review weekly, not yearly.
|
How GPM Uses Complexity
A complexity rating is not a verdict on your project. It is a companion to GPM's assessment models. When a GPM360° assessment is read together with the complexity rating, the result is more honest and more useful.
For example, a project with a strong assessment score in Simple conditions is doing well. The same score in Complex conditions means something different: the project may be doing well today, but the conditions can change, and the team should review more often. Same score. Different meaning. Without the complexity rating, the reader would not know which meaning applies.
This is why GPM provides the complexity rating as a free, public tool. The rating is for the project team, the sponsor, the board, and anyone who reads a GPM assessment of the project.
A complexity rating describes the terrain your project sits on. It does not judge the project, the team, or the result. It helps everyone read what comes next with the right expectations.
How to Check Your Project
The tool is free. It takes about four minutes. You answer twelve short questions about your project. Each question has five answers to choose from, with clear descriptions. There are no right or wrong answers — only the answer that best describes your project.
|
Step 1 — Start the tool
|
|
Open the tool. Enter your name and country. You can add your project name and organisation if you want — these are optional and only used to personalise your report.
|
|
Step 2 — Answer twelve questions
|
|
Five questions about Internal Complexity, five about External Complexity, and two about Coupling. For each one, choose the answer that best matches your project today. Nothing is sent anywhere while you answer — your responses stay in your browser.
|
|
Step 3 — See your result
|
|
You will see your three scores, your category, and short notes explaining how to read the result. You can save the report as a PDF, or have it sent to your email so you can forward it to your sponsor or team.
|
Free · Four minutes · Nothing saved unless you choose to email it
Check Your Project's Complexity
Twelve questions. A clear report. Useful whether or not you ever do a full GPM360° assessment.
Start the Free Tool →
Want to go further? The complexity rating is the companion to GPM360° — our independent third-party certification of project sustainability for investors, boards, and regulators.
