When Nobody Is Conducting

Some effective teams coordinate not because every action is directed from above, but because people respond continuously to one another and to the work.

Management literature often describes teams as though someone must first design them: roles defined, responsibilities allocated, objectives agreed and methods established. That is sensible when a project must mobilise quickly, but it implies that coordination is mainly a product of formal design. Some of the strongest teams form less tidily.

People begin by doing the work in front of them. One notices a gap and fills it; another responds to what has been done. Roles emerge because individuals repeatedly move towards the tasks they handle best, and norms develop through repetition before anyone writes them down. The group becomes coordinated without any moment at which coordination was formally launched. Leadership is not absent in such teams but distributed through action rather than position. The person with the deepest technical understanding leads one part of the work, someone with better relationships another, and someone else holds the overall structure together. Authority moves with the problem, and an arrangement that looks untidy from outside can be entirely clear from within.

Biology offers a comparison. Social insects build complex structures without a central planner because each responds to traces left in the shared environment, a mechanism biologists call stigmergy. Human collaboration is richer and more deliberate, but something similar appears in open-source software, collaborative knowledge projects and well-functioning operational teams: people coordinate partly by seeing what others have done and adjusting their own contribution.

The shared environment therefore matters. A clear board, drawing, shared model, workspace or repository can coordinate action without a meeting for every handover, because people can see where progress has been made, what is incomplete and where they are needed. The work itself becomes part of the communication system. Formal organisations often weaken this unintentionally. Information is split across systems, responsibilities are narrowed and people are told to stay within role boundaries, so coordination has to be recreated through meetings because the natural traces of the work are no longer visible across the boundary. Management is then added to compensate for information the structure has hidden.

Emergent coordination has limits. Safety-critical work, regulated activity and complex projects still need explicit authority, standards and decision rights, and informal groups can develop poor norms as easily as good ones. The useful distinction is between what must be directed and what can organise through local judgement. A leader who decides every interface removes ambiguity, but may also remove the space in which people learn to coordinate directly. A team that always waits for instruction looks disciplined and is fragile, because when circumstances change faster than instructions can be updated, the ability to read the situation and one another becomes essential.

The question is therefore not whether a team should be managed or left alone, but which parts of coordination genuinely require central direction and which would work better if the environment made the necessary information visible. Sometimes a leader adds most value by deciding, and sometimes by removing whatever stops people from responding intelligently to one another. A team that coordinates only while someone conducts every movement may be well controlled, but it is not yet resilient. The stronger test is whether the work continues when the conductor steps away, not because leadership is ignored, but because enough judgement has become shared for the group to keep its shape.