Mutual Trust as an Organizational Capability

Definition

Mutual trust in the adVANTAGE model is inter-organizational trust: the assumption that a client and contractor, both serving their own legitimate business interests, will fundamentally act fairly toward each other and prioritize the shared goal of a successful project over short-term individual advantage. This is not romantic faith in human goodness; it is a rational recognition that long-term cooperation benefits both parties more than tactical deception. It is enabled by transparent structures (like shared pain) that make deception costly and honesty rewarding.

In the Book

The authors acknowledge that trust between legally and economically independent organizations might seem impossible. Yet they argue that organizations consist of people, and people do develop trust through repeated interaction, shared vocabulary, and shared success. More critically, they argue that the absence of trust signals a deeper incompatibility: if both parties fundamentally doubt each other's fairness, they should not enter an agile contract relationship at all.

The book illustrates why trust is essential by describing a specific example: the Definition of Done (DoD). In traditional contracts, the DoD is specified exhaustively upfront (feature X is "done" when it has property A, property B, property C, property D...). adVANTAGE deliberately leaves the DoD open to some degree, requiring judgment at the end of each sprint. This is intentional: the authors argue that any exhaustively detailed DoD is "diametrically opposite to the agile philosophy" because it pretends certainty can be algorithmic when the reality is context-dependent and judgment-based. But this openness only works if client and contractor trust each other to judge fairly. If there is any suspicion that one side will exploit the ambiguity to claim work is incomplete (to delay payment) or complete (to skip quality), the relationship is broken.

The book lists reasons both sides could distrust each other: clients fear contractors will deploy second-rate developers, implement features minimally without generating business value, or optimize capacity utilization even while accepting price risk. Contractors fear clients will stall approval to get more performance, stuff functionality into vaguely defined features, or delay acceptance procedures. All of these have happened and could happen again. Yet the authors argue that such distrust is shortsighted: the closer and longer a client-supplier relationship is, the more efficient both parties become (shared understanding, shared vocabulary, shared learning). Deception harms that efficiency; honesty and transparency improve it. Over time, teams that work together repeatedly develop shared context that makes misunderstandings less likely.

Why It Matters

Mutual trust as a capability matters because it is the constraint that determines whether agile contracts can work at all. All the structures (shared pain, interactive scoping, two daily rates) assume that people will use them honestly. If the client culture is inherently adversarial—assume the contractor is trying to cheat, scrutinize every decision, escalate disagreements to legal—then adVANTAGE fails. If the contractor culture is inherently risk-averse—assume the client will exploit ambiguity, document every conversation, protect margin above partnership—then adVANTAGE fails. The book's insight is that trust is not a nice-to-have; it is a prerequisite that must be assessed before entering the contract. A project leader can ask: "Do both sides' cultures actually align with the assumptions in this model?" If the answer is no, a different contract model should be chosen.