What is information overload at work?
Information overload at work is the point where incoming email, chat, documents, and meetings exceed what you can hold in mind and act on. It is not a character flaw or a sign you are falling behind. The useful distinction is between information that demands a decision and information that merely requests attention.
The term entered common use with Alvin Toffler's Future Shock in 1970, and the economist Herbert Simon later described the mechanism plainly: information consumes attention, and attention is the scarce resource. Peer-reviewed reviews of workplace overload agree. The issue is the rate and volume of input measured against a capacity that does not grow.
Standard advice is a checklist: define priorities, batch intake, mute notifications, delegate, disconnect. Every item is reasonable, and none of them sorts information by what it demands from you. They organise tasks. People describe the result the same way: my brain feels too full. Meeting-heavy workers sit through frequent calls and cannot return to focused work. Readers describe rereading passages and losing context.
Why does more input make simple decisions harder?
Because attention and working memory are fixed. Every unread message, half-read document, and unresolved thread occupies one of the few slots you have, so adding input removes capacity from the decision in front of you. The noise is not in the inbox. It is in the open loops.
Working memory has been studied since the 1950s, when George Miller described a limit of about seven items; later work put the practical number lower, closer to a handful. Whatever the exact figure, it is small and it does not negotiate. You cannot expand it by caring more.
The second cost is attention residue, the term Sophie Leroy used for the part of your mind that stays on the previous task after you switch. Interruption research by Gloria Mark and others shows the practical version: returning to your earlier depth of focus takes minutes, not seconds. People compensate by moving faster and reading shallower, the shallowing hypothesis in daily life.
Which information deserves attention right now?
Ask one question of each arriving item: does this change a decision I am about to make, or an action I am about to take? If yes, it moves now. If no, it waits in a list or it goes. Decision impact, not someone else's urgency, sets the order.
Urgency is contagious. A message marked urgent carries the sender's priority, not yours, and treating the two as the same thing is how a calendar fills with other people's emergencies. The two-minute triage rule helps with small tasks, but it sorts by how long something takes rather than what it changes.
Keep one channel genuinely live, and one only. If three systems can ring, nothing means now, so you check all three continuously to find out which one is real. That checking is the behaviour people describe as their brain feeling too full.
How do I build a four-bucket filter?
Sort each item into one of four buckets as it arrives: must know now, must act later, useful reference, or discard. Assign the bucket in seconds, before you read the thing in full. The four buckets are the system, and the fourth one is the one most people skip.
Must know now: it changes a decision today or has a deadline inside a few hours. Keep it on screen, in one place, and act. This bucket should hold only a few items; if it holds more, you have turned it into an inbox.
Must act later: one line on one list with the trigger attached, a date, a person, a dependency. A starred message has no trigger, so you reread it five times. Useful reference: file it, retrieve on demand, and when you do open it write down the points you would need to defend in a meeting. That act of reproducing from memory instead of recognising is retrieval practice. Discard: delete it, do not save for later; bookmarking feels like learning while doing nothing.
When should I batch email, Slack, documents, and meetings?
Match the schedule to the cost of delay. Communication two or three times a day, documents in one protected block, meetings inside a window with buffer gaps, and one channel left open for true emergencies. The schedule does the filtering, so you stop re-deciding every time something arrives.
Documents deserve their own block because a document read in fragments costs two readings: you lose the thread, return to the top, and spend the same attention twice. One sitting gives you the argument in order.
Buffer gaps after meetings are where the must act later items get captured while you still remember why they mattered. If your workplace expects instant replies, name the exception instead of pretending to be always on: one channel for genuine urgency, and a stated response window for everything else.
How do I recover when my brain already feels full?
Stop intake for a set period, empty every open loop onto one page, then finish one small item that has a single visible output. Recovery is regaining one thread, not catching up. Catching up is not available to you today, and pretending otherwise is what keeps the state going.
The one-page dump works because writing an open loop down closes it for working memory. You do not have to resolve the item to release it. You only have to give it a home you trust, then finish the item that unblocks the most other things.
For the reading half of the problem, expect to reread. After a stretch of fragmented input that is normal, not evidence of a decline in ability. What rereading does not tell you is what you kept. If you want to see what you actually absorbed after a heavy reading day, Absorb on the App Store is built around that: ten to twelve minutes of reading, listening, and analyzing with scored feedback on how well you stayed with the material.