Systems Thinking in Project Management Training Course

Duration 10 days 21 modules · 65 contact hours
Level Intermediate Certificate on completion
Who attends Project Managers, Programme Managers and others
Fee from USD 2,200 KSh 190,000 for Kenyan organisations
Where 52 cities + online See dates by city
Next start 9 Nov 2026 Course code SD-PM-078

Before you join: Participants should have practical experience working on projects, programmes, operational change or major workstreams.

Dates & prices

Two start dates a month in every city, and live online on weekdays or weekends. Fees are per participant; classroom fees include tuition, materials, lunch and refreshments, and the certificate.

Suggest a date or city

Showing the next six months. Later dates, other cities and private deliveries for your team are available on request.

Course overview

Projects rarely fail because one task was missed in isolation. They fail when decisions in one area create delayed effects elsewhere: a schedule recovery plan increases rework, a procurement saving reduces supplier reliability, or a governance change slows technical decisions. Project managers must understand interdependencies among people, processes, technology, suppliers, funding, risks and external conditions. Systems thinking provides practical ways to identify these relationships before they become costly delivery problems.

This course teaches participants to view projects as dynamic systems rather than linear plans. Participants use system boundaries, stakeholder maps, rich pictures, causal loop diagrams, stock-and-flow models, system archetypes and Soft Systems Methodology to diagnose difficult project situations. They learn to identify feedback loops, time delays, unintended consequences, constraints and recurring patterns such as shifting the burden, fixes that fail and success to the successful. The course also connects systems thinking with established project management practices including governance, risk, change control, scheduling, benefits management and lessons learned.

Instructor-led sessions combine short technical briefings with cases drawn from infrastructure, technology, public-sector transformation, financial services and operational change. Participants analyse project scenarios, test interventions through group simulations and apply each method to a current or recent project. They leave with a practical project systems analysis pack: a defined system boundary, stakeholder and interface analysis, causal loop diagrams, priority interventions, monitoring measures and a systems-informed action plan. A certificate of completion is awarded to participants who attend the course.

The course is designed for project professionals who already understand core project management and need stronger methods for managing complexity, uncertainty and cross-functional dependencies.

What you will be able to do

  • Define project system boundaries, actors, interfaces and external influences
  • Construct causal loop diagrams that expose feedback, delays and unintended consequences
  • Apply system archetypes to recurring delivery and governance problems
  • Develop stock-and-flow models for project capacity, backlog and resource constraints
  • Use Soft Systems Methodology to structure ambiguous stakeholder situations
  • Assess project interventions through system dynamics, scenarios and feedback effects
  • Integrate systems insights into risk, governance, change and benefits plans
  • Present a complete project systems analysis and intervention plan

Benefits of attending

For you

  • Diagnose recurring project problems beyond immediate symptoms
  • Explain complex dependencies clearly to sponsors and delivery teams
  • Make stronger intervention choices before committing budget or resources
  • Recognise feedback loops that distort schedules, risks and performance reports
  • Produce credible systems analyses for complex project assignments

For your organisation

  • Earlier identification of cross-functional delivery risks and hidden constraints
  • Fewer corrective actions that create additional rework or delays
  • Better coordination between project teams, operations, suppliers and governance bodies
  • More informed investment decisions through visible assumptions and feedback effects
  • Stronger lessons learned from patterns that recur across projects

Course modules

21 modules over 10 days

Participants can describe a project as an interacting system with defined boundaries and relationships.

  • Projects as open systems with boundaries, purpose, interfaces and feedback
  • Distinguishing complicated work from complex adaptive project conditions
  • ISO 21502 principles interpreted through interdependencies, uncertainty and value delivery
  • Project success criteria examined beyond scope, schedule, cost and quality
  • Recognising emergence, nonlinearity and unintended consequences in delivery decisions
  • System archetypes used to explain recurring project performance patterns

Participants can set useful system boundaries for a project issue without excluding critical influences.

  • Defining focal system, environment, subsystems and relevant external actors
  • Boundary critique tests for excluded stakeholders, assumptions and consequences
  • PESTLE factors linked to project constraints and changing conditions
  • Mapping upstream inputs, downstream outcomes and operational handovers
  • Identifying boundary disputes between sponsors, users, suppliers and regulators
  • Framing project questions that support systems-level investigation

Participants can map stakeholder perspectives and critical interfaces affecting project performance.

  • Stakeholder maps showing influence, interest, dependencies and conflicting objectives
  • Rich pictures representing relationships, tensions, information flows and power
  • Interface analysis between project teams, business units and external suppliers
  • Customer journeys connected with project outputs, adoption and service outcomes
  • Surfacing tacit assumptions through perspective comparison and structured questioning
  • RACI limitations when accountability crosses organisational and contractual boundaries

Participants can build and interpret causal loop diagrams for project delivery problems.

  • Variables written as measurable conditions rather than vague management labels
  • Causal links marked with polarity and directional influence
  • Reinforcing loops explaining escalation, growth and accelerating project pressures
  • Balancing loops explaining control, limits and corrective action
  • Time delays identified between decisions, actions and observed results
  • Causal loop diagrams tested against evidence, stakeholder experience and logic

Participants can identify feedback structures that produce delayed or disproportionate project outcomes.

  • Feedback loops connecting schedule pressure, overtime, errors and rework
  • Delay structures affecting approvals, procurement, recruitment and benefit realisation
  • Nonlinear relationships between workload, productivity, quality and team morale
  • Threshold effects triggered by capacity limits, compliance breaches or stakeholder resistance
  • Tracing second-order consequences of accelerated delivery and cost reduction decisions
  • Leading indicators selected for feedback loops before performance deterioration appears

Participants can use system archetypes to diagnose common patterns behind project difficulties.

  • Fixes that Fail applied to short-term schedule recovery actions
  • Shifting the Burden diagnosed in consultant dependency and capability gaps
  • Limits to Growth examined through resource, approval and supplier constraints
  • Success to the Successful assessed in portfolio funding and priority decisions
  • Escalation patterns recognised in competing workstreams and departmental targets
  • Tragedy of the Commons analysed for shared specialists and technical environments

Participants can structure ambiguous project situations using Soft Systems Methodology.

  • Soft Systems Methodology for problems lacking agreed definitions or objectives
  • Rich pictures developed from multiple stakeholder perspectives and contested concerns
  • CATWOE analysis identifying customers, actors, transformation, worldview, owners and environment
  • Root definitions written using purposeful activity system language
  • Conceptual activity models compared with current project practices
  • Feasible and desirable changes identified through stakeholder dialogue

Participants can model accumulations and rates that affect project throughput and delivery capacity.

  • Stocks distinguished from flows in work backlog, defects and available capacity
  • Stock-and-flow diagrams built for project demand, throughput and rework
  • Little's Law used to examine work-in-progress and cycle time
  • Resource loading linked with utilisation, queues and service delays
  • Backlog growth traced through intake rates, completion rates and quality losses
  • Capacity policies assessed for delayed effects on project commitments

Participants can analyse project risk interactions, escalation paths and control feedback.

  • Risk registers extended with causal dependencies, triggers and feedback pathways
  • Bowtie analysis connecting threats, preventive controls, consequences and recovery controls
  • Risk networks showing common causes across schedule, cost and quality exposure
  • Control effectiveness assessed through detection delays and response capacity
  • Assumption logs linked to uncertainty, decision points and monitoring indicators
  • Escalation criteria designed for emerging system-level risk patterns

Participants can assess how governance structures influence project decisions and delivery outcomes.

  • Governance structures mapped as decision rights, information routes and escalation paths
  • Decision latency measured from issue detection through authorised action
  • Stage gates assessed for learning value, control value and delay effects
  • Information asymmetry examined between sponsors, delivery teams and suppliers
  • Management dashboards tested for feedback quality, timing and decision usefulness
  • Decision logs used to trace assumptions, choices and resulting consequences

Participants can assemble a first systems analysis of a selected project issue.

  • Selecting a material project issue with multiple interacting causes
  • System boundary statement drafted for the chosen project challenge
  • Stakeholder and interface map created from available project evidence
  • Initial causal loop diagram developed around observed delivery symptoms
  • Key assumptions recorded with owners, evidence sources and review dates
  • Problem framing reviewed against sponsor objectives and operational outcomes

Participants can identify system effects hidden by conventional project schedules.

  • Critical path assumptions tested against resource constraints and feedback effects
  • Dependency structure matrices reveal coupled tasks and iterative rework cycles
  • Schedule buffers assessed for protection, visibility and behavioural consequences
  • Milestone reporting examined for false certainty and delayed risk signals
  • Rolling-wave planning linked to uncertainty reduction and learning cycles
  • Recovery plans tested for quality losses, capacity strain and downstream delays

Participants can diagnose resource and team dynamics that influence project execution.

  • Resource pools mapped across projects, operational work and unplanned demand
  • Multitasking effects examined through switching costs, queues and incomplete work
  • Skills matrices linked to bottlenecks, single points of failure and succession
  • Overtime feedback analysed for fatigue, defects, absence and productivity decline
  • Team psychological safety connected with issue reporting and corrective learning
  • Supplier capacity assessed through lead times, incentives and contractual dependencies

Participants can model how project outputs produce adoption and sustained benefits.

  • Benefits dependency networks connect outputs, capabilities, outcomes and strategic objectives
  • Adoption loops analysed through training, usability, confidence and local support
  • Change impact assessments linked to process, role, technology and policy interfaces
  • Resistance patterns distinguished from valid operational concerns and design defects
  • Benefits measures separated into leading indicators, outcomes and longer-term impacts
  • Transition plans address handover capacity, ownership and service stabilisation

Participants can design and compare interventions for complex project situations.

  • Intervention points selected from causal structures, constraints and stakeholder influence
  • Scenario planning tests plausible changes in demand, funding and supplier performance
  • Policy resistance anticipated when controls conflict with local incentives
  • Small tests designed to generate evidence before wider project commitments
  • Trade-off matrices compare intervention cost, timing, risk and expected effects
  • Monitoring plans connect intervention actions with leading feedback indicators

Participants can adapt project controls to provide earlier and more useful system feedback.

  • Integrated control plans connect scope, schedule, cost, risk and benefits measures
  • Leading indicators chosen for workload, rework, decision latency and adoption
  • Control limits defined for escalation before critical thresholds are crossed
  • Earned value data interpreted alongside quality, capacity and dependency indicators
  • Change control evaluates system-wide effects before approval decisions
  • Lessons learned structured around patterns, causes, interventions and observed outcomes

Participants can communicate systems findings clearly to different project decision-makers.

  • Audience-specific system maps prepared for sponsors, teams and operational owners
  • Diagram conventions improve readability, traceability and challenge of causal claims
  • Narrative walkthroughs explain feedback loops without specialist terminology
  • Evidence labels distinguish facts, estimates, assumptions and stakeholder perceptions
  • Briefing papers link system diagnosis with decisions, owners and timescales
  • Facilitated review methods surface disagreement without losing analytical discipline

Participants can apply systems thinking to interactions among projects, programmes and portfolios.

  • Portfolio dependency maps identify shared resources, enabling projects and bottlenecks
  • Programme outcomes traced through capabilities, adoption and operating model changes
  • Prioritisation criteria tested for unintended effects on strategic delivery capacity
  • Funding cycles examined for stop-start costs, talent loss and supplier instability
  • Cross-project risk aggregation reveals correlated threats and common control weaknesses
  • Portfolio reviews use feedback indicators alongside financial and milestone reporting

Participants can establish learning and assurance practices that respond to changing project conditions.

  • Project assurance questions test assumptions, interfaces, feedback and adaptive capacity
  • After-action reviews examine decisions, system conditions and delayed consequences
  • Double-loop learning challenges governing assumptions behind recurring project issues
  • Knowledge repositories capture causal patterns rather than isolated lessons
  • Adaptive review cycles align monitoring frequency with project uncertainty and change
  • Independent challenge strengthens evidence, alternatives and intervention decisions

Participants can integrate multiple systems methods into a coherent project analysis.

  • Boundary, stakeholder and causal analyses reconciled into one project system model
  • Priority loops selected using impact, uncertainty, controllability and evidence criteria
  • Stock-and-flow elements added where accumulation drives delivery performance
  • Archetypes used to test whether proposed explanations match recurring patterns
  • Risk, governance and benefits implications derived from the integrated model
  • Intervention options refined with owners, dependencies, indicators and review points

Participants can build, review and present a complete project systems analysis and intervention plan.

  • Complete project systems analysis assembled from boundary, stakeholder and causal evidence
  • Priority delivery problem framed with explicit assumptions and success measures
  • Causal loop diagram presented with feedback, delays and critical uncertainties
  • Intervention plan specifies actions, owners, dependencies, indicators and decision dates
  • Peer review challenges model logic, evidence quality and implementation feasibility
  • Executive presentation communicates findings, recommendations and required governance decisions

Exercises and examples are adapted to each cohort's sectors and roles.

What you take back to work

  1. Project system boundary statement template
  2. Stakeholder and interface mapping template
  3. Causal loop diagram model
  4. System archetype diagnostic checklist
  5. Systems-informed project controls plan
  6. Project systems intervention plan

Who should attend

  • Project Managers — manage dependencies that conventional plans do not reveal
  • Programme Managers — coordinate interacting projects, workstreams and strategic outcomes
  • PMO Managers — improve governance, assurance and portfolio reporting methods
  • Project Sponsors — test proposed decisions for wider delivery consequences
  • Business Analysts — structure ambiguous problems involving multiple stakeholder groups
  • Operations Managers — manage projects that alter processes, capacity and service performance

Skills and tools covered

Systems mappingCausal loop modellingStakeholder analysisComplexity diagnosisFeedback analysisIntervention planning

Tools and standards

ISO 21502, Causal Loop Diagrams, Soft Systems Methodology, Cynefin Framework

How the course runs

Training methodology

The course uses short instructor briefings to introduce each method, followed by facilitated case analysis, group mapping and structured simulations. Participants work with realistic project scenarios involving competing stakeholders, delayed information and changing constraints. Individual application planning links the methods to a current or recent project. Trainers review diagrams, assumptions and proposed interventions using peer critique and practical questioning. Classroom delivery is available in more than 50 cities, with the same instructor-led format also offered live online.

Requirements and prerequisites

Participants should have practical experience working on projects, programmes, operational change or major workstreams. They should understand familiar project concepts such as scope, schedule, cost, risk, stakeholders, governance and change control. Experience with a current or recent project is useful because course methods are applied to realistic delivery situations. No previous study of systems thinking, system dynamics, mathematics, coding or specialist modelling software is required. This is not an introductory project management course; participants should already be comfortable discussing project plans and delivery decisions.

A typical training day

08:30 – 10:30First session
10:30 – 10:45Refreshment break
10:45 – 12:30Second session
12:30 – 13:30Lunch and networking
13:30 – 15:00Third session
15:00 – 15:15Refreshment break
15:15 – 16:30Workshop and daily review

Live online deliveries follow the same structure in East Africa Time, with shorter screen blocks and longer breaks.

What the fee includes

  • Instruction by a practitioner facilitator
  • Full course workbook and materials
  • Exercise files, templates and case studies
  • Refreshments and lunch on classroom deliveries
  • Certificate of completion
  • Post-course application plan

Frequently asked questions

You should have experience working on projects, programmes or operational change and understand core project management terms. No prior systems thinking, modelling, coding or advanced mathematics experience is needed.

Bring details of a current or recent project with meaningful dependencies, stakeholder issues or delivery pressures. You do not need confidential documents; an anonymised description, plan or risk summary is sufficient.

It is best suited to project managers, programme managers, PMO professionals, business analysts, sponsors and operations managers. It is particularly relevant where work crosses teams, suppliers, technologies or organisational boundaries.

Standard project management courses focus primarily on planning, scheduling, cost, risk and control processes. This course examines the relationships and feedback effects that shape whether those processes produce the intended results.

Participants can use the templates to investigate a delayed project, recurring rework, stakeholder resistance, capacity constraints or weak benefit adoption. The methods can also support governance reviews, risk workshops and recovery planning.

Each day runs from 08:30 to 16:30 and provides about 6.5 contact hours. The first week establishes core systems methods and develops an initial project analysis; the second week applies deeper modelling, intervention design, controls and the capstone presentation.

Questions about this course?

Ask about dates, fees, group bookings or running it for your team. Our training team replies by email.