Cross-Functional Coordination Capacity

In The You On AI Field Guide

These cross-functional relationships were the target of Prahalad's critique of the SBU structure. The Strategic Business Unit fragmented organizations into silos that optimized locally at the expense of cross-functional integration. Headcount reduction does the same thing, but more destructively — it does not merely discourage cross-functional coordination; it severs the specific personal relationships through which coordination occurs.

The mechanism is personal. The engineer in backend systems who has spent three years building a working relationship with the designer in UX — learning her vocabulary, understanding her priorities, developing the mutual trust that enables quick conflict resolution — embodies a piece of the organization's cross-functional capacity. Remove either one, and the capacity is gone. Not degraded. Gone. The replacement hire, however individually skilled, begins from zero in building the cross-functional relationships that effective coordination requires.

The AI age amplifies the value of cross-functional coordination because the dimensional multiplier dissolves specialty boundaries. When a backend engineer can build user interfaces and a designer can write production code, the coordination between them becomes even more consequential — and more dependent on relationships that predate the AI transition. The organization that severs these relationships has eliminated the scaffolding on which AI-augmented cross-functional work depends.

Origin

The concept applies Prahalad's observations about Japanese corporate structure — where lifetime employment and rotational assignments deliberately built cross-functional relationships — to explain the specific vulnerability of AI-augmented organizations to coordination collapse.

Key Ideas

Relationship-based, not process-based. Coordination depends on personal relationships that process documentation cannot substitute for.

Years of accumulation. The mutual understanding that enables rapid coordination takes sustained working together to build.

Binary loss. The capacity is destroyed by removal of either side of the relationship — it does not degrade gradually.

SBU pathology generalized. Headcount reduction produces the same fragmentation the SBU structure produces.

AI amplifies the stakes. Dissolving specialty boundaries makes cross-functional relationships more consequential, not less.