On Documentation as Design Practice

Interactive figure (view on site): Documentation as Infrastructure.

Figure 1. Documentation as Infrastructure.

This schema maps documentation as a living system: decisions, assumptions, and feedback loops that keep reasoning legible across time.

Introduction

Design work is often evaluated as if it arrives fully formed: a finished artifact, a deployed system, a published policy. What precedes that arrival—the provisional models, assumptions, discarded alternatives, and contextual judgments—tends to vanish. The work is expected to speak for itself.

This disappearance is not neutral. When reasoning dissolves once an outcome exists, later interpretation substitutes inference for evidence. Trade-offs harden into inevitabilities. Contingencies become principles. Over time, what was once uncertain is remembered as obvious.¹

This distortion is not a historical inconvenience; it is a structural weakness. In environments defined by complexity and time, the absence of preserved reasoning undermines the ability to learn. The problem is not intelligence or effort, but the lack of a durable record against which understanding can accumulate.

Documentation is typically framed as a retrospective obligation: a justification produced after decisions are made. In this role, it explains outcomes without shaping what follows. Its leverage has already been lost.

There is another posture. Writing can function as an active instrument of design. When reasoning is externalized while still in motion, it becomes available for inspection, critique, and revision. Writing does not merely record thought; it alters it.

Across disciplines, this effect is well established. Laboratory notebooks preserve failed paths as well as successful ones. Philosophical writing functions as a scaffold for attention, not a summary of conclusions. Design practice is no different. It operates under negotiated criteria and shifting constraints. Without context, judgments become brittle.

Writing provides that context. It captures not only what was decided, but why it appeared reasonable at the time. It preserves uncertainty rather than resolving it prematurely. It resists the reconstructive drift of memory by anchoring interpretation in contemporaneous language.²

The claim advanced here is simple: documentation is most valuable when it participates directly in thinking. Integrated into practice, it becomes reflective infrastructure—supporting judgment across time rather than narrating it after the fact. Figure 1 sketches this infrastructure logic.

As shown in Figure 2, outcome-only memory preserves results but erases the path that makes later judgment possible.

Documentation as Design: In Practice

• Document decisions while reasoning is live
• Preserve assumptions and trade-offs, not just outputs
• Treat records as revisitable infrastructure
• Separate “constraints” from “choices”
• Record what would change your mind

Figure 2. Documentation vs. Outcome-Only Memory.

Outcome-only records preserve results but collapse the reasoning that makes future interpretation and revision possible.

Documentation and the Visibility of Reasoning

Moments of transition expose the danger of invisible reasoning. When authority changes hands, decisions made under one set of assumptions are interpreted under another. Without documented rationale, continuity gives way to improvisation.

Post-conflict and post-authoritarian transitions make this explicit. In Iraq after 2003, de-Ba’athification removed not only personnel but institutional memory.³ Technical knowledge vanished with the people who held it; systems designed under pragmatic constraints became unintelligible to successors.

The collapse of the Soviet Union produced similar failures.⁴ Physical infrastructure persisted, but planning logic did not. Enterprises were dismantled or privatized without understanding the interdependencies that sustained them.

Even stable democracies experience subtler versions of this problem. Policies implemented through discretionary authority are inherited as outcomes rather than judgments, so revision becomes oscillation rather than evolution.

The British civil service offers a counterexample.⁵ Its durability rests not on preventing political change, but on preserving records that allow judgment to persist across it. Decisions can be revisited because their rationales remain accessible.

Visibility of reasoning is therefore not transparency for its own sake. It is a condition for responsible judgment under transition. Without it, change becomes blind.

Design, Judgment, and Time

Corporate mergers illustrate how undocumented judgment decays over time. Decisions justified under one configuration of assumptions persist long after those assumptions expire.

Daimler–Chrysler failed not simply due to “cultural mismatch,” but because assumptions about governance and integration were never stabilized as traceable reasoning.⁶ As leadership changed, successors inherited structures without understanding the judgments that had produced them.

AOL–Time Warner followed a similar pattern.⁷ Strategic logic collapsed with market conditions, leaving slogans in place of rationale. Hewlett-Packard–Compaq persisted longer, but drifted for the same reason: integration choices outlived their premises.⁸

In each case, judgment was exercised under uncertainty, as it must be. The failure was not risk, but memory. Without records, strategy becomes reactive rather than analytical.

Documentation does not prevent error. It preserves the conditions under which error can be understood. It allows later leaders to distinguish between judgments that were reasonable at the time and assumptions that went unexamined.

Time exposes undocumented strategy. Decisions that cannot explain themselves become liabilities. Those whose reasoning is preserved retain flexibility.

Traceability and the Architecture of Memory

As shown in Figure 3, traceability determines whether a system’s memory supports adaptation or becomes a source of fragility.

Figure 3. Traceability and System Memory.

Traceability keeps decisions legible across time so complex systems can adapt rather than fracture.

Complex systems fail when accumulated decisions become opaque. Traceability determines whether such systems adapt or fracture.

NASA’s post-Apollo programs illustrate the cost of lost reasoning.⁹ Specifications survived; judgments did not. Engineers could recover what was built, but not always why. Overengineering and redesign followed—not because prior designs were flawed, but because their rationale was inaccessible.

This mirrors failures seen in other forms of organizational memory and design practice.

The Boeing 737 lineage reveals the same vulnerability.¹⁰ Decades of incremental extensions embedded assumptions that were never fully re-articulated as conditions changed. When the 737 MAX introduced new compensatory systems, cumulative reasoning was fragmented across teams. Individual decisions were defensible; the system-level logic was not.

Software systems replicate this pattern. Code explains what happens, not why.¹¹ Architectural decisions persist without rationale, making change hazardous. Technical debt accumulates as lost reasoning rather than poor implementation.

Institutional investigations repeatedly underscore this point. Reports like the Columbia Accident Investigation Board and the NTSB’s account of Lion Air Flight 610 foreground how missing traceability converts localized decisions into system-level surprises.

Traceability externalizes memory. It allows present actors to reconstruct how systems came to be and under what assumptions. Without it, systems resist change. With it, they retain plasticity.

As shown in Figure 4, the function of documentation shifts depending on whether records remain internal or become public.

Figure 4. Internal vs. Public Accountability.

Documentation can preserve internal continuity or invite public scrutiny; both require explicit reasoning to be durable.

Public Records, Accountability, and Intellectual Risk

Public documentation distributes responsibility. When reasoning becomes contestable, authority no longer rests on opacity.

The Pentagon Papers revealed not a single deception, but a pattern of inherited commitment detached from doubt. Watergate exposed a sequence of opportunistic decisions whose power lay in their traceability. In both cases, documentation did not create failure; it made its structure visible.

Truth and reconciliation processes operate on the same principle.¹² Visibility enables accountability without requiring unanimity. Forgetting preserves stability only by preserving ignorance.

Organizations fracture less from exposure than from the sudden revelation of reasoning never meant to be examined. Institutions that document doubt survive scrutiny. Those that suppress it accumulate fragility.

Public records impose discipline. Claims are qualified. Assumptions are named. Unsupported certainty becomes costly. Trust forms not from infallibility, but from explainability over time.

Documentation as Infrastructure for Complex Systems

Institutions that endure invest in records that outlast individuals. Authority shifts, but judgment remains legible.

The Roman bureaucracy and British civil service illustrate this principle.¹³ Governance persisted because reasoning was embedded in records rather than personalities. Change occurred without epistemic collapse.

Founder-led organizations reveal the inverse. Informal knowledge scales poorly. When leadership disperses, undocumented reasoning hardens into constraint. Post-acquisition integrations fail not from disagreement, but from opacity.

Documentation is infrastructure only when it is used. Living records are revisited, assumptions re-tested, and rationales re-examined. This practice moderates speed with understanding and redistributes power from memory-holders to arguments.

As shown in Figure 5, documentation becomes durable only when it is treated as living infrastructure rather than static archive.

Figure 5. Documentation as Living Infrastructure.

Records retain power when they are maintained, revisited, and used to adjudicate new decisions.

When Documentation Matters Most

• Irreversible decisions
• Assumptions that constrain future options
• Decisions made under time pressure
• Choices justified primarily by alignment or speed

Closing Reflections

Documentation does not eliminate uncertainty. It preserves the conditions under which judgment remains possible across time.

When reasoning is not preserved, uncertainty collapses into myth.¹⁴ Outcomes appear inevitable, failures inexplicable. Writing interrupts this collapse. It preserves the texture of uncertainty before hindsight flattens it.

This does not require exhaustive recording. It requires discernment about which judgments shape what follows. Over time, these records form a medium of thought rather than a static archive.

Documentation is not an accessory to design practice. It is one of its core materials.

Contextual Recommendation

Additional context on ongoing projects, frameworks, and applied work related to these themes is available here:

Explore Primary Design Co’s ongoing work

---

This essay treats documentation not as a moral virtue, but as infrastructure: a system that allows disagreement, revision, and learning without collapse.

Notes

References

Arendt, H. (1982). Lectures on Kant’s Political Philosophy. University of Chicago Press.

Columbia Accident Investigation Board. (2003). Columbia Accident Investigation Board Report. NASA.

Latour, B. (1987). Science in Action: How to Follow Scientists and Engineers Through Society. Harvard University Press.

National Transportation Safety Board. (2019). Aircraft Accident Report: Lion Air Flight 610, Boeing 737 MAX 8, PK-LQP; Java Sea, Indonesia, October 29, 2018.

Popper, K. R. (1959). The Logic of Scientific Discovery. Hutchinson.

Ryle, G. (1949). The Concept of Mind. Hutchinson.

Schön, D. A. (1983). The Reflective Practitioner: How Professionals Think in Action. Basic Books.

Simon, H. A. (1969). The Sciences of the Artificial. MIT Press.

Whitehead, A. N. (1925). Science and the Modern World. Cambridge University Press.

Wittgenstein, L. (1953). Philosophical Investigations. Blackwell Publishing.

Badrtalei, J., & Bates, D. L. (2007). “Effect of Organizational Cultures on Mergers and Acquisitions: The Case of DaimlerChrysler.” International Journal of Management, 24(2), 303–317.

Coalition Provisional Authority. (2003). CPA Order Number 1: De-Ba’athification of Iraqi Society.

Federal Communications Commission. (2001). Memorandum Opinion and Order: AOL Time Warner Inc. and Time Warner Inc.

Financial Times. (2005). “HP says Compaq merger savings ahead of schedule.”

Fukuyama, F. (2004). State-Building: Governance and World Order in the 21st Century. Cornell University Press.

Hayner, P. B. (2011). Unspeakable Truths: Transitional Justice and the Challenge of Truth Commissions (2nd ed.). Routledge.

Hewlett-Packard. (2002). Merger Integration Planning Materials and Shareholder Communications.

Kahneman, D. (2011). Thinking, Fast and Slow. Farrar, Straus and Giroux.

Munk, N. (2004). Fools Rush In: Steve Case, Jerry Levin, and the Unmaking of AOL Time Warner. HarperBusiness.

Northcote, S. H., & Trevelyan, C. E. (1854). Report on the Organisation of the Permanent Civil Service.

U.S. House Committee on Transportation and Infrastructure. (2020). The Design, Development & Certification of the Boeing 737 MAX.

U.S. Senate Select Committee on Intelligence. (2004). Report on the U.S. Intelligence Community’s Prewar Intelligence Assessments on Iraq.

Vlasic, B., & Stertz, B. A. (2000). Taken for a Ride: How Daimler-Benz Drove Off with Chrysler. William Morrow. The National Archives (UK). (2023). Records Collection Policy and Appraisal Guidance.