Why Cross-Functional Work Gets Stuck at “Everyone Agrees, Nobody Moves”
A game theory and collaboration article on fake consensus, incentives, and why cross-functional work stalls after apparently aligned meetings.
There is a version of alignment that looks good in the room and means almost nothing outside it. Everyone says yes. Everyone nods. The meeting ends with apparent support. Then nothing actually starts. People usually explain this by saying another team is slow, political, or uncommitted. Sometimes that is true. But a lot of the time the real issue is simpler: agreement was cheap and execution was not.
Cross-functional work stalls when the payoff structure is misaligned. Sales wants speed. Product wants coherence. Engineering wants risk contained. Leadership wants visible progress. Those goals can overlap, but they do not produce identical incentives. If the shared plan gives one team downside without a believable upside, passive delay becomes a rational move.
This is where a game theory lens becomes useful, not because people are calculating in some cold abstract way, but because organizations constantly create small strategic situations. Who owns the failure if this slips? Who gives up capacity first? Who gets blamed for quality? Who gets credit if it works? Unless those answers are made explicit, “support” often means little more than “I am not objecting right now.”
That is why fake consensus is so common in cross-functional work. Opposition is expensive in the meeting, so people hold back. Commitment becomes expensive after the meeting, so people slow down. The gap between public agreement and private movement is not hypocrisy as much as structure.
When I am trying to unstick something like this, I stop asking whether people are aligned in principle. I start asking what is verifiable. What exactly is each side giving? What cost are they absorbing? What handoff proves movement? What deadline creates real exposure if no one acts? Those questions sound operational, but they are really about incentives.
This is also one of the better uses for Team Sandbox. If you model the event clearly enough, the interesting part is not whether the system predicts perfect outcomes. It is whether it helps surface the likely hesitation points before they become narrative problems like “they are not collaborative.” Sometimes the moment a project becomes legible as a strategic interaction, people stop moralizing and start designing better commitments.
Cross-functional progress rarely comes from better intentions alone. It comes from building a structure where movement is easier than delay.