Viable System
Why Projects Fail Quietly: The Hidden System That Shapes Delivery Excellence
1. Introducing the Disturbance At first glance, high-performing project delivery seems like a matter of planning, discipline, and execution. Yet anyone who has worked inside a real project…
1. Introducing the Disturbance
At first glance, high-performing project delivery seems like a matter of planning, discipline, and execution. Yet anyone who has worked inside a real project environment knows the deeper truth: success or failure is shaped less by plans and more by the patterns of interaction between people: how they interpret information, coordinate decisions, and adapt when reality pushes back.
A project team can have clear objectives, solid methodology, and strong sponsorship, and still stall. And when it does, the cause is rarely incompetence or lack of effort. More often, it is the system itself trying to maintain equilibrium in the face of competing expectations, unclear communication, and ambiguous regulation (unclear mechanisms for sensing what’s happening, interpreting what it means, and coordinating who adjusts in response).
Team dynamics are not a soft layer around the work. They are the work. They determine how information flows, how decisions are made, and how teams absorb disturbance without fragmenting.
To understand project delivery excellence, we need to understand the human system doing the delivering.
2. The System Beneath the Surface
Let’s start by challenging a common assumption:
Teams fail because individuals fail.
In practice, this is almost never true. What actually fails is the coordination function: the set of interactions through which people interpret information, update their assumptions, and align their decisions.
In cybernetic terms, a project team is a self-regulating control system. Every conversation, decision, and meeting is a feedback signal attempting to maintain coherence in the work. When those signals become distorted, unclear requirements, inconsistent leadership priorities, or delayed feedback, the system loses the ability to regulate itself. It drifts into noise: chaos.
Under stress, teams shift from collaboration to self-preservation. From shared priorities to local priorities. From learning to defensiveness. All of this happens quietly, often unnoticed, because the team is doing what every system does when equilibrium is threatened: it protects its internal stability, even if that stability undermines the project.
This is not a moral problem. It’s a structural one.
3. Reframing the Problem: What Looks Like Failure Is Misaligned Equilibrium
Most “team issues” in projects, communication gaps, silos, unclear ownership, passive leadership, are not personality problems. They are symptoms of a system not in equilibrium.
Imagine a system with three equilibrium forces:
- Delivery rhythm, timelines, tasks, execution
- Human rhythm, cognition, emotion, uncertainty
- Organizational rhythm, shifting priorities, political pressures, resource tensions
When these rhythms fall out of sync, teams stop acting like integrated units and start acting like loosely connected clusters of effort. Alignment becomes episodic. Communication becomes transactional. Decisions become reactive.
What looks like conflict is actually feedback.
What looks like resistance is a sign the system is trying to rebalance itself.
Project delivery excellence is not the absence of disturbance; it is the ability to absorb and learn from disturbance faster than it accumulates.
4. The Principle: Communication Is Control
In any system, control is achieved through information flow. When communication breaks down, the system loses its ability to regulate itself, not because people stop caring, but because the feedback mechanism can no longer detect and correct error.
To understand team dynamics, we need to observe how communication operates inside a system. Not the formal communication, the slide decks, updates, or reports, but the real communication:
- What gets said
- What gets withheld
- What gets misunderstood
- What gets distorted
- What gets avoided
- What gets repeated because it wasn’t understood the first time
Every organization has a built-in drive toward equilibrium, and communication is the mechanism through which this equilibrium is maintained. When information flows freely, the system adapts. When information becomes constrained, it collapses into rigidity.
In project environments, three distortions are most common:
- Ambiguous feedback: People assume others understand. They rarely do.
- Delayed feedback: Issues surface late, when they’ve already metastasized.
- Filtered feedback: Team members hide discomfort to avoid conflict, looking incompetent, or slowing the group down.
These distortions are not failures of professionalism; they are predictable patterns in human systems under pressure. In cybernetic terms, the feedback loop loses sensitivity. It cannot detect errors early enough to correct course. The system becomes low-resolution. It can detect only catastrophic signals, by which point, correction is expensive or impossible. High-performing teams maintain high-resolution feedback, detecting micro-disturbances before they amplify.
Project delivery excellence requires a feedback system capable of sensing reality in real time.
5. Application: Designing Teams That Learn Faster Than They Fail
To restore equilibrium, teams must increase their requisite variety, the ability to respond to the variety of challenges they face. This means introducing structures that amplify learning, reduce distortion, and support adaptation.
Below are practices not as techniques, but as control functions that improve system behaviour.
A. Establish clarity before coordination
Most projects enter execution while essential questions remain unexamined:
- What assumptions are we making about the other team’s priorities?
- What information is considered critical versus optional?
- How will we handle ambiguity when it arises (because it will)?
When leaders focus only on behaviour, they miss the structure generating it. Clarity is structural, it shapes every downstream interaction. Without shared clarity, coordination becomes guesswork.
B. Build communication loops, not communication events
Status meetings, dashboards, and reports create events of communication, but high-performing teams rely on loops**,** ongoing cycles of inquiry, feedback, and adjustment.
A (cybernetics) loop looks like this:
- Signal emerges: New information, concern, or risk
- Team interprets: What does this mean for the work?
- Team adapts: Change course based on the meaning
- Team confirms: Did the adjustment work?
This is how a learning system behaves. It doesn’t just communicate; it recalibrates.
C. Translate across cognitive worlds
Technical teams and business teams live in different cognitive environments. They process risk differently. They use different models to interpret complexity. They work with different forms of uncertainty.
When translation is missing, misunderstanding is guaranteed.
Translation is not dumbing down. It is bridging models of thinking so people can make decisions using the same mental map.
D. Reduce distortion at the executive level
Projects collapse when executives receive filtered data. When reports become overly curated, overly optimistic, or overly sanitized, they stop informing and start deceiving, not maliciously, but structurally.
A leadership team that receives distorted information makes distorted decisions.
Restoring fidelity at the top is often the most critical intervention for restoring equilibrium across the entire project system.
E. Create psychological slack
In tightly scheduled projects, people hide problems because they are afraid of becoming the problem.
When the system has no slack, it cannot learn. It can only react.
Psychological slack, permission to express uncertainty, doubt, or incomplete understanding, becomes a structural requirement for accuracy. It increases the sensitivity of the feedback loop.
Without slack, truth becomes dangerous; and when truth becomes dangerous, performance becomes theatre.
6. Reflective Closing
What this means for leaders is simple but not easy: align awareness before you align action: ensuring the team shares not just goals, but a common understanding of the system they are operating within, its constraints, its feedback loops, its signals of disturbance.
Team dynamics are not interpersonal issues to be managed; they are control functions of a living system navigating uncertainty. When teams learn to sense their own signals, the subtle shifts in language, behaviour, and energy, they naturally restore equilibrium.
Project delivery excellence doesn’t begin with tools, governance, or methodology.
It begins with how the system learns.
Because in any human system, the rate of learning ultimately determines the rate of success.