ManageTime

Article

Tasks that live as flagged email: when the inbox works as your to-do list

Your inbox can work as a to-do list, and a survey of managers found the people handling email best were doing exactly that. It holds while two conditions hold: every message gets its decision the first time you open it, and the inbox ends each session empty. Break either one and the flags become a pile nobody reads. This article covers what that survey actually measured, why a flagged message stops behaving like a task, and where the line sits between work your inbox can carry and work it cannot.

Should you use your inbox as a to-do list?

A column of flags down the side of the inbox, most of them older than a fortnight. You can say what two of them are for. The rest are messages you did not want to lose, marked at a moment when marking was cheaper than deciding, and they have been sitting there ever since. That is the version of inbox-as-list most people are running, and the advice columns are right about it.

The advice is less settled than it sounds. A 2024 paper in Omega by Letmathe and Noll surveyed managers on how they handle mail, then ran factor and regression analyses to identify a full set of email management strategies rather than the single tips earlier studies had tested one at a time. Two strategies came out ahead of the rest on email management performance: using the email client as a to-do list, and keeping the inbox at zero. Those two, out of the full set the paper measured. Not the advice you usually get.

Read the design before you rearrange anything. It is survey work, so it connects what managers reported doing with how well they reported coping, and an association measured that way does not establish that one produces the other. The sample is managers, whose mail arrives carrying more decisions than a support queue does. What the paper does show is that the arrangement most productivity advice tells you to abandon was, in this sample, sitting with the people who reported handling email best.

The two findings arrive together, and that matters more than either does alone. An inbox used as a task list and an inbox kept at zero are one arrangement seen from two sides. If every message gets a decision on sight, the list stays short enough to read; if it stays short enough to read, the decisions keep happening. Drop the second half and the first stops working within a week, which is what the flag column at the top of this page describes.

So the honest answer is conditional. Your inbox can hold your tasks when you empty it on a schedule, when each message gets its decision the first time you open it, and when the work in question arrived by mail in the first place. The email pillar covers the session mechanics all three conditions depend on. Miss one and you are not running a to-do list. You are running a pile with a search box on it.

Why does a flagged email stop being a task?

Because a flag records that you noticed something. It does not record what you decided to do about it.

Compare the two objects on your screen. A task names an action you could start this afternoon, in your own words, with your own date on it and enough context to begin without opening anything else. A flagged message names a sender and a subject line. To find the action inside it you open the thread, read down to the part that concerns you, work out what was actually being asked, and try to remember what you concluded the last time you did all that. Every review charges you that again, and reviews pile up fastest on the messages you are avoiding.

Order is the second problem. An inbox sorts by arrival, so work with a real deadline sits wherever it happened to land, interleaved with newsletters and delivery confirmations. A task list is ordered by you. That difference decides which piece of work you see first on a bad morning, which is the morning it counts.

Changing the habit takes more than a rule you announce to yourself. Russell, Daniels, Jackson and Fullman ran a 12-month wait-list study in a UK organization to shift work-email habits, published in 2021, with 127 people at the first measurement and 46 supplying data at every point. The model they tested needs two stages rather than one: people had to meet a rationalized plan of action repeatedly, and they had to state an intention to use it. Habits moved for the participants with higher self-efficacy. A Monday resolution supplies neither stage.

Their framing is the part worth carrying to your own mailbox. Work habits are rarely good or bad in themselves, the authors argue, so changing one needs a clear rationale. They count a change as a good one when it improves both what you get done and how the work leaves you feeling. Flagging is not a vice. It becomes one when nothing downstream of the flag was ever decided, and that is a missing plan rather than a missing virtue.

When should a task move out of the inbox?

Some work outgrows the mailbox it arrived in, and it announces the moment. The first sign is a date nobody in the thread set. Once a piece of work carries a deadline that came from your own plan rather than from the sender, the inbox no longer holds the information that matters about it, and the flag has become a note that a conversation once happened.

The second sign is steps. A message you can finish in one sitting belongs where it is, and the Two-Minute Rule (for tasks) draws that line at the point where writing the task down costs more than doing it. Work needing three sittings and a document does not fit in a reply box. The third sign is other people: when a colleague needs to see where this work stands, a flag in your private mailbox is the one place they cannot look.

The fourth is how much is open at once. Personal Kanban caps what may sit in progress and refuses to start anything new until something leaves, a rule your inbox cannot enforce, because it has no idea how many of its flags represent live commitments and how many are archaeology. If the capture step is what keeps going wrong, Getting Things Done makes clarifying each item into a named next action its own stage, and that stage is exactly the one a flag skips.

There is a reason to settle this yourself rather than wait for a better tool. Lanctot and Duxbury interviewed 30 knowledge workers for a 2025 study, 15 in education and 15 at an insurance firm, asking what would help them manage email better. Most answered that the fix lay with somebody else: policy, training, technology. The authors read that as a self-serving attribution bias, and they make a fair case that email volume does need answers at the organizational level. Where your own tasks live is not one of those answers. That part sits on your desk.

Moving a task out does not mean losing the mail. Archive the message, carry the two lines of context across to wherever the task now lives, and let the mailbox go back to being a record of what people said rather than a ledger of what you owe.

How does your working style change the answer?

Which arrangement survives depends less on the argument than on how you already work. Readers closest to this site's Architect style want the separate system and will maintain it, so the failure they should watch for is the opposite: two lists, both half true, and a daily reconciliation nobody asked for. Sprinters clear the inbox fast and flag whatever needs thought, which works well right up to the point where the flagged pile becomes the only place the difficult work lives. Improvisers can often run the whole thing from the mailbox, provided the emptying session survives a busy week. Visionary-leaning readers should watch what an inbox cannot hold at all, which is the work nobody has emailed you about, and that is usually the work deciding the quarter.

Volume and role set the outer edge of this. If mail is your actual job, a support queue or a dispatch desk, the inbox already is the task system and the question does not arise. If you get little mail and run several projects, your flags will never carry enough of the week to be worth the experiment. And the people in the Omega survey were managers, whose inboxes are unusually decision-dense. Read the finding as evidence that the arrangement can work, not as an instruction to adopt it. Your own mail decides.

Two weeks is long enough to find out which one you are.

Pick the setup you are not currently running, give it a fixed emptying session every working day, and at the end of the fortnight count the work that slipped and note where it was sitting when it did. If the answer is that it was flagged, the mailbox was not the list. The email pillar has the session mechanics, and the working-style self-check points at the methods most likely to hold for the way you already work.

Frequently asked questions

Should you use your inbox as a to-do list?

Yes, if you empty it on a schedule and decide each message the first time you open it; no, if flagging is what you do instead of deciding. A 2024 survey of managers published in Omega found the two strategies most strongly linked to email management performance were using the email client as a to-do list and keeping the inbox at zero. The two arrive together. Without the session that empties it, the flagged pile stops being a list anybody reads.

Is flagging emails a good way to track tasks?

Only for work that is still one message and one short action away from finished. A flag records that you noticed something, not what you decided to do about it, so every review costs you a reread of the thread. Once a piece of work has several steps, a date you set yourself, or a colleague waiting on its status, it needs an entry in a task list instead.

What happens to a flagged email nobody looks at again?

It becomes a record that a decision was postponed, and the flag column stops carrying any signal at all. The failure is gradual. Each unresolved flag makes the next one cheaper to add, and once the column runs longer than a screen you have to reread messages to find what still matters. That is where people conclude an inbox cannot hold tasks, when what actually failed was the session meant to empty it.

When should tasks move out of the inbox into a task list?

Move a task out as soon as it has a deadline you set, more than one sitting of work in it, or somebody else who needs to see where it stands. Getting Things Done makes that translation its own stage, turning each item into a named next action before it joins any list. Personal Kanban adds the cap a mailbox cannot enforce, since an inbox has no idea how many of its flags are live commitments. Archive the message once the task exists, and keep the context with the task rather than in the thread.

Sources