Interactive graph
Slow Productivity
Table of Contents
Slow productivity is fewer active projects so work finishes deep instead of piling as guilt.
Key Concept
- Busy is not the same as finished.
- Level 1: Running around all day does not mean the important job is done yet.
- Level 2: A full calendar can feel productive while the one project that matters stays unfinished in the corner.
- Level 3: Fewer active projects protect depth - notes and builds ship instead of stacking up as guilt you never touch.
- Level 4: Cut active projects until one important build can finish this month - busy is not the scoreboard.
- Level 5: Fewer lanes on purpose trades looking productive for work you can finish - same move as Deep Work and Minimum Effective Dose on project count.
- I run fewer active projects so notes become shipped work, not a guilt backlog.
- Four half-started builds eat the one client site that was supposed to ship this month.
Examples
- I dropped a fourth side project to finish one book draft - depth beat breadth this quarter.
- One deep client build this month beat three half-started sites on the portfolio.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| contradicts | The 12 Week Year | when fewer deep projects beat quarterly sprints |
| extends | Creative Output | Fewer active projects turn notes into finished output instead of endless backlog |
| extends | Deep Work | Fewer deep projects - Newport's focus frame nearby |
| extends | Energy Protects Judgment | Fewer deep projects protect the energy budget |
