Coordination, communication, and common understanding
Mars Climate Orbiter was lost after ground software supplied thruster-impulse data in pound-force seconds where the interface specification required newton-seconds, and project controls did not detect the mismatch. The case supports a narrower distinction: communication moves representations, while coordination must join interdependent action through accountable roles, predictable exchanges, and enough tested common meaning for the dependency at hand.
Governing questionWhat must participants share for one team's valid output to become another team's safe action?
A specified interface carried incompatible units
Mars Climate Orbiter entered Mars occultation on September 23, 1999, and its
signal was not recovered. NASA's mishap board found that the SM_FORCES
ground-software output reported thruster impulse in pound-force seconds even
though the software interface specification required newton-seconds. The
navigation algorithm treated the values as metric and underestimated their
effect by a factor of 4.45.1
The official record supports a units mismatch, not the slogan that NASA as a whole “forgot metric.” Lockheed Martin Astronautics generated the small-forces data; the Jet Propulsion Laboratory operations navigation team consumed it; and the written interface already specified the expected units. The defect crossed the boundary because development, testing, operations, and anomaly controls did not detect or correct the violation.12
The spacecraft's final physical fate is less certain than later summaries imply. The 1999 board reported that it either was destroyed in the Martian atmosphere or passed back into heliocentric space. A NASA mission summary updated in 2025 says it burned up. The contemporaneous investigation's unresolved alternative should remain visible rather than being converted into certainty by the later institutional summary.3
The immediate defect had several routes to detection
The Phase I board named one root cause and eight contributing causes. The latter included undetected mismodeling of velocity changes, insufficient spacecraft knowledge in the operations navigation team, failure to perform a fifth trajectory-correction maneuver, a weak development-to-operations transition, inadequate communication, insufficient navigation staffing and training, and inadequate verification and validation of ground software.2
Several observations preceded the loss. Angular-momentum-desaturation events occurred much more often than the navigation team expected. A line-of-sight error was detectable in tracking data, but its significance was not understood. The operations navigation team joined late, had not participated in ground- software testing or major design reviews, and did not receive critical spacecraft information. A contingency maneuver was discussed but not prepared or executed, and end-to-end validation of the small-forces software did not appear to have occurred.2
Those findings distinguish transmission from coordination. Data moved. Concerns existed. A specification existed. What failed was the combined capacity to test meaning across the dependency, assemble anomalies, identify who could decide, and change the flight plan.
Official reviews locate responsibility at different levels
The Phase II mishap report widened the account. It attributed risk to inadequate systems engineering, unclear roles, an understaffed project, a discontinuous handover, weak problem reporting and follow-up, insufficient institutional involvement, and communication barriers among project elements. It also found that mission scientists were not adequately involved in the decision not to perform the fifth trajectory-correction maneuver.4
A separately chartered Mars Program Independent Assessment Team reached a compatible but not identical diagnosis. Its mixed government, industry, and academic membership found the Mars '98 project underfunded relative to its requirements, described operations personnel managing several spacecraft, and treated the development-to-operations discontinuity as consequential. It also called the JPL–Lockheed project-management relationship close and positive in many respects while arguing that the same relationship became insular around risk. Coordination failure therefore did not mean that every relationship was distant or every communication channel was absent.5
Within a week of the loss, JPL's preliminary announcement had already framed the problem as a failure to recognize and correct an information-transfer error and announced internal, outside-expert, and NASA reviews. That is a contemporaneous institutional account from senior NASA and JPL leaders, not testimony from the software developers, navigators, scientists, or contractor workers whose work the later reports evaluated.6
The board reports and commissioned assessment are strong evidence for records reviewed, findings made, and corrective recommendations. They were produced within NASA's response to failed missions, relied heavily on organizational interviews and records, and sought to improve mission reliability. Their areas of agreement do not turn them into independent worker or public accounts.
Communication, common ground, and coordination are different constructs
Gerardo Okhuysen and Beth Bechky define coordination as interaction that integrates interdependent tasks. Their research review groups mechanisms such as plans, rules, objects, roles, routines, meetings, and proximity around three conditions: accountability, predictability, and common understanding.7 That framework supports a narrower claim than “more communication improves coordination.” A message can be understood yet arrive too late, lack an owner, or carry no authority to change another task.
Herbert Clark and Susan Brennan use grounding for the work by which participants establish enough evidence of mutual understanding for their current purpose. Their model treats grounding as medium- and task-sensitive, not as proof that two minds contain identical knowledge.8 A file format can reduce the cost of grounding syntax while leaving the unit, context, or consequence untested.
Paul Carlile distinguishes syntactic, semantic, and pragmatic knowledge boundaries. Shared syntax may support transfer; differences in meaning require translation; differences in interests and consequences may require participants to transform what they know and do.9 Mars Climate Orbiter fits the first two categories as an analytical comparison, but Carlile did not study the mission and his framework does not establish its historical cause.
Shared mental models form another research tradition. A meta-analysis of 23 independent studies found positive relationships between shared mental models, team process, and performance, while also finding that measurement choices changed the observed relationships.10 The underlying studies examine bounded teams and use heterogeneous measures. That evidence does not show that universal agreement is desirable, that one team score captures unequal authority, or that a shared model would by itself have prevented the loss.
Common understanding, then, is selective. Participants need tested agreement about claims on which their actions depend: what an artifact represents, when it is valid, who owns it, how it is checked, and what discrepancy can stop normal work. They need not erase every difference in expertise, value, or language.
Historical examples are comparisons, not a chain of inheritance
I04-N01, Roman military organization, uses Polybius's description of
legions, offices, and a recurring camp layout to mark an early example of
coordination through differentiated roles and familiar arrangements.11
Polybius is an ancient elite observer whose account concerns a particular
period; it cannot establish a timeless military model or the experience of
ordinary soldiers and subject peoples.
I04-N02, The Benedictine rule, uses a community-governing text that calls
for counsel, names deans and other offices, regulates rank, and assigns signals
for recurring work.12 The rule is prescriptive evidence for an
intended order, not a measurement of compliance in every monastery or evidence
that monastic coordination was consensual.
I04-N03, Railroad standard time and telegraphy, marks a later network
problem. North American railroad managers adopted standard time zones in 1883,
and telegraphy helped distribute the common time used in operations.13
The comparison with the railroad case and
The Visible Hand concerns shared operating
semantics at scale. It does not make railroads descendants of monasteries or
ancestors of spacecraft software.
For that reason, I04-E01 and I04-E02 are Grade C parallel comparisons. The
first compares recurring roles and procedures in Roman and Benedictine sources;
the second compares rule-bound community life with railroad coordination across
distance. Neither asserts institutional transmission, equivalent purposes, or
equivalent distributions of coercion.
Barnard, Mintzberg, Weick, and McChrystal ask different questions
I04-N04, Barnard, points to
Chester I. Barnard and
The Functions of the Executive.
Barnard makes communication, willingness to cooperate, and common purpose
elements of formal organization; he also treats whether a communication is
understood and accepted as conditions of authority.14 His
executive theory is a primary conceptual source, not empirical evidence about
Mars Climate Orbiter.
I04-N05, Mintzberg, points to Henry Mintzberg
and Structure in Fives. Mintzberg begins with
the division of labor and coordination, then distinguishes mutual adjustment,
direct supervision, and standardization of work processes, outputs, and skills.15
The Mars unit convention can be compared with standardization of output, while
the anomaly response required adjustment and authority. The taxonomy does not
show that one missing mechanism caused the mission loss.
I04-N06, Weick and McChrystal, joins two unlike works for comparison.
Sensemaking in Organizations asks how
people select cues and construct plausible accounts under ambiguity.16
Team of Teams argues from its authors' military
experience for broad shared awareness paired with decentralized execution.17
They are analytical comparisons, not documented influences on the 1999 mission.
McChrystal's book is also an author-participant management argument with broad
generalization beyond its wartime setting, not an independent evaluation of the
model.
I04-E03, I04-E04, and I04-E05 therefore remain Grade C comparative
relations. They connect railroad practice to Barnard, Barnard to Mintzberg, and
Mintzberg to Weick and McChrystal without asserting direct influence or one
cumulative theory. No separately encoded counterevidence record exists for the
relations; each qualification carries the absence of demonstrated lineage and
the relevant difference in method or setting.
Digital systems can preserve a promise without settling its meaning
I04-N07, Digital event systems, is a present-day analytical extension.
Schemas, queues, logs, versioned artifacts, and automated tests can make units,
owners, states, and timing inspectable. Mars Climate Orbiter shows the boundary:
software can repeatedly process a value that is syntactically consumable and
semantically wrong.1
Classification is not neutral plumbing. Geoffrey Bowker and Susan Leigh Star show how categories and standards become information infrastructure, privilege some viewpoints, and make other experience difficult to represent.18 Susan Leigh Star and Anselm Strauss similarly argue that work becomes visible or invisible through context-dependent indicators and representations.19 These works support asking who defines an interface and whose translation labor disappears. They do not show that every standard is oppressive or every unrecorded activity is beneficial.
AI adds another failure mode. NIST's generative-AI risk profile identifies confident false output, automation bias, privacy risks, and loss of information integrity, including loss of distinctions among fact, opinion, inference, and uncertainty.20 A plausible situation summary is not common understanding until participants can inspect its sources, assumptions, groupings, and authority.
I04-E06 is consequently Grade D and marked research needed. It proposes that
digital systems can encode some coordination conditions while leaving
interpretation and power unresolved. It does not claim historical descent from
Weick or McChrystal or a general performance benefit.
Four Workloop proposals remain hypotheses
The I04-P records are design hypotheses motivated by the case and research,
not established effects.
I04-P01proposes durable intent, delegation, artifact, decision, review, and escalation objects instead of treating chat as operational truth. The mishap reports make specification compliance, anomaly follow-up, and reconstructable responsibility material, but they do not compare chat with work objects.24 A test must measure lost decisions, provenance recovery, handoff ambiguity, newcomer reconstruction, and the cost of maintaining the record. Formal objects could become bureaucracy, strip context, or drive work into shadow channels.I04-P02proposes explicit request, acceptance, delivery, and review states at coworker dependencies. Coordination and knowledge-boundary research motivate accountability and translation, but neither validates customer-supplier language or a particular workflow.79 Tests must cover different dependency types, renegotiation, rework, delivery reliability, and beneficiary outcomes. A powerful requester could dictate the contract, while a formally complete delivery still harms the person it is meant to serve.I04-P03proposes bundling related events into situations before escalation. The MCO anomalies motivate assembling scattered cues; NIST's warning about confabulation and information integrity limits any AI-generated grouping.220 Evaluation must compare comprehension time, escalation precision, missed weak signals, urgent-event delay, and action while preserving event-level provenance. Aggregation can erase a minority signal or manufacture a causal story.I04-P04proposes direct human contact for trust, conflict, and tacit knowledge while retaining minimum durable commitments. A review of remote- collaboration research identifies common ground, task coupling, collaboration readiness, and technology readiness as distinct conditions; it does not prove that colocated contact is always superior.21 Tests need interviews and workflow traces across settings, including conflict repair, later reconstruction, accessibility, privacy, and power. Minimal records can protect intimacy or shelter favoritism, coercion, and exclusion.
Affected parties and missing evidence bound the case
Mars Climate Orbiter was an uncrewed public science mission intended to study Mars and relay communications for other probes. Its loss removed those planned observations and relay capacity.22 The selected records do not quantify how the loss distributed financial burden, career effects, investigative labor, later scientific opportunity, or consequences for particular publics.
The Phase II board says mission scientists were not adequately included in one flight-critical decision. Yet none of the sources used here supplies a representative, participant-authored account from software developers, navigators, mission scientists, contractor staff, administrative workers, or members of the public who financed the program. The JPL announcement quotes senior leaders; the boards synthesize interviews and organizational records. Those perspectives cannot substitute for workers' own accounts.23
The reviewed records do not assess ecological or planetary-protection effects of the spacecraft's loss. That is an evidence gap, not a finding of no effect. The adjacent benefit for all life record keeps nonhuman life, ecosystems, and future generations visible as questions without inventing an impact that the sources do not establish.
No structured impact observations are encoded. Their absence means benefit and harm have not been assessed in that part of the record; it does not negate the documented mission loss or imply zero public, worker, scientific, or ecological consequence. No reading-dependency records are encoded either. The linked works and cases are comparison paths, not prerequisites, intellectual lineage, or proof that one institution inherited another's coordination system.
The comparison field is intentionally heterogeneous
The closest conceptual path is executive attention, information, and organizational sensing: coordination joins interdependent action, while sensing moves consequential change toward someone able to respond. Organizational ignorance asks how an organization can preserve or produce what it does not know. Those adjacencies do not make the concepts interchangeable.
Religious, military, administrative, and industrial comparisons include the Jesus movement and earliest Christian communities, the pre-Constantinian church, Roman military organization, the Venetian Arsenal and Republic, the British Royal Navy, the Prussian-German General Staff, Allied and U.S. World War II mobilization, Toyota, Procter & Gamble brand management, the NASA Apollo program, and the Joint Special Operations Command team-of-teams case.
Technology and corporate paths include Apple, Boeing, Dell, Google/Alphabet, Meta/Facebook, Microsoft, Netscape, Nvidia, and Valve.
Public-health, infrastructure, community, state, coercion, and resistance paths include the Africa CDC regional coordination system, the Aswan High Dam administration, Bali subak irrigation governance, the Botswana kgotla assemblies, Brazil's Family Health Strategy, the Brazilian Landless Workers' Movement, Cecosesola, Charagua Iyambae, the Colombian military false-positives system, the Columbia River Inter-Tribal Fish Commission, the Cuban national literacy campaign, ECOWAS and the Gambian transition, Ethiopian Airlines, FaSinPat and Argentine recovered factories, the First Intifada popular committees, the Foxconn production system, Ghana Community-based Health Planning and Services, the termination of CICIG in Guatemala, the Haiti 2010 humanitarian cluster response, the Islamic State administrative apparatus, the Kenya M-Pesa ecosystem, the Lebanon confessional power-sharing system, the Mali Office du Niger, the Nigeria Ebola emergency-operations center, the northern Nigeria polio-vaccine boycott, the Odebrecht bribery organization, Oman aflaj irrigation institutions, Operation Condor, Porto Alegre participatory budgeting, Project Cybersyn, the Regional Indigenous Council of Cauca, the rival Libyan state institutions, Rwanda gacaca courts, the Rwanda genocide local administrative machinery, the Senegal River Basin Organization, Shining Path, the Somaliland peace conferences, the South Africa Treatment Action Campaign, South African stokvels, the South African Truth and Reconciliation Commission, the Sudan Gezira Scheme, Tanzania ujamaa villagization, Te Awa Tupua governance, the Tunisian National Dialogue Quartet, United Fruit in Guatemala, Ushahidi, and vTaiwan and g0v.
The comparison field includes cooperative, democratic, commercial, military, colonial, coercive, and violent institutions. Adjacency identifies a question about coordination; it does not establish common purpose, moral equivalence, causal similarity, or endorsement.
The durable question is not whether information moved. It is whether the people whose actions depended on it had tested meaning, accountable ownership, a route for disagreement, and authority to change course.
Additional reciprocal institution comparisons
Newly developed institutional records add these reciprocal comparison paths:
- Athens, 508/7–403 BCE — institution-comparison
- British East India Company — institution-comparison
- Dutch East India Company (VOC) — institution-comparison
- Dutch Republic through the Disaster Year — institution-comparison
- European Union — institution-comparison
- Haudenosaunee Confederacy — institution-comparison
- Linux ecosystem — institution-comparison
- Polish-Lithuanian Commonwealth — institution-comparison
- Soviet planning and the sovnarkhoz cycle, 1957–1965 — institution-comparison
- Switzerland — institution-comparison
- W3C — institution-comparison
- Wikipedia — institution-comparison
Each path identifies a sourced case where this idea is a defining emphasis. The relation is editorial comparison, not evidence of direct influence, shared terminology, or equivalent outcomes.
Source notes
Primary official investigation: Mars Climate Orbiter Mishap Investigation Board, Phase I Report (November 10, 1999), executive summary and §4, report pp. 7–9 and 17–18, NASA Langley Research Center PDF. The board identifies the specified and delivered units, the 4.45 conversion factor, and the erroneous trajectory. It establishes the board's causal finding from NASA and contractor records, not each worker's intention or knowledge.
↩ ↩ ↩Primary official investigation: Mars Climate Orbiter Mishap Investigation Board, Phase I Report, executive summary and §§5–6, report pp. 8–9 and 18–30, especially pp. 19–28, NASA Langley Research Center PDF. These sections document the eight contributing causes, detectable tracking error, staffing, handover, communication, contingency, and verification findings. The time-constrained inquiry was also charged with protecting the imminent Mars Polar Lander mission, which shaped its scope and recommendations.
↩ ↩ ↩ ↩ ↩Conflicting official summaries: Mars Climate Orbiter Mishap Investigation Board, Phase I Report, executive summary, report p. 8, NASA Langley Research Center PDF, says the spacecraft either was destroyed in the atmosphere or returned to heliocentric space; NASA, “Mars Climate Orbiter,” “About the Mission,” page updated September 15, 2025, NASA Science, states that it burned up. The later page is a concise institutional mission summary and does not explain how the earlier uncertainty was resolved.
↩Primary official organizational review: Mars Climate Orbiter Mishap Investigation Board, Report on Project Management in NASA (March 13, 2000), executive summary and §2, report pp. 7–24, especially pp. 16–23, NASA Langley Research Center PDF. The board conducted meetings with JPL and Lockheed Martin and attributes the systems-engineering, staffing, authority, communication, science-involvement, and mission-assurance findings to its inquiry. It was appointed by NASA and is not an independent labor or public history.
↩ ↩Commissioned independent assessment: Thomas Young et al., Mars Program Independent Assessment Team Report (March 14, 2000), pp. 3–6, 18, and 22–33, NASA Technical Reports Server PDF. The NASA Administrator chartered a mixed government, industry, and academic team that held structured and informal sessions at NASA, JPL, and Lockheed Martin. Its wider program comparison adds an external-to-project check, but members included NASA, JPL, and Lockheed representatives and its conclusions remain an integrated commissioned assessment rather than worker testimony.
↩Contemporaneous participant-institution source: Jet Propulsion Laboratory, “Mars Climate Orbiter Team Finds Likely Cause of Loss,” September 30, 1999, paragraphs 1–10, JPL release. The release records the preliminary framing and statements of senior NASA and JPL leaders before the formal reports. It is public communication by the institution under review, not an independent finding or a representative account from the affected workforce.
↩Independent scholarly synthesis: Gerardo A. Okhuysen and Beth A. Bechky, “Coordination in Organizations: An Integrative Perspective,” Academy of Management Annals 3, no. 1 (2009), pp. 463–502, especially pp. 469–92, publisher record and DOI. The article reviews multiple organizational traditions and proposes accountability, predictability, and common understanding as integrating conditions. It is a conceptual synthesis, not a tested intervention or an analysis of Mars Climate Orbiter.
↩ ↩Primary theoretical chapter: Herbert H. Clark and Susan E. Brennan, “Grounding in Communication,” in Perspectives on Socially Shared Cognition, ed. Lauren B. Resnick, John M. Levine, and Stephanie D. Teasley (American Psychological Association, 1991), pp. 127–49, especially pp. 127–35, publisher DOI. The chapter models evidence of mutual understanding and medium-specific grounding costs. It is a theory of communication, not evidence that agreement was measured on the mission or that common ground removes conflict and power.
↩Independent conceptual and case-based research: Paul R. Carlile, “Transferring, Translating, and Transforming: An Integrative Framework for Managing Knowledge Across Boundaries,” Organization Science 15, no. 5 (2004), pp. 555–68, especially pp. 555–61, publisher DOI. Carlile develops the syntactic, semantic, and pragmatic distinction using product-development research. Applying it to Mars Climate Orbiter is a later comparison, not a source-derived historical explanation.
↩ ↩Primary ancient text: Polybius, Histories, book 6, §§19–42, especially §§24, 31–37, and 41–42, trans. Evelyn S. Shuckburgh, Perseus Digital Library. Polybius describes Roman selection, unit roles, discipline, and camp arrangement. His elite literary account is temporally specific and cannot stand for all ancient armies, soldiers' experience, or later institutional transmission.
↩Community-controlled primary text: The Rule of Saint Benedict, trans. Leonard J. Doyle, chapters 3, 21, 47, and 63, Order of Saint Benedict archive. The chapters specify counsel, deans, signals for communal work, and rank. A normative rule establishes intended governance, not uniform historical practice or the perspectives of everyone subject to monastic authority.
↩Official museum history grounded in collection artifacts: National Museum of American History, “Synchronizing Time,” section “Time Zones,” accessed July 14, 2026, Smithsonian Institution. The exhibit identifies the railroad-led 1883 time-zone plan and telegraphic distribution of time. It supports the standard-time example, not a claim that common time alone made railroad work safe or caused later management theory.
↩Primary theoretical work: Chester I. Barnard, The Functions of the Executive, 30th anniversary edition (Harvard University Press, 1968; first published 1938), chapters VII, XII, and XV, pp. 65–95, 161–84, and 215–34, Google Books edition record. Barnard's text establishes his definitions and executive argument. It is not a measured general effect or evidence of influence on the mission.
↩Primary theoretical work: Henry Mintzberg, Structure in Fives: Designing Effective Organizations (Prentice-Hall, 1983), chapter 1, especially pp. 1–18, Google Books edition record. The source establishes Mintzberg's coordination mechanisms and structural argument. Applying them to one interface is analytical and does not prove a complete taxonomy or a mission counterfactual.
↩Primary theoretical work: Karl E. Weick, Sensemaking in Organizations (SAGE, 1995), chapters 1–3, publisher record and contents. Weick develops sensemaking as an account of organizing under ambiguity. The source does not document use by the Mars project or establish one tested corrective intervention.
↩Author-participant management account: Stanley McChrystal, Tantum Collins, David Silverman, and Chris Fussell, Team of Teams: New Rules of Engagement for a Complex World (Portfolio/Penguin, 2015), parts III–IV, publisher record. The authors argue for shared awareness and empowered execution from their military experience and broader examples. The book is evidence for their framework, not independent proof that it generalizes or bears on the 1999 mission.
↩Independent historical and sociotechnical scholarship: Geoffrey C. Bowker and Susan Leigh Star, Sorting Things Out: Classification and Its Consequences (MIT Press, 1999), introduction and chapters 1–2, pp. 1–64, MIT Press record. The authors use multiple classification systems to show that standards embed viewpoints and distribute consequences. Their cases do not make every interface equally political or determine a particular design response.
↩Independent sociotechnical analysis: Susan Leigh Star and Anselm Strauss, “Layers of Silence, Arenas of Voice: The Ecology of Visible and Invisible Work,” Computer Supported Cooperative Work 8 (1999), pp. 9–30, especially pp. 9–18, publisher DOI. The paper develops a framework from several kinds of work rather than estimating the prevalence or effects of hidden translation labor in the Mars project.
↩Authoritative technical-risk guidance: Autio et al., Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile, NIST AI 600-1 (July 2024), §§2.2, 2.4, and 2.7–2.8, pp. 6–10, National Institute of Standards and Technology PDF. NIST identifies confabulation, human over-reliance, privacy, and information-integrity risks in voluntary guidance. It does not test a Workloop situation bundle or guarantee that provenance controls prevent misleading synthesis.
↩ ↩Independent research review: Gary M. Olson and Judith S. Olson, “Distance Matters,” Human–Computer Interaction 15, nos. 2–3 (2000), pp. 139–78, especially pp. 146–64, publisher DOI. The review organizes prior distributed-collaboration evidence around common ground, coupling, collaboration readiness, and technology readiness. Its late-1990s technology base and reviewed settings do not prove a universal advantage for direct contact or prescribe minimum records.
↩Official mission records: Mars Climate Orbiter Mishap Investigation Board, Phase I Report, executive summary, report pp. 7–8, NASA Langley Research Center PDF, and NASA, “Mars Climate Orbiter,” “About the Mission,” updated September 15, 2025, NASA Science. They establish the uncrewed spacecraft's planned climate-observation and relay purposes and its loss. They do not measure the distribution of later scientific, labor, fiscal, or ecological effects.
↩Evidence-boundary statement: the Phase II board reports interviews, management findings, and inadequate science involvement, Report on Project Management in NASA, pp. 11–23, NASA Langley Research Center PDF, while JPL's September 30, 1999 release presents statements from senior leaders, JPL. Neither source is a representative participant-authored study of developers, navigators, scientists, contractor staff, administrative workers, or the public. The named omissions bound the selected evidence; they are not findings that those groups had one shared experience.
↩
Research record
Evidence basis
Claim Cited. Material claims carry source locators; comparative interpretation may still evolve.
Open questions and affected lives
Benefit-to-life status: Seed
- Whose vocabulary, categories, schedules, and protocols become the shared standard, and whose knowledge becomes difficult to express through them?
- How much information must travel for coordinated action without exposing private life, sensitive knowledge, or vulnerable participants?
- When does common understanding reduce avoidable uncertainty, and when does it suppress moral conflict, dissent, or useful local variation?
- Who performs and pays for the translation, repair, and relationship work at interfaces when formal coordination breaks down?
These questions remain open; absence from the record does not imply absence of benefit or harm.
Structured atlas record
Lineage nodes
- Roman military organizationillustrates fixed roles, recurring unit structures, and a familiar camp layout as early coordination devices
- The Benedictine rulespecifies counsel, offices, rank, daily signals, and obedience inside a monastic community
- Railroad standard time and telegraphycoordinates movement through a shared time standard distributed through railroad operations and telegraphy
- Barnardplaces communication, willingness to cooperate, and common purpose inside the definition of formal organization
- Mintzbergdistinguishes mutual adjustment, direct supervision, and several forms of standardization as coordination mechanisms
- Weick and McChrystaloffer different accounts of sensemaking and shared consciousness under ambiguity and speed
- Digital event systemsencode some coordination promises while introducing new risks of scale, abstraction, surveillance, and false synthesis
Typed relationships
CRoman military organization → The Benedictine rule
Parallel Solution: Roman military descriptions and the Benedictine rule both show coordination through recurring roles and expected procedures.
The comparison does not establish direct institutional transmission, equivalent purposes, or equivalent authority.CThe Benedictine rule → Railroad standard time and telegraphy
Parallel Solution: Benedictine rule and railroad operating time solve different problems of recurring interdependence through shared expectations.
Railroad time and telegraphy are not presented as descendants of monastic organization.CRailroad standard time and telegraphy → Barnard
Historical Comparison: Railroad coordination gives concrete historical form to the communication constraints Barnard later made central to formal organization.
No cited source establishes that railroad practice directly caused Barnard's theory.CBarnard → Mintzberg
Theoretical Comparison: Barnard and Mintzberg both treat coordination as constitutive of organization but divide its mechanisms differently.
The relation compares primary works; it does not claim one taxonomy validates or fully contains the other.CMintzberg → Weick and McChrystal
Parallel Solution: Mintzberg, Weick, and McChrystal emphasize different structural, interpretive, and information-sharing conditions for coordinated action.
The works arise from different methods and settings and do not establish a single cumulative theory.DWeick and McChrystal → Digital event systems
Analytical Extension: Digital work systems can encode representations, ownership, timing, and escalation while leaving interpretation and power unresolved.
This is a present-day analytical extension; no historical lineage or general performance effect has been established.Provenance and sources
Online anchors
- https://discovery.larc.nasa.gov/pdf_files/MCO_report_2.pdf
- https://discovery.larc.nasa.gov/discovery/PDF_FILES/mars_climate_orbiter_phaseII.pdf
- https://ntrs.nasa.gov/api/citations/20000032458/downloads/20000032458.pdf
- https://science.nasa.gov/mission/mars-climate-orbiter/
- https://www.jpl.nasa.gov/news/mars-climate-orbiter-team-finds-likely-cause-of-loss/
- https://www.perseus.tufts.edu/hopper/text?doc=Plb.+6&fromdoc=Perseus%3Atext%3A1999.01.0234
- https://www.archive.osb.org/rb/text/index.html
- https://americanhistory.si.edu/ontime/synchronizing/zones.html
- https://books.google.com/books/about/The_Functions_of_the_Executive.html?id=W9BsFQf834wC
- https://books.google.com/books?id=J063AAAAIAAJ
- https://uk.sagepub.com/en-gb/eur/sensemaking-in-organizations/book4988
- https://www.penguin.co.uk/books/292118/team-of-teams-by-stanley-mcchrystal-with-tantum-collins-david-silverman-and-chris-fussell/9780241250846
- https://doi.org/10.5465/19416520903047533
- https://doi.org/10.1037/10096-006
- https://doi.org/10.1287/orsc.1040.0094
- https://doi.org/10.1037/a0017455
- https://doi.org/10.1207/S15327051HCI1523_4
- https://mitpress.mit.edu/9780262522953/sorting-things-out/
- https://doi.org/10.1023/A:1008651105359
- https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf