2 July, 2026

See the WHOLE Picture: How Systems Thinking Helps!


Projects rarely fail because of one isolated problem. In this video, youโ€™ll learn how Systems Thinking helps project managers uncover hidden patterns, understand complexity, and make smarter decisions.

You’ll learn about tools like the Iceberg Model, Causal Loop Diagrams, leverage points, and the Cynefin Framework. Whether you manage projects, teams, or change initiatives, this practical introduction will help you think more strategically and solve problems more effectively.

This video is safe for viewing in the workplace.

This is learning, so, sit back and enjoy

Systems Thinking

Projects are complex, and if you try to simplify them too much, youโ€™re storing up problems. Seeing the bigger picture and taking a holistic view is what Systems Thinking is all about.

What is Systems Thinking?

Systems thinking is a framework for understanding complex situations. It:

  • Considers interconnections and relationships between parts rather than examining them in isolation.
  • Looks for causal loops, which recognize that actions often loop back on themselves.  Feedback replaces simple linear thinking, where A causes B.
  • Seeks out underlying patterns and structures, instead of reacting to isolated events.
  • Looks for leverage points, where a small change can produce big, long-term changes.
  • Understands that a system’s performance depends on how its parts fit together as an integrated whole.

Ultimately, systems thinking is a discipline for seeing the ‘big picture’.

Why is Systems Thinking Important for Project Professionals?

Project-based work is often complex, balancing multiple objectives and constraints. Performance depends on how the parts of a project fit together, not just how they act separately.

Systems thinking allows project professionals to understand the relationships between stakeholders, agendas, activities, dependencies, and requirements. It can anticipate consequences, make better decisions, reduce risk, and deliver more effectively.

When you move from seeing the world as a collection of separate parts to treating projects, programs, and portfolios as dynamic and interconnected systems, you raise the chances of success.

Systems thinking applies in many ways, like:

  • Understanding context, finding the levers to success
  • Identifying interdependencies and constraints
  • Project planning and resource optimization
  • Stakeholder analysis and relationship mapping
  • Risk management and scenario planning
  • Analyzing the impacts of scope, function, and technical changes
  • Continuous improvement by understanding feedback loops

Systems thinking is vital for broad organizational change and business transformation. It gives a holistic view of the complex interactions of the different parts of an organization. This ensures change initiatives stay aligned with long-term goals, and enhances overall performance and value delivery.

What are Some Key Systems Thinking Methods and Tools?

There are a wide range of models and tools that support systems thinking. Here are five important examples:

The Iceberg Model

This assesses visible impacts into four levels:

  1. Events: Visible symptoms, like a missed deadline.
  2. Patterns of Behavior: Trends and behaviors that drive events.
  3. System Structures: The systems and policies causing the patterns.
  4. Mental Models: Deeply held beliefs and ways of thinking that underpin choices of structure.

Most PMs stay in fire-fighting mode at the event level. True leverage is found in the deeper levels of Structures and Mental Models.

Finding Leverage

Leverage points are places in a system or process where a small shift produces big results. For project managers, powerful levers include:

  • Incentives that align individual objectives with the projectโ€™s goals.
  • Frequent cycles of proactive risk management.
  • Attention to milestones and product delivery
  • Information flows and active stakeholder communication
  • Project Sponsor involvement

The further down the iceberg model we work, the greater the leverage we can get.

Causal Loop Diagram (CLD)

This is a visual tool for mapping out the relationships between different parts of a system. It shows how changes in one thing can influence other things, creating loops of cause and effect.

It is like a map of how different factors are connected. Arrows show how one thing causes another. It shows:

  • Reinforcing Loops: factors that reinforce each other to amplify change (positive loops)
  • Balancing Loops: factors that create balancing forces to stabilize the system (negative loops). These often manifest as resistance to change.

The Cynefin Framework

The Cynefin Framework is a model for understanding the different types of problems we can face. So we use Cynefin to categorize the environment:

  • Simple with linear, obvious cause-and-effect relationships that are susceptible to best practices
  • Complicated, also with cause-and-effect relationships but now harder to identify and understand. Use experts and good practices.
  • Complex with weak cause-and-effect relationships that are only clear in retrospect. Use multi-disciplinary teams to probe the situation, make sense of it, and craft a response.
  • Chaotic with no discernible patterns. You need to design experiments and find creative solutions. Applying best-practice solutions to complex problems is a major cause of project failure.

We have a full video on the Cynefin Framework.

System Archetypes

These are common patterns of behavior that appear in many different systems. Recognizing archetypes helps you quickly identify potential problems or opportunities in a system. They are like reusable blueprints of how systems organize themselves.

  • Fixes That Fail: A quick fix (like a temporary patch) works now but creates an unintended consequence that makes the problem worse later.
  • Shifting the Burden: Relying on solutions to the symptoms (like overtime) instead of addressing fundamental issues (like process improvement).
  • Tragedy of the Commons: Multiple projects competing for the same limited pool of shared resources (e.g., the same senior architect), eventually crashing the whole system. These models aren’t mutually exclusive. They can be used together to gain a deeper understanding of complex systems. The best model to use depends on the specific problem you’re trying to solve.

Carefully curated video recommendations for you:


What Kit does a Project Manager Need?

I asked Project Managers in a couple of forums what material things you need to have, to do your job as a Project Manager. They responded magnificently. I compiled their answers into a Kit list. I added my own. 

Check out the Kit a Project Manager needs

Note that the links are affiliated.

Learn Still More

For more great Project Management videos, please subscribe to the OnlinePMCourses YouTube channel.

If you want basic Management Courses – free training hosted on YouTube, with 2 new management lessons a week, check out our sister channel, Management Courses.

For more of our Project Management videos in themed collections, join our Free Academy of Project Management.

For more of our videos in themed collections, join our Free Academy of Project Management

Mike Clayton

About the Author...

Dr Mike Clayton is one of the most successful and in-demand project management trainers in the UK. He is author of 14 best-selling books, including four about project management. He is also a prolific blogger and contributor to ProjectManager.com and Project, the journal of the Association for Project Management. Between 1990 and 2002, Mike was a successful project manager, leading large project teams and delivering complex projects. In 2016, Mike launched OnlinePMCourses.
{"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}

Never miss an article or video!

 Get notified of every new article or video we publish, when we publish it.

>