# Capture Without Creating a Second Inbox: Academic Evidence Dossier

**Research snapshot:** October 10, 2026  
**Perspective:** Academic  
**Decision supported:** Which capture rules reduce lost ideas without building an unprocessed backlog?  
**Primary transfer target:** Knowledge workers, founders, and managers  
**Geographic lens:** Czech Republic / EU and United States where materially different

## Executive decision and uncertainty

### Bottom line

The evidence does **not** support either extreme:

- **“Capture everything and sort it out later.”** External reminders and note-taking can protect intentions and reduce some cognitive burden, but every captured item creates a future information-management obligation. Workplace PIM studies repeatedly show accumulation, heterogeneous filing behavior, and substantial unprocessed stores; educational and laboratory evidence also shows that external storage can shift memory away from internal retention. citeturn23search4turn22search9turn23search3
- **“Classify everything correctly at the moment of capture.”** Categorization itself imposes judgment costs, categories are often ambiguous before future use is clear, and older PIM studies show strong individual variation in filing strategies. There is no strong professional-task evidence that mandatory immediate taxonomy produces better overall outcomes than low-friction capture followed by bounded processing. citeturn22search0turn22search4turn22search9

The strongest defensible policy is therefore a **bounded capture-first system with immediate minimal interpretation, automatic provenance, and enforced disposal or promotion**.

In practical terms:

> **Capture selectively; interpret enough to preserve meaning; classify only as much as the next use requires; route commitments out of the knowledge inbox immediately; and never allow an unprocessed capture queue to become permanent storage.**

The key distinction is **“classification can wait” ≠ “thinking can wait.”** A raw fragment without provenance or expected use is cheap to create but expensive to understand later. Conversely, forcing a folder, tag taxonomy, PARA category, or Zettelkasten relationship at the instant an idea appears can make capture unnecessarily costly. Early office-information research explicitly identified categorization difficulty as a reason people use piles rather than neat filing systems; later cross-tool work likewise found substantial variation in filing and piling strategies. citeturn22search4turn22search9

A defensible default capture record is therefore only:

**content + source/provenance + date + one small piece of interpretation (“why might I need this?”)**

Everything else—taxonomy, links, summarization, deduplication, destination suggestions—can often be postponed or automated.

### Confidence by proposition

| Proposition | Assessment | Why |
|---|---|---|
| External reminders can help people remember delayed intentions | **High** | Direct experimental prospective-memory evidence, including four online experiments with **N = 1,196** in Gilbert's study. citeturn23search0turn23search4 |
| A specific plan can reduce cognitive interference from an unfinished goal | **Moderate–high** | Multiple experiments by Masicampo & Baumeister; laboratory transfer is the main limitation. citeturn25view3 |
| Merely writing something into an inbox provides the same benefit | **Low / unsupported** | The planning evidence concerns resolved intentions and specific plans, not undifferentiated note capture. citeturn25view3 |
| Capturing more is always better | **Contradicted as a general claim** | Offloading has trade-offs; external storage can weaken unaided memory, and PIM stores accumulate. citeturn23search3turn22search9 |
| Immediate categorization is always better | **Unsupported** | Categorization has cognitive cost; available PIM studies are mainly qualitative, observational, or interface-specific rather than decisive causal comparisons. citeturn22search0turn10search15 |
| Search means organization is unnecessary | **Unsupported** | Classic PIM studies found strong navigation preferences even after desktop search improved; technology has changed, so this is a boundary condition rather than a timeless law. citeturn22search3turn22search7 |
| One universal inbox is scientifically superior | **No direct evidence found** | Some empirical work documents cross-tool fragmentation and email-as-storage, but does not establish a universal-inbox optimum. citeturn22search9turn1search16 |
| PARA, GTD, Zettelkasten, or Inbox Zero is scientifically superior overall | **No direct comparative evidence found in this review** | These are productivity/organization frameworks; their prescriptions should not be confused with experimental evidence about prospective memory, learning, or retrieval. GTD's own current description is provider/author documentation, not a controlled evaluation. citeturn21search0 |
| Bigger AI context windows remove the need for curation | **False as a general assumption** | Long-context models can fail to use relevant material robustly depending on position; retrieval/citation systems also have measurable support failures. citeturn18view2turn18view1 |

The largest uncertainty is exactly the one most relevant to the decision: **there appears to be little direct longitudinal experimental evidence in professional knowledge work comparing “immediate classification” against “capture first, triage later” while jointly measuring lost ideas, backlog growth, retrieval success, and maintenance effort.** Much of the usable evidence must therefore be triangulated from prospective memory, note-taking, PIM, information overload, and information-retrieval research rather than treated as one unified causal literature. citeturn23search4turn22search9turn23search2turn13search12

## Evidence synthesis around the decision

The most important conceptual separation is between **human memory**, **personal information management**, and **retrieval technology**. They solve different problems.

**Cognitive offloading can be useful, especially for intentions.** Gilbert's *Strategic offloading of delayed intentions into the external environment* reports four online experiments totaling **N = 1,196** using a task in which people could externalize intentions by creating reminders. The work supports the broader proposition that people strategically use external cues to support prospective memory, with reminder use related to metacognitive judgments about unaided memory. The same task also predicted fulfillment of a naturalistic intention embedded in everyday activity up to a week later. That is meaningful evidence for writing down “remember to do X,” but not evidence that every observation, link, quote, or speculative thought should be permanently captured. citeturn23search0turn23search4

A related but different result comes from Masicampo and Baumeister. Across several experiments, unfulfilled goals were associated with intrusive thoughts, greater accessibility of goal-related material, and impaired performance on an unrelated task; allowing participants to form a **specific plan** eliminated these interference effects in the reported experiments. The important operational implication is not “dump it into an inbox.” It is closer to **resolve the intention enough to know what happens next**. A note saying “pricing???” is not equivalent to a plan saying “Ask Petra for the enterprise pricing assumptions at Monday's product meeting.” citeturn25view3

This distinction matters because externalization can also change what people remember internally. Eskritt and Ma tested note-taking as a naturalistic case of intentional forgetting. In their first experiment, participants using notes while learning card locations subsequently had the notes unexpectedly removed; the study found evidence consistent with people relying on the external store rather than encoding all of the information internally. The result is a laboratory memory task, not professional knowledge work, but it establishes an important boundary condition: **external capture is not free additional memory; it can substitute for biological memory.** citeturn23search3turn23search7

The educational note-taking literature reinforces the need for caution. Kobayashi's 2005 meta-analysis covered **57 note-taking versus no-note-taking comparisons** and characterized the encoding benefit of note-taking as positive but modest and contingent on factors such as presentation and testing conditions. A separate meta-analytic literature examines combined note-taking and review. These studies concern learning from instruction, mostly not founders deciding which customer insight to preserve, so transfer should be limited to the narrower proposition that *the cognitive consequences of note-taking depend on what the person does during and after capture*. citeturn23search2turn9search5

The professional-information evidence points to another issue: **keeping is itself work.** Malone's 1983 interviews with professional and clerical office workers found that physical information organization served a reminding function as well as a retrieval function, and argued that categorization difficulty helped explain the use of piles. This is early qualitative evidence and cannot estimate an optimal capture policy, but it directly undermines the assumption that filing is cognitively costless. citeturn22search0turn22search4

Boardman and Sasse provide unusually useful longitudinal workplace-adjacent evidence. Their CHI study covered files, email, and bookmarks: Phase 1 involved **31 participants**, and the longitudinal Phase 2 followed **8 participants**, with snapshots every two weeks for the first three months and a final snapshot five months later; average participation was **286 days**. Participants were experienced computer users but were heavily drawn from university research/student environments, so this is not a representative sample of executives or contemporary SaaS-heavy teams. citeturn22search9turn22search13

The descriptive backlog numbers are revealing. Among the longitudinal participants, the reported mean numbers of “unfiled” items were approximately **66 files, 828 emails, and 44 bookmarks**; the corresponding mean proportions of the collections marked unfiled were roughly **3%, 41.6%, and 38.8%**. These numbers are from 2004-era systems and should not be projected numerically onto 2026 software, but they demonstrate the basic stock-flow problem: an easy arrival channel plus weak processing can produce a very large residual store. citeturn5view1

Studies of “keeping found things found” show why users create these stores in the first place. Participants kept web information through several mechanisms—including bookmarks, self-email, paper notes, and printing—and no single observed mechanism fulfilled all keeping/refinding needs. Self-email is particularly instructive for the present question: it turns a communication inbox into a reminder/reference mechanism, but that only works if the person later revisits and processes the inbox. citeturn1search0turn1search16turn1search4

Search technology does not automatically erase this management problem. Bergman and colleagues compared improved desktop search with older search systems in Windows and Mac settings. Participants still reported a strong preference for navigation: estimates placed navigation at roughly **56–68% of file-retrieval events** and search at approximately **4–15%**, with search often used as a fallback. Because this work predates today's semantic search and LLM interfaces, the exact percentages are historically bounded; the robust lesson is narrower: **better search should not simply be assumed to make filing, context, or provenance irrelevant.** citeturn22search3turn22search7

Nor is there convincing evidence for a universally correct taxonomy. Civan and colleagues compared folder- and tag-based organization in a small within-subject exploratory study in which participants experienced both conditions and kept diaries; later work likewise found substantial folder preferences in specific interfaces. Those studies are useful evidence that representation matters, but their small samples and dependence on contemporary Gmail/Hotmail-style interfaces make them poor grounds for saying “folders beat tags,” much less “PARA beats Zettelkasten.” citeturn10search15turn10search33

At a more general level, information-overload reviews describe overload as a function not merely of item count but of information characteristics, the receiver, task/process demands, organizational design, and technology. That makes “capture as much as possible because storage is cheap” an incomplete optimization objective: **storage cost can approach zero while interpretation and decision costs remain scarce.** Eppler and Mengis's cross-disciplinary review and Roetzel's later bibliometric review both treat overload as a multi-factor phenomenon rather than a simple storage-capacity issue. citeturn13search6turn13search12

This produces the central decision logic:

**The scarce resource is not bytes. It is future human judgment.**

Capture rules should therefore minimize the expected sum of two losses:

\[
L = L_{\text{missed}} + L_{\text{processing}} + L_{\text{retrieval}} + L_{\text{staleness}}
\]

where:

- \(L_{\text{missed}}\) = value lost because a useful intention/evidence item was not captured;
- \(L_{\text{processing}}\) = time and cognitive cost spent clarifying, classifying, deduplicating, and reviewing;
- \(L_{\text{retrieval}}\) = value/time lost when stored material cannot be found or understood;
- \(L_{\text{staleness}}\) = harm from retrieving obsolete, contradictory, or decontextualized material.

This formula is **a decision model introduced in this dossier, not a published empirical equation**. The literature supports the existence of the component trade-offs, not these particular weights or functional form. citeturn23search4turn22search9turn13search12

## Knowledge lifecycle and automation boundary

A useful capture system should be modeled as a lifecycle, not as a notebook:

\[
\text{capture}
\rightarrow
\text{interpretation}
\rightarrow
\text{provenance}
\rightarrow
\text{storage}
\rightarrow
\text{retrieval}
\rightarrow
\text{review/update}
\rightarrow
\text{archive/delete}
\]

The important design question at each transition is not “can AI automate this?” but **“what is the cost of being wrong, and is the system preserving enough evidence for a person to reverse the decision?”**

| Lifecycle transition | Human judgment normally required | Good automation candidates | Failure to guard against |
|---|---|---|---|
| **Capture** | Whether something is plausibly useful; whether recording is appropriate | Voice/text capture, transcription, timestamp, meeting/document identity | Capturing everything because it is cheap |
| **Interpretation** | Why it matters; commitment vs reference vs speculation; intended future use | Candidate summary, entities, suggested next action | AI turning an ambiguous fragment into falsely precise “knowledge” |
| **Provenance / source** | Usually little judgment if source is known; judgment for contested claims | URL, document ID, author/speaker, timestamp, version, quoted span | Orphan facts with no route back to evidence |
| **Storage** | Which items deserve durable promotion; source-of-truth choice | Indexing, deduplication, candidate routing, semantic embeddings | Multiple divergent copies becoming competing truths |
| **Retrieval** | Whether returned evidence actually answers the present question | Keyword/semantic search, RAG, ranking, query expansion | Relevant source omitted; irrelevant or stale source confidently synthesized |
| **Review / update** | Resolve contradictions; decide which evidence supersedes which | Detect age, conflicts, changed source, broken links; propose refresh | Silent replacement of old facts without preserving history |
| **Archive / delete** | Consequential/legal records; uncertain high-value material | TTL for low-value queue items, duplicate collapse, stale-candidate flags | Permanent hoarding or irreversible deletion of authoritative evidence |

This allocation is a **design recommendation**, not an experimentally validated universal division of labor. It follows from evidence that classification is cognitively non-trivial, provenance/retrieval are distinct PIM problems, and current AI retrieval/context systems remain fallible. citeturn22search0turn22search9turn18view2turn18view1

### AI does not collapse the lifecycle into “remember everything”

RAG is specifically valuable because it separates a model's parametric knowledge from an external non-parametric information store. Lewis et al.'s 2020 RAG paper used a dense Wikipedia index and demonstrated improvements over a parametric-only baseline on several knowledge-intensive benchmarks. Conceptually, that is an argument for **retrieving selected external evidence at use time**, not for inserting every historical item into every prompt. citeturn18view3

Long context is not equivalent to reliable recall. Liu et al. evaluated models on multi-document QA and key-value retrieval and found that performance could change substantially based on where relevant information occurred in the context; information in the middle was often used less reliably than information at the beginning or end, including by explicitly long-context models. The study concerns the models available around 2023–2024, so it should be treated as a demonstrated failure mode rather than an eternal property of every 2026 model. citeturn18view2

Citations improve inspectability but do not eliminate evidence failures. In the ALCE benchmark, Gao et al. evaluated answers along fluency, correctness, and citation quality; on ELI5, even the best evaluated systems lacked complete citation support **50% of the time**. That is a historical benchmark result, not an estimate of current ChatGPT, Claude, or other 2026 systems. It nevertheless demonstrates why “the answer has citations” is not equivalent to “every important claim is supported.” citeturn18view1

Persistent AI memory introduces a further distinction between **assistant memory and canonical evidence**. OpenAI's current documentation states that saved memories can be stored separately from chat history; deleting the original chat does not necessarily delete the associated saved memory, and fully removing remembered information may require deleting it from multiple underlying sources. It also says memory may draw on past chats, saved memories, files, and connected apps, depending on plan and region. These are provider-documented product semantics, not empirical evidence that memory improves professional decision quality. citeturn25view1

That architecture suggests a conservative rule:

> **AI memory should usually be treated as a personalization/cache/index layer, not as the authoritative record of a fact, decision, customer requirement, contract term, or research result.**

The durable object should preserve a route to the canonical source: document/email/meeting, author or speaker where relevant, date, version, and ideally the exact supporting passage. This recommendation is also compatible with RAG's explicit separation between retrieved external knowledge and model parameters. citeturn18view3turn25view1

For Czech/EU contexts, automatic indiscriminate capture of personal data also creates a legal dimension beyond productivity. GDPR Article 5 requires personal data to be adequate, relevant, and limited to what is necessary; accurate where necessary; and identifiable no longer than necessary for the processing purpose, subject to stated exceptions. The Regulation's recitals also discuss establishing time limits for erasure or periodic review. Thus, for captures involving identifiable people—customer calls, employee notes, CRM material, meeting transcripts—**“keep everything forever because AI might use it someday” can conflict with data-minimization and storage-limitation principles.** citeturn19view0turn19view1turn19view2

I did **not** perform a current 50-state US privacy-law survey, so this dossier deliberately does not claim an equivalent or opposite US-wide rule. The cognitive and PIM evidence itself does not provide a meaningful Czech-versus-US distinction; the material difference identified here is the explicit EU/GDPR governance layer.

## Decision rules and observable evaluation

The best-supported operating model is a **single logical intake surface with multiple physical entry points**, rather than a demand that every idea literally enter one app.

The distinction matters. A voice note, starred email, meeting highlight, mobile quick capture, and browser clipping can all feed one processing view without forcing the user to copy everything into a second repository. Cross-tool PIM research shows that people naturally use multiple tools and strategies, while older “keeping found things found” work found no single keeping method that satisfied every function. citeturn22search9turn1search16

A useful rule set is:

**Admission rule — capture only when future value is plausible.** Keep an item when at least one is true: it represents a commitment/intention; it is evidence likely to influence a foreseeable decision; it contains original thinking that cannot simply be re-found; or its future retrieval cost is expected to be materially higher than capture cost. A generic article that can be found again and has no current use normally stays at its source. This is a decision heuristic derived from PIM and overload evidence, not a validated universal cutoff. citeturn1search0turn13search12

**Commitment rule — tasks leave the knowledge inbox immediately.** An intention with a real next action should become a task, calendar event, or explicit reminder, with the evidence note linked if needed. This is the most direct transfer from prospective-memory experiments and planning research: reminders and concrete plans have better evidence than vague storage as mechanisms for supporting future action. citeturn23search4turn25view3

**Minimum-context rule — interpret now, classify later.** Preserve content, provenance/date, and a brief statement of expected use. Do not require a perfect folder, taxonomy, PARA area, Zettelkasten link network, or tag set during capture unless the destination is obvious. Malone's categorization argument and cross-tool PIM evidence support treating classification as a nonzero cognitive cost. citeturn22search4turn22search9

**No-orphan rule — claims should point backward.** For externally sourced evidence, save a pointer to the original item rather than only an AI summary or paraphrase. This becomes more important as AI is used for synthesis because retrieval and citation systems can still omit or incompletely support claims. citeturn18view1turn18view3

**Queue-not-library rule — an inbox has an expiry condition.** Unprocessed capture is a temporary state. Every item ultimately becomes one of: action/reminder, promoted durable reference/evidence, intentionally deferred item, archive, or deletion. “Still sitting in capture” is not a sixth permanent category. Boardman and Sasse's descriptive results illustrate what happens when accumulation outpaces organization, although they do not test this rule experimentally. citeturn5view1turn22search9

**Promotion rule — durable knowledge requires a higher bar than capture.** AI may propose a promotion, summary, link, duplicate merge, or task, but a human should usually approve promotion of ambiguous material into an authoritative project record, CRM fact, decision log, policy, or persistent AI memory when errors matter. This is an engineering inference from current retrieval/memory limitations, not a directly tested cognitive effect. citeturn18view1turn18view2turn25view1

**Forgetting rule — make disposal an intended system behavior.** Low-value provisional captures should have a review or expiry policy rather than accumulate indefinitely. For personal data in the EU, this also aligns with GDPR's data-minimization and storage-limitation principles; exact retention periods depend on purpose and legal obligations, so no universal “30-day rule” is implied. citeturn19view0turn19view1

### Backlog needs a stock-flow constraint

Let:

- \(C_t\) = new captures during period \(t\)
- \(P_t\) = items processed/promoted/routed during period \(t\)
- \(D_t\) = items intentionally discarded or expired during period \(t\)
- \(B_t\) = unprocessed backlog at end of period \(t\)

Then:

\[
B_t = B_{t-1} + C_t - P_t - D_t
\]

A capture system is **flow-stable** over a review window \(W\) when:

\[
\sum_{t \in W} (P_t+D_t) \geq \sum_{t \in W} C_t
\]

or equivalently:

\[
\Delta B_W \leq 0
\]

after startup transients.

These equations are accounting identities introduced here, not published psychological laws. Their practical value is that they make “I will process this later” falsifiable. If the capture rate persistently exceeds the resolve/discard rate, backlog is mathematically guaranteed to grow regardless of app, taxonomy, or AI quality.

Count alone is insufficient. A system with 100 raw captures processed tomorrow may be healthier than one with 15 items that have been ignored for six months. At minimum measure:

| Metric | Operational definition |
|---|---|
| **Capture friction** | Median and p90 seconds from decision-to-capture to return-to-primary task |
| **Capture volume** | Captures/person/week |
| **Triage latency** | Median and p90 time from capture to explicit fate |
| **Backlog stock** | Number of items with no explicit fate |
| **Oldest unprocessed age** | Age of oldest queue item |
| **Flow balance** | \((P+D)-C\) per review period |
| **Duplicate-capture rate** | Duplicate captures / total captures |
| **Discard/archive rate** | Items deliberately discarded or archived / processed items |
| **Promotion rate** | Captures promoted into durable knowledge / captures processed |
| **Provenance completeness** | Captures with recoverable source + date / relevant externally sourced captures |
| **Retrieval success** | Defined work questions for which correct supporting evidence is retrieved within a fixed time |
| **Stale-evidence error rate** | Decisions/tests using material known to have been superseded / evaluated decisions |
| **Maintenance burden** | Human minutes/week spent capturing, triaging, cleaning, and repairing the system |

No universal evidence-based threshold emerged from this review for “acceptable” seconds of capture friction, backlog size, or triage latency. Those should be treated as **local service-level objectives**, then optimized against actual task success rather than copied from a productivity author.

A useful field experiment can compare three workflows rather than argue about them abstractly:

| Condition | Capture behavior |
|---|---|
| **Immediate classification** | Capture requires destination/category before saving |
| **Bounded capture-first** | Content + provenance + expected-use cue now; classification deferred; processing deadline enforced |
| **Low-friction capture-all** | Almost anything may be captured; minimal mandatory interpretation |

For each condition, evaluate **lost/reconstructed items, retrieval success, provenance completeness, backlog growth, duplicates, stale-use errors, and maintenance minutes**. A crossover design over repeated professional tasks is preferable to measuring subjective “feeling organized” alone. Carryover between conditions is a methodological problem because old captures remain available, so team-level counterbalancing or clean project-specific stores would produce better comparisons.

The observable end point should be the work, not the notebook:

> **Did the person retrieve the right evidence, understand where it came from and when, recognize uncertainty or staleness, make the intended decision, and maintain the system at an acceptable cost?**

That evaluation logic is consistent with the PIM literature's separation of keeping, organization, refinding, and use rather than assuming that collection size itself indicates success. citeturn1search0turn22search9turn22search7

A portable measurement asset for such a test is:

```csv
participant_id,project_id,condition,capture_id,captured_at,triaged_at,capture_seconds,source_present,source_date_present,expected_use_present,final_fate,duplicate_of,retrieval_test_id,retrieved_correct_item,retrieval_seconds,stale_item_used,intended_decision_completed,maintenance_minutes
```

This is a dossier-created evaluation schema, not an external validated instrument.

## Worked example and context transfer

Consider a founder in a customer call. The customer says:

> “Our CFO will probably require export controls before we can deploy this company-wide.”

The goal is to preserve a potentially important signal without creating another pile of meeting snippets.

**Bad capture-first implementation:** the transcription system automatically saves every sentence from every meeting into a permanent “Second Brain.” Nothing distinguishes commitment, hypothesis, objection, fact, or small talk. Later, semantic search can retrieve all of it—but it can also surface stale, speculative statements. Storage is solved; knowledge management is not.

**Bad immediate-classification implementation:** while still in the conversation, the founder must decide whether the sentence belongs under `Areas/Security`, `Projects/Enterprise`, `Sales/Objections`, `Product/Compliance`, or a Zettelkasten concept. The classification may be premature, and the interruption can be more expensive than the note deserves. Categorization difficulty is precisely the kind of problem identified in classic PIM work. citeturn22search4

**Bounded capture implementation:**

| Stage | Result |
|---|---|
| Capture | “CFO may require export controls for company-wide deployment.” |
| Automatic provenance | Customer/account, meeting ID, speaker, timestamp, call-recording link, date |
| Human micro-interpretation | “Potential enterprise blocker; affects security/product roadmap. Needs verification.” |
| Commitment extraction | Candidate task: “Confirm exact export-control requirement with CFO/security contact.” |
| Human approval | Task goes to the task system; it does **not** remain an implicit promise inside notes |
| Storage | Raw evidence remains linked to the meeting; no duplicate canonical copy needed |
| Review | If verified by another stakeholder/document, promote requirement to account/project evidence |
| Archive/delete | If disproved or irrelevant, retain only according to the organization's evidentiary/retention need |

The prospective-memory evidence is most relevant to the **approved reminder/task**, not to the archived quote; PIM evidence is most relevant to provenance, keeping and later retrieval; AI evidence is relevant to transcription, extraction, retrieval, and summarization. These mechanisms should not be conflated. citeturn23search4turn1search16turn18view3

An illustrative, explicitly hypothetical operating target could be:

- 20 captures/week;
- 30 seconds of human context per capture = **10 minutes/week**;
- 12 promoted, routed, or otherwise resolved;
- 8 deliberately discarded;
- therefore \(C=20,\; P+D=20,\; \Delta B=0\).

If instead 20 are captured and only 12 resolved per week:

\[
\Delta B = 20 - 12 = +8/\text{week}
\]

After 12 weeks, absent other changes:

\[
B_{\text{added}} = 8 \times 12 = 96 \text{ items}
\]

That is how a “helpful capture habit” becomes a second inbox. The numbers are illustrative assumptions, not literature-derived benchmarks.

### Where Czech and US transfer differs

There is little reason in the reviewed cognitive evidence to prescribe different prospective-memory or note-taking mechanisms to Czech versus US knowledge workers; the studies do not establish a geography-specific cognitive effect. The larger transfer limitations are **student/laboratory versus professional work, old desktop/file systems versus current cloud/AI systems, and individual versus organizational information management**. citeturn23search2turn22search9turn22search7

The concrete Czech/EU difference is governance when captured material contains personal data. Automatic call transcription, AI memory, CRM extraction, and permanent archives should be designed with purpose limitation, minimization, accuracy, retention, and deletion paths in mind under GDPR rather than optimizing purely for maximum future recall. citeturn19view0turn19view2

## Contradictions, framework audit, and unresolved gaps

The evidence contains several tensions that should remain visible rather than be resolved rhetorically.

**Externalize versus remember.** Prospective-memory research supports external reminders, while note-taking experiments show that expected external storage can reduce unaided memory. Those are not contradictory once the objective is specified: a reminder system may be excellent when the goal is *future execution*, while deliberate internal encoding may matter when the goal is *learning*. A founder trying to remember to send a contract and a medical student trying to learn anatomy are optimizing different outcomes. citeturn23search4turn23search3turn23search2

**Low-friction capture versus future processing.** Lowering capture friction plausibly prevents some omissions, but it also makes acquisition cheaper than disposal. The professional PIM evidence shows accumulation problems but does not give a causal dose-response curve telling us how much friction is optimal. citeturn22search9turn5view1

**Search versus organization.** Older PIM research found continued navigation preferences despite better desktop search, but modern semantic retrieval and LLMs materially change the interface. Those historical findings argue against casually assuming search eliminates organization; they do **not** prove that a 2008 folder hierarchy remains optimal in 2026. citeturn22search3turn22search7

**More context versus better AI performance.** Retrieval can improve knowledge-intensive generation, but larger input context does not guarantee robust use of all relevant evidence. RAG, context windows, durable memory, and source-of-truth storage are separate mechanisms. citeturn18view3turn18view2

**Citations versus truth.** Citation-aware generation improves verifiability in principle, but a citation can be incomplete, irrelevant, stale, or insufficient. ALCE explicitly found incomplete support in evaluated systems. citeturn18view1

**Delete versus retain.** Retention can protect future refinding; accumulation creates processing, privacy, and staleness costs. Very recent work by Englefield and Beale specifically studies PIM tactics, strategies, and outcomes, but the primary Oxford Academic article could not be fetched through the inspected HTML endpoint during this research session; I therefore did not use its detailed results as load-bearing evidence. Bibliographic metadata identifies the article as published online December 12, 2025 and subsequently in *Interacting with Computers*. citeturn24search5turn25view0

### Framework audit

**GTD.** David Allen's official description currently specifies five stages: capture, clarify, organize, reflect, engage, and tells users to write, record, or gather what has their attention into a collection tool. That is attributable framework documentation. The cognitive evidence above offers plausible support for externalizing commitments and clarifying plans, but I found no direct evidence in this review establishing the **GTD system as a whole** as scientifically superior to alternative professional workflows. citeturn21search0

An important nuance is that criticizing GTD simply as “capture everything” is incomplete: its own framework requires subsequent clarification, organization, and review. A GTD inbox that is never clarified is not the workflow its documentation describes. citeturn21search0

**PARA.** Forte Labs describes PARA as a general system for organizing digital information into four categories and presents it as a practical productivity framework. Nothing found in the reviewed empirical literature establishes those four categories as a psychologically or retrieval-theoretically optimal partition. It may be a useful convention; that is different from scientific superiority. citeturn20search34turn20search25

**Zettelkasten.** The reviewed note-taking and PIM evidence does not establish Zettelkasten as superior for professional retrieval, decision quality, or backlog prevention. Evidence that note-taking can aid learning under some conditions cannot legitimately be re-labelled as evidence for a specific linked-note architecture. citeturn23search2

**Inbox Zero.** I found no direct controlled evidence that obtaining a literal zero count in an email or capture inbox improves professional decision quality, idea retention, or aggregate productivity. The relevant empirical literature instead supports studying strain, processing behavior, accumulation, interruption, and retrieval separately. A “zero” count may be a useful process constraint, but it is not itself a validated outcome measure.

**AI capture.** Provider documentation establishes that AI systems can persist, retrieve, update, and use context; it does not establish that automatic comprehensive capture improves human decisions. Current OpenAI documentation itself distinguishes memory from underlying sources and notes that memory need not retain every detail. citeturn25view1

### Research gaps that materially affect the recommendation

The highest-value missing study would be a longitudinal professional randomized or counterbalanced comparison of:

\[
\text{immediate classify}
\quad vs \quad
\text{bounded capture-first}
\quad vs \quad
\text{capture-all}
\]

with objectively logged capture time, processing delay, backlog stock, discard rate, retrieval success, source preservation, stale-evidence errors, actual task/decision completion, and maintenance effort.

A second gap is **idea capture specifically**. Prospective-memory studies concern delayed intentions, while educational note-taking studies concern learning. “I had a novel strategic insight and later needed it” sits between these literatures but is not well represented by either.

A third gap is contemporary professional PIM under semantic search and generative AI. Much foundational work predates cloud search, Slack, Notion-like workspaces, automatic meeting transcription, vector retrieval, and persistent LLM memory. Those studies remain useful for identifying human problems, but technology-specific effect sizes should not be treated as current.

A fourth gap is organizational source-of-truth behavior. Personal notes are increasingly downstream of shared systems—CRM, issue trackers, documents, chat, email, code repositories. Copying an artifact into a private “second brain” may improve personal access while worsening organizational provenance and freshness. This plausible trade-off deserves direct empirical study.

## Claim-to-source dossier, article angles, and freshness triggers

The table below separates empirical studies, reviews, framework/provider documentation, and law. “Inspected” means reviewed for this dossier on **2026-10-10**; it does not imply full-text access in every case.

| Claim supported | Source and date | Exact scope / design | Evidence type | Direct URL / DOI | Inspected |
|---|---|---|---|---|---|
| Office organization supports reminding as well as finding; categorization is cognitively difficult | Malone, 1983, *How Do People Organize Their Desks?* citeturn22search0turn22search4 | Interviews/guided investigation of professional and clerical office information organization | Qualitative empirical PIM | https://doi.org/10.1145/357423.357430 | 2026-10-10 |
| People use multiple strategies to keep found web information | Jones et al., 2001, *Keeping Found Things Found on the Web* citeturn1search0 | User behavior around keeping/re-finding web information | Empirical HCI/PIM | https://doi.org/10.1145/502585.502607 | 2026-10-10 |
| Keeping mechanisms include bookmarks, self-email, notes, printing; no one method serves every role | Bruce, Jones & Dumais, 2004 / Bruce 2004 citeturn1search16turn1search4 | Workplace/web keeping and refinding behavior | Empirical PIM | https://doi.org/10.1002/meet.1450410115 | 2026-10-10 |
| Cross-tool PIM strategies vary; unfiled stores can grow substantially | Boardman & Sasse, 2004 citeturn22search9turn5view1 | Phase 1 N=31; longitudinal subset N=8; files/email/bookmarks; average longitudinal participation ~286 days | Longitudinal descriptive empirical PIM | https://doi.org/10.1145/985692.985766 | 2026-10-10; PDF visually inspected |
| Better desktop search did not eliminate navigation preference | Bergman et al., 2008 citeturn22search3turn22search7 | Windows longitudinal comparison and larger Mac comparison; desktop file retrieval | Empirical HCI/PIM | https://doi.org/10.1145/1402256.1402259 | 2026-10-10 |
| Folder-vs-tag organization has been experimentally/exploratorily compared, but context is interface-specific | Civan et al., 2008 citeturn10search15 | Small within-subject comparison over time with participant diaries | Exploratory empirical HCI | https://doi.org/10.1002/meet.2008.1450450214 | 2026-10-10 |
| External reminders support strategic prospective-memory offloading | Gilbert, 2015 citeturn23search0turn23search4 | Four online experiments; **N=1,196**; delayed-intention task; naturalistic intention prediction up to one week | Experimental cognitive psychology | https://doi.org/10.1080/17470218.2014.972963 | 2026-10-10 |
| Specific planning can remove reported cognitive interference from unfinished goals | Masicampo & Baumeister, 2011 citeturn25view3 | Multiple laboratory studies: intrusive thoughts, lexical accessibility, anagrams, planning | Experimental social/cognitive psychology | https://doi.org/10.1037/a0024192 | 2026-10-10 |
| Note-taking has positive but condition-dependent encoding effects in learning studies | Kobayashi, 2005 citeturn23search2 | Meta-analysis of **57 note-taking vs no-note-taking comparisons** | Meta-analysis, education/cognition | https://doi.org/10.1016/j.cedpsych.2004.10.001 | 2026-10-10 |
| External notes can induce reliance on an external memory store | Eskritt & Ma, 2014 citeturn23search3turn23search7 | Laboratory card-memory experiments; note access manipulated | Experimental memory research | https://doi.org/10.3758/s13421-013-0362-1 | 2026-10-10 |
| Cognitive offloading is a broader class of using external action to reduce cognitive demand | Risko & Gilbert, 2016 citeturn6search3 | Review of cognitive-offloading research | Scholarly review | https://doi.org/10.1016/j.tics.2016.07.002 | 2026-10-10 |
| Information overload is multi-factorial, not merely “too many bytes” | Eppler & Mengis, 2004 citeturn13search6 | Cross-disciplinary review: organization science, accounting, marketing, MIS and related work | Literature review | https://doi.org/10.1080/01972240490507974 | 2026-10-10 |
| Information-overload literature spans business administration, business psychology and related disciplines | Roetzel, 2019 citeturn13search12 | Bibliometric/literature review with framework development | Scholarly review | https://doi.org/10.1007/s40685-018-0069-z | 2026-10-10 |
| Retrieval-augmented generation separates parametric generation from an external retrievable index and improved benchmark performance over compared parametric systems | Lewis et al., 2020 citeturn18view3 | RAG using dense Wikipedia retrieval; several knowledge-intensive NLP benchmarks | Primary ML experiment | https://proceedings.neurips.cc/paper/2020/hash/6b493230205f780e1bc26945df7481e5-Abstract.html | 2026-10-10 |
| Long contexts are not necessarily used reliably; position of relevant evidence can affect model performance | Liu et al., 2024 citeturn18view2 | Multi-document QA and key-value retrieval across long contexts | Primary ML experiment | https://doi.org/10.1162/tacl_a_00638 | 2026-10-10 |
| Citation-bearing LLM answers can still lack complete support | Gao et al., 2023 citeturn18view1 | ALCE benchmark; fluency, correctness, citation quality; ELI5 support analysis | Primary ML benchmark | https://doi.org/10.18653/v1/2023.emnlp-main.398 | 2026-10-10 |
| Recent research directly studies professional PIM tactics/strategies/outcomes | Englefield & Beale, online 2025 / issue 2026 citeturn24search5turn25view0 | Current PIM research; substantive full HTML could not be retrieved in this session | Peer-reviewed empirical article; **access limitation** | https://doi.org/10.1093/iwc/iwaf054 | 2026-10-10 |
| GTD prescribes capture → clarify → organize → reflect → engage | David Allen Company, current documentation citeturn21search0 | Description by framework provider; no controlled comparator on page | Productivity-framework documentation | https://gettingthingsdone.com/what-is-gtd/ | 2026-10-10 |
| PARA is presented as an organizing framework, not established here as a scientific optimum | Forte Labs, current site citeturn20search34turn20search25 | Author/provider explanation of PARA | Practitioner framework / author opinion | https://fortelabs.com/ | 2026-10-10 |
| Current ChatGPT memory is distinct from underlying chat/source storage and may draw on several sources | OpenAI, Memory in ChatGPT, updated September 2026 at inspection citeturn25view1 | Official product behavior/documentation | Provider documentation; **not efficacy evidence** | https://help.openai.com/en/articles/8590148-memory-in-chatgpt | 2026-10-10 |
| EU personal-data processing is subject to minimization, accuracy, storage limitation, and security principles | GDPR Article 5, Regulation (EU) 2016/679 citeturn19view0turn19view2 | Binding EU regulation; relevant where the capture system processes personal data | Primary legal source | https://eur-lex.europa.eu/eli/reg/2016/679/oj | 2026-10-10 |

**Access limitations.** The Oxford Academic page for Englefield & Beale's current PIM article redirected to an endpoint that the research tool could not retrieve; bibliographic metadata was accessible, but detailed findings were therefore not used as decisive evidence. citeturn24search5turn25view0 Some publisher full texts for older papers were likewise restricted; where usable abstracts or author/open repositories existed, claims above were limited to what those sources actually exposed. No unavailable result was silently replaced with an inferred effect size.

### Candidate article angles

| Angle | Distinct thesis | Evidence strength |
|---|---|---|
| **Your second inbox is a queueing problem, not a note-taking problem** | Capture systems fail when acquisition rate persistently exceeds resolution/discard rate | Strong as systems reasoning; professional causal thresholds untested |
| **Capture now, classify later—but think once now** | The useful compromise is low-friction capture plus immediate micro-interpretation and provenance | Strong synthesis; exact rule not directly trialed |
| **A note is not a reminder** | Prospective-memory evidence supports explicit cues/plans more directly than storing vague notes | Relatively strong cognitive evidence |
| **Search doesn't turn garbage into knowledge** | Better retrieval reduces some filing costs but cannot reconstruct missing provenance or correct stale meaning | Good PIM + retrieval/AI support |
| **The point of forgetting** | Good knowledge systems intentionally discard provisional information instead of optimizing accumulation | Strong conceptual case; direct professional experimental evidence thinner |
| **Why AI memory should not be your source of truth** | Memory, context, RAG, canonical storage, and citations solve different problems | Strong technical distinction; product capabilities change rapidly |
| **Stop asking which note-taking method wins** | PARA/Zettelkasten/GTD are workflow conventions; empirical evidence addresses narrower mechanisms | Strong evidence-classification argument |
| **The metric isn't notes captured; it's decisions recovered** | Evaluate systems through evidence retrieval, source/date preservation, staleness recognition, decisions, and maintenance cost | Recommended evaluation model; needs field validation |

### Optional reusable assets

The **stock-flow backlog equation**, **lifecycle/automation matrix**, and **CSV evaluation schema** above are original portable assets included in this dossier and may be reused independently of any particular app.

A particularly compact capture-policy card derived from the synthesis is:

```text
CAPTURE GATE

1. Is this a commitment?
   YES → Task/calendar/reminder now. Link source.
   NO  → Continue.

2. Is there a foreseeable decision, question, project, or reuse?
   NO  → Leave at source / discard.
   YES → Continue.

3. Can it be reliably re-found at the source?
   YES → Prefer a pointer over a duplicate.
   NO  → Preserve the content.

4. On capture, preserve:
   - source
   - date
   - content
   - one sentence: "Why might I need this?"

5. Do not require taxonomy unless destination is obvious.

6. Inbox items must acquire a fate:
   action | durable evidence | defer | archive | delete

7. Monitor:
   captures <= processed + discarded
   over the chosen review window.
```

This card is **a research synthesis and testable hypothesis**, not a validated productivity protocol.

### Freshness triggers

This dossier should be materially revisited when any of the following occurs:

**New professional field evidence.** A longitudinal or randomized study directly compares capture-first and classify-first workflows on objective retrieval, backlog, decision, and maintenance outcomes.

**Modern PIM replication.** New studies replicate classic Boardman/Malone/Bergman findings under current cloud workspaces, semantic search, meeting transcription, or AI assistants.

**AI context architecture changes.** Model evaluations show robust elimination—or significant modification—of long-context position effects such as those documented by Liu et al. citeturn18view2

**Retrieval/citation reliability changes.** New benchmarks show materially different source-completeness or attribution behavior than ALCE-style results. citeturn18view1

**Persistent-memory product changes.** OpenAI, Anthropic, Microsoft, Google, or major knowledge-work providers materially change memory promotion, source visibility, retention, permissions, forgetting, or deletion semantics. OpenAI's memory documentation was already updated shortly before this October 2026 snapshot, illustrating why product-specific claims need active refreshing. citeturn25view1

**Legal changes.** EU/Czech rules affecting automated recording, personal-data retention, AI processing, employee/customer monitoring, or source deletion change materially; a US-specific deployment would separately require a current jurisdictional privacy review. citeturn19view0

The resulting decision is therefore not “find the perfect inbox.” It is to **make capture a short-lived state in a knowledge lifecycle, minimize irreversible decisions at capture time, preserve enough context to make the item intelligible later, and constrain inflow by the system's demonstrated ability to process, discard, and retrieve what it keeps.** That conclusion is better supported by the combined cognitive, PIM, and retrieval evidence than either comprehensive capture or mandatory immediate classification.