Knowledge Concepts
Intermediate packets are small, discrete, reusable units of work — an outline, a research summary, a slide deck draft, a set of notes — that can be saved and reused across future projects rather than starting from scratch each time.
Intermediate packets are small, discrete, self-contained units of work produced during a project — a research summary, an outline, a set of annotated notes, a first-draft section, a slide deck — that can be saved and reused in future projects rather than discarded or buried in project files. Coined by Tiago Forte (Building a Second Brain, 2022), intermediate packets are the "lego bricks" of knowledge work: modular pieces you can recombine in future contexts, so every project contributes to the next one instead of starting from zero.
The opposite of intermediate packets: work done once and lost, never reusable.
Tiago Forte introduced the term "intermediate packets" in Building a Second Brain (2022) as a key concept in his CODE method's "Express" stage — the phase where accumulated knowledge converts into creative output.
Forte's observation: knowledge workers routinely produce valuable intermediate outputs during projects — research summaries, annotated bibliographies, slide decks, meeting notes, first drafts of sections — that get buried in project folders and never reused. A consultant writes a competitive analysis for one client; the next client in a similar industry gets a new analysis from scratch because the first one was in a client-specific file.
Forte drew from software engineering's modular design thinking: functions are written once and called many times. A database query written for one feature can power three others. The analog in knowledge work: a research summary written for one report can inform three more.
The intellectual antecedent is also the commonplace book tradition — writers like Francis Bacon, Erasmus, and John Locke maintained collections of quotations, examples, and observations organized for reuse, treating intellectual material as transferable inventory.
An intermediate packet is any unit of work that:
Common intermediate packets:
| Type | Description | Example |
|---|---|---|
| Research summary | Distilled notes on a topic | "Summary of the literature on remote work and team cohesion" |
| Annotated outline | Structured argument with notes on each section | "Outline of the case for async communication" |
| Slide deck | Presentation with explanation notes | "Deck explaining machine learning basics for executives" |
| Framework or model | A structured way of thinking about a problem | "3x3 prioritization matrix for product roadmap decisions" |
| First-draft section | A fully written but unpolished section | "Introduction to the market sizing section of investor decks" |
| Interview digest | Key takeaways from user/expert interviews | "Findings from 10 customer interviews on onboarding experience" |
| Comparison table | Structured side-by-side analysis | "Comparison of Postgres vs. MongoDB for document-heavy apps" |
| Boilerplate text | Language that recurs across similar contexts | "Standard privacy section for grant applications" |
A product manager at a fintech company is preparing a product review for a new payment feature.
Without intermediate packets: They start from scratch: research the payment market, summarize competitor features, draft the framing section explaining why payment UX matters to retention. Total: 12 hours of work for a one-time document.
With intermediate packets: From previous projects, they have:
Opening the product review: they search their second brain for "payment" and "conversion." They find the comparison table — update it with the new data (2 hours instead of 6). They find the research summary — extract the 3 most relevant studies, add 2 new ones (45 minutes instead of 3 hours). They find the first-draft section — adapt it to this context (30 minutes instead of 2 hours).
Total with intermediate packets: ~3.5 hours. Same quality, different source.
In Forte's framework, intermediate packets are the output of the "Distill" stage feeding into the "Express" stage:
The critical insight: when a project ends, move its intermediate packets from "Projects" to "Resources" — making them available to future projects rather than archiving them with the project folder.
Intermediate packets create compound returns on knowledge work — each project you complete makes future projects easier. The first time you research a topic, you spend 5 hours. The second time, you spend 2 hours building on the first. The fifth time, you spend 45 minutes. The investment in saving and organizing intermediate packets creates this compounding.
Forte calls this "return on luck": when a new project arrives that happens to match previous work, you can respond rapidly because you have intermediate packets ready. But this isn't really luck — it's the designed result of treating every project's intermediate outputs as assets for the portfolio rather than waste.
At project midpoint: As you work through a project, notice when you produce something self-contained and potentially reusable. A research summary for your own reference? Save it distinctly. A comparison table you built to make a decision? The table itself is reusable; save it separately.
At project end: Before archiving the project, review its contents. Which pieces could transfer to a future context? Those become intermediate packets saved in Resources. The rest gets archived with the project.
Naming and findability: Intermediate packets are useless if you can't find them. Name them descriptively: "Research summary: remote work and productivity (2024)" not "Remote work notes." Tag by topic so they surface in searches. The title should describe what's inside so future-you knows whether it's relevant.
Self-contained documentation: The test of a reusable intermediate packet: can you understand it without remembering the original project? If the context has leaked out — if it references "the client's preferences" without stating them — add enough context to make it standalone.
"This is just saving your work." Saving files in project folders isn't the same as creating intermediate packets. The distinction: intermediate packets are extracted from project context, made self-contained, and filed where they're findable for future projects — not buried in an archived project folder named "Client X - Q2 2024."
"Only creative workers benefit from this." Intermediate packets apply to any recurring knowledge work: consultants (reusable analysis frameworks), developers (code snippets, architecture decision records), salespeople (competitive analysis tables), academics (literature review sections). If you do similar work across multiple projects, intermediate packets compound.
"Everything should be an intermediate packet." The decision of which intermediate outputs to save requires judgment. Not everything is reusable — highly client-specific or context-specific material isn't worth saving for future reuse. Save what has genuine transfer potential; don't add overhead by saving everything.
CODE method: Intermediate packets emerge in the "Express" stage of Forte's CODE framework.
Second brain / PARA: The system in which intermediate packets live and are organized for retrieval.
Progressive summarization: The distillation technique that converts captured research into distilled intermediate packets.
Commonplace book: The historical predecessor — maintaining organized collections of reusable intellectual material.
How granular should an intermediate packet be? Granular enough to be useful, not so granular it becomes a database. A "research summary on payment friction" is useful; breaking it into one packet per study is too granular for most uses. A complete slide deck is a valid intermediate packet; so is a single exemplary slide. The test: would I search for this, find it, and be able to use it in a future project?
What tool should I use to store intermediate packets? Your main note tool — Notion, Obsidian, Evernote. Intermediate packets live in the "Resources" section of your PARA system, organized by topic. They need to be searchable and portable, not buried in a project-management tool.
Should I update intermediate packets or create new versions? For living reference material (a comparison table that tracks a fast-changing market), update in place with a date stamp. For snapshots (research on what was true at a point in time), create new versions rather than overwriting — the historical version may be valuable for comparison.
Intermediate packets are the mechanism that converts knowledge work from a series of independent projects — each starting from scratch — to a compounding portfolio where each project builds on the last. The concept is simple: every substantial piece of work you do produces valuable intermediate outputs; save the ones that could transfer, make them findable, and use them in future work. The discipline is in the habit: at project midpoint, noticing reusable pieces; at project end, extracting and filing them before archiving. This 20-minute investment at the end of each project compounds into hours saved on every future project.
More WebSnips articles that pair well with this topic.
A bullet journal (BuJo) is an analog organization system created by Ryder Carroll using a dot-grid notebook: rapid logging with bullet symbols, collections (logs, trackers, lists), and migration (intentional task review). It combines daily planner, to-do list, diary, and habit tracker in one notebook.
A KWL chart is a three-column learning organizer: K (What I Know), W (What I Want to Know), L (What I Learned). It activates prior knowledge before learning, sets specific goals, and documents what you actually learned — making the learning process active and self-directed.
A literature note is a processed reading note — what you learned from a source, written entirely in your own words, kept with the source reference, serving as the bridge between reading and the permanent ideas in your knowledge system.