Team Cohesion and Organizational Silos: One Team Inside the Walls
This page draws on a change engagement inside one of the largest business units of an international research and advisory business. Nine product and technology teams made up that unit, and its revenue ran to hundreds of millions of dollars annually, with doubling it as the goal. Evidence came first: we put twenty-five dimensions of the organisation to a scored question set and ran a qualitative pass beside it for what the scoring could not reach.
The analysis started with the map.
Start with the map
Correlation, not causation: every edge is a measured statistical association (p<0.05) from this engagement, not an asserted cause. Edges below |r|=0.35 are omitted for legibility; the rest are drawn thicker and more opaque the stronger they are. The map stays focused on Team alignment: hover any dimension to preview its own connections against it, and use the strength slider to keep only its strongest links.
The map opens centred on one team: whether the organisation behaves like a single team or a federation of them. Its two closest neighbours are smooth flow of work and obstacle removal, the dimensions that live in the spaces between teams. That’s the tell worth keeping: cohesion isn’t correlated here with culture or morale dimensions. It’s correlated with whether work and blockers can cross a boundary.
What the numbers said
Scores centre on 8 out of 10, and seven of the sixty-one respondents put it at 4 or below. A healthy-looking dimension, and here the words don’t simply contradict the score. They qualify it, precisely: the phrase “one team” was true at exactly the scale the question asked about.
What the words said
The two dark blobs not lining up is the chart.
Mixed is the honest verdict: sixteen coded mentions, nine sore and six positive. And the split has a geography. Inside the walls:
“But I do think that the individual teams embody the ‘one team’ mindset which is great to see.”
Then the same survey stream, in the next breath:
“However, I don’t know how well the teams are embodying ‘one team’. It sometimes feels very difficult to get the teams to work together on certain projects.”
And the boundary isn’t only between delivery teams, it runs vertically, between delivery and the business:
“Lack of participating from the business in joining standup, retrospectives, etc.”
“2 different organizations, 2 different leaders, although we’re aligned directionally, on the ground their goals are organization-wide goals and this doesn’t always coincide with team-based goals.”
Every team was one team. The teams together weren’t. The score measured the first thing; the work depends on the second.
Where it lived
Nine teams, anonymised, best to worst. Thin rows render wider and flatter; less data looks uncertain, not falsely precise.
Ranked, the nine team medians put seven at 7 or above, up to 9, with the last two down at 5.5. Read against the words, the shape fits: cohesion is strong where a team’s work stays inside its own walls, and weakest for the teams whose daily work depends on crossing them.
What “one team” turned out to be entangled with
The neighbourhood as measured:
- Smooth flow of work (r = .70), the strongest pull
- Risk and obstacle removal (r = .66)
- Product intake (r = .66)
All three are boundary dimensions: how work moves between teams, how blockers get cleared across them, how work enters at the front door. Where the units describe togetherness, the work flows; where they describe two organisations aligned only directionally, it stalls. The structural answer this client was already reaching for is the one traced in the cross-team cadence case study: shared planning as the room where the walls come down. A coherent account of cohesion tracking flow rather than sentiment. Correlation carries the reading; causation is not asserted.
What happened next
What’s easy to miss in a boundary story: the raw material was genuinely there. The positive units aren’t polite noise, they name a real asset:
“Competitive pride (let’s get it done).”
“The culture. Everyone comes in and helps. The ownership and responsibility that the team feels is a definite plus.”
An organisation with that culture inside each team doesn’t have a cohesion problem, it has a boundary problem, which is better news: boundaries respond to structure. The check that travels: list the five people outside your team you most depend on, and ask when you last shared a planning room with any of them. “Never” is the boundary, measured.
A note on the data
A real engagement; an unnamed client, and it stays that way. Team names and identifying details are removed, and quotes are lightly edited for anonymity. Every figure and chart on this page draws fresh off the underlying assessment data at render time, close to 2,000 data points spanning both the quantitative and qualitative sides, none of it asserted. One organisation, correlations not causes.
Read Next
- PI Planning: the business context session
The one room where the walls this client measured come down: business and delivery teams on the same clock, in person.
- Why team flow is essential for scaling agility
Cohesion that stops at the team wall shows up downstream as flow that stops at the team wall, the same boundary, seen in motion.