Module 03 · 14 min

The Dimensions of Complexity

Complicated is knowable. Complex is not.

What complexity actually means in organisational, project and information-systems terms, and why the distinction from 'complicated' changes how you manage.

Organisational complexity

Organisational complexity is associated with the intricate inter-relationships of individuals, of individuals with artefacts such as IT and with ideas, and with the effects of interactions within the organisation as well as between institutions within a social eco-system. complexity arises through connectivity and processes of feedback and emergence.

Eve Mitleton-Kelly, complexity Research Programme, London School of Economics

Project complexity

Baccarini's classic analysis sets out why complexity is not a footnote to project management but a determinant of almost every management choice you make:

  • It determines planning, coordination and control requirements.
  • It hinders clear identification of goals and objectives.
  • It drives the choice of project organisational form.
  • It sets the expertise and experience requirements of the management team.
  • It shapes the procurement arrangement you should select.
  • It affects time, cost and quality directly — broadly, the higher the complexity, the greater the time and cost.

complexity is the enemy in software; inherent complexity in software rises exponentially.

Fred Brooks, 1987

The tensions inside information-systems change

IS projects are intrinsically uncertain. The management complexity arises from the necessity to deal simultaneously with several tensions.

Roger Elvin, Cranfield School of Management
  • Innovation versus risk
  • Learning versus control
  • Organisational change to deliver benefit versus stakeholder resistance to that change
  • Multiple stakeholder perceptions of the project's purpose
  • Delivering value versus satisfying time, quality and cost targets
  • Managing the detail and the big picture at once

Modern delivery has added its own tensions: cloud vendor roadmaps you do not control, SaaS release cycles that change the product underneath you, data protection and AI governance obligations, and legacy systems nobody fully understands any more.

Complicated versus complex

Technically complex projects are complex because of the human aspects and not the technical intricacies, which are just complicated.

Thomas Docker, citi, 2008

Key takeaways

  • complexity arises from connectivity, feedback and emergence — not from technical difficulty.
  • complexity determines the management approach, the procurement route and the people you need.
  • You can analyse your way through complicated. You cannot analyse your way through complex.

Take it back to work

  • Is your current programme complicated, complex, or both — and which parts are which?
Share thisLinkedIn