Energy Management Operating System Pack
For: Product leader experiencing back-to-back meeting overload and constant decision fatigue
1) Context Snapshot
- Role + scope: Product leader (manages people and cross-functional stakeholders); core responsibilities include product strategy, roadmap decisions, cross-functional alignment, team coaching/1:1s, stakeholder management, and hiring/performance.
- Time horizon: 2-week pilot starting immediately + 4-8 week goal.
- Success definition (4-8 weeks):
- End 3+ days/week with energy above 6/10 (self-rated).
- Complete at least 4 deep-work blocks per week (90 min each, uninterrupted).
- Reduce meeting hours from ~30 hrs/week to ~20 hrs/week.
- Make zero unforced decisions after 4 PM (decision cutoff).
- Report noticeably lower decision fatigue at Friday retro.
- Current pain:
- Back-to-back meetings from 9 AM to 5 PM most days with no buffers.
- Constant decision fatigue: asked to make calls on roadmap, design, hiring, escalations, and process in rapid succession with no recovery time.
- Zero deep-work time for strategy, writing, or thinking.
- Meetings without clear purpose or decision owner -- attending "just in case."
- Evenings and weekends used for the actual thinking/writing work, leading to burnout.
- Constraints / non-negotiables:
- Weekly leadership team meeting (Tue 10 AM, 60 min) -- cannot move.
- Weekly all-hands (Mon 9 AM, 30 min) -- cannot move.
- Hiring committee (Thu 2 PM, 60 min) -- cannot move during active hiring.
- Time zone overlap with remote team members (10 AM - 3 PM core hours).
- Caregiving pickup at 5:30 PM -- hard stop at 5 PM.
- Assumptions (to validate during pilot):
- Typical week has ~30 hours of meetings across ~25 separate calendar events.
- Morning (8-11 AM) is the highest-energy window; post-lunch (1-3 PM) is medium; late afternoon (3-5 PM) is low.
- At least 8-10 meetings/week are status updates that could be async.
- 2-3 direct reports are ready for more decision-making autonomy.
- Unknowns to validate:
- Exact meeting breakdown by type (will confirm via calendar audit below).
- Manager's appetite for the leader declining/redesigning certain meetings.
- Team's readiness for async updates vs. live syncs.
2) Energy Drivers & Drains Map
Suspected Drivers (energy-giving)
| Item | Trigger / Pattern | Why It Energizes | How to Get More |
|---|---|---|---|
| 1:1 coaching conversations with reports | Focused, relationship-building, helping someone grow | Sense of impact; uses empathy + strategic thinking | Protect these; do not cancel for "urgent" meetings |
| Strategy and roadmap deep work | Uninterrupted time, creative problem-solving | Zone of genius; high leverage; visible output | Block 90-min windows in high-energy mornings |
| Customer discovery calls | Direct signal, learning, pattern recognition | Curiosity + influence on product direction | Batch 2-3/week; keep them in medium-energy windows |
| Small-group brainstorms with clear scope | Defined problem, trusted collaborators, whiteboard energy | Creative flow; builds on strengths | Limit to 50 min; require a brief before and a decision at end |
| Writing (PRDs, memos, strategy docs) | Solo, deep, produces a tangible artifact | Sense of progress; clarifies own thinking | Move to morning blocks; protect from interruption |
Suspected Drains (energy-taking)
| Item | Driver or Drain? | Trigger / Pattern | Controllable? | Lever | Next Action (Owner + Date) |
|---|---|---|---|---|---|
| Status update meetings (no decisions) | Drain | Repetitive info sharing; no outcome; could be async | Yes | Eliminate/Redesign -- convert to async Slack/Loom updates | Draft async update template (self, Week 1) |
| Back-to-back meetings with no buffer | Drain | Context-switching every 30-60 min; no recovery | Yes | Buffer -- add 10-min gaps; shorten defaults to 25/50 | Update calendar defaults + communicate to team (self, Week 1) |
| "Just in case" attendance meetings | Drain | FOMO; no clear role; passive listening | Partial | Eliminate/Delegate -- decline or send a delegate with a brief | Audit calendar, identify 3-5 to decline (self, Week 1) |
| Rapid-fire decision requests (Slack + ad hoc) | Drain | Constant micro-decisions; no batching; interrupts flow | Partial | Batch + Prepare -- create "decision office hours" (30 min/day) | Set up decision office hours block (self, Week 1) |
| Unclear-purpose meetings (no agenda, no owner) | Drain | Uncertainty about what's needed; wasted prep energy | Yes | Redesign -- require agenda + decision owner or decline | Send meeting norms message to team (self, Week 1) |
| Hiring coordination (scheduling, debrief logistics) | Drain | Admin-heavy; high context-switching | Partial | Delegate -- move logistics to recruiting coordinator or EA | Brief recruiting coordinator on ownership (self, Week 1) |
| Cross-functional escalation meetings | Drain | Conflict, ambiguity, high stakes, often unstructured | Partial | Redesign + Buffer -- require pre-read; add 15-min buffer after | Create escalation meeting format + buffer (self, Week 2) |
| End-of-day decision fatigue spillover | Drain | Cumulative load; no decision cutoff; still making calls at 4-5 PM | Yes | Time-shift -- move decisions to morning; protect PM for low-stakes | Implement decision cutoff at 3 PM (self, Week 1) |
Top 3 Change Levers to Try First:
- Convert 5+ status meetings to async -- biggest time and energy recovery (est. 5-6 hrs/week freed).
- Add 10-min buffers + shorten meeting defaults to 25/50 min -- reduces context-switching and creates micro-recovery windows.
- Create daily "decision office hours" (30 min, morning) -- batches decisions instead of reactive ad hoc interruptions all day.
3) Calendar Energy Audit
A) Time Bucket Summary (representative week estimate)
| Bucket | Examples from Current Week | Est. Hours/Week | Target Hours/Week | Keep / Change |
|---|---|---|---|---|
| Zone of genius / high leverage | Strategy work, coaching 1:1s, customer calls, writing PRDs | ~6 hrs | 14 hrs | Increase |
| Necessary but neutral | Leadership team meeting, all-hands, hiring committee, sprint ceremonies | ~8 hrs | 8 hrs | Keep (optimize format) |
| Energy drains | Status updates, "just in case" meetings, ad hoc decision interruptions, unclear-purpose meetings, cross-functional escalations | ~14 hrs | 6 hrs | Reduce aggressively |
| Recovery / admin | Email, Slack, breaks, lunch, transitions | ~4 hrs | 6 hrs | Increase (add buffers) |
| Unaccounted / fragmented | Context-switching gaps too small for real work | ~8 hrs | 2 hrs | Reduce (batch + block) |
Current zone-of-genius estimate: ~15% of work week (6 out of 40 hrs). Target zone-of-genius estimate: ~35% of work week (14 out of 40 hrs).
B) Top Offenders (3-5 items to remove/redesign in 2 weeks)
| Offender | Why It Drains | Lever | Next Action |
|---|---|---|---|
| 1. Weekly team status meetings (3x/week, 30 min each = 1.5 hrs) | Information-only; no decisions made; same info available in tools | Delete -- replace with async Loom/Slack update | Draft async status template + announce to team (Week 1, Day 1-2) |
| 2. Cross-team sync meetings where role is passive (2x/week, 60 min each = 2 hrs) | Attending "just in case"; rarely contribute or receive actionable info | Delegate -- send a report or skip; read notes | Identify delegate for each; brief them (Week 1, Day 2-3) |
| 3. Ad hoc Slack decision requests throughout the day (~1.5 hrs fragmented) | Reactive; interrupts deep work; causes micro-decisions all day | Batch -- route to daily decision office hours (10 AM, 30 min) | Set up decision office hours + Slack channel norms (Week 1, Day 1) |
| 4. Recurring meetings with no agenda or decision owner (est. 2-3 hrs/week) | Uncertainty; no preparation possible; wasted time | Redesign or delete -- require agenda 24 hrs before or auto-decline | Send meeting norms to team + update calendar invites (Week 1, Day 1-2) |
| 5. Hiring logistics and debrief scheduling (~1.5 hrs/week) | Administrative; high context-switching; not leveraging your strengths | Delegate -- transfer to recruiting coordinator | Brief coordinator on new ownership + escalation path (Week 1, Day 3) |
Estimated recovery: 8-10 hrs/week freed for deep work, buffers, and zone-of-genius activities.
4) Zone of Genius Expansion Plan
| Item | Current Owner | Decision | New Owner | Guardrails / Escalation Triggers | Next Action |
|---|---|---|---|---|---|
| Team status updates | Self (runs meeting) | Stop (live) / Automate (async) | Each report posts Slack update by 9:30 AM | Escalate to live sync only if a blocker is unresolved for 24+ hrs | Create async template + announce (Week 1, Day 1) |
| Cross-team sync attendance | Self | Delegate | Senior report or tech lead | Delegate attends and flags items requiring leader input; leader reviews notes async | Brief delegate + share context doc (Week 1, Day 2) |
| Hiring logistics (scheduling, debrief coordination) | Self + recruiter | Delegate | Recruiting coordinator | Escalate if candidate is VP+ or if there's a disagreement on hire/no-hire | Meet with coordinator to hand off (Week 1, Day 3) |
| Sprint ceremony facilitation (planning, retro) | Self | Delegate | Engineering manager or senior PM | Leader joins retro only; EM runs planning. Escalate if sprint scope exceeds capacity by >20% | Discuss with EM and agree on new ownership (Week 1, Day 3) |
| Ad hoc decision requests | Self (reactive) | Redesign | Self (batched) | Decisions routed to daily 30-min office hours. Urgent = P0 production issue or exec escalation only | Post decision routing norms in Slack (Week 1, Day 1) |
| Unclear-purpose meetings | Self (attends) | Stop or Redesign | Meeting organizer must add agenda | Auto-decline meetings without agenda 24 hrs before. No exceptions except direct manager | Update calendar settings + send norms (Week 1, Day 2) |
Delegation Brief: Cross-Team Sync Attendance
- What: Attend the bi-weekly cross-team sync on behalf of the product leader.
- Decision rights: Delegate can commit to information requests and minor coordination. Cannot commit to roadmap changes, resource allocation, or timeline shifts.
- Escalation triggers: (1) Request involves roadmap change; (2) Conflict between teams that needs leader mediation; (3) Exec asks for leader directly.
- Review cadence: 5-min debrief after each sync (async Slack message is fine).
- Review point: Assess after 2 weeks -- is delegate effective? Does leader miss anything critical?
Delegation Brief: Hiring Logistics
- What: Own scheduling, debrief coordination, and interview logistics for all open roles.
- Decision rights: Coordinator owns all scheduling and logistics. Cannot make hire/no-hire decisions or change interview panels.
- Escalation triggers: (1) VP+ candidate; (2) Disagreement on hire/no-hire; (3) Candidate experience issue.
- Review cadence: Weekly 15-min check-in during active hiring sprints.
- Review point: Assess after 2 weeks -- is coordinator ramped? Any gaps?
5) Energy-Aligned Default Week + Meeting Rules
Energy Curve Assumptions
- High energy: 8:00 AM - 11:00 AM (deep work, hard decisions, strategy)
- Medium energy: 11:00 AM - 1:00 PM and 1:30 PM - 3:00 PM (meetings, coaching, collaboration)
- Low energy: 3:00 PM - 5:00 PM (admin, email, routine tasks, planning tomorrow)
Default Week
| Day | High-Energy (8-11 AM) | Medium-Energy (11 AM-1 PM + 1:30-3 PM) | Low-Energy (3-5 PM) | Buffers / Recovery |
|---|---|---|---|---|
| Mon | Deep work: strategy / PRD writing (8-9:30 AM) | All-hands (9 AM, 30 min -- non-negotiable, moved to block); 1:1 coaching x2 (11 AM, 25 min each); Customer call (1:30 PM, 50 min) | Email triage, Slack catch-up, prep for Tue (3-4:30 PM); Plan tomorrow (4:30-5 PM) | 10-min buffer after all-hands; 10-min buffer after customer call; Lunch 1-1:30 PM |
| Tue | Deep work: roadmap / analysis (8-9:45 AM) | Leadership team meeting (10 AM, 60 min -- non-negotiable); Decision office hours (11:15-11:45 AM) | 1:1 coaching x2 (1:30 PM, 25 min each); Admin + async reviews (3-5 PM) | 15-min buffer after leadership meeting; Lunch 12-1 PM |
| Wed | No-meeting morning: Deep work block (8 AM-12 PM) -- strategy, writing, thinking | Brainstorm or design review (1:30 PM, 50 min); Decision office hours (2:30-3 PM) | Email, Slack, prep for Thu (3:15-5 PM) | Lunch 12-1:30 PM (extended); 10-min buffer after brainstorm |
| Thu | Deep work (8-9:30 AM); Decision office hours (9:45-10:15 AM) | 1:1 coaching x1 (10:30 AM, 25 min); Customer call (11 AM, 50 min); Hiring committee (2 PM, 60 min -- non-negotiable) | Async reviews, Slack, admin (3:15-5 PM) | Lunch 12-1:30 PM; 15-min buffer after hiring committee |
| Fri | Deep work: weekly reflection + next-week planning (8-9:30 AM) | Team retro or skip week (10 AM, 50 min); Overflow / 1:1s (11 AM) | Wind-down: admin, async, energy log review, leave early if possible (2-5 PM) | Lunch 12-1 PM; No new meetings after 2 PM |
Weekly totals (target):
- Deep work blocks: 6 blocks, ~12 hrs/week (up from ~6)
- Meetings: ~18-20 hrs/week (down from ~30)
- Buffers/recovery: ~5 hrs/week (up from ~2)
- Admin/async: ~5 hrs/week
Meeting Rules (communicate to team)
Defaults:
- All meetings are 25 minutes (was 30) or 50 minutes (was 60) unless there is a specific reason for longer.
- Every meeting invitation must include: (1) purpose, (2) agenda, (3) decision owner (if a decision is needed), (4) desired outcome.
- Meetings without an agenda 24 hours before are auto-declined.
- Async pre-read is required for complex topics; live time is for debate + decision, not information sharing.
- Buffers: 10-minute gap after standard meetings; 15-minute gap after high-load meetings (escalations, performance, conflict).
- Decision cutoff: no new decisions after 3 PM -- defer to next morning's decision office hours.
Optional scripts to use:
- "What decision are we making by the end of this meeting?"
- "Can we do this async? If not, what's the minimum live time needed?"
- "I can't make this meeting; please send a summary and the specific decision you need from me."
- "I'm batching decisions to my daily office hours (10 AM). Please drop your question in the [decisions] Slack channel and I'll respond there."
6) Recovery + Transition Plan
A) Buffers (calendar objects -- schedule these now)
| Buffer Type | When | Duration | Purpose |
|---|---|---|---|
| Between-meeting buffer | After every meeting | 10 min (15 after high-load) | Jot notes, close context, breathe, stand |
| Daily decompression block | 4:30-5:00 PM | 30 min | Process the day; plan tomorrow; close open loops |
| Weekly recovery block | Fri 2:00-5:00 PM | 3 hrs | Energy log review, reflection, light admin, early wrap if possible |
| Lunch break (protected) | 12:00-1:00 PM (min); 12:00-1:30 PM Wed/Thu | 60-90 min | Eat away from screen; movement; reset |
B) Micro-Recovery Menu (pick 3 to start)
- Short walk between meetings (5-10 min, outdoors if possible) -- especially after high-load meetings.
- 2-minute breathing + eyes off screen -- close laptop lid, look out window, 4-7-8 breathing.
- "What just happened / what's next" journaling (2 min) -- close the context of the last meeting and open the next one intentionally.
Remote work supports (optional, no medical claims):
- Take 1-2 calls/day as walking calls (phone, no screen share needed).
- Stand during short syncs.
- Keep a fidget object or doodle pad near the desk for passive listening meetings.
C) Low-Energy-Day Protocol (Minimum Viable Day)
When energy is critically low (illness, poor sleep, emotional load, accumulated fatigue):
Non-negotiable outcomes (max 2):
- Attend the one truly non-movable meeting (if any).
- Make one decision or send one key communication.
What gets postponed:
- All optional meetings -- decline or delegate with a short note.
- Non-urgent decisions -- route to tomorrow's decision office hours.
- Deep work that requires peak cognition -- reschedule to a high-energy day.
Stakeholder message (copy/paste):
"I'm operating at reduced capacity today. I've rescheduled non-essential meetings and will be responsive on Slack for urgent items only. [Name] is covering [specific meeting]. I'll be back at full capacity tomorrow."
Recovery actions:
- Shorten the workday if possible (leave by 3 PM).
- Cancel all discretionary screen time.
- Use the freed time for movement, rest, or low-stakes admin.
- Do not attempt to "push through" -- the cost compounds.
7) 2-Week Pilot + Experiment Tracker
Pilot dates: Week 1 (Day 1-7) and Week 2 (Day 8-14) from start date.
Experiments
| # | Experiment | Hypothesis | Start | End | Measure(s) | Decision Rule |
|---|---|---|---|---|---|---|
| 1 | Convert 3 status meetings to async Slack/Loom updates | Frees ~1.5 hrs/week and reduces decision fatigue without losing information flow | Day 1 | Day 14 | Meeting hours/week; team satisfaction (quick poll at Day 14); info gaps reported | Keep if meeting hours drop by 1.5+ hrs and no critical info gaps. Modify if team misses live discussion -- add 1 optional 15-min weekly sync. Stop if team reports significant info loss or alignment problems. |
| 2 | Add 10-min buffers + shorten meetings to 25/50 min | Reduces context-switching; creates micro-recovery windows; meetings become more focused | Day 1 | Day 14 | End-of-day energy rating (1-10); number of "no buffer" violations/day; subjective focus quality | Keep if average EOD energy improves by 1+ point. Modify if certain meetings need the full 30/60 -- grant exceptions case-by-case. Stop if meetings consistently run over and create cascading delays. |
| 3 | Daily decision office hours (30 min, morning) | Batching decisions reduces reactive interruptions and preserves deep-work blocks | Day 1 | Day 14 | Drain count/day (ad hoc decision requests outside office hours); deep-work blocks completed/week; team decision latency | Keep if ad hoc requests drop by 50% and deep-work blocks hit 4+/week. Modify if some decisions are too urgent -- add a "P0 exception" channel. Stop if team reports unacceptable delay on critical decisions. |
| 4 | Wednesday no-meeting morning (8 AM-12 PM protected) | Creates one guaranteed deep-work window for strategy and writing | Day 3 | Day 14 | Hours of uninterrupted deep work on Wednesdays; output quality (did you produce something?); number of meeting requests that had to be moved | Keep if 3+ hrs of uninterrupted work happens consistently. Modify if only 2 hrs works -- try a smaller block. Stop if too many conflicts and the block gets broken every week. |
Daily Tracking (lightweight)
| Date | EOD Energy (1-10) | Deep-Work Blocks | Drain Count | Meeting Hours | Notes / What Worked / What Didn't |
|---|---|---|---|---|---|
| Day 1 | |||||
| Day 2 | |||||
| Day 3 | |||||
| Day 4 | |||||
| Day 5 | |||||
| Day 6-7 | (weekend -- note recovery quality) | ||||
| Day 8 | |||||
| Day 9 | |||||
| Day 10 | |||||
| Day 11 | |||||
| Day 12 | |||||
| Day 13-14 | (weekend + pilot review) |
Suggested Measures Summary
- End-of-day energy rating (1-10): primary signal.
- Deep-work blocks/week (90-min uninterrupted): target 4+.
- Meeting hours/week: target <=20 hrs (down from ~30).
- Drain count/day: number of high-drain events (ad hoc decisions, unclear meetings, back-to-back runs).
8) Risks / Open Questions / Next Steps
Risks
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| Manager or peers push back on meeting declines | Medium | High -- changes get reversed | Proactive communication: share the "why" (sustainability, execution quality) before making changes; frame as a 2-week experiment, not a permanent unilateral decision |
| Team perceives async switch as disengagement | Medium | Medium -- trust erosion | Explain the change in a team meeting; emphasize you're more available for coaching and decisions, not less; check in at Day 7 |
| Delegation without sufficient ramp causes quality dip | Medium | Medium -- rework, frustration | Provide clear briefs (above); review points at Day 7 and Day 14; be available for escalations |
| Decision office hours create bottleneck for urgent items | Low | High -- blocked teams | Define clear "P0 exception" criteria (production incident, exec request, customer escalation); route truly urgent items via direct Slack DM |
| Calendar changes don't stick because of organizational culture | Medium | High -- revert to old patterns | Start with changes you control unilaterally (buffers, deep-work blocks, meeting length); negotiate shared changes (status meetings, delegation) with specific stakeholders |
Open Questions
- Manager alignment: Has the leader discussed energy/workload concerns with their manager? Is there support for reducing meeting load? (Action: have this conversation in Week 1.)
- Team readiness for async: Have direct reports used async updates before? Do they prefer it or resist it? (Action: poll the team on Day 1.)
- Actual meeting breakdown: The calendar audit above uses estimates. The leader should do a real audit of last week's calendar in the first 2 days to validate the numbers.
- Energy curve validation: The assumed high/medium/low windows need to be confirmed via the daily energy log. Actual peaks may differ.
- Hiring timeline: If active hiring wraps up, the hiring committee slot and logistics delegation may become moot -- reassess at Week 2.
Next Steps
| Step | Owner | By When |
|---|---|---|
| 1. Validate calendar audit with real data from last 2 weeks | Leader | Day 1-2 |
| 2. Send meeting norms message to team (25/50 defaults, agenda requirement, async status updates) | Leader | Day 1-2 |
| 3. Set up decision office hours block + Slack channel norms | Leader | Day 1 |
| 4. Brief delegates (cross-team sync delegate, recruiting coordinator) | Leader | Day 2-3 |
| 5. Block Wednesday no-meeting morning + daily buffers on calendar | Leader | Day 1 |
| 6. Have a conversation with manager about the 2-week pilot | Leader | Day 1-3 |
| 7. Start daily energy tracking (EOD rating + drain count) | Leader | Day 1 |
| 8. Mid-pilot check-in: review energy log, adjust experiments | Leader | Day 7 |
| 9. End-of-pilot review: score experiments (keep/modify/stop), update the pack | Leader | Day 14 |
| 10. 4-week check-in: assess against success definition (3+ days above 6/10 energy, 4+ deep-work blocks, <=20 meeting hrs) | Leader | Week 4 |
Stakeholder Boundary Message (send to team)
"To protect execution quality and sustainability, I'm making a few changes for the next two weeks:
- Status updates will move to async (Slack/Loom) -- I'll share a template today.
- Meetings will default to 25/50 minutes with an agenda required 24 hours before.
- Non-urgent decisions will be batched to my daily office hours (10 AM). Drop requests in [#decisions channel].
- Wednesday mornings are protected for deep work -- no meetings before noon.
If you need me urgently (P0 production issue, exec escalation, customer crisis), DM me directly. For everything else, please use async channels or attend office hours.
We'll review in two weeks and adjust based on what works and what doesn't."
Quality Gate: Checklist + Rubric Score
A) Pack Completeness
- Includes a clear 4-8 week success definition and a 2-week pilot
- Includes an Energy Drivers & Drains Map with specific levers and next actions
- Includes a Calendar Energy Audit with time buckets and "top offenders"
- Includes a Zone of Genius Expansion Plan (stop/delegate/automate/defer) with owners
- Includes an Energy-Aligned Default Week (time blocks aligned to energy)
- Includes Meeting Rules (agenda/decision owner, shorter defaults, async-first, buffers)
- Includes a Recovery + Transition Plan and a Low-Energy-Day Protocol
- Includes a 2-week experiment tracker with measures and decision rules
- Includes Risks / Open questions / Next steps
B) Actionability + Realism
- Top 3 changes are scheduled (not just suggested)
- The plan removes/redesigns at least 2 recurring drains in the next 2 weeks
- Delegation items include guardrails/escalation triggers (not vague handoffs)
- Calendar design assumes real constraints ("can't move" meetings are handled)
C) Energy-Quality (not time-only)
- The plan explicitly reduces context switching and decision fatigue
- High-load work has buffers and transitions (no back-to-back "hard" meetings)
- Recovery actions are framed as system design, not moralizing
D) Measurement + Iteration
- Measures are lightweight and attributable (2-4 experiments max)
- Each experiment has a clear decision rule: keep / modify / stop after 2 weeks
- Next-step schedule exists (pilot start/end dates; review moment)
E) Safety Boundaries
- Avoids medical advice and does not request sensitive personal health details
- Includes a redirect for crisis/HR/legal situations (via scope boundary in SKILL.md)
- Does not ask for secrets/credentials; uses anonymized summaries when needed
Rubric Score
| Dimension | Score | Rationale |
|---|---|---|
| 1) Goal clarity + boundaries | 2 | Crisp 4-8 week success definition with 4 observable signals; 2-week pilot scope is explicit; safety boundaries stated |
| 2) Drivers/drains diagnosis quality | 2 | 8 specific drains with triggers, controllability, levers, and next actions with owners; 5 drivers identified; top 3 change levers prioritized |
| 3) Calendar + zone-of-genius redesign quality | 2 | 5 concrete offenders with deletion/redesign plans; energy-aligned default week with time blocks, buffers, and meeting hygiene rules; zone-of-genius expanded from 15% to 35% target |
| 4) Delegation/offload effectiveness | 2 | 6-item stop/delegate/automate/defer plan; 2 detailed delegation briefs with decision rights, escalation triggers, and review cadence; 5+ energy taxes addressed in first 2 weeks |
| 5) Measurement + sustainability | 2 | 4 testable experiments each with hypothesis, measure, and keep/modify/stop decision rule; recovery routines are scheduled calendar objects; low-energy-day protocol included |
| Total | 10/10 | Ready to execute immediately |