Analytic Memo¶

Externalise interpretive reasoning in writing during analysis — dated, typed, indexed memos sitting between raw evidence and finished claims — so the analysis becomes generative, auditable, and revisable.

Core Idea¶

An analytic memo is a written intermediate artifact in which a qualitative researcher records emerging interpretations, candidate categories, relationships among codes, unresolved questions, and the reasoning behind analytic decisions during ongoing data analysis. It occupies the space between raw evidence — interview transcripts, field notes, observational records — and finished theoretical claims, and the grounded-theory tradition (Glaser and Strauss 1967; Strauss and Corbin 1990; Charmaz 2006) treats it as generative rather than merely documentary: the act of writing the memo is itself the analytic move in which structure is discovered, not just transcribed. A code-focused memo written in week three becomes input to a category-relationship memo in week five, which feeds the integrative memos that eventually become the theoretical statement. The corpus of memos, dated and indexed, constitutes the researcher's working theory and provides an audit trail that an independent reviewer can in principle walk backward from any final claim to the specific transcript segments and the reasoning steps that produced it. The key structural commitment is that analytic reasoning must be externalised in writing during analysis rather than reconstructed after the fact: an interpretive process leaving no intermediate written record cannot be audited, and its conclusions cannot be assessed for grounding in the data, revised transparently, or transmitted intact to collaborators or successors. Methodological-memo types in grounded theory are typically distinguished by scope and function: code memos elaborate a single code; theoretical memos develop emerging categories and their relationships; operational memos record procedural decisions; integrative memos attempt synthesis across the emerging category structure.

Structural Signature¶

Sig role-phrases:

the researcher — the inquirer doing interpretive work over time (coding transcripts, field notes, documents)
the raw evidence — the data the memo sits above: transcripts, observations, documents
the memo — a dated, authored, written record of intermediate interpretation (candidate category, emerging relationship, open question, decision rationale), positioned between raw evidence and the final claim
the memo typology — the functional kinds the corpus sorts into by scope: code memo (one code), theoretical memo (a category and its relations), operational memo (a procedural decision), integrative memo (synthesis across the structure)
the corpus of memos — the dated, indexed accumulation that is the working theory in progress, not a record of it
the generative function — the load-bearing commitment: writing the memo is the analytic move in which structure is discovered, not transcribed afterward
the audit trail — the guarantee that follows: a reviewer can walk backward from any published claim, through the dated memos, to the prompting transcript segments
the externalization boundary — the deliberate limit: an interpretive process leaving no contemporaneous written trace falls outside what can be audited, revised transparently, or transmitted intact (distinct from the definitional codebook and from a post-hoc reconstruction)

What It Is Not¶

Not a codebook. The codebook is the definitional artifact — "this code means this"; the memo is the interpretive one — "here is what I think is happening, and what I am unsure of." Conflating them hides exactly the reasoning the method needs externalised, folding the analytic move into a glossary entry that records a decision without the thinking that produced it.
Not mere documentation or record-keeping. Treated as overhead, memo-writing looks like paperwork to minimise. The grounded-theory commitment is that the writing is generative — the memo is the place where a category is discovered, not transcribed after the fact — so skipping or deferring it does not merely lose documentation, it skips the analytic move itself. The practitioner's question is "have I written my way to it yet?", not "have I written down what I found?"
Not the raw data, and not the final claim. The memo is the intermediate term, sitting between the transcript or field note and the finished theoretical statement. Collapsing all three into "my analysis" is what makes a chain of interpretation un-auditable; keeping the middle term visible is what lets a reviewer walk backward from a published claim to the evidence that prompted each step.
Not a post-hoc reconstruction. The structural commitment is that reasoning be externalised during analysis, at the moment of the analytic move — not narrated afterward from the raw data. An interpretive process that leaves no contemporaneous written trace falls outside what the method can audit; a category with no dated memo marking its emergence is a sign the move was reconstructed rather than recorded.
Not the same as its sibling artifacts. Architecture Decision Records, lab notebooks, reviewer memos, and retrospective notes share the dated-externalised-revisable shape, but they carry none of the grounded-theory machinery — no theoretical-sampling-by-memo, no constant-comparison forms, no saturation criteria, no memo-to-theory progression. They are co-instances of the parent pattern (externalised intermediate cognition), not exports of analytic-memo content; calling an ADR "an analytic memo" over-reads a shared shape as a shared method.

Scope of Application¶

The analytic memo lives across the interpretive subfields of qualitative research methodology, with the grounded-theory tradition as its home; its reach as a named method is bounded to that domain, while the externalised-intermediate-cognition pattern it instantiates recurs as sibling practices (lab notebooks, ADRs) under the documentation / audit-trail parent rather than as exports of this entry's content.

Grounded theory — the canonical home, where the memo typology (code / theoretical / operational / integrative) and the memo-to-theory progression make the writing the analytic move in which categories are discovered.
Ethnography — where memos sit alongside field notes to externalise the fieldworker's emerging interpretation and keep it auditable.
Phenomenology — recording the reduction and the analyst's evolving reading of lived-experience accounts as an intermediate, revisable trace.
Narrative inquiry — capturing candidate plot structures and thematic relations across collected stories before the final account.
Action research — logging the reasoning behind iterative intervention-and-reflection cycles so decisions can be revisited and shared.
CAQDAS-supported coding practice — NVivo, ATLAS.ti, and Dedoose ship explicit memo features that operationalise the dated, indexed memo corpus across all of the above.

Clarity¶

Naming the analytic memo pulls apart three artifacts that qualitative practice routinely collapses into "my analysis": the raw data (the transcript, the field note), the intermediate reasoning (what the coder is noticing, the candidate category, the still-open question), and the final claim (the paper, the theoretical statement). Keeping the middle term visible is what makes a chain of interpretation auditable — a reviewer can walk backward from any published claim, through the dated memos that built it, to the specific transcript segments that prompted each step — and it is what exposes the failure mode the concept exists to forbid: an analysis that produces conclusions with no contemporaneous written trace, reconstructed after the fact and therefore impossible to check for grounding or to revise transparently. It also separates the memo from its neighbor the codebook: the codebook is definitional (this code means this), the memo is interpretive (here is what I think is happening and what I am unsure of), and conflating the two hides exactly the reasoning the method needs externalised.

The deeper clarity is a reframing of what the writing is for. Treated as mere record-keeping, memo-writing looks like overhead to be minimised; the grounded-theory commitment is that the writing is generative — the memo is the place where a category is discovered, not transcribed after the fact — so skipping or deferring it does not just lose documentation, it skips the analytic move itself. That reframing changes the practitioner's question from "have I written down what I found?" to "have I written my way to it yet?", and it makes the corpus of dated, indexed memos legible as the working theory in progress rather than a paperwork residue alongside the real work.

Manages Complexity¶

A qualitative project is, materially, an overwhelming mass: hundreds of hours of interview transcripts, field notes, and documents, against which a researcher must build a theory that is grounded in all of it, traceable to specific evidence, and defensible to a skeptical reviewer. The naive alternatives both fail under that load. Holding the emerging interpretation in one's head leaves it un-auditable, lost the moment the analyst leaves the project, and impossible for a collaborator to enter. Reconstructing the analysis after the fact, from the raw data, irrecoverably loses the contemporaneous reasoning state — the why-this-category-here that the finished claim depends on but the transcript does not contain. The analytic memo tames this by externalising the interpretive process into a second corpus that is itself navigable: dated, authored, indexed memos that sit between the raw evidence and the final claim and are the working theory in progress. The compression has a definite shape. The sprawl of an unbounded interpretive process collapses to a small set of tracked artifacts whose type tells the analyst what each is doing — a code memo elaborating one code, a theoretical memo developing a category and its relations, an operational memo logging a procedural decision, an integrative memo synthesizing across the category structure — so that "where is my reasoning about X?" is answered by scope and date rather than by re-reading the data. And it converts the project's central anxiety, is this conclusion actually grounded?, into a single mechanical operation an outside reviewer can perform: walk backward from any published claim, through the dated memos that built it, to the specific transcript segments that prompted each step. That backward-traceability is the parameter the method makes everything turn on; its presence or absence reads off directly whether a finding can be audited, revised transparently, or transmitted intact. The reframing that the writing is generative — that the memo is where the category is discovered, not merely recorded — is what makes the audit trail honest rather than a post-hoc gloss, because the trace is laid down at the moment of the analytic move, not narrated afterward. So the researcher does not have to keep the whole theory live in memory or hope to recover it later; they track a growing, indexed set of typed memos and read both the state of the theory and its grounding off that corpus. An interpretive process of essentially unbounded dimension becomes a finite, navigable, backward-walkable artifact set.

Abstract Reasoning¶

The analytic memo licenses a distinctive set of moves in qualitative inquiry, all flowing from the commitment that interpretive reasoning must be laid down in writing at the moment of analysis and that the resulting corpus is the working theory rather than a record of it. The signature interventionist move is generative and runs counter to a record-keeping intuition: facing a cluster of passages that resist the existing codes, the researcher does not first decide what the category is and then write it down — they write in order to find it, articulating in prose what seems to be happening across interviews 4 and 12, and the act of writing is what surfaces a new category ("boundary-defence failure") that the silent reading had left implicit. The predicted effect is concrete and testable against the corpus: a category that emerged through a memo will have a dated memo marking its first appearance and the evidence that prompted it, so a category with no such memo is a sign that the analytic move was skipped or reconstructed after the fact. The reasoning is therefore "write the memo → discover the structure," with the absence of the memo predicting the absence of grounded discovery.

The diagnostic move runs backward along the same trace and is the one an outside reviewer performs. Confronted with a finished claim, the auditor reasons from the published statement, through the dated memos that built it, to the specific transcript segments that prompted each step — and the recoverability or non-recoverability of that path is itself the verdict. A claim that can be walked back to its evidence is grounded; a claim whose backward path dead-ends at a memo gap is, by the method's own commitment, un-auditable and its grounding unassessable. The memo type sharpens the diagnosis: asking "where is my reasoning about X?" is answered by scope and date rather than by re-reading the data, because a code memo elaborates one code, a theoretical memo develops a category and its relations, an operational memo logs a procedural choice, and an integrative memo synthesizes across the structure — so the analyst infers from the kind of question what kind of memo should hold the answer and where in the dated sequence to look.

The boundary-drawing move fixes what counts as a memo and when externalization is obligatory, which is what keeps the practice from collapsing into either raw data or finished prose. The analyst separates the definitional artifact (the codebook: this code means this) from the interpretive one (the memo: here is what I think is happening and what I am unsure of), and refuses to let a procedural log or a polished report stand in for the contemporaneous reasoning the method requires — because each substitution hides exactly the analytic step that needs to be visible. The governing regime rule is sharp: an interpretive process that leaves no intermediate written trace falls outside the method's auditability entirely, so the requirement to externalize is not advice about thoroughness but the boundary of what can be checked, revised transparently, or transmitted intact to a collaborator or successor. Finally, an order-of-events inference structures the whole: a code memo in week three feeds a category-relationship memo in week five which feeds the integrative memos that become the theoretical statement, so the analyst can read the maturity of the working theory off where in that progression the memo corpus currently sits, and can predict that an integrative synthesis attempted before the underlying code and theoretical memos exist will lack the substrate it needs to be grounded.

Knowledge Transfer¶

Within its home — qualitative research methodology — the analytic memo transfers as a full practice, machinery included, across grounded theory, ethnography, phenomenology, narrative inquiry, and action research, with coding software (NVivo, ATLAS.ti, Dedoose) providing explicit memo features. What carries is not just the idea of writing-during-analysis but the domain-specific apparatus: the memo typology (code, theoretical, operational, integrative memos, sorted by scope and function), the progression (code memo in week three feeding a category-relationship memo in week five feeding the integrative memos that become the theoretical statement), the generative commitment (the memo is where a category is discovered, not transcribed), the backward-traceable audit trail (walk from any published claim through dated memos to the prompting transcript segments), and the saturation-and-constant-comparison criteria that the memo corpus instruments. Across these subfields the vocabulary and the moves are stable, and "where is my reasoning about X?" is answered by memo type and date rather than by re-reading the data. That is genuine within-domain transfer as mechanism.

Beyond qualitative methodology the transfer is real but routes through a shared abstract parent, not through the memo's own machinery — and the seed is explicit about the distinction. The portable structure is externalised intermediate cognition during inquiry: a dated, authored, navigable corpus of contemporaneous reasoning, written at the moment of the analytic or design move, that confers auditability, generativity, and revisability. That parent genuinely recurs as co-instances across professions — Architecture Decision Records and design-rationale documents in software and engineering, lab notebooks and bench books in experimental science, reviewer and clerks' bench memos in law, working-paper drafts in policy, agile retrospective notes — each independently a place where an inquirer writes reasoning down while doing the work rather than reconstructing it after. But these are sibling practices, not exports of analytic-memo content: an ADR shares the dated-externalised-revisable shape while carrying none of the grounded-theory furniture (no theoretical-sampling-by-memo, no constant-comparison memo forms, no saturation criteria, no Glaser-Strauss-Charmaz progression). So the honest cross-domain statement is that the lesson — externalise intermediate reasoning at the time of inquiry, and your conclusions become auditable, your structure discoverable, your revisions transparent — should be carried by the parent pattern (externalised cognition / documentation / audit-trail), under which the analytic memo and the lab notebook and the ADR all sit as cousins. The cross-domain reach belongs to that parent; "analytic memo," as named, carries qualitative-research-specific cargo that does not and need not travel.

The boundary to mark is therefore one of level, not of metaphor-versus-mechanism: calling an Architecture Decision Record "an analytic memo," or importing grounded theory's memo-to-theory progression into a lab notebook, over-reads a shared shape as a shared method — the externalisation function transfers, the methodological machinery does not. Stated plainly: within qualitative inquiry the named practice transfers as a complete method; one level up, the externalised-intermediate-cognition pattern it instantiates recurs literally across science, engineering, law, and policy and owns the cross-domain lesson; and treating the sibling artifacts as the same thing as the analytic memo conflates co-instances of a parent with transfer of the entry's own content (see Structural Core vs. Domain Accent).

Examples¶

Canonical¶

The defining practice is grounded-theory memoing as codified by Glaser and Strauss and elaborated by Charmaz. Picture a researcher coding interview transcripts about newly diagnosed patients. In week three, noticing that several interviewees describe rehearsing how to tell their families, she writes a code memo on the code "disclosure rehearsal," quoting the passages and noting what puzzles her. In week five, comparing that memo against one on "protecting others from worry," she writes a theoretical memo proposing a category — "managing others' distress" — that links them, and records the open question of how it relates to the patient's own coping. Those feed integrative memos that eventually become a section of the theory. The category was not decided and then noted; it was discovered in the act of writing the memo, and every step is dated and tied to specific transcript segments.

Mapped back: The coder is the researcher and the transcripts the raw evidence; each dated write-up is a memo, sorted by scope into the memo typology (code, then theoretical, then integrative). That the category surfaced through writing is the generative function, and the dated chain from claim back to passages is the audit trail.

Applied / In Practice¶

In applied qualitative research — health-services and education studies, for instance — the memo corpus does concrete methodological work by satisfying the "audit trail" standard that Lincoln and Guba established for demonstrating trustworthiness. A team coding dozens of transcripts in software such as NVivo or ATLAS.ti attaches dated memos to codes and categories as they analyze, so that when the study is written up and scrutinized (by co-investigators, peer reviewers, or an external auditor), any reported theme can be traced backward through the memos to the interview extracts and reasoning that produced it. This externalized trace is what lets a skeptical reader assess whether the findings are grounded rather than imposed, lets a departing team member hand off the analysis intact, and lets the team revise a category transparently when later data contradict it.

Mapped back: The dated, software-indexed memos are the corpus of memos functioning as the audit trail an auditor walks backward. Sorting them by the memo typology answers "where is my reasoning about X?", and requiring the trace to exist contemporaneously is the externalization boundary — reasoning left unwritten falls outside what the study can defend.

Structural Tensions¶

T1: Generative writing versus busywork (crediting all memoing as analysis). The load-bearing reframe is that writing the memo is the analytic move in which structure is discovered, not mere documentation. This is genuinely illuminating, but it also licenses treating any volume of writing as analytic progress: if the writing is generative by definition, an analyst can mistake copious memoing for insight, and there is no internal test to separate a memo that discovered a category from one that merely restated the data at length. The generative claim dissolves the very distinction — writing-that-thinks versus writing-that-fills-pages — that would let a reviewer tell productive memoing from busywork. The method's central virtue (writing produces structure) can become its central alibi (I wrote, therefore I analyzed). Diagnostic: Did this memo surface a category or relationship that was not already in the data or the codes, or is it generative in name while merely transcribing what was already evident?

T2: Auditable process versus grounded conclusion (a trace of reasoning is not proof it was right). The audit trail promises that a reviewer can walk backward from any claim to the transcript segments that prompted it — the method's guarantee of grounding. But the trace is the researcher's own contemporaneous narrative of how they reasoned, and it certifies transparency of process, not correctness of conclusion: a wrong interpretation, diligently memoed, is fully auditable and traces cleanly back to selectively-read evidence. Walking the trail confirms the analyst took those steps from those passages; it does not confirm the passages compelled the reading or that a different analyst would reach it. Auditability is to grounding as reliability is to validity — necessary, visible, and easily mistaken for the stronger property it does not deliver. Diagnostic: Does the audit trail show that the conclusion was forced by the evidence, or only that the analyst arrived at it from evidence they chose to foreground?

T3: Contemporaneous externalization versus premature crystallization (writing can freeze a category too soon). The commitment that reasoning be written at the moment of the analytic move prevents post-hoc reconstruction, but it has a cost the method underweights: articulating an interpretation in prose tends to fix it, and the pressure to leave a dated trace can push an analyst to commit a candidate category to writing before it has ripened, crystallizing a reading that further data would have dissolved. Some interpretive work matures best held loosely and un-articulated; forcing it into a memo early can foreclose the ambiguity that was doing useful work. The externalization requirement trades the risk of lost reasoning against the risk of prematurely hardened reasoning, and the method's insistence on writing-now does not price the second. Diagnostic: Is writing this memo now capturing a genuine analytic move, or prematurely crystallizing a still-forming interpretation that would benefit from staying provisional?

T4: Transmissible audit trail versus authored interpretation (a quasi-positivist standard in an interpretive tradition). The memo corpus lets a departing analyst hand off the work intact and lets a skeptical auditor assess whether findings are "grounded rather than imposed" — the Lincoln-Guba trustworthiness ideal. But qualitative interpretation is, in much of the same tradition, avowedly perspectival and authored: the researcher's situated reading is a feature, not a defect to be audited away. The demand for a transmissible, backward-walkable trace imports a standard of inter-subjective checkability that sits in tension with the interpretivist premise that the analysis is inseparable from the analyst. The more the memo corpus is built to satisfy an external auditor, the more it pulls toward a documentary objectivity the method elsewhere disclaims. Diagnostic: Is the memo trail serving genuine interpretive discovery, or being shaped to perform an auditability that treats situated interpretation as if it should be reader-independent?

T5: No-memo-means-skipped versus unwritten insight (equating the trace with the analysis). The diagnostic reads a category with no dated memo as a sign the analytic move was skipped or reconstructed after the fact. But this equates the written trace with the analysis itself, penalizing the real phenomenon of unwritten cognition: a skilled analyst may genuinely discover a category while reading, driving, or discussing, and memo it later without the insight being any less grounded. The method's own commitment forces a choice — either such insight is illegitimate (implausible) or it is legitimate but invisible to the audit (undermining the trace-equals-analysis premise). Treating the absence of a memo as the absence of thinking mistakes the medium for the act. Diagnostic: Does a missing memo indicate the analytic move never happened, or that a genuine unwritten discovery was recorded late — and can the audit tell these apart?

T6: Autonomy versus reduction (a grounded-theory method, or externalised intermediate cognition). The analytic memo transfers as a complete method within qualitative inquiry — the memo typology, the code-to-integrative progression, saturation and constant-comparison, the Glaser-Strauss-Charmaz apparatus all carry across grounded theory, ethnography, and narrative inquiry. But one level up, its portable structure is externalised intermediate cognition during inquiry: a dated, navigable corpus of contemporaneous reasoning conferring auditability, generativity, and revisability — the parent under which lab notebooks, Architecture Decision Records, reviewer memos, and retrospective notes all sit as siblings, not exports. An ADR shares the shape while carrying none of the grounded-theory furniture. The tension is one of level: the named practice is a full method in its home, but the cross-domain lesson belongs to the externalised-cognition / documentation / audit-trail parent, and calling an ADR "an analytic memo" over-reads a shared shape as a shared method. Diagnostic: Resolve toward the externalised-intermediate-cognition parent (documentation / audit-trail) when carrying the lesson to science, engineering, law, or policy; toward "analytic memo" only where the grounded-theory machinery — memo typology, memo-to-theory progression, saturation — is actually in use.

Structural–Framed Character¶

The analytic memo is framed-leaning on the structural–framed spectrum — off the structural side by a clear margin, though it never reaches the framed pole of a normative verdict, because at its core is a portable cognitive-practice structure rather than a classification of right and wrong. The criteria run consistently framed with one mixed. Evaluative_weight is low and functional rather than moral: the concept carries a methodological-quality valence — an analysis with an intact audit trail is "grounded rather than imposed," a memo can be genuine discovery or busywork (T1) — but this is craft-and-rigor evaluation, not a verdict on conduct or truth, so evaluative weight leans structural. Human_practice_bound points hard framed and is the decisive mark: the analytic memo is constituted by the human practice of qualitative inquiry and dissolves without it — it requires a researcher doing interpretive work over time, a body of evidence to sit above, and a final claim to sit below; strip the inquiring practice and there is no memo, only text. There is no observer-free analytic memo. Institutional_origin is framed: the entry is furniture of a specific methodological tradition — Glaser–Strauss–Charmaz grounded theory, the Lincoln–Guba trustworthiness standard, the memo typology and memo-to-theory progression — a scholarly apparatus, not a fact of nature. Vocab_travels points framed: code/theoretical/operational/integrative memo, theoretical sampling, constant comparison, saturation are pinned to qualitative-methodology substrate and lose their referents off it. Import_vs_recognize is bimodal in the entry's own terms: within qualitative inquiry the practice transfers as a complete method (recognition across grounded theory, ethnography, phenomenology, narrative inquiry, action research), but beyond it the sibling artifacts (lab notebooks, ADRs, reviewer memos) are co-instances of the parent, not exports — calling an ADR "an analytic memo" over-reads a shared shape as a shared method.

The portable structural skeleton is a single idea — externalised intermediate cognition during inquiry: a dated, authored, navigable corpus of contemporaneous reasoning, laid down at the moment of the analytic or design move, that confers auditability, generativity, and revisability. That skeleton is genuinely portable and is carried by the parent documentation / audit-trail (externalised cognition), under which lab notebooks, Architecture Decision Records, and retrospective notes all sit as siblings. It is what tempts a more structural reading, but it does not pull the analytic memo off its framed-leaning position, because that skeleton is exactly what the memo instantiates from its parent, not what makes the named grounded-theory practice travel: the cross-domain reach belongs to the externalised-cognition parent, while the memo's distinctive cargo — the memo typology, the code-to-integrative progression, theoretical sampling, constant comparison, and saturation — is the qualitative-research furniture that stays home. Its character: an evaluatively functional, tradition-constituted research method wholly dependent on the practice of inquiry, structural only in the externalised-intermediate-cognition skeleton it borrows from the documentation parent and dresses in grounded-theory machinery that does not leave qualitative methodology.

Structural Core vs. Domain Accent¶

This section decides why the analytic memo is a domain-specific abstraction and not a prime — and, unusually, the case turns on level rather than on metaphor-versus-mechanism.

What is skeletal (could lift toward a cross-domain prime). Strip the grounded-theory apparatus away and a thin relational structure survives: an inquirer externalises intermediate reasoning in a dated, authored, navigable corpus at the moment of the analytic or design move, so that the reasoning between raw inputs and finished outputs is laid down while the work is being done rather than reconstructed afterward — conferring auditability (walk backward from any claim to its evidence), generativity (writing is where structure is found), and revisability (a recorded reading can be transparently changed). Stated that abstractly the pieces are portable — an intermediate written trace sitting between inputs and conclusions, laid down contemporaneously, indexed so it can be walked. This is genuinely substrate-portable, which is exactly why it recurs as the parent the analytic memo instantiates, documentation / audit-trail (externalised cognition), and why it independently co-instantiates as lab notebooks, Architecture Decision Records, reviewer memos, working-paper drafts, and retrospective notes across science, engineering, law, and policy. But that skeleton is the core the memo shares with all its siblings, not what makes it the analytic memo.

What is domain-bound. Almost everything that makes the concept the analytic memo in particular is qualitative-research furniture that does not survive extraction. It requires an interpretive-inquiry substrate: a researcher coding transcripts and field notes, a body of evidence to sit above, and a final theoretical claim to sit below. Its distinctive content is the grounded-theory machinery — the memo typology (code / theoretical / operational / integrative, sorted by scope and function), the memo-to-theory progression (a week-three code memo feeding a week-five category-relationship memo feeding the integrative memos that become the theory), theoretical sampling by memo, constant comparison, saturation criteria, and the Glaser–Strauss–Charmaz and Lincoln–Guba trustworthiness apparatus. The decisive test: remove the interpretive-inquiry practice and none of this holds — an ADR shares the dated-externalised-revisable shape but carries no theoretical sampling, no constant-comparison memo forms, no saturation, no memo-to-theory progression, so it is a sibling, not a stripped-down analytic memo. Import the memo typology and progression into a lab notebook and they have no referents; what is left is the bare externalisation function, which is the parent, not this entry.

Why this does not clear the prime bar. A prime is a relational structure whose vocabulary travels and whose transfer is recognition of the same mechanism. The analytic memo's transfer is bimodal, but the boundary is one of level, not of mechanism-versus-analogy. Within qualitative methodology it transfers as a complete method — the typology, the progression, saturation, constant comparison all carry intact across grounded theory, ethnography, phenomenology, narrative inquiry, and action research, and the vocabulary moves without translation because the substrate is one interpretive-inquiry practice. Beyond it, the transfer does not fail into metaphor so much as route up a level: the externalised-intermediate-cognition pattern recurs literally — not analogically — as lab notebooks, ADRs, and reviewer memos, but it recurs as the parent, with the analytic memo's own machinery left behind. So when the cross-domain lesson genuinely is needed — externalise your intermediate reasoning at the time of inquiry and your conclusions become auditable, your structure discoverable, your revisions transparent — it is already carried, in more general form, by documentation / audit-trail, under which the analytic memo and the lab notebook and the ADR all sit as cousins. The cross-domain reach belongs to that parent; calling an ADR "an analytic memo" over-reads a shared shape as a shared method, and the entry's distinctive cargo — memo typology, memo-to-theory progression, theoretical sampling, saturation — is qualitative-research baggage that should stay home.

Relationships to Other Abstractions¶

Current abstraction Analytic Memo Domain-specific

Parents (2) — more general patterns this builds on

Analytic Memo is a kind of Memoing Prime

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

Analytic memo contains interpretation because writing it recovers and revises meaning from transcripts, fieldnotes, codes, and other evidence under an evolving framework.

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

Action Research Domain-specific is part of, typical Analytic Memo

Action research typically contains analytic memos recording how observed consequences changed interpretation, practical choice, and theoretical claim between cycles.
Axial Coding Domain-specific is part of Analytic Memo

Axial coding contains analytic memoing because the grounded-theory procedure externalizes proposed relations, comparisons, revisions, and the density-to-core handoff while its map develops.
Thematic Analysis Domain-specific is part of, typical Analytic Memo

Thematic analysis typically contains analytic memos that externalize how codes become candidate themes, are revised against the corpus, and acquire final definitions.

Hierarchy paths (2) — routes to 2 parentless roots

Analytic Memo → Memoing → Logging → Observability

Show alternative path (1)

Not to Be Confused With¶

Codebook. The definitional artifact of the same coding workflow — "this code means this" — sitting beside the memo but doing the opposite job: it fixes stable definitions, while the memo records unstable, in-progress interpretation ("here is what I think is happening, and what I am unsure of"). They are complementary, not rival; conflating them folds the analytic reasoning into a glossary entry that records a decision without the thinking that produced it. Tell: does the document define a label for reuse (codebook) or reason toward a category and expose its open questions (memo)?
Field notes. The ethnographer's contemporaneous record of what was observed — closer to raw evidence than to interpretation. The memo sits above field notes as the intermediate interpretive term; a field note captures the scene, a memo reasons about what, across scenes, it might mean. Tell: is the writing a record of what happened in the field (field notes) or a dated interpretation of what the accumulating records add up to (memo)?
Reflexive / research journal. A related qualitative artifact recording the researcher's own positioning, feelings, and biases — reflexivity about the inquirer, not analysis of the data. It shares the dated, personal, contemporaneous form but its object is the self, not the emerging category structure. Tell: does the entry track the researcher's subjectivity and its influence on the reading (reflexive journal), or advance a claim about the evidence and its coding (analytic memo)?
Architecture Decision Record / lab notebook (sibling co-instances). Dated, externalised, revisable records of reasoning-in-progress in software and bench science — genuine siblings, but co-instances of the same parent, not exports of this entry. They share the shape while carrying none of the grounded-theory machinery: no theoretical-sampling-by-memo, no constant comparison, no saturation, no memo-to-theory progression. Tell: is the grounded-theory apparatus (typology, memo-to-theory progression, saturation) actually in use (analytic memo), or only the bare externalise-your-reasoning shape (an ADR or lab notebook)?
The externalised-intermediate-cognition parent (documentation / audit-trail). The substrate-neutral pattern the memo instantiates — a dated, navigable corpus of contemporaneous reasoning conferring auditability, generativity, and revisability — under which the analytic memo, the lab notebook, the ADR, and the reviewer memo all sit as cousins. It is the parent, treated more fully in Knowledge Transfer and Structural Core vs. Domain Accent, that carries the cross-domain lesson. Tell: to carry the lesson to science, engineering, law, or policy, invoke the externalised-cognition parent; "analytic memo" applies only where the qualitative-inquiry machinery operates.

Neighborhood in Abstraction Space¶

Analytic Memo sits in a sparse region of the domain-specific corpus (62^nd percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Qualitative Research Rigor & Reflexivity (14 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-07-12