Intermediate Packets

2 minutes read

Summary

An intermediate packet is a small, tangible, reusable unit of progress produced at the end of a short sprint — instead of one large final deliverable. The idea comes from Tiago Forte’s “Just-in-Time PM” series: stage a large project as a sequence of short, intense sprints, each ending with an intermediate deliverable (notes, brainstorm, examples, outline, prototype, draft) that can be picked up again later or reused in another project.

Definition

  • Intermediate packet — a tangible, intermediate deliverable produced at the end of a short sprint: a set of notes, a brainstorm, a series of examples, an outline, a prototype, or a draft.
  • Sprint staging — progress is staged as a series of short, intense sprints rather than delivered as one lump at the end.
  • Reuse — previously built packets can be reused for new projects.

Why it matters

Small, self-contained pieces make a large project less intimidating, easier to restart after an interruption, and easier to get early feedback on. They fit short blocks of time, and saved packets can be reused later, which compounds value across projects. The framing supports focus and creativity by giving clear goals, quick feedback, and material that sparks new ideas.

Source-backed content

  • Source-backed: Instead of delivering one big lump of value at the end, progress is staged in short, intense sprints, each ending with a tangible intermediate deliverable (notes, brainstorm, examples, outline, prototype, draft).
  • Source-backed: These packets are not the final deliverable but are enough to wrap together for next use; several loops happen before the final one.
  • Source-backed: Previously built packets can be reused for new projects.
  • Source-backed (Readwise metadata summary): Small pieces make it easier to restart after interruptions, get early feedback, and use short blocks of time well.
  • Source-backed (Readwise metadata summary): Small pieces make large projects feel less scary, and saved pieces can be reused in future work.
  • Source-backed (Readwise metadata summary): The approach supports focus and creativity through clear goals, quick feedback, and useful materials that spark ideas.

Practical implications

  • Inference: For knowledge work, produce an explicit intermediate artifact (note, outline, draft, prototype) per working block rather than only at the end of a project.
  • Inference: Packet-based workflows compose with a second-brain / LLM knowledge base, where packets act as reusable building blocks or atomic notes.
  • Inference: The “several loops” framing implies iterative refinement — an early packet is expected to be revised, not final.

Evidence and provenance

  • Just-in-Time-PM-4-Intermediate-Packets-Summary
  • Personal Knowledge Management
  • LLM-Knowledge-Base

Open questions

  • The captured source is mostly images; the author’s full argument and the specifics of sprint mechanics are not transcribed.
  • Whether “intermediate packets” should be treated as a distinct formal method or a framing device for an existing agile/atomic-note practice is not established by this single source.

Updated: