How to write a personal principle about multitasking you can actually check
"Do one thing at a time" is a rule almost everyone already agrees with, which is exactly why writing it down changes nothing about the next time a second task shows up while the first one is still open. Multitasking rarely starts as a lapse in discipline. It starts as a real decision, made in about a second, about whether the thing that just arrived is more urgent than the thing already in front of you — and a principle that only restates the ideal has nothing to say about that decision, because it was never built to reach the moment where the decision actually gets made.
Why "single-task" cannot be violated
A rule can only do work if there is a moment where keeping it costs you something, and a moment where breaking it is a choice you could point to afterward. "I do one thing at a time" fails both tests. There is rarely a single instant when you decide to multitask the way there is an instant when you decide to check a phone — it accumulates from a string of individually reasonable-looking yeses: answering one message while a document is still open, glancing at a second screen during a call that has gone quiet for a moment, starting dinner while helping with homework because both are already running late. None of those, taken alone, looks like the failure the rule was written to prevent, so the rule never gets a chance to intervene.
Two different things get called "multitasking"
The word covers two patterns that come from different places and need different rules. The first is boredom-driven — the task in front of you has gotten slightly uncomfortable and something else is available, which is really a focus problem wearing a multitasking costume. The second is urgency-driven — a second, genuinely real task has arrived, and the fear is not boredom but the cost of appearing to have dropped it: the reply that looks unresponsive, the ball someone thinks you caught and didn't. Most advice aimed at multitasking is written for the first pattern and quietly assumes the second one doesn't exist, which is why it stops working the moment the interruption is a real obligation rather than a distraction.
What holding two tasks open actually costs
You don't lose the time twice — you lose it once, in the reload. Coming back to a task you stepped away from mid-thought takes a moment to reconstruct where you were, what you had already decided, and what you hadn't, even when the interruption itself lasted thirty seconds. Psychologists have a name for the part of your attention that stays on the task you just left: attention residue. It isn't a discipline failure, and no amount of guilt about having switched pays it back any faster. It's simply the cost of the switch itself, and it's worth knowing it's there before deciding whether a given interruption is worth paying it for.
Mine your own actual pattern before writing anything
Skip "I need to focus more" and look at one real day instead:
- The last time you were holding two things open at once, was the second one actually urgent, or did it just arrive urgently — a notification, a ping, a raised voice — with no real deadline behind it?
- What were you afraid would happen if you'd finished the first task before looking at the second? Would anything have actually gone wrong in that gap?
- Is there a specific kind of task you almost never hold open alongside something else, and a specific kind you always do? What's different about them?
- The last time you did finish the first task before switching, what actually happened to the second one while it waited? Was the wait ever as costly as it felt in the moment?
Write down one real instance, not a summary. "I opened the second monitor's chat the moment the paragraph I was writing needed a sentence I wasn't sure of yet" tells you exactly where a rule needs to hold. "I multitask too much" doesn't, because it never names the moment the decision actually happens.
Write the rule about the decision, not the tab count
A principle about multitasking is not a ban on ever holding two things at once — plenty of pairings are genuinely fine, like listening on a call while taking notes on that same call. It's a rule for the specific moment a second task arrives while the first is still open and unfinished. "I focus on one thing" can't be checked against any real afternoon. "When something new arrives while I'm mid-task, I finish the sentence, the step, or the paragraph I'm on before I look at it" can — there's a moment, a specific response, and an outcome you can honestly check by evening.
Run the same two tests any principle needs to pass. Can it be violated — is there a real moment where someone watching only your actions could say whether you kept it or didn't? Does it cost something — a rule that only ever agrees with switching the instant something pings isn't steering anything, because switching immediately is what would have happened anyway.
Attach behavior standards that name the moment in advance
Keep the principle general and put the specifics underneath it, decided before the pull shows up rather than negotiated inside it, because inside it is exactly when finishing "just this one thing first" feels hardest to justify. For a principle like I finish the piece I'm on before I open what just arrived, useful standards might be: notifications stay closed during any single task under twenty minutes; if a message looks urgent, I check only whether it says so in the first line before deciding whether to switch; once a task is open, I don't open a second one on the same device until the first reaches a natural stopping point, even a rough one. Each of these can be checked the same day — did the notification stay closed, did I check just the first line, did the second thing wait — which is what makes them a standard instead of an intention.
Where this differs from a Do Not Disturb setting
Turning off notifications for a stretch removes the interruption itself, and that's genuinely useful when a task can survive being sealed off for an hour. What it can't do is tell you why the pull to check was there in the first place, and it has nothing to say for the tasks that can't be sealed off — the call where you're also expected to answer questions in the chat, the evening where two people both need something from you at once. A principle sits underneath the setting: it's what decides the moment the setting is off the table, because the interruption was never really the problem. The urgency behind it was.
Stress-test it against the day it always happens
Take the specific kind of afternoon where this keeps showing up — the overlapping meetings, the cooking-while-helping-with-homework evening, the inbox that never actually closes — and run the rule against it directly. If finishing the piece you were on, or checking just the first line before switching, would have changed what you actually did last time, the rule has teeth; keep it as written. If it wouldn't have changed anything, the rule is aimed at the wrong moment, and the pattern is worth locating more precisely rather than abandoning, because the real decision is still in there somewhere.
Efficiency is one of six areas CreedOS ships templates for, alongside cognition, social, emotion, money and health, with curated creeds and behavior standards already written that you can take as they are or edit until they name the exact moment your own attention gets pulled toward a second task. It is free, with no in-app purchases.