Limit active work in progress
Keep many projects stored if necessary, but choose a smaller set that is actively advancing this week. A project can remain valid without demanding attention every day.
An explicit active list prevents every open project from competing equally for the next hour.
Leave a restart note
Before switching away from a project, record the next concrete action and any important unresolved decision. This creates a low-friction restart point.
A good restart note answers: what was I doing, what is already decided, and what should I do next?
Batch similar contexts
Group phone calls, document review, errands, approvals, or administrative submissions when possible. Batching reduces the setup cost of repeatedly changing tools and mental context.
Do not batch work that depends on fresh creative attention simply because the tasks look similar.
Use the calendar to protect deep work
Deadlines tell you when work must be finished; they do not reserve the time needed to finish it. Place focused work sessions before important deadlines, especially for projects that require sustained attention.
Keep some open space between demanding sessions so delays do not cascade across the day.
Review the portfolio weekly
Once a week, check every active project for deadline changes, blocked dependencies, missing next actions, and items that can be paused or archived.
The goal is not to touch every project. The goal is to know deliberately which projects will move and which will wait.
Keep fixed dates on the calendar, executable actions as tasks, and multi-step outcomes inside projects. Preserve source evidence whenever a date came from a document.
Separate urgency from activation
A project can be important without being active today. Keep a portfolio view for everything you are responsible for, then mark a smaller subset as active for the current week. This distinction prevents a long project list from behaving like one giant inbox.
When a project is paused, record why it is paused and what event will make it active again. That makes waiting deliberate rather than accidental.
Design your restart points
Context switching is most expensive when you return to a project and cannot remember the state of the work. End each session with a compact restart note: the last completed step, the unresolved question, the file or source you need next, and the next physical action.
That note becomes especially valuable when a project is interrupted for several days by another deadline.