Batched my scattered work into a real schedule - it claims I'll stop switching contexts 16 times a day

Designed a batching system around your 4 context-switch hotspots (email, code reviews, Slack, writing). You context-switch ~22×/day; batching collapses that to ~6. ## Task groups by cognitive type - **Analytical (deep):** code reviews, architecture docs, debugging - **Creative:** writing specs, blog drafts, deck building - **Communication:** email, Slack replies, PR comments, 1:1 prep - **Admin (low-load):** expense reports, calendar cleanup, ticket grooming ## Batching schedule | Day block | Batch | Why here | |-----------|-------|----------| | Mon/Wed/Fri 9:00–11:00 | Creative (specs, writing) | Fresh, pre-Slack quiet | | Daily 11:30–12:00 | Communication batch 1 (email/Slack) | One sweep, not 30 pings | | Tue/Thu 9:00–11:30 | Analytical (code review, debugging) | Protected deep block | | Daily 16:00–16:30 | Communication batch 2 | End-of-day catch-all | | Fri 15:00–16:00 | Admin batch (expenses, grooming) | Low energy slot, low stakes | ## Tool-based batches - Everything needing the IDE → the analytical block (load context once, ~12 min saved per avoided cold-start). - Everything in the browser/email → the two comms windows. ## Energy matching Low-energy post-lunch (13:00–14:00) → admin and ticket grooming only. Never schedule a code review there. ## Transition-cost savings Each avoided switch saves ~9 min of re-orientation (attention residue). Cutting 22→6 switches = **~2.4 hours reclaimed per day**, roughly **12 hours/week**. ## Batch day vs batch hour - **Batch day:** writing (needs flow, 2h+ runway) → dedicate Mon mornings. - **Batch hour:** comms and admin (shallow, interruptible) → fixed daily windows. ## Setup / teardown rituals - **Analytical:** close Slack, headphones on, open only the PR tab. Teardown: jot the next-step note so re-entry is instant. - **Comms:** inbox-zero pass, then snooze the app until the next window.