The Mission-Project-Daily Goal Hierarchy
Limit active commitments across three tiers to stay focused
Newport's first core principle, Do Fewer Things, centers on a three-tier system for limiting commitments. At the top are overarching missions, which are the significant goals or callings that direct your professional life. Below those sit ongoing projects, the specific multi-week or multi-month efforts that advance your missions. At the bottom are daily goals, the one or two concrete tasks you will focus on in a given workday.
The key insight is that you must impose hard limits at each tier. Newport suggests limiting yourself to a small number of active projects at any given time and focusing on just one major project per day. When new requests arrive, they enter a holding queue rather than immediately becoming active commitments. This approach directly combats the knowledge worker tendency to accumulate obligations until every day becomes a frantic attempt to make incremental progress on dozens of things simultaneously.
The framework also addresses the overhead tax, the administrative and coordination burden that accompanies every commitment. Each project you take on does not just require the work itself; it requires emails, meetings, check-ins, and context switching. By limiting the number of active projects, you dramatically reduce this overhead, freeing time and cognitive energy for the actual work that matters.
- Every commitment carries an overhead tax of coordination and communication beyond the work itself
- Limiting active projects reduces overhead more than it reduces output
- One focused project per day produces better results than incremental progress on many projects
- New requests should be queued, not immediately accepted as active commitments
- Saying no to good opportunities is essential when your active project slots are full
- Define your overarching missionsIdentify 1-3 missions that represent the significant commitments or callings in your professional life. These are enduring directions, not specific deliverables. For example, a mission might be 'become a recognized expert in data engineering' or 'build a sustainable consulting practice.' Missions change rarely and serve as a filter for which projects you accept.
- List all current projects and limit the active setWrite down every project you are currently committed to. Then select no more than 3-5 to keep as active ongoing projects. Move the rest into a waiting queue. Projects that come in go into the queue by default. You only pull a new project into the active set when an existing one completes or is paused. This is what Newport calls a simulated pull system.
- Set one primary project per dayEach morning or the evening before, designate one project as the primary focus for the day. This project gets your best hours and deepest attention. Other active projects may get small maintenance work, but the bulk of your creative and cognitive energy goes to the day's chosen project. Newport emphasizes working on one project per day rather than splitting focus across several.
- Create an intake procedure for new requestsEstablish a clear process for handling incoming requests and opportunities. Ask for any additional details you need before you can start. Share the number of existing projects along with a time estimate. Have a standard response that acknowledges the request, indicates when you might be able to begin, and sets expectations. This prevents the reflexive yes that leads to overcommitment.
- Review and rebalance weeklyAt the end of each week, review your active project list. If a project is causing delays, acknowledge that transparence is key, update stakeholders, and adjust your plan. Pull work to the next stage only when ready instead of pushing everything forward simultaneously. Update your queue and decide what enters the active set the following week.
Newport describes how software teams use kanban-style pull systems where developers only pull new work items when they complete their current task, rather than having managers push multiple tasks onto them simultaneously. He suggests knowledge workers can simulate this same approach individually: maintain a visible backlog, limit work-in-progress to a fixed number, and pull new items only when capacity opens up. This prevents the cognitive overload that comes from having too many open loops.
Newport draws on research showing that time spent in meetings increased two to threefold during the pandemic as organizations attempted to coordinate increasingly fragmented workloads through video calls. He connects this to the concept of overhead tax: every new project a person takes on generates a back-and-forth communication burden that compounds as the number of projects increases. The solution is not better time management but fewer things to manage in the first place.