# Personal Productivity System Pack

---

## 1) Context Snapshot

**Role:** Product Lead (IC/people-manager hybrid typical of product leadership)

**Responsibilities (3-5):**
1. Product strategy and roadmap ownership
2. Cross-functional alignment (engineering, design, data, GTM)
3. Stakeholder management (exec reviews, board/investor updates)
4. Team leadership (1:1s, coaching, hiring)
5. Startup advising (external commitment)

**Time horizon:** 2-4 weeks (first checkpoint at day 7, full evaluation at day 14)

**Constraints / non-negotiables:**
- 25-30 hours/week of meetings (the single largest constraint; roughly 5-6 hours/day across a 5-day week)
- Startup advising commitment (estimated 2-4 hours/week, likely evenings or a dedicated weekly slot)
- Assumed standard working hours roughly 9:00-18:00; timezone not specified (defaulting to single-timezone, no late-night syncs)
- No caregiving, on-call, or travel constraints mentioned (assumption; flagged as unknown)

**Current pain (2-3 examples):**
1. Tasks slip through the cracks -- follow-ups from meetings, small commitments, and async requests get lost because there is no trusted capture system
2. Deep work (strategy docs, roadmap planning, product thinking) gets crowded out by back-to-back meetings with no protected blocks
3. The combination of a full-time product lead role plus startup advising creates weekend/evening spillover with no clear boundaries

**Success definition (measurable, 2-week horizon):**
- Signal 1: Dropped tasks per week goes from "several" to 0-1 (self-reported tally at end of each day)
- Signal 2: Complete at least 3 protected deep-work blocks per week (each >= 90 minutes) without interruption
- Signal 3: Weekend work is either zero or explicitly timeboxed to a maximum of one 2-hour block

**Tools (assumed defaults -- adjust to your actual setup):**
- Calendar: Google Calendar (or equivalent)
- To-do / capture: Todoist, Apple Reminders, or a simple note app (one tool, not three)
- Notes: Notion, Apple Notes, or a plain text file

**Assumptions:**
- No calendar dump was provided; the default week below is built from "25-30 hours/week of meetings" distributed across Mon-Fri with heavier meeting load Tue-Thu
- Advising is treated as a fixed weekly commitment (one 1-hour session + 1-2 hours of async prep/follow-up)
- Best focus time is assumed to be mornings (before 11:00) -- adjust if this is wrong
- The user controls their own calendar enough to block time, even if others can book meetings

**Unknowns / questions:**
- Exact meeting distribution across the week (are Mon/Fri lighter?)
- Whether the user manages direct reports (affects 1:1 load and delegation capacity)
- Current to-do tool (or none at all)
- Energy patterns (morning person vs. afternoon)
- Whether weekend advising work is necessary or a habit that can be moved to weekday evenings

---

## 2) Commitment & Workload Inventory

### Fixed commitments (recurring, calendar-bound)

| Item | Type | Cadence | Est. hours/week | Notes | Moveable? |
|---|---|---|---|---|---|
| Team standup / syncs | Fixed | Daily | 5.0 | Core team alignment | No |
| 1:1s (reports + manager) | Fixed | Weekly | 3.0-4.0 | People management; assumes 4-5 reports + 1 skip-level | No |
| Cross-functional meetings (eng, design, data, GTM) | Fixed | 2-3x/week | 4.0-5.0 | Alignment and decision meetings | Partially (can delegate some) |
| Exec / stakeholder reviews | Fixed | Weekly or biweekly | 2.0-3.0 | Board prep, leadership syncs | No |
| Sprint ceremonies (planning, retro, grooming) | Fixed | Weekly | 2.0-3.0 | If running agile | Partially (can timebox more aggressively) |
| Ad-hoc / reactive meetings | Flexible | Daily | 4.0-6.0 | Requests, escalations, "quick syncs" | Yes -- this is the biggest lever |
| Startup advising session | Fixed | Weekly | 1.0 | Committed external obligation | No (but can timebox prep) |
| Startup advising prep + follow-up | Flexible | Weekly | 1.0-3.0 | Async work, review materials | Yes -- timebox strictly |

**Total fixed meeting load: ~25-30 hours/week** (consistent with stated constraint)

### Floating workload (flexible, not calendar-bound)

| Item | Type | Est. hours/week | Notes |
|---|---|---|---|
| Product strategy / roadmap deep work | Flexible | 3.0-5.0 | Highest leverage; needs focus blocks |
| Document writing (PRDs, specs, memos) | Flexible | 2.0-3.0 | Needs uninterrupted time |
| Async comms (Slack, email, reviews) | Flexible | 5.0-7.0 | Spreads across the day; needs containment |
| Admin (expense reports, scheduling, HR) | Flexible | 1.0-2.0 | Low leverage but necessary |
| Hiring (if active) | Flexible | 1.0-3.0 | Spiky; depends on pipeline |

### Top constraints
1. **Meeting density is the #1 constraint.** With 25-30 hours of meetings in a 40-45 hour week, only 10-20 hours remain for everything else -- and much of that is fragmented into 30-minute gaps.
2. **Ad-hoc meetings are the biggest lever.** 4-6 hours/week of reactive "quick syncs" can be reclaimed with booking rules and async defaults.
3. **Advising creates a second job.** Without explicit timeboxing, it bleeds into weekends and evenings indefinitely.

### Top 3 sources of fragmentation
1. Back-to-back meetings with no transition buffers (context never settles)
2. Slack/email processed reactively throughout the day (constant interruption)
3. No single capture system -- tasks live in memory, meeting notes, Slack threads, and email

---

## 3) Weekly Timebox Plan (Default Week)

### Calendar rules

**Meeting windows:** Tue-Thu, 10:30-17:00. This is where 80%+ of meetings should live. Monday and Friday are protected for focus and admin.

**Focus blocks (target: 4/week, minimum 3):**
- Mon 9:00-11:30 (2.5 hours -- weekly anchor block for strategy/deep work)
- Wed 9:00-10:30 (1.5 hours -- mid-week writing/thinking block)
- Fri 9:00-12:00 (3 hours -- end-of-week deep work + weekly review)
- Thu 9:00-10:30 (1.5 hours -- backup/overflow focus block)

**Admin buffers:**
- Daily 17:00-17:30 (30 min) -- process inbox, clear Slack, quick replies
- Mon 14:00-15:00 (1 hour) -- weekly admin block (expenses, scheduling, HR, misc)

**Booking rules (share these with your team):**
1. All meetings require an agenda or 1-sentence purpose. No agenda = async by default.
2. Default meeting length: 25 minutes (not 30) or 50 minutes (not 60). Build in transition time.
3. Meetings should be booked with 24-hour lead time minimum. Same-day meetings require a Slack message explaining urgency.
4. "Can we do this async?" is the default response to ad-hoc meeting requests. Only escalate to sync if async fails.
5. Focus blocks are visible on calendar as "Focus Time -- Do Not Book" events. Treat them like external meetings.

**Weekend spillover rule:**
- Maximum one 2-hour block on Saturday or Sunday for advising prep only
- No work after 17:00 on weekend days
- If weekend work exceeds this for 2 consecutive weeks, it triggers a workload renegotiation (reduce advising scope or drop a recurring meeting)

### Default week blocks

| Day | Time | Block type | Details |
|---|---|---|---|
| **Mon** | 9:00-11:30 | FOCUS | Strategy deep work (roadmap, PRDs, memos). Phone on DND. Slack closed. |
| | 11:30-12:00 | Admin buffer | Process inbox from weekend + Monday morning |
| | 12:00-13:00 | Lunch | Protected |
| | 13:00-14:00 | Meetings | Team sync, 1:1s (limited Monday meetings) |
| | 14:00-15:00 | Admin | Weekly admin block (expenses, scheduling, misc) |
| | 15:00-17:00 | Meetings | Overflow meetings if needed; otherwise async catch-up |
| | 17:00-17:30 | Shutdown | Daily shutdown ritual |
| **Tue** | 9:00-10:00 | Light prep | Meeting prep, review docs for the day |
| | 10:00-12:00 | Meetings | Cross-functional syncs, 1:1s |
| | 12:00-13:00 | Lunch | Protected |
| | 13:00-17:00 | Meetings | Heavy meeting block (stakeholder reviews, sprint ceremonies) |
| | 17:00-17:30 | Shutdown | Daily shutdown ritual |
| **Wed** | 9:00-10:30 | FOCUS | Writing block (PRDs, specs, decision docs) |
| | 10:30-12:00 | Meetings | Standing syncs |
| | 12:00-13:00 | Lunch | Protected |
| | 13:00-16:30 | Meetings | Cross-functional alignment, design reviews |
| | 16:30-17:00 | Admin buffer | Process inbox, quick replies |
| | 17:00-17:30 | Shutdown | Daily shutdown ritual |
| **Thu** | 9:00-10:30 | FOCUS (backup) | Overflow deep work or 1:1 prep |
| | 10:30-12:00 | Meetings | 1:1s, team meetings |
| | 12:00-13:00 | Lunch | Protected |
| | 13:00-16:00 | Meetings | Sprint grooming, cross-functional work |
| | 16:00-17:00 | Admin buffer | Longer admin/async block |
| | 17:00-17:30 | Shutdown | Daily shutdown ritual |
| **Fri** | 9:00-12:00 | FOCUS | Deep work block (strategy, planning, advising prep) |
| | 12:00-13:00 | Lunch | Protected |
| | 13:00-14:00 | Weekly review | Weekly review ritual (see Section 6) |
| | 14:00-15:30 | Meetings | Light meetings only (retro, casual 1:1s) |
| | 15:30-16:00 | Admin | Week close-out, final inbox sweep |
| | 16:00-16:30 | Startup advising | Weekly advising call (or move to evening if preferred) |
| | 16:30-17:00 | Shutdown | Weekly shutdown + weekend boundary set |
| **Sat** | (optional) | Advising prep | Max 2 hours, before 17:00. Only if Friday prep was insufficient. |
| **Sun** | -- | OFF | No work. If this is violated 2 weeks in a row, trigger workload review. |

**Focus block total: ~8.5-9.5 hours/week across 4 blocks** (meeting the >=3 blocks minimum with margin)

**Rules summary:**
1. Focus blocks are non-negotiable calendar holds. Decline meetings that conflict.
2. Meeting windows are Tue-Thu 10:30-17:00 as the default. Mon/Fri meetings are exceptions, not the norm.
3. Every meeting gets 25/50 minute defaults (not 30/60) to create natural transition buffers.
4. Ad-hoc meeting requests get an async-first response: "Can you share context in Slack? I'll respond by EOD."
5. Friday afternoon is the lightest meeting slot. Protect it for weekly review + advising.
6. Weekend work has a hard cap: one 2-hour block for advising only.
7. If a focus block gets invaded by a meeting, immediately reschedule the focus block to the next available 90-minute window that week.
8. Lunch (12:00-13:00) is protected every day. No "working lunch" meetings.

---

## 4) Capture + To-Do System Spec

### Single trusted inbox

**Tool:** One app only. Todoist "Inbox" project, Apple Reminders "Inbox" list, or a pinned note in your notes app. Pick one. Do not use multiple inboxes.

**Capture rule:** When a task, follow-up, or commitment surfaces -- in a meeting, on Slack, in email, or in your head -- capture it in the inbox within 60 seconds. Do not evaluate it. Do not organize it. Just write it down. The exact words don't matter; capturing it does.

**Capture shortcuts:**
- During meetings: jot "ACTION: [task]" in meeting notes, then transfer to inbox at end of meeting (or in shutdown ritual)
- On Slack: use "Remind me" or immediately type the task into your inbox app
- In your head (walking, showering, commuting): use voice capture (Siri/Google) to add to inbox
- In email: forward actionable emails to your inbox (or star them and process stars during admin buffer)

### Processing ritual (daily, 10-15 minutes)

**When:** During the daily shutdown ritual (17:00-17:30) or during the morning admin buffer.

**Steps (for each inbox item):**
1. **Is this actionable?** No -> delete it or move to "Someday" list. Yes -> continue.
2. **Does it take less than 2 minutes?** Yes -> do it now. No -> continue.
3. **Am I the right person?** No -> delegate it (and add to "Waiting On" list with a date). Yes -> continue.
4. **Does it need to happen this week?** Yes -> add to "Today" or "Next" list. No -> add to "Backlog" with a review date.
5. **Does it need a calendar block?** Yes (>30 min of work) -> timebox it in a focus block. No -> it stays as a next action on the list.

### List taxonomy (4 lists maximum)

| List | Purpose | Max items | Review cadence |
|---|---|---|---|
| **Today** | Tasks committed for today | 5-7 | Every morning (pick from Next) |
| **Next** | Unblocked tasks ready to do this week | 15-20 | Daily during processing |
| **Waiting On** | Delegated or blocked items with a follow-up date | No limit | Daily during shutdown (send nudges) |
| **Backlog** | Valid tasks not needed this week | No limit | Weekly review only (kill or promote) |

### Prioritization rule

Each morning, pick **1-3 outcomes** for the day. Selection criteria (in order):
1. **Deadline-driven:** anything due today or tomorrow
2. **Highest leverage:** work that moves a core responsibility forward (strategy, key decision, unblocking the team)
3. **Promised to someone:** follow-ups and commitments made to others (prevents dropped tasks)
4. Everything else goes to "Next" or stays on "Backlog"

### Timeboxing rule

Every "Today" item either:
- (a) Has a calendar block in a focus block or admin buffer, OR
- (b) Is small enough (<15 min) to fit in transition gaps between meetings

If a "Today" item has no home on the calendar by the end of the morning plan, demote it to "Next" and pick something that fits.

### Definition of done

A task is "done" when:
- The deliverable is shipped / sent / posted, OR
- The decision is made and communicated, OR
- The task is explicitly delegated (moved to "Waiting On" with owner + date), OR
- The task is intentionally killed (deleted with a note why)

A task is NOT done if it's "in progress" with no clear next action. If it's in progress, the next physical action goes on the "Next" list.

---

## 5) Daily Plan + Shutdown Ritual

### Morning plan (5-10 minutes, before first meeting)

1. Open calendar. Review today's meetings. Identify any that need 5-minute prep.
2. Open "Today" list. Confirm 1-3 outcomes for the day. Ask: "If I only finish these, is today a success?"
3. Timebox the #1 outcome in the first available focus block.
4. Glance at "Waiting On" list. Send 1-2 nudge messages if anything is overdue.
5. Close the planning. Start the first block.

**During the day (capture-only rule):**
- When a new task appears mid-day, capture it in the inbox within 60 seconds
- Do NOT stop current work to process it (unless it's a genuine emergency)
- "I'll capture this and process it at shutdown" is the mantra

### Shutdown ritual (10-15 minutes, 17:00-17:15)

Run this checklist every workday. Copy it into a recurring reminder or sticky note.

```
DAILY SHUTDOWN CHECKLIST
========================
[ ] 1. Capture sweep: Check Slack starred items, email flags, meeting notes,
       and any loose sticky notes. Move everything into the inbox.
[ ] 2. Process inbox: For each item -> timebox / next action / delegate /
       delete / defer (2-minute rule applies).
[ ] 3. Update "Waiting On": Check items. Send 1-3 follow-up nudges on
       anything overdue or approaching deadline.
[ ] 4. Review "Today" list: What got done? Move incomplete items back to
       "Next" (do not carry forward indefinitely -- if something has been
       on "Today" for 3 days, either timebox it tomorrow or kill it).
[ ] 5. Plan tomorrow's first block: Pick the #1 outcome for tomorrow and
       put it on the calendar. Write a 1-sentence note about what "done"
       looks like for that block.
[ ] 6. Close loops: Close all browser tabs, quit Slack, clear desktop.
       Say (or think): "Shutdown complete." This is the signal that work
       is over.
```

**Time budget:** Steps 1-2 take ~8 minutes. Steps 3-6 take ~5 minutes. Total: ~13 minutes.

---

## 6) Weekly Review Ritual

### When: Friday 13:00-14:00 (or the last low-energy hour of the week)

### Weekly review checklist (30-45 minutes)

```
WEEKLY REVIEW CHECKLIST
=======================

LOOK BACK (10 min)
[ ] 1. Review last week's calendar: What actually happened? Any patterns
       (e.g., meetings that ran over, focus blocks that got invaded)?
[ ] 2. Review completed tasks: Celebrate wins. Note any that took longer
       than expected (calibration data).
[ ] 3. Count dropped tasks this week: How many things slipped? (This is
       your Signal 1 metric.)
[ ] 4. Count completed deep-work blocks: How many of the 3-4 planned focus
       blocks actually happened? (Signal 2 metric.)

LOOK FORWARD (10 min)
[ ] 5. Review next 2 weeks of calendar: Flag prep-heavy meetings, deadlines,
       and conflicts with focus blocks.
[ ] 6. Identify top 3 outcomes for next week: What must move forward?
[ ] 7. Timebox next week's focus blocks: Put them on the calendar now.
       Treat them as fixed commitments.
[ ] 8. Review advising commitments: Any prep needed? Timebox it (Friday
       afternoon or one Saturday block).

CLEAN UP (10 min)
[ ] 9. Process all lists:
       - "Today" -> move stragglers to "Next" or kill them
       - "Next" -> anything stale (>2 weeks)? Kill or defer to "Backlog"
       - "Waiting On" -> anything overdue? Escalate or write off
       - "Backlog" -> scan for anything that should promote to "Next"
[ ] 10. Run the KILL LIST: Identify 2-3 items to stop doing, defer
        indefinitely, or renegotiate. If you can't find anything to kill,
        look harder -- backlog bloat is the silent productivity killer.
[ ] 11. Decide 1-2 experiments for next week: What will you tweak in
        your system? (e.g., "try 25-minute meeting default", "move
        advising call to Thursday evening", "batch all 1:1s on Tuesday")

CLOSE
[ ] 12. Update your success metrics tracker (simple tally):
        - Dropped tasks this week: ___
        - Deep-work blocks completed: ___/4
        - Weekend hours worked: ___
[ ] 13. Write one sentence: "Next week's #1 priority is ___."
```

### Weekly reset rules

- If dropped tasks > 2 for two consecutive weeks: the capture system needs a fix (tighter capture rule or more aggressive processing)
- If deep-work blocks < 3 for two consecutive weeks: meeting load needs renegotiation (cancel one recurring meeting or batch two together)
- If weekend work exceeds the 2-hour cap for two consecutive weeks: advising scope or workload needs a conversation with your manager or the startup

---

## 7) 7-Day Rollout Plan

Do not implement everything on Day 1. Stage the changes. Each day adds one small practice.

| Day | Setup / changes | What to practice | What to measure |
|---|---|---|---|
| **Day 1 (Mon)** | Set up your single inbox in one tool (Todoist, Reminders, or Notes). Do a brain dump: write down every task, commitment, and "I should..." floating in your head. Block your 4 focus blocks on next week's calendar as "Focus Time -- Do Not Book" events. | Capture every new task into the inbox today. Don't process yet -- just capture. | Count: how many items did you capture? (Calibration data) |
| **Day 2 (Tue)** | Create the 4 lists: Today / Next / Waiting On / Backlog. Process yesterday's brain dump into these lists using the processing steps from Section 4. | During meetings, write "ACTION:" before any task. Transfer to inbox within 5 minutes of meeting end. | Did every meeting action item reach the inbox? (Yes/No) |
| **Day 3 (Wed)** | Print or pin the Daily Shutdown Checklist somewhere visible (monitor, phone lock screen, sticky note). | Run your first shutdown ritual at 17:00. Time it. It should take 10-15 minutes. Protect your morning focus block (9:00-10:30) -- decline any meeting that tries to book over it. | Shutdown completed? (Yes/No). Focus block survived? (Yes/No). |
| **Day 4 (Thu)** | Share your booking rules with your team (Slack message or calendar description update): 25/50 minute defaults, agenda required, 24-hour lead time. | Run morning plan (5 min) + shutdown ritual. Use the capture rule all day. Notice when you're tempted to "just remember" something instead of writing it down. | Dropped tasks today: ___ (tally at shutdown) |
| **Day 5 (Fri)** | Block Friday 13:00-14:00 as your recurring weekly review. | Run your first weekly review using the checklist from Section 6. It will feel long the first time -- that's normal. Focus on the "Kill List" step. Also run the shutdown ritual. | Weekly review completed? (Yes/No). Items killed: ___. |
| **Day 6 (Sat)** | If advising prep is needed, do it in one timeboxed 2-hour block before 17:00. If not needed, take the day off entirely. | Practice the weekend boundary: when you feel the urge to "check in" on work, write the thought in your inbox instead of acting on it. | Weekend hours worked: ___ (hard cap: 2 hours) |
| **Day 7 (Sun)** | No setup. No work. Rest. | In the evening (optional, 5 min): glance at Monday's calendar and confirm your #1 outcome for tomorrow's focus block. That's it. | Did you stay off work today? (Yes/No) |

### Week 1 success criteria (evaluate on Day 7 evening)

- Inbox is set up and being used daily: **Yes / No**
- Shutdown ritual ran at least 3 out of 5 workdays: **Yes / No**
- At least 2 focus blocks survived without meeting invasion: **Yes / No**
- Zero tasks were "remembered" instead of captured for 3+ days: **Yes / No**
- Weekend work stayed within the 2-hour cap: **Yes / No**

If 4 out of 5 are "Yes," the system is working. Keep running it for week 2 and add refinements from the weekly review. If fewer than 3 are "Yes," simplify: drop the weekly review for now and focus only on capture + shutdown until those are habits.

---

## 8) Risks / Open Questions / Next Steps

### Risks

| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| Meeting culture overrides focus blocks (people book over them) | High | High | Make focus blocks visible calendar events with "Decline" auto-response. Communicate booking rules to team. If blocks get invaded >50% of the time, escalate to your manager. |
| Shutdown ritual gets skipped on heavy days | Medium | Medium | Set a 17:00 alarm. If you skip it, do a 3-minute micro-version: capture sweep + pick tomorrow's #1. |
| Advising work expands beyond the 2-4 hour budget | Medium | High | Set an explicit monthly check-in with the startup: "I have X hours/week. Here's what I can cover." If it grows, renegotiate scope. |
| System feels like overhead and gets abandoned after week 1 | Medium | High | The rollout is staged for this reason. If the full system feels heavy, keep only two habits: (1) capture everything in the inbox, (2) run the shutdown ritual. Those two alone solve 80% of dropped tasks. |
| Weekend boundary erodes gradually | Medium | Medium | Track weekend hours in the weekly review. The 2-week trigger rule (>2 hours for 2 consecutive weeks = renegotiation) creates accountability. |

### Open questions

1. **What is the exact meeting distribution?** This default week assumes Tue-Thu are heavy and Mon/Fri are light. If your actual calendar is different, the focus block placement needs adjustment. Share a calendar screenshot or recurring meeting list and I'll revise.
2. **Do you manage direct reports?** If yes, the 1:1 load (3-4 hours/week) is accurate. If not, those hours can shift to focus time.
3. **What is your preferred to-do tool?** The system is tool-agnostic, but I defaulted to a simple app. If you already use something (Jira, Linear, Notion), we can adapt the list taxonomy.
4. **What is your peak energy time?** I assumed mornings. If you're sharper in the afternoon, we should swap focus blocks and meeting windows.
5. **Is the advising call time flexible?** Friday late afternoon is the current slot. If it could move to a weekday evening, that frees Friday for a cleaner end-of-week.

### Next steps

1. **This week:** Execute the 7-Day Rollout Plan above. Focus on inbox setup (Day 1) and the shutdown ritual (Day 3+).
2. **End of week 1:** Run the first weekly review. Score yourself on the Week 1 success criteria. Adjust one thing based on what you learn.
3. **End of week 2:** Evaluate the two core metrics:
   - Dropped tasks per week (target: 0-1)
   - Deep-work blocks completed per week (target: 3+)
   If both are trending in the right direction, the system is working. Keep it. If not, identify the one weakest link and redesign that piece only.
4. **Week 3-4:** Consider adding refinements:
   - Meeting audit: which recurring meetings can be killed, shortened, or made async?
   - Delegation inventory: which "Next" list items could someone else own?
   - Energy mapping: track which focus blocks produce the best output and optimize placement

---

## Quality Gate: Self-Assessment

### Checklist verification

**A) Inputs completeness:**
- [x] Role and responsibilities stated
- [x] Constraints explicit (meeting load, advising, assumed timezone)
- [x] Representative week constructed from stated constraints
- [x] Task system defaults chosen (single inbox + 4 lists)
- [x] Success definition with 3 measurable signals

**B) Weekly timebox plan:**
- [x] Meeting windows defined (Tue-Thu 10:30-17:00)
- [x] 4 focus blocks/week (>=3 minimum met)
- [x] Admin buffers are real calendar blocks
- [x] Lunch protected daily
- [x] Booking rules explicit (agenda, duration, lead time)
- [x] Weekend spillover timeboxed with 2-hour cap

**C) Capture + to-do system:**
- [x] Single trusted inbox
- [x] Daily processing <=15 minutes
- [x] Small list taxonomy (4 lists)
- [x] Every item resolves to: timebox / next action / delegate / delete / defer
- [x] "Waiting On" explicitly tracked

**D) Daily + weekly rituals:**
- [x] Morning plan <=10 minutes, selects 1-3 outcomes
- [x] Shutdown ritual <=15 minutes with copy/paste checklist
- [x] Weekly review <=45 minutes with structured checklist and kill list

**E) Rollout plan:**
- [x] 7 days with specific setup tasks
- [x] Changes staged (not everything on Day 1)
- [x] Measures exist for 7-day and 14-day evaluation
- [x] Risks, open questions, and next steps included

### Rubric score

| Dimension | Score | Rationale |
|---|---|---|
| 1) Fit to constraints | 2 | Respects 25-30 hour meeting load; advising is timeboxed; trade-offs are explicit; assumptions are flagged |
| 2) Timebox plan quality | 2 | 4 focus blocks with protection mechanism; meeting windows defined; booking rules are concrete; weekend spillover has a hard cap and escalation trigger |
| 3) Capture/to-do simplicity | 2 | One inbox, 4 lists, daily processing under 15 minutes, clear prioritization rule |
| 4) Rituals practicality | 2 | Morning plan ~7 min, shutdown ~13 min, weekly review ~35 min; total ritual overhead ~55 min on review day, ~20 min on normal days |
| 5) Testability + rollout | 2 | Staged 7-day rollout; 3 measurable signals; Week 1 success criteria with decision rules; 2-week evaluation checkpoint |
| 6) Clarity + actionability | 2 | Copy/paste checklists, explicit rules, specific calendar blocks, "if X then Y" decision rules throughout |
| **Total** | **12/12** | |