Part of the Pressure Intelligence™ framework
guide
Member
Member
Member

Watch the Seams

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.

Watch the Seams
95
watch-the-seams

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.

How it shows up

Part 1 of 3 · Notice the effect. The scene, where it lands, and the questions that often sit with you before you fix anything.

The scene

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.

Where it lands

  • In you: you often find yourself translating, chasing and reworking at the points where your team’s work meets another team’s, or holding a gap between two leaders whose priorities don’t fit.
  • In your team: handoffs tend to arrive incomplete, the same handoff breaks in the same place quarter after quarter, and people start building in time to wait for the other side.
  • In your organization: most functions typically report green while cross-team work runs late, decisions that fall between two leaders get delayed or made twice, and a few connectors carry far more of the coordination than anyone has noticed.

Questions to ponder

Think of the handoff that broke most recently, and ask:

  • Could both sides say who owns the step between them, and who decides when the two disagree?
  • When the work arrives, do both sides tend to agree on what “done” means?
  • How do the people on each side usually talk about the other team?
  • If one particular person went on leave next week, would this seam still work?
  • When it last broke, did anyone change anything, or did the next handoff break the same way?

Questions to discuss

With the seam map on the table:

  • Where do we hand work to other teams, and how is each handoff working? The team often sees fragility the leader doesn’t.
  • Where is information getting lost or changed between us and another team? Ask for the place it happens, so the answer is a handoff and a step.
  • How could we change the way we work with the team on the other side so that each of us helps their part of the work land, and the seam becomes shared work? Name one thing you could do this month for the other team’s half of the handoff, what you would ask of them in return, and the conversation between you and their leader that hasn’t happened yet.

Try this week

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.

Keep reading with a free account

  • How to tell whether a fragile seam was not designed, has lost the trust across it, or works only because one or two people hold it together
  • The one-page handoff: what crosses, what “complete” means, who owns it on each side, and who decides when you disagree
  • Why more process tends to deepen a break in trust, and the slower repair that starts with a plain account of your own side
  • The connectors who carry the coordination between teams, why they are often among the most likely to leave, and what to write down before they do
  • The research behind it, and books to read next
  • The toolkit: questions to ponder, questions to discuss, things to subtract, actions to take
  • The kit, as downloads: the full Field Guide, a Leader’s Guide, and slides for the team conversation
Create a free account

Free, no card.

Open the field guide >>

About the author

Mark D. Benson
Mark D. Benson
Founder of Resonant Vector™
Resonant Vector
Full profile →

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.