# Day 9 — Inbox, Calendar & Project Management

- The operator's job is to close loops, not merely answer email. Inbox Zero means every communication or promise you started is finished or assigned.
- Gmail's open API makes it the most flexible processing hub. If the founder uses Outlook, migrate or forward to Gmail where possible; Spark is a fallback.
- Shortwave adds sorting, persistent bundles, context-aware drafts, calendar actions, intent search, and To-Dos tied to the underlying thread.
- For an overloaded inbox, choose a cutoff date and archive older mail in bulk. Maintain a founder-specific rule book where each new exception becomes a durable rule.
- Calendar practices: time block, protect 60–90 minute deep-work blocks, mirror notes into events, color-code by type, add buffers, and batch similar meetings during a weekly review.
- Confirm time zones out loud, use a second time zone or WorldTimeBuddy, send the actual invite, account for daylight saving changes, and check every relevant calendar.
- Project management has four stages: Problem, Plan, Progress, Present. Define the real problem, assign owners and deadlines with resources, choose an update channel, then present the result first and reasoning second.
- A Work Breakdown Structure turns a project into milestones, tasks, and subtasks. ClickUp terms are Workspace, Spaces, Lists, Tasks, and Subtasks.
- Close projects with three questions: what went well, what did not, and what should become a rule. Turn the answer into an SOP with purpose, details, and a walkthrough.
- Homework: practice real inbox and calendar work, draft a reply with a booking link, and create an SOP.

## Relevance to the final project

- Build the ClickUp breakdown, assign owner/deadline/status/priority, write the lead-magnet launch SOP, and present the final work with the Pyramid Principle.