A field guide for work that stalls between teams: why it moves well inside each team but slows in the handoffs, and how to make them hold.

Why work that moves well inside each team slows down between them, and how to make the handoffs hold.
Between people and teams
The challenge: Work stalls between people and teams
Cross-team work tends to lose its time in the handoffs, where the work belongs to both sides and is measured by neither. Under pressure each team narrows to its own measures, and the informal effort that kept a seam working goes first. A seam can break in its design, in who decides, in how each side reads the same words, or in trust, and each needs a different repair. The guide helps you map where your team’s work meets others’, name the kind of break, and make the handoffs hold.
Who it’s for: Leaders whose team’s work depends on other teams: a function head, a program lead, a manager whose handoffs cross a boundary every week. Read it on your own first, then take the conversation in part three to your team and, where you can, to your counterpart on the other side.
Part 1 of 3 · Notice the effect. The scene, where it lands, and the questions that often sit with you before you fix anything.
A program review goes around the table. Engineering is on track. Product is on track. Operations is on track. The program is six weeks late. When the group traces where the time went, very little of it was lost inside any one team. It was lost in the handoffs: the spec that arrived missing a decision, the dependency each side assumed the other was watching, the question that sat in a queue between two groups for nine days because it belonged to neither of them. Each leader can show that their own team did its part. The program manager, who has spent the quarter walking between desks to keep things moving, is the only person who saw the whole delay happen, and she is tired of being the one holding it together.
Think of the handoff that broke most recently, and ask:
With the seam map on the table:
Draw each place your team’s work meets another team’s: where you receive something, where you hand something off, where a decision needs both of you. Mark each one reliable or fragile, and be straight about which is which; your team already knows. Then pick the fragile one most likely to be tested in the next month and send one message to your counterpart: “I noticed this in the last handoff. Can we talk about what would make it cleaner next time?” It treats the seam as shared work, and it opens the conversation without blame.
Free, no card.
Mark D. Benson is the founder and principal writer of Resonant Vector, the home of Pressure Intelligence, and the host of Pressure Rising™. He is a product and systems leader who has spent his career running global teams, complex platforms, and consequential decisions under real constraint.
His career sits where strategy, technology and large human systems meet, in places where high stakes are the norm.
Resonant Vector is his commitment to learning in public and sharing what helps leaders and teams perform under pressure.
More about Mark can be found at markdbenson.com.