How do ships really know where they are? Drawing on Edwin Hutchins’ ethnographic research, this essay explores distributed cognition, complex adaptive systems, and why effective leadership is about sustaining collective sense-making rather than command and control.
A ship does not arrive at its destination; it continuously discovers it. The path it follows emerges from the coordinated efforts of many people, and it continues on its course as long as this coordination persists.
In the late 1980s, Edwin Hutchins, while serving as a Personnel Research Psychologist at the US Navy Personnel Research and Development Centre, boarded the USS Okinawa, a US Navy ship in San Diego. His task was to study the operators of the steam propulsion system.
In his private life, Hutchins, who was an offshore racing yacht navigator, began observing the navigation work of the team on the ship's bridge alongside his main task. At that time, cognition studies viewed navigation as largely an individual expertise consisting of measurements, calculations, and determining position and route. However, what Hutchins encountered was much different and more complex than this classical view. Information was constantly coming and going on the bridge, never staying static. Directions were announced verbally, repeated, and confirmed. A line was drawn on the chart, only to be crossed by another line a few minutes later. Instruments stored traces of past readings, procedures encoded assumptions about errors, but no one paused to piece together the whole picture. Yet the ship stayed on its course.
Educated in cognitive science but with an affinity for anthropology, Hutchins approached thinking not as an abstract mental process but as human activities occurring within a specific context. Rather than laboratory experiments, he relied on ethnographic methods involving detailed recording of long-term observations and interactions, encompassing attention to the devices, indicators, gauges, language, and routines employed. When Hutchins spoke directly with sailors, he found that none of them knew the ship's exact position. Each had a role, a sequence, a responsibility. Crucially, the information was not held by a single person. It was fixed and redundantly organised through the coordination of many people, devices, and routines. Navigation was not the execution of a command, but the maintenance of a collective discipline.
According to Hutchins, who compiled and shared these observations in his 1995 book Cognition in the Wild, cognition was not limited to our minds or bodies. It was distributed among people, objects, practices, and time. The ship did not move because someone knew where it was. It seemed to be moving along a certain course because the system was constantly reconstructing its position and behaviour.
We call this emergent behaviour. This view does not fit the authority model we know. In the classic command and control system, information is expected to be gathered upwards, analysed and simplified here, and then converted into orders. Control depends on clarity, hierarchy and conformity. Such systems work well when the environment is stable and problems are known in advance. However, there is no such luxury when sailing a large ship. Information arrives in bits and pieces, and sometimes late. Instruments and indicators can malfunction. Conditions can change while we are still making calculations. In this environment, insisting on a centralised approach slows down the system and increases risk. Instead, authority takes on the task of protecting this process rather than issuing instructions.
What we are referring to here are actually complex adaptive systems. Organisations, markets and societies live with similar uncertainties and emerging conditions. Cause and effect are rarely discernible in advance. Local conditions matter more than global plans. Despite this, many organisations continue to rely on command-and-control assumptions, expecting leaders to resolve uncertainty by making decisions rather than through systems approaches and design.
Hutchins proposes another role for leaders. The captain does not replace distributed cognition with personal judgement but ensures that the system's ability to think is preserved. He encourages adherence to processes, the reporting of anomalies and changes, and cross-checking without blind obedience to devices and indicators. Rather than attempting to transform complexity into certainty, authority keeps complexity operational.
Failures in complex systems often occur not because there is no one responsible, but because interpretation is attempted only at the top. Signals are filtered to match expectations. Deviations are corrected before they are understood. Local knowledge is dismissed as noise. The system appears to continue functioning but ceases to learn.
Distributed cognition anticipates fallibility and absorbs it. Error is expected rather than denied. Redundancy is not sacrificed to efficiency. No single perspective is granted exclusive privilege. These capacities are embedded in the system itself. They do not depend on exceptional individuals.
In complex environments, leadership is less about managing actions than about sustaining momentum. It involves creating conditions in which information flows freely, tensions and disagreements surface early, and adjustments can be made without waiting for permission. When this work succeeds, it is rarely visible. Nothing remarkable occurs. The ship simply remains on course.
Navigation, as Hutchins observed, is not a matter of commanding a vessel toward a fixed point, but of sustaining the practices that allow it to remain oriented while in motion. In complex systems, leadership resembles this task more than it does planning or control. The question is not whether the ship obeys, but whether it can continue to find its way.