Memoing

Version

v1 · 2026-08-24 · History

Prime #

985

Origin domain

Ethnography & Qualitative Methods

Subdomain

analytic practice → Ethnography & Qualitative Methods

Core Idea

Memoing produces a parallel, contemporaneous, durable record of the in-flight reasoning that generates an artifact — decisions, alternatives, doubts, frame-shifts — kept alongside rather than folded into the artifact. The point is anti-collapse: absent the trace, "we deliberately chose X over Y" and "we never considered Y" become indistinguishable.

How would you explain it like I'm…

The Building Notebook

When you build a Lego castle, you only see the finished castle — not all the times you tried a piece, changed your mind, or wondered what to do. Memoing means keeping a little notebook beside you as you build, writing down your choices and questions while you make them. Later, anyone can read the notebook and understand not just *what* you built but *why* you built it that way.

Saving the Path, Not Just the Result

Memoing means keeping a running diary of your thinking right next to whatever you're making — and keeping the two separate. The finished thing, like a report or a drawing, doesn't show the choices you weighed, the ideas you tried and dropped, or the questions you left open. So you write those down as they happen, not from memory afterward. The point is that the finished thing alone can't tell anyone how you got there — the same result could come from totally different paths. Memoing saves that path so a reviewer, your future self, or whoever takes over can understand and continue the work.

The Parallel Trace

Memoing is the practice of producing a parallel, chronological, durable record of the in-flight reasoning that generates a primary artifact — keeping the reasoning trace *alongside*, not folded into, the artifact itself. The trace captures working interpretations, alternatives considered, decisions made, questions left open, doubts felt, and frame-shifts that occurred during the build. The defining commitment is that the artifact alone *underdetermines* what was actually done: the same finished output can result from many reasoning paths, and reviewers, future-self, auditors, or successors need the path itself to evaluate, repair, or continue the work. The payoff is anti-collapse — without the parallel trace, the difference between 'we deliberately chose X over Y' and 'we never considered Y' becomes unrecoverable.

 

Memoing is the structural practice of producing a parallel, chronological, durable record of the in-flight reasoning that generates a primary artifact, with the reasoning trace preserved alongside — not folded into — the artifact itself. The trace captures working interpretations, alternatives considered, decisions made, questions left open, doubts felt, and frame-shifts that occurred while the artifact was being built. The defining structural commitment is that the artifact alone underdetermines what was actually done: the same finished output can result from many different reasoning paths, and downstream actors — reviewers, future-self, auditors, successors — need the path itself to evaluate, repair, or continue the work. The skeleton has five parts: a primary stream (the artifact being produced — a coded dataset, a body of code, a model, a clinical chart, a policy document); a parallel trace (a running record of reasoning in real time, distinct from the primary stream); a contemporaneity discipline (entries made when the reasoning happens, not reconstructed after); a signal-not-noise filter (capturing the moments worth tracing — frame-shifts, decisions, unresolved doubts — and not the rest); and a re-encounter affordance (the trace must be readable later, often by someone else, often across years). The structural payoff is anti-collapse: absent the parallel trace, the trajectory by which the artifact was reached collapses irretrievably into the artifact, and the difference between 'we deliberately chose X over Y' and 'we never considered Y' becomes unrecoverable.

Broad Use

• Qualitative research: Analytic memos are the engine of category emergence, distinct from descriptive fieldnotes.
• Software engineering: Architecture Decision Records capture each decision's context, alternatives, and rationale in version control.
• Laboratory science: The bound, paginated, time-stamped, signed lab notebook sits alongside the apparatus and its outputs.
• Clinical practice: Progress notes carry the clinician's in-flight reasoning — assessment, differential, plan — beside the patient record.
• Law: Attorney work product is recognized as a distinct, valuable object and protected by privilege.
• Machine learning: Experiment logs, model cards, and ablation rationale carry reasoning alongside the trained model.
• Audit: Workpapers form the regulated chronological record of sampling decisions, exceptions, and resolutions.

Clarity

Surfaces the distinction between the artifact and the reasoning that produced it, relocating a class of failures — an undebuggable model, an unexplained code branch — to their actual cause, the absent trajectory.

Manages Complexity

Compresses a high-dimensional reasoning trajectory into a streamlined parallel trace at low marginal cost — eighty contemporaneous words per decision — averting an otherwise intractable later reconstruction cost.

Abstract Reasoning

Yields the artifact-trajectory distinction, the real-time-versus-post-hoc point (reconstruction is biased by hindsight), the signal-not-noise trainable filter, and the protection dimension (the trace must be shielded to stay honest).

Knowledge Transfer

• Lab notebook → software: The contemporaneous, append-only, dated discipline ports directly to architecture decision records.
• Grounded theory → ML: Letting emerging analysis direct the next move ports as follow-up runs guided by prior runs, rationale preserved.
• Clinical → operations: Contemporaneous assessment under time pressure ports as live incident-timeline capture.

Example

A single eighty-word grounded-theory memo — "merged 'reluctant compliance' into 'strategic accommodation' because the former implied an attitude the data did not support; considered keeping them separate but the markers were identical" — preserves a distinction the finished category scheme alone cannot recover.

Relationships to Other Abstractions

Current abstraction Memoing Prime

Parents (1) — more general patterns this builds on

• Memoing is a kind of Logging Prime

  Memoing is event-time durable logging specialized to the reasoning trajectory that produces a parallel primary artifact.

Children (3) — more specific cases that build on this

• Analytic Memo Domain-specific is a kind of Memoing

  Analytic memo is memoing specialized to qualitative inquiry, where the contemporaneous reasoning trace develops codes, categories, relations, and theory between evidence and claims.

• Reflexive Journal Domain-specific is a kind of Memoing

  A reflexive journal is memoing specialized to observer stance, preserving in-flight assumptions and reactions alongside analysis and linking them to the decisions they shaped.

• Peer Debriefing Domain-specific is part of Memoing

  Peer debriefing contains memoing because its output is a contemporaneous parallel reasoning trace of probes, alternatives, changes, and defended choices alongside the evolving analysis.

Hierarchy path (1) — routes to 1 parentless root

• Memoing → Logging → Observability

Not to Be Confused With

• Memoing is not Sensemaking because memoing is the practice of externalizing and preserving reasoning in a durable trace, whereas sensemaking is the cognitive activity of constructing understanding.
• Memoing is not Versioning because memoing records the reasoning that moved between states (the why-of-the-move), whereas versioning records successive states of the artifact (the what-at-each-checkpoint).
• Memoing is not an Audit Trail because memoing captures the human why — decisions and rejected alternatives — whereas an audit trail is a machine-generated record of what was done.