Understanding Complexity at the Heart of Human Systems
Understanding Complexity at the Heart of Human Systems.
The previous article introduced the Golden Triangle: People, Process and Technology.
Three dimensions that together shape every knowledge-intensive human system.
Over the years, however, I reached a conclusion that completely changed the way I understand leadership.
Although these three dimensions are deeply connected, they do not represent the same kind of complexity.
Processes can be designed.
Technology can be engineered.
But people…
People must be understood.
Because processes do not learn.
Technology does not learn.
People do.
And when people collaborate over time, they stop behaving as isolated individuals.
They become a human system.
A living system.
One that continuously learns, adapts and evolves.
The complexity we usually ignore
When we try to understand a team, we usually begin by observing what is easiest to measure.
Velocity.
Lead Time.
Cycle Time.
KPIs.
Dashboards.
Incidents.
Defects.
All of these are useful.
But they only describe the visible behaviour of the system.
Beneath those indicators lies another reality.
One that is considerably harder to observe.
- Trust
- Motivation
- Shared Knowledge
- Psychological Safety
- Relationships
- Learning Capacity
- Purpose
- Confidence
- Experience
These variables rarely appear on a dashboard.
Yet they have a greater influence on the future of the system than almost anything else.
They shape how people collaborate.
How knowledge is shared.
How decisions are made.
How technology evolves.
How processes mature.
And ultimately, how much value the team is capable of creating over time.
Perhaps the most important of all is motivation.
Not understood as a temporary emotional state.
But as the energy that keeps a human system moving through time.
A motivated system learns faster.
Shares knowledge more naturally.
Absorbs uncertainty with greater resilience.
And becomes progressively more capable of adapting to change.
When these variables deteriorate, organisations often respond by introducing new methodologies, new tools or new processes.
Sometimes those changes help.
Sometimes they simply treat the symptoms.
Not the real cause.
Understanding what cannot easily be measured is often far more important than optimising what can.
Nothing stays the same
Perhaps the biggest mistake we make as leaders is assuming that a team remains in the same state over time.
Reality is very different.
People change.
Products change.
Technology changes.
Business priorities change.
Knowledge changes.
Relationships change.
Motivation changes.
Even the interactions between all these dimensions evolve continuously.
This means that two apparently similar teams may require completely different decisions.
And the same team may require different leadership approaches depending on the moment it is experiencing.
Understanding this variability is far more valuable than searching for a universal methodology.
Because what worked six months ago may no longer be the right answer today.
Not because the practice was wrong.
But because the situation has changed.
There are no universal solutions.
There are only different situations.
And every situation deserves to be understood before we decide how to intervene.
Evolving also means knowing when to change
Every organisation needs change.
Teams evolve.
Products evolve.
Technology evolves.
Markets evolve.
Standing still is rarely an option.
But introducing change is not only about deciding what should change.
It is equally about understanding when to introduce that change.
And just as importantly…
How to introduce it so the system is capable of absorbing it.
The same intervention can strengthen a team.
Or destabilise it.
The same idea can accelerate learning.
Or create resistance, frustration and uncertainty.
Not because the idea itself is good or bad.
But because it arrived at a different moment in the evolution of the system.
For this reason, I increasingly see change not as a project, but as the consequence of observation.
Observe.
Understand.
Recognise the current situation.
Choose the right moment.
Intervene.
Observe again.
The quality of an intervention depends not only on the solution itself.
It also depends on the moment in which it is introduced.
However, not every organisation has the luxury of waiting for the perfect moment.
Business priorities change.
Markets evolve.
Regulations appear.
Technology forces transformation.
Sometimes change is simply unavoidable.
In those situations, SAMM does not attempt to delay change.
Its purpose is different.
It helps us understand the current state of the system before intervening, allowing us to anticipate where change will be naturally absorbed, where resistance is likely to emerge and what consequences that intervention may produce.
Because even when change is inevitable, understanding the situation allows us to introduce it with greater awareness and minimise unnecessary disruption.
Observation requires a common language
One of the biggest misconceptions about SAMM is believing that it replaces existing methodologies.
It does not.
In fact, I believe every human system needs a common foundation from which it can evolve.
A shared language.
A minimum framework.
Common principles.
Regular feedback loops.
A consistent way of working.
Not because the framework itself is the answer.
But because it makes the system observable.
Without a common reference it becomes extremely difficult to distinguish between normal variability and meaningful change.
Without observability there is no shared understanding.
Without shared understanding there is no meaningful learning.
Frameworks such as Scrum, Kanban, XP or Lean should not be seen as universal solutions.
They provide something equally valuable.
A stable baseline from which the behaviour of the system can be observed, understood and continuously improved.
Methodologies therefore are not the destination.
They are the starting point.
They make the system visible.
Only then can Situational Awareness begin.
Evolution instead of optimisation
We often talk about optimising teams.
I increasingly prefer another word.
Evolution.
Great teams are not created because they adopt the perfect methodology.
They emerge because they continuously learn.
They share knowledge.
They develop trust.
They understand the product.
They maintain curiosity.
They adapt without losing cohesion.
Over time, knowledge stops belonging to individuals.
It becomes a property of the system itself.
The team develops a shared language.
Shared intuition.
Better judgement.
And gradually, it becomes increasingly capable of dealing with complexity.
The ultimate goal is not simply to make better decisions today.
It is to increase the system’s ability to make better decisions tomorrow.
Because sustainable systems do not depend on exceptional leaders.
They progressively learn to understand themselves.
To recognise the challenges they are facing.
To identify their own strengths and limitations.
To understand when they need structure.
When they need autonomy.
When they need stability.
And when they are ready for change.
That, to me, is the real meaning of organisational maturity.
Not eliminating uncertainty.
But developing the collective capability to evolve through it.
True sustainability is not about preserving a process.
It is not about protecting a methodology.
It is about preserving the system’s ability to continue learning while everything around it keeps changing.
The purpose of SAMM
The Situational Awareness Management Model is built on a simple assumption.
Human systems continuously evolve.
Therefore, management decisions cannot remain static.
Every intervention should begin with understanding the situation the system is experiencing.
Not because SAMM tries to eliminate complexity.
Quite the opposite.
Complexity is a natural property of every human system.
The purpose of SAMM is to help leaders—and ultimately the systems themselves—develop the ability to observe, understand and respond to that complexity consciously.
Not by optimising People, Process or Technology independently.
But by understanding how these dimensions continuously interact throughout the life of the system.
SAMM emerged from years of leading software engineering teams.
However, its principles extend far beyond software.
Any knowledge-intensive organisation where people collaborate to solve complex problems faces the same challenge.
Not building better processes.
Not adopting better tools.
But continuously helping the system evolve while the world around it keeps changing.
Because before changing a process…
Before introducing a new framework…
Before redesigning a technology…
Before reorganising a team…
There is always one question that matters more than any other.
What situation is this system experiencing right now?
Everything else begins there.
Next
In the next article we will explore why no human system can evolve unless it first becomes observable.
Because before understanding a situation…
We first need to make the system visible.
Only then can observation become knowledge.
And only then can knowledge become evolution.