The Simulated Pull System
Control your workload by pulling tasks instead of having them pushed
The Simulated Pull System is Newport's adaptation of manufacturing pull systems, such as kanban, for individual knowledge workers. In manufacturing, a pull system means that a workstation only begins a new item when it has finished the current one and has capacity, rather than having items pushed onto it continuously by upstream processes. The result is smoother flow, less work-in-progress inventory, and higher quality.
For knowledge workers, the simulated pull system works as follows: you maintain a visible list of all potential work (the backlog), you set a strict limit on how many items can be active at any given time (the work-in-progress limit), and you only pull a new item from the backlog when you complete an active item. Projects that come in go into the backlog by default. You select up to a fixed number of projects to be on the active list.
The system also includes an intake procedure that slows down the rate at which new items enter the backlog. When someone asks you to take on new work, you ask for any additional details you need before you can start, share the number of existing projects along with a time estimate, and share an estimate of when you expect to be able to begin the new work. This transparency manages expectations and reduces the pressure to say yes immediately.
- You should pull work when ready, not have it pushed on you when others want it done
- A visible backlog with a work-in-progress limit prevents overcommitment
- Transparency about your current load is more respectful than a premature yes followed by delays
- New requests enter a queue by default rather than immediately becoming active commitments
- Completing work before starting new work creates better flow than incremental progress on many fronts
- Create a visible backlog of all pending workList every project, task, and commitment you currently have or have been asked to take on. This includes work you have agreed to but not started, ideas you want to pursue, and requests from others. The backlog must be visible and maintained in one place, whether that is a physical board, a digital tool, or a simple document.
- Set a strict work-in-progress limitDecide on the maximum number of projects or major tasks you will have active at any time. Newport suggests a small number, typically 3-5 active projects. This limit is non-negotiable. When you are at capacity, no new item moves from the backlog to the active list regardless of how urgent or appealing it seems.
- Establish an intake procedure for new requestsWhen someone asks you to take on new work, follow a standard procedure: ask for all the details you need to understand the scope, share your current active project count and estimated completion dates, and provide a realistic estimate of when you could begin the new work. This prevents the reflexive yes that leads to an ever-growing active list.
- Pull new work only when capacity opens upWhen you complete an active item, and only then, review your backlog and select the next highest-priority item to pull into the active set. The pull decision should consider your missions, the overhead tax of the new project, and whether you have the energy and focus for it right now. Push versus pull is the fundamental mindset shift: pull work to the next stage when ready instead of pushing everything forward simultaneously.
Newport describes how a freelancer might implement the pull system by maintaining a client project board with three columns: Backlog, Active (max 3), and Completed. When a new client inquiry arrives, the freelancer responds with their current active count, estimated completion dates, and a target start date for the new project. The client can choose to wait in the queue or look elsewhere. Most choose to wait, because the transparency signals competence and demand.
Newport draws directly from lean manufacturing and software development practices. He observes that software teams have long used kanban boards with work-in-progress limits to prevent overload and maintain flow. He adapts this for individual knowledge workers who typically have no formal system for managing the inflow of work, instead accumulating commitments until they are overwhelmed. The simulated pull system provides that missing structure.