Slow Productivity: Reducing Active Projects to Enable Deep Work
Cal Newport's slow productivity framework is built on one central insight: every active project generates...
Cal Newport's slow productivity framework is built on one central insight: every active project generates administrative overhead (emails, meetings, check-ins), and when multiple projects run simultaneously, their overhead aggregates into an unmanageable burden that eliminates time for deep work. The solution is not better time management but radical project reduction. Newport argues that the number of concurrent active projects is the single most important variable in your ability to do meaningful creative work. By maintaining a very short 'active' list and a longer 'waiting' list, and being transparent about the system with collaborators, you preserve the focused blocks necessary for your most important contributions.
- List All Projects and Create Active vs. Waiting Categories
- Be Radically Transparent About Your System
- Work in Series Rather Than Parallel
- List All Projects and Create Active vs. Waiting CategoriesWrite down every project you're committed to. Designate only one to three as 'active' - these are the only ones you send emails about, have meetings about, or dedicate thinking time to. Everything else goes on the 'waiting' list.
- Be Radically Transparent About Your SystemPut your active and waiting lists in a shared document visible to all stakeholders. When someone's project is position seven on the waiting list, show them. When their project moves to active, let them know you're fully committed to it now.
- Work in Series Rather Than ParallelInstead of making small daily progress on many projects simultaneously, dedicate entire weeks to single projects. This eliminates the micro-switching costs that destroy deep work quality even though macro-switching still feels frustrating.
- Control Administrative Overhead on Active ProjectsFor the few active projects, replace ad-hoc back-and-forth communication with structured processes. Define where information goes, when check-ins happen, and how decisions get made - liberating projects from the 'send me a message when you need something' default.
Ali Abdaal describes his breakthrough moment: he assumed working on his book a little each day while also making YouTube videos and running his business would keep everything moving forward. Instead, almost nothing got done. Switching to dedicating entire weeks to single projects - one week of intense book writing, then a week of batching YouTube videos, then business work - finally produced real progress.
Newport developed this framework through his dual career as a computer science professor and bestselling author, experiencing the cyclical pattern of overcommitment firsthand. During the pandemic, fear about university shutdowns and publishing industry contraction drove him into entrepreneurial hustle mode, adding too many projects. A year and a half later, he found himself unable to do deep work because the overhead from all those projects consumed his entire schedule - leading to the slow productivity thesis.