Work used to be one thing at a time
For most of the history of personal productivity advice, the shape of knowledge work was roughly the same: pick the most important thing, work on it until it’s done or you run out of day, then pick the next. To-do apps were designed for exactly that: a list you work through, top to bottom.
That shape is changing quickly. With AI assistants and agents doing more of the drafting, coding, researching and summarizing, a single person can now have several streams of work running at once. A typical hour might be: kick off a draft, review an agent’s output on a different project, answer a client, come back and steer the draft, check a long-running task on a third project.
You’re not working through a list anymore. You’re checking in, steering, reviewing, and switching.
The real cost is context, not time
More parallel work doesn’t mean more parallel attention. Researchers have a name for what happens when you switch away from something before finishing it: attention residue. Part of your mind stays on the last thing, and you do the next thing a little worse. Multiply that by dozens of switches a day and the cost adds up.
You can’t eliminate switching in this kind of work; it’s the job now. What you can do is make each switch cheaper: know what you’re switching to, know where you left it, and know afterwards where your attention actually went.
Why heavy systems break here
Elaborate systems (every task filed, tagged, estimated and linked) assume you have time to maintain them between pieces of work. In a multi-project day, by the time you’ve properly filed a task you’ve switched three times. The system falls behind within a morning, and a system that’s behind stops being trusted.
The opposite failure is just as common: no system at all, and an evening spent wondering where the day went and which project got nothing.
A lightweight system for juggling projects
1. One list for the day, across every project
Don’t keep a separate to-do list per project and try to visit each one. Keep one list for today, with each item tagged by project. You plan the day once, and you can see at a glance whether one project is crowding out the rest. (My ten-minute daily planning routine works well here.)
2. Let the timer follow your attention
When your attention moves to a different project, move the timer with it. Don’t wait until there’s a well-defined task: if you’re reviewing an agent’s work on Project B, track it on Project B. If it’s a burst of messages and calls that belong to nothing in particular, track it on the day. The goal isn’t a perfect timesheet; it’s an honest picture. (More on that in how to track time without making everything a task.)
3. Keep a running note per project
The most expensive part of switching back to a project is remembering where you were. Keep one running note on each project: what’s in flight, what the agent is working on, what you decided, what the next step is. Before you switch away, add one line. Coming back then takes thirty seconds instead of ten minutes of rereading.
4. Use a day note for everything in between
Plenty of what comes up doesn’t belong to any project: a thought, a follow-up, a name to remember. Put it in today’s note rather than forcing it into a project or losing it. You can always move it later.
5. End with a five-minute review
At the end of the day, look at where your time went by project and ask two questions: did the project that mattered most actually get the most attention? And is there a project I keep checking in on that never gets real time? The answers decide tomorrow’s list.
Signs you’re juggling too much
- A project shows up in your time every day, but only in five-minute fragments.
- Your running notes keep saying “next step: figure out next step.”
- Day-level time (calls, messages, odds and ends) is eating most of every day.
- You can’t say, without checking, which project got the most time this week.
When you see these, the fix is rarely a better tool. It’s fewer projects in flight at once, or one protected block a day for the one that matters most.
How Zympl fits this way of working
I built Zympl for exactly this kind of day. The planner is one list per day, with tasks tagged by project. Timers run on the day, on a project, or on a task, so you can track a project before it has a single task, and the messy in-between time still counts. Every project and every day has its own note, and standalone notes live in folders of their own. At the end of the day the timeline and reports show where your attention actually went, across every project, without anything to reconcile.