A team can miss a deadline even when every person works hard. Sometimes the problem lies in how their contributions connect. Adding a daily meeting may help, but first identify whether the work is mostly pooled, sequential or reciprocal.
OpenStax’s discussion of intergroup performance distinguishes these forms of interdependence. They describe different relationships between units, helping explain why one coordination method does not suit every activity.
Three patterns to recognise
Pooled: people make largely separate contributions to a shared result. Imagine several branches reporting into an organisation’s overall service total. Common definitions and standards help the contributions fit together.
Sequential: one person’s output becomes another’s input. In an illustrative publishing workflow, a checked manuscript goes to layout, then an approved layout goes to production. Handover quality and timing matter because the next stage depends on what arrives.
Reciprocal: work moves back and forth. A designer and engineer may repeatedly revise a product together because each decision changes the other’s options. Coordination has to support those exchanges rather than pretend the task is a one-way handoff.
Map one real piece of work
Choose a recent deliverable and draw the actual movement of information. Mark where someone waited, where a decision returned for revision, and where two people needed the same definition. Ask those involved to correct the map.
Keep the exercise small. Mapping an entire organisation at once can produce an impressive diagram with little practical value. One troublesome handover or recurring revision loop is enough to begin.
Change the coordination where the problem occurs
A shared reporting definition may help pooled work. A clearer acceptance checklist may help a sequential handover. A short joint decision session may help reciprocal work. These are possible responses to test, not automatic prescriptions.
Agree what improvement would look like: fewer returned files, less waiting, or quicker resolution of a named decision. Review that observation after the change instead of measuring success by the number of meetings held.
Most teams contain all three patterns in different activities. The useful question is therefore local and concrete: how does this piece of work depend on the next person, and what would make that connection easier?