Liaison Program
The liaison program addressed the fundamental limitation of the team of teams model: trust within small units was organic (built through training and shared operations), but trust between units was absent. Without inter-unit trust, shared consciousness became surveillance and coordination became conflict. The liaison program embedded a member of one unit — a SEAL, a Ranger, an intelligence analyst — inside a different unit for rotations of three to six months. The embedded member participated fully in the host unit's work, shared their operational rhythm, learned their culture, and developed personal relationships with people they would later need to trust across organizational boundaries. When the liaison returned to their original unit, they carried human knowledge: I know how signals intelligence works because I watched it happen. I trust their analysts because I worked alongside them. The knowledge was not abstract or policy-derived; it was experiential, built through presence and participation. The program was expensive — pulling skilled operators out of direct operational roles to serve as bridges between units — and indispensable, because it was the only mechanism that reliably built the trust the network required.
In the AI Story
The program's structure was deliberate: rotations long enough to build genuine relationships (three months minimum), participation deep enough to produce shared vulnerability (the liaison was not an observer but a contributor), and rotations numerous enough to create a network of personal connections across the entire Task Force. By 2008, virtually every unit had hosted a liaison from another unit and had sent a liaison outward. The network of personal relationships that resulted was JSOC's true organizational chart — not the formal reporting lines but the map of who trusted whom, built one rotation at a time.
The liaison's role was translation as much as relationship-building. The SEAL who rotated into a signals intelligence unit returned to his team able to translate intercepted communications into operational context his team could use — not because he had become an intelligence analyst but because he understood the analysts' methods, constraints, and interpretive frameworks. The translation was bidirectional: the SEAL also translated his team's operational needs into questions the analysts could answer, closing the loop between intelligence collection and operational application. The liaison was a human API, converting requests and responses between units that spoke different professional languages.
For AI-augmented organizations, the liaison principle addresses the trust-atrophy problem: when AI tools reduce the operational necessity for cross-functional collaboration, the incidental trust-building that collaboration provided must be replaced with deliberate trust-building. The mechanism is immersion: a backend engineer spending two weeks inside the design team's process, not because the work requires it but because the culture requires it. A product manager coding alongside an engineer for a sprint, not to become a coder but to understand viscerally what the engineer's work feels like from the inside. The immersions are expensive, they reduce short-term productivity, and they are — by McChrystal's framework — the only reliable mechanism for building the trust that makes autonomous coordination possible.
Origin
The liaison concept was not new; military organizations have used liaison officers for centuries to coordinate between allied forces. McChrystal's innovation was scale and depth: turning liaison from an occasional coordination role into a systematic, mandatory, trust-building practice that every unit participated in continuously. The program was formalized around 2005, after early experiments demonstrated that units with embedded liaisons coordinated more effectively than units relying on formal communication channels.
McChrystal has credited the program's effectiveness to its requirement of genuine participation. A liaison who merely observed did not build trust; observation created the appearance of involvement without the substance. The liaison had to do the work of the host unit — participate in their operations, share their risks, experience their successes and failures — because trust is built through shared consequence, not shared space.
Key Ideas
Trust is built through shared experience under consequence. Abstract familiarity does not produce operational trust; participation in situations where reliability matters does.
Rotations must be long enough to matter. Three months minimum; shorter rotations do not allow relationships to develop past professional courtesy into genuine mutual knowledge.
The liaison translates, not just transmits. The embedded member learns the host unit's language, methods, and constraints well enough to interpret between units that would otherwise miscommunicate.
Personal trust scales through movement. As liaisons rotate and return, they carry relationships with them; the network of personal connections emerges organically from individual movements.
The investment is invisible until tested. Liaison programs look like overhead — pulling productive people out of direct work — until the first crisis reveals that coordination works because the relationships exist.
Appears in the Orange Pill Cycle
Further reading
- McChrystal et al., Team of Teams, Chapter 10
- Ronald Burt, Structural Holes (Harvard University Press, 1992)
- Mark Granovetter, 'The Strength of Weak Ties,' American Journal of Sociology (1973)
- Etienne Wenger, Communities of Practice (Cambridge, 1998)
- J. Richard Hackman, Leading Teams (Harvard Business Review Press, 2002)