The Input Audit: Where Your Attention Actually Goes
Before you can fix overload, you need to see where the volume is coming from. Here's what a typical day looks like for someone who "stays on top of things":
| Source | Daily Count | Signal % | Time |
|---|---|---|---|
| Email (work) | 80-120 | 15% | 90 min |
| Slack / Teams | 50-80 messages | 20% | 60 min |
| Newsletters / RSS | 10-25 | 5% | 30 min |
| News / social media | Infinite scroll | 2% | 45 min |
| Meetings | 3-6 | 30% | 180 min |
| Reports / docs shared | 5-10 | 25% | 40 min |
| Notifications (apps) | 30-60 | 10% | 20 min |
Total: ~7.5 hours processing inputs. Signal ratio: maybe 15%. That means 6+ hours spent on noise.
How to Know You're Overloaded (Not Just Busy)
Overload feels like busy-ness, but it's different. Busy people have too much to do. Overloaded people have too much to decide about.
"You read the same email three times without responding"
→ Your brain is full. It can't process another decision.
"You feel busy but can't name what you accomplished"
→ You consumed information without converting it to action
"You save articles "for later" that you never read"
→ You're hoarding inputs instead of filtering them
"You check email/Slack within 5 minutes of closing it"
→ You're seeking dopamine from new inputs, not doing deep work
"You dread opening your inbox Monday morning"
→ The volume exceeds your processing capacity
The 4-Level Information Filter
Most people try to process faster. That's the wrong approach. You can't out-speed the firehose. Instead, reduce what reaches you, then batch what remains.
Level 1: Block at the Source
The best information to process is information you never receive.
Unsubscribe from every newsletter you haven't read in 30 days (use the 30-day rule: if you didn't miss it, you don't need it)
Leave Slack/Teams channels where you haven't posted in 60 days
Turn off all app notifications except calendar and direct messages
Set email rules: auto-archive CC-only emails, mailing lists → digest folder
Block news/social sites during work hours (Freedom, Cold Turkey, or phone settings)
Level 2: Batch What Remains
Process information in batches, not as it arrives.
Email: 3 processing sessions per day (10:30, 2:30, 4:30). Close between sessions.
Slack/Teams: 2 check-ins per day (11:00, 3:00). Mute between checks.
News/industry reading: One 20-minute block per day (after lunch, never morning)
Reports/documents: Friday afternoon review block, process the week's docs at once
Meetings: Consolidate to 2-3 blocks per day, leave gaps for processing
Level 3: Process to Zero
Every input gets one of four outcomes: Act, Delegate, Schedule, or Delete.
Act: Takes less than 2 minutes → do it now
Delegate: Someone else should handle this → forward with clear instructions
Schedule: Needs your attention but not now → add to task list with a date
Delete: No action needed → archive or delete immediately
The key: never leave anything in "I'll deal with this later" limbo
Level 4: Protect What Matters
Create information-free zones for your most important work.
First 90 minutes of the day: no email, no Slack, no inputs. Deep work only.
Meeting-free mornings (at least 3 days/week)
Phone on Do Not Disturb during focus blocks
Close all tabs except what you're working on (if you need it, you'll find it)
End-of-day shutdown: process remaining inputs → plan tomorrow → close everything
The Weekly Information Diet
Here's what a week looks like when you control your inputs instead of letting them control you:
| Day | Morning | Midday | Afternoon |
|---|---|---|---|
| Monday | Deep work (no inputs) | Email batch #1 + Slack check | Meetings + Email batch #2 |
| Tuesday | Deep work (no inputs) | Email batch #1 + Slack check | Client calls + Email batch #2 |
| Wednesday | Deep work (no inputs) | Email batch #1 + 20-min reading block | Admin + Email batch #2 |
| Thursday | Deep work (no inputs) | Email batch #1 + Slack check | Meetings + Email batch #2 |
| Friday | Deep work (no inputs) | Email batch #1 + document review | Weekly review + cleanup + Email batch #2 |
Notice: every morning is information-free. That's not optional. That's where your most valuable work happens.
Why This Is Hard (And Why Most Advice Doesn't Work)
Every "information overload" article tells you to unsubscribe from newsletters and turn off notifications. That's necessary but insufficient. The real problem is that your most important information (client emails, team updates, project status) arrives in the same firehose as the noise.
You can't just "check less." You need a way to separate signal from noise before you see it. That's the difference between an information diet (reducing volume) and an information filter (extracting what matters).
A human executive assistant does this naturally: they read your email, flag what's important, handle the routine stuff, and only interrupt you for things that need your brain. That's the model. The question is whether you can build that filter without a $60K/year hire.
What If the Noise Was Already Filtered?
The 4-level filter works. But Level 1 (blocking at the source) still leaves your most important channel, email, unfiltered. That's where the real overload lives.
alfred_ applies the filter before you see your inbox. It reads every email, identifies what's actually important, extracts tasks and deadlines, drafts replies to the routine stuff, and presents you with a clean priority view. Your 120-email inbox becomes 12 things that need your attention.
That's not "checking email less." That's having the noise removed so you only see signal.
Try alfred_
Stop Drowning in Noise
alfred_ filters your inbox so you only see what matters. Less noise, more signal, better decisions.
Try alfred_ FreeFrequently Asked Questions
Won't I miss something important if I reduce my information intake?
The fear of missing something important is exactly what keeps you overwhelmed. In practice, truly urgent things reach you through direct messages, phone calls, or people walking to your desk, not through your 47th newsletter or a CC'd email chain. When you reduce noise, signal becomes clearer. You'll actually catch more important things because you have the cognitive capacity to recognize them.
How do I convince my team that I'm not ignoring them by batching Slack?
Set expectations proactively. Update your Slack status: "Checking messages at 11 & 3. DM for urgent." Most people don't actually need an instant response. They just got used to one. After a week, your team will adapt. For true emergencies, they'll call or DM you. For everything else, a few hours of delay is fine.
I need to stay current for my industry. How do I read without getting overwhelmed?
Staying current is a 20-minute daily habit, not a constant drip. Pick 3 sources max (not 30). Read during your afternoon reading block. Use a "read later" app (Pocket, Instapaper) to capture interesting links during the day, then batch-read them. If you haven't read a saved article in 2 weeks, delete it. It wasn't important.
What if my boss expects immediate email responses?
Most bosses care about outcomes, not response speed. But if yours explicitly expects fast replies, create a VIP filter that alerts you only for their messages. Everyone else follows your batch schedule. You can also have a direct conversation: "I'm trying to improve my focus time. I'll check email 3x/day but I'll always prioritize your messages within 30 minutes."
How long does it take to see results from an information diet?
You'll feel the difference within 48 hours. The first morning you spend 90 minutes in deep work without checking anything, you'll produce more than most people do in a full scattered day. Within a week, you'll notice less anxiety, clearer thinking, and better sleep. Within a month, you'll wonder how you ever functioned under the old volume.
How does alfred_ help with information overload?
alfred_ acts as an intelligent filter between you and your inbox. It auto-triages email by priority so you only see what matters during your processing windows. It extracts tasks and follow-ups so nothing slips through even when you're not checking. It drafts replies to routine messages so your response batch takes 10 minutes instead of 45. The net effect: you process the same information in a fraction of the time, with less cognitive load.