After four posts on hand-offs, dependencies, decisions and weekly rhythms, a pattern became impossible to ignore. Many of the problems that create friction in delivery do not come from individual teams, they come from the places where teams meet.
• A hand-off where the expectations were never made explicit
• A dependency where the impact was never made visible
• A decision that drifted because no one was sure who owned it
• A small risk that stayed hidden until it became Friday’s problem
The cost of unclear hand-offs is not theoretical. NASA lost $125 million on a spacecraft mission because engineers and builders used different measurement systems during a handoff, a failure that came down to unspoken assumptions about something as fundamental as units of measure. If an organisation with NASA’s rigour can stumble at the point where teams meet, it underscores how easily these inter-team connections can break down when expectations are left implicit.
Every organisation relies on these connections: the moment work moves from one group to another, the point where a decision crosses a boundary, the place where one team’s delay quietly becomes another team’s headache. When these connections are vague or informal, people end up working harder than they should. Not because the work is complex, but because the system around the work is unclear.
This series was really about that system. Each post looked at one part of it, but the bigger lesson sits above all four. You cannot run a multi-team organisation on informal, unspoken rules about how teams connect. Most organisations have structure, tooling and processes inside their teams, but far fewer have deliberately shaped what happens between them. That is where small slips turn into late nights. It is also where a little design goes a long way. Clarity inside teams is great, but the connections need clarity as well.
If you want a practical place to begin, here are two questions that can make an immediate difference based on our client work.
• Have we discussed how this hand-off actually works, and do both sides agree with it?
• Is there a regular review where people can highlight potential risks while they are still easy to fix?
If the answer to either of those is no, then that’s a good area to look at first.
Cross-team work improves fastest when expectations are clear, connections are visible and people have a predictable place to raise concerns early. None of this requires heavy process. It simply requires taking the in-between spaces seriously.
At Oak Mountain, we help organisations do this design work consciously: mapping the connections between teams, creating clear working agreements, and building light rhythms that keep delivery moving without adding heavy process. If you would like to explore that for your teams, email: enquiries@oakmountain.ltd.