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.
- 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.
Level 1 - Recognize
Slow productivity means running fewer active projects so work finishes deep instead of piling as guilt.
Level 2 - Explain
Busy is not the same as finished - a full calendar can feel productive while the one build that matters stays untouched.
Level 3 - Use
Drop a fourth side project to finish one book draft this quarter - depth beats breadth when guilt stacks.
Level 4 - Connect
Because attention is finite, parallel WIP taxes finish rate - a full calendar can hide the one build that never ships.
Level 5 - Create
Trade looking productive for work you can ship - same lane as Deep Work and Minimum Effective Dose on project count.
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 |
