Build an optimized time-blocked daily schedule from your task list

# Optimized Daily Schedule — Wednesday, July 3 **Energy Pattern:** Peak from 9am–12pm, secondary peak 2–4pm, low energy after 4:30pm **Constraints:** Standing meeting at 11:30am (30 min), school pickup at 5:15pm, need to finish the API design doc today --- ## Schedule Overview | Time | Block | Type | |---|---|---| | 8:00 – 8:20 | Morning startup | Routine | | 8:20 – 9:50 | Deep work: API design doc | Deep work | | 9:50 – 10:05 | Break + movement | Break | | 10:05 – 11:15 | Deep work: API design doc (cont.) | Deep work | | 11:15 – 11:30 | Meeting prep | Buffer | | 11:30 – 12:00 | Team standup | Meeting | | 12:00 – 12:15 | Meeting follow-up: action items | Buffer | | 12:15 – 1:00 | Lunch (away from desk) | Break | | 1:00 – 1:30 | Comms batch: email + Slack | Admin | | 1:30 – 1:45 | Buffer / transition | Buffer | | 1:45 – 3:15 | Focus block: code review + PR feedback | Focus work | | 3:15 – 3:30 | Break + snack | Break | | 3:30 – 4:15 | Task batch: small tasks | Batch work | | 4:15 – 4:30 | Second comms batch: email + Slack | Admin | | 4:30 – 4:50 | Shutdown routine | Routine | | 4:50 – 5:00 | Buffer (leave for pickup by 5:05) | Buffer | --- ## Detailed Block Breakdown ### 8:00 – 8:20 | Morning Startup Routine - Review today's schedule (2 min) - Check calendar for any changes (2 min) - Scan email/Slack for anything truly urgent — reply to nothing, just flag (5 min) - Review yesterday's shutdown note for context (3 min) - Set up workspace: close unnecessary tabs, put phone on DND, open only what you need (5 min) - Set an intention for the day: "Today's win = API design doc completed and sent for review" > **Rule:** Do NOT get pulled into Slack threads during startup. You're surveying the landscape, not engaging. ### 8:20 – 9:50 | Deep Work Block 1: API Design Doc **Why now:** This is your most cognitively demanding task and you're at peak energy. The 90-minute block protects flow state. **Setup:** - Slack: set status to "Deep work until 9:50 — will respond after" - Phone: DND mode - Browser: only the doc and reference materials open - If you get stuck in the first 10 minutes, write a bad first draft of the section — momentum matters more than quality in the first pass **Goal for this block:** Complete sections 1–3 (Overview, Motivation, Detailed Design) ### 9:50 – 10:05 | Break - Stand up, stretch, walk to the kitchen - Do NOT check Slack or email during this break — it will fragment your attention before block 2 - Hydrate, look out a window, let your brain idle ### 10:05 – 11:15 | Deep Work Block 2: API Design Doc (continued) **Goal:** Complete sections 4–6 (Alternatives, Migration, Open Questions) and do a full read-through **If you finish early:** Use remaining time for the executive summary (write it last — now you know what you're summarizing). Send the doc for review immediately. Don't let it sit in drafts. ### 11:15 – 11:30 | Meeting Prep Buffer - Review standup agenda (3 min) - Write down your update: what you did yesterday, what you're doing today, blockers (5 min) - Note any questions you need answered from the team (2 min) - Mental transition: shift from heads-down to collaborative mode ### 11:30 – 12:00 | Team Standup - Give your update concisely (under 2 min) - Take notes on anything that affects your work today - If a side conversation starts that doesn't need you, suggest taking it offline ### 12:00 – 12:15 | Meeting Follow-Up - Process your meeting notes immediately while they're fresh - Send any action items you committed to as messages/tickets (don't just "remember" them) - Update your task list if priorities shifted ### 12:15 – 1:00 | Lunch - Away from desk. Non-negotiable. - Eat, go outside, listen to something non-work. Your brain needs this for the afternoon. ### 1:00 – 1:30 | Comms Batch 1 - Process all email: respond, delegate, archive, or add to task list. Inbox zero. - Process Slack: respond to threads, acknowledge messages, flag anything that needs a longer response - This is the ONLY time you check comms until 4:15. Everything else can wait. ### 1:30 – 1:45 | Transition Buffer - Unscheduled. Use for overflow from comms, a quick bio break, or re-orienting to the afternoon. - Review what's left on the task list and confirm the afternoon plan still makes sense. ### 1:45 – 3:15 | Focus Block: Code Reviews + PR Feedback **Why now:** Code review is cognitively demanding but not as creative as writing — perfect for your secondary energy peak. - Review in order of priority/urgency, not order received - For each PR: read the description first, check the test coverage, then review the code - Leave actionable feedback — "consider X because Y" not just "this doesn't look right" - Target: 3-4 PRs reviewed with substantive feedback ### 3:15 – 3:30 | Break - Stand, stretch, walk. Energy is dipping — a short movement break extends your productive window by 60-90 minutes. ### 3:30 – 4:15 | Small Task Batch **Why now:** Energy is lower, so batch small tasks that don't require deep thinking. Suggested batching order: 1. Reply to that design feedback thread (10 min) 2. Update Linear tickets with today's progress (10 min) 3. Review and approve the expense report (5 min) 4. Prep tomorrow's agenda items (10 min) 5. Quick Slack replies that need more than a one-liner (10 min) ### 4:15 – 4:30 | Comms Batch 2 - Final email/Slack sweep of the day - Anything non-urgent gets flagged for tomorrow - Send any end-of-day updates to stakeholders ### 4:30 – 4:50 | Shutdown Routine This is the most important 20 minutes of your day. It's what lets you actually stop thinking about work. 1. **Capture:** Write down any open loops still in your head (3 min) 2. **Review:** Check tomorrow's calendar — any prep needed? (3 min) 3. **Plan:** Write tomorrow's top 3 priorities (5 min) 4. **Tidy:** Close all tabs, clear desktop, file loose notes (5 min) 5. **Declare:** Say out loud or write: "The workday is complete." (This sounds silly but it works — it signals your brain to shift modes.) --- ## Daily Metrics to Track - Deep work hours achieved: Target 3.5 hours (today: blocks 1 + 2 + focus = 3.75h) - Tasks completed vs. planned - Did you stick to the comms batches? (Yes/No) - Energy level at shutdown (1-10) - Biggest distraction today and how to prevent it tomorrow