You built the cross-functional team on purpose. Sales, operations, product, finance — the people who together can actually move the thing. On paper it is the strongest group in the building.
Then it stalls. Decisions take three meetings. Work bounces back for rework. Two functions quietly blame each other in the hallway. And you start to wonder whether you put the wrong people in the room.
You did not. The people are fine. They each perform inside their own function. What broke is the hand-off — the moment information has to cross from one function to the next, under pressure, where nobody is watching. Cross-functional team challenges are almost never people problems. They are hand-off problems wearing a people costume.
Why the Same People Work Fine Apart and Break Together
Inside one function, information barely has to move. Everyone shares the same context, the same shorthand, the same idea of what "done" looks like. A handoff between two people who sit together costs nothing.
Now add a boundary. Sales hands a deal to operations. Operations hands a build to product. Product hands a number to finance. Every boundary is a place where context can fall out. The person sending it assumes the next group already knows the part that lives in their head. The person receiving it assumes the gap was left out on purpose, not by accident.
Multiply that across four or five functions and you do not have a people problem. You have five boundaries where information has to survive a hand-off, and under any real pressure, at least one of them leaks. The team looks dysfunctional. What is actually happening is that the work keeps arriving with the context stripped off.
The Three Places Cross-Functional Teams Break
Almost every cross-functional team challenge traces to one of three hand-off failures. Once you can name them, you stop blaming people and start fixing the pattern.
The context drop. Work moves to the next function with the facts but not the context — why it matters, what is at stake, who it affects. People do not act on raw information. They act on context. A brief that made perfect sense to the person who wrote it makes no sense to the person who received it. The tell is the phrase "I didn't know that mattered," said three weeks too late.
The silent assumption. Two functions each assume the other owns a piece of the work, so nobody does. Or each assumes the other already knows something, so nobody says it. The gap is invisible until a deadline lands on it. Nobody lied and nobody slacked. The information simply never crossed the boundary, because both sides thought it already had.
The buried disagreement. Two functions disagree on direction and, rather than fight it out in the room, they go quiet and route around each other. The disagreement does not disappear. It moves underground and shows up later as rework, missed dates, and a hallway feud you only hear about secondhand.
None of the three is a character flaw. Each one is a hand-off that dropped something. And each one is fixable — once the team can see exactly where it happened.
Why You Cannot Fix This in a Meeting
Here is the trap. You feel the friction, so you call a meeting about collaboration. Everyone agrees to communicate better, share more, align earlier. The list goes on a slide. Everyone nods.
Three weeks later the hand-offs break in exactly the same places. Because a calm meeting cannot show you where they break. People describe how they think information moves, not how it actually moves when the deadline is tomorrow and three functions want different things. The breaks only appear under pressure, and a planning meeting has none.
This is the same gap that makes most diagnostics lie. A survey or a calm conversation measures how the team feels on a quiet Tuesday, not what it does when the stakes are live. If you want a read you can trust, you have to check the hand-offs in conditions where the truth can show up — which is exactly the logic behind a behavior-based team health check template rather than an opinion survey.
So the meeting is not useless. It is just blind. To fix a hand-off you have to see it break.
Surface the Breaks in Real Time
The fastest way to find where a cross-functional team breaks is to put it under enough pressure that the hand-offs fail in front of everyone — in a contained setting where a failure costs nothing real.
That is what an immersive simulation does. In the Save the Titanic experience, a mixed team becomes the senior officers on the ship in the minutes after the iceberg strikes. Different officers hold different information. None of them has the full picture alone. They have limited time, limited resources, and 2,200 lives on the line. To survive, information has to move across every silo, fast and with context intact.
It rarely does on the first try. One officer holds a fact that another desperately needs and never passes it. Two assume someone else is handling the boats. A disagreement about which deck to clear goes quiet and the team routes around it. Every hand-off failure you see at work shows up here in three and a half hours — except here it is visible, because the clock makes the cost immediate. This is why a cross-functional read works so well under pressure: the simulation is built to make information cross boundaries or fail trying. For teams whose whole challenge is the space between functions, Bridge the Gap runs the same pressure test pointed straight at the silos.
Then you debrief, while the memory is still hot. The team sees the exact moment context dropped, the exact assumption that went unspoken, the exact disagreement that went underground. Not a vague "we should communicate better." A specific, named hand-off the team can rebuild on purpose.
Fix the Pattern, Not the Blame
The point of seeing the break is not to find who dropped the ball. It is to fix the hand-off so it stops dropping.
When a team watches its own information fail to cross a boundary, the conversation changes. It stops being "operations is slow" or "sales overpromises" and becomes "we lose context at the sales-to-operations hand-off, and here is the one we just watched fail." That is a pattern you can fix. Blame is not. Build a simple rule for every hand-off — what is done, what is not done, and what the next function needs to know — and the silent assumptions and context drops have nowhere to hide.
This is the difference between fixing people and fixing conditions. You cannot make functions like each other more. You can make the hand-off between them carry the context it needs. Do that and the same team that looked dysfunctional last quarter starts to move, because the information finally survives the trip.
The results are real when the hand-offs hold. When ArcelorMittal ran 710 leaders through the experience in partnership with Duke Corporate Education, cross-functional decisions came out 30 to 40% faster — not because the people changed, and because the information finally moved across the boundaries that had been dropping it. Bell MTS moved from $800 million toward $1.4 billion in revenue in a single year on the back of teams that stopped working in silos and started sharing what they each knew.
If you want to see exactly where your own cross-functional team breaks — the hand-off that keeps dropping context, the assumption nobody says out loud — watch how the Save the Titanic experience works. You will see the breaks in real time, fix the pattern instead of the blame, and stop being surprised by a team that was strong all along.
Read next: A Team Health Check Template That Measures Behavior, Not Opinions