## Summary Small-Batch Projects have three properties: 1. Tightly scoped, short-term commitments. 2. Clear desired outcomes that describe end states (criteria for success). 3. Deadlines or delivery dates (explicit accountability). ## Why it's important In the modern information age, to handle information overload, not only do we need to organize information input in the form of small, discrete notes (the [[Zettelkasten Method]], [[Evergreen notes]]), but we need to make our outputs -- projects -- small and discrete as well. This is where small-batch projects come in. > A "project" in the new economy has evolved to become a lean, agile tiger: small, adaptable, omnivorous, willing to hunt but preferring to watch for opportunities.[^1] **The main benefit of making projects small is that they reduce burn-out.** Small-batch projects come and go more quickly, which forces you to spend more time reviewing and planning and increases turnover so your project list does not become stale. If it feels hard to start a project, you can also keep making it smaller until the reward feels more tangible than the pain. ## In the context of P.A.R.A. The [[The PARA Method|PARA]] system organizes horizons (stacks) of actionability, which are each letter in P.A.R.A. This allows you to focus on one horizon at a time, which allows other stacks to grow without impact on your attention. Thus it is crucial to clearly define the line between each horizon. Small-batch projects ('P') are the most actionable layer of the "PARA" stack. [^1]: Forte, T. (April 13, 2018). Small-Batch Projects for Focus, Creativity, and Perspective. Forte Labs. https://fortelabs.co/blog/p-a-r-a-part-vi-small-batch-projects-for-focus-creativity-and-perspective/.