Why Agile Teams Collapse Easily: The Hidden Saboteur Playbook

Agile Saboteur Handbook

Building an agile team is hard, but destroying its agility is easy because agility relies on efficiency and delivering real customer value. This article adapts William J. Donovan’s “Simple Sabotage Field Manual” to software teams, offering practical “saboteur” tactics that undermine agility and how to avoid them.

Agile stems from mutual learning

Agile skills are largely acquired through interaction with peers and community participation; learning to get along with people is the foundation of true agility.

First tactic – Ask the supervisor for everything

Blindly following every rule and seeking approval stifles initiative; sometimes breaking rules is necessary for rapid iteration and feedback.

Supervisor’s attitude shapes the team

A fair, trustworthy leader fosters self‑organization and collective ownership, while an unjust supervisor creates a “compliant saboteur” culture.

Detecting team tendencies

Use a simple questionnaire to classify members as “compliant” or “violators”, visualizing the distribution with a normal‑curve chart.

Balance between compliance and violation

Teams that lean too far toward compliance lose agility; the optimal point lies where shared values enable autonomous decision‑making.

Efficiency is the heart of agility

Any practice that reduces efficiency—such as over‑building features no customer needs—directly sabotages agile outcomes.

Give customers only what they need

Focus on “just enough” functionality and apply iterative refinement (e.g., the SLIP principle) instead of delivering overly complex solutions.

References

William J. Donovan, “Simple Sabotage Field Manual” (1944)

“Who Is Sabotaging the Team?” by Robert M. Gelfort, Bob Frechette, Kerry Green

John Maeda, “The Laws of Simplicity”