Cross-Team Cadence: Teams Heard About the Deadline After It Was Set
This page draws on a change programme we ran at a research and advisory firm with a global footprint, in one of the largest business units under its roof. Nine product and technology teams sat inside that unit, turning over hundreds of millions of dollars every twelve months, under a mandate to double it. To ground the change in evidence, we scored the organisation on twenty-five dimensions and ran a separate qualitative pass to catch what the scores alone would miss.
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 Cross-team planning: 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 cross-team planning cadence: whether the teams plan together, on a shared clock. Now look at what it connects to. Not logistics. Its strongest neighbours are meaning dimensions: how features and their benefits are defined, how clear the business value is, how visible the strategy is. In this organisation, shared planning wasn’t where schedules got coordinated. It was where shared understanding got made, or didn’t.
What the numbers said
Behind a median of 7 out of 10 sits a heavy tail: of sixty-one respondents, nineteen scored the planning cadence at 4 or below. Nearly a third of the organisation experiences planning as something that happens to them.
What the words said
The two dark blobs not lining up is the chart.
Counted up: nine coded units, five negative and two positive. The written signal centres at 3 once mapped to the score scale, against 7 for the scores themselves. Read in sequence, the negative units describe one failure, step by step:
“The visibility at the planning stages is missing across IT.”
“That results in development teams being brought in late to efforts that already have defined due dates.”
“Resources and prioritization happen within per team but not really across teams.”
Planning worked inside each team and broke between them, so the big, multi-team efforts arrived pre-scheduled: scope handed over with the meaning already stripped out, dates attached before the people delivering them were in the room.
Where it lived
Nine teams, anonymised, best to worst. Thin rows render wider and flatter; less data looks uncertain, not falsely precise.
Dropping from 10 the whole way to 3.5, the team medians spread wide over the nine of them. Which is exactly what a missing shared cadence looks like from above: each team’s planning experience depends on which efforts it gets pulled into, and how late.
What the planning cadence turned out to be entangled with
The measured neighbourhood:
- Defining features and their benefits (r = .74), the strongest pull
- Business value clarity (r = .71)
- Portfolio vision and strategy (r = .65)
The pattern in those three: teams that plan together know what the work is for. Teams brought in after the due date is set receive scope without meaning, and it shows up in the sore units:
“The key challenge we have is with larger cross-IT efforts that require multiple IT teams.”
And the counter-evidence sits in the same dataset, because this organisation had started standing up exactly the missing structure:
“PI Planning process has been established: there is a structure around what is submitted each quarter.”
“We should align by presenting our quarterly visions all at once.”
Where the quarterly structure existed, the units flip positive; where it didn’t, teams heard about deadlines after they were set. A coherent reading of why cadence correlates with meaning rather than logistics, offered as a reading of correlations, not a proven cause.
What happened next
The quarterly planning structure the positive units describe was already spreading during the engagement, and the training investment in the product and portfolio teams supported the same muscle: putting the people who define work and the people who deliver it in one room on one clock. Monitoring continued as conditions changed, and I won’t claim the numbers that came after. The check that travels: list your last five cross-team efforts and ask when each delivering team first heard the date. If the answer is ‘after it was set’, your planning cadence is a meaning problem, not a calendar problem.
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. This page’s charts and figures recompute against the underlying assessment data on every render, roughly 2,000 data points across the quantitative and the qualitative work, and none of it is asserted. One organisation, correlations not causes.
Read Next
- PI Planning: the business context session
Teams in the room when context is presented is the exact inverse of hearing about the deadline after it was set.
- Connecting the portfolio to PI Planning
Late discovery is what a portfolio process disconnected from the planning cadence produces by default.