The 1-3-5 Rule for Executives: Cut Priority Overload in Minutes

A one-line problem and one-minute promise

Your calendar is wall-to-wall, your inbox never ends, and strategic work slips. The 1-3-5 Rule gives you a one-minute nightly or morning ritual that reduces decision fatigue and increases the odds of one meaningful win each day, then an EA enforces the plan with time-blocks, buffers, and disciplined follow-through.

What the 1-3-5 Rule is (definition + quick example)

Pick 1 big task, 3 medium tasks, and 5 small tasks you’ll commit to today. Common sizing conventions (not absolutes): big = 2–4 hours; medium = 30–60 minutes; small = <30 minutes. Example: 1 = finalize investor deck (3 hours); 3 = prep for client QBR (45 min), review demo metrics (45 min), approve contractor invoices (30 min); 5 = email follow-ups, two calendar swaps, quick vendor call, sign NDAs, update team Slack. The rule was popularized in U.S. productivity circles by Alex Cavoulacos at The Muse, see “The 1-3-5 Rule for Truly Great To-Do Lists” (https://www.themuse.com/advice/the-135-rule-for-truly-great-to-do-lists). It pairs well with time-blocking and deep work practices (for example, HBR on timeboxing: https://hbr.org/2018/12/timeboxing-the-powerful-time-management-technique-youre-probably-not-using; Cal Newport on deep work: https://www.calnewport.com/blog/).

Why the 1-3-5 Rule works for busy executives

• Limits cognitive load: nine pre-sized items beat an infinite, amorphous list.
• Enforces time reality: big/medium/small sizing aligns work with available attention blocks.
• Protects deep work: the explicit '1' becomes the anchor around which your day is built.
• Creates a delegation surface: it’s immediately obvious what your EA should own or close.
• Fits U.S. rhythms: back-to-back meetings and coast-to-coast schedules need a simple daily focus.

Where it’s limited, and what to pair it with

• Eisenhower Matrix: if a crisis-heavy morning erupts, triage urgent vs important first, then feed 1-3-5.
• Pomodoro Technique: run 25–50 minute sprints inside the '1' or '3' blocks for sustained focus.
• Rule of Three (weekly/quarterly): pick 1–3 priorities for the week or quarter, then translate them into daily 1-3-5 items.
• Project trackers: keep Asana/Jira/Notion for multi-step work; 1-3-5 is the daily throttle, not the Gantt chart.

Escalation triggers and path

• Triggers that exceed 1-3-5 alone: multi-quarter initiatives, regulatory filings, financing rounds, board preps, M&A diligence, major launches, incident response.
• Escalation path (lightweight): 1) Set a quarterly Rule of Three; 2) Build a RACI with owners/approvers; 3) Break work into tickets in your tracker; 4) Use 1-3-5 only to surface the next-most-leveraged actions for today.
• When you’re highly interruptible (earnings week, litigation): downgrade daily expectations to 1 big and 1–2 mediums, pre-plan buffers, and move smalls to your EA.

The executive playbook (fast adoption, U.S.-calibrated)

1. 1Nightly EA prep + morning approval (2–5 minutes): your EA reviews calendar, project tracker, and inbox flags by 5 PM local; drafts your 1-3-5 in one note for one-touch approval; and pre-loads calendar holds. You approve on mobile in 30–90 seconds. For inbox prep, see Inbox Management for Executives: How an EA Takes Control.
2. 2Time-block the '1' (make it sacred): reserve a 2–4 hour block when interruptions are lowest (often 8–11 AM local). Add 15–30 minute buffers before/after. Your EA declines conflicting requests and routes update-only meetings to async.
3. 3Translate and delegate mediums: list three 30–60 minute moves. Your EA drafts briefs, gathers data, or schedules the right collaborators so you only make decisions. Use 15 Tasks Every Executive Should Delegate to an EA Immediately for ideas.
4. 4Batch the five smalls: put them in a 30–45 minute end-of-day slot, or hand most to your EA (approvals, vendor pings, follow-ups).
5. 5Gatekeeping + triage: during East/West overlap (for example, 12–4 PM ET / 9 AM–1 PM PT), your EA shields the '1' time and redirects low-ROI meetings. For concrete rules, see Calendar Management for Executives: What to Delegate.
6. 6Close the loop: 10-minute weekly review (Friday or Monday). Agenda: review KPI tracker; confirm next week’s Rule of Three; pre-select likely '1's; capture risks; identify handoffs.

Daily 10-minute check-in script (EA ↔ Executive)

• EA (60 seconds): Yesterday’s outcomes vs 1-3-5; blockers; meetings to decline/convert; proposed 1-3-5 for today.
• Executive (60–120 seconds): Confirm/adjust today’s '1'; approve/deny medium tasks; escalation decisions per delegation matrix.
• EA (60 seconds): Calendar triage plan; security-sensitive items queued; recap and post updated 1-3-5 in shared note.

Copy-and-paste assets you can use today

Nightly EA draft note (example, 5 lines): • 1 (2–4h): Finalize Series B board deck; draft done; needs exec review + narrative polish. • 3 (30–60m): Prep for Acme QBR (brief attached); Review Oct pipeline; Approve vendor SOW. • 5 (<30m): Sign 3 NDAs; Email follow-ups to Redline, Fincorp, Juno; Swap Wed 1:1. • Risks: Legal may need 20 min for clause change; block 3:30–3:50 PM ET as buffer. • Decisions needed: Keep/decline Ops standup invite? Confirm talking points for QBR. Calendar invite language for the sacred '1': Title: Focus Block: Do Not Schedule (Executive Priority) Description: Reserved for today’s '1' strategic deliverable. EA has discretion to decline/reschedule non-critical requests; use async updates. Delegation email template (medium task → EA): Subject: Please drive: QBR prep for Acme (due Thu 1 PM ET) Hi [EA Name]: please take first pass on the QBR brief: pull last 2 quarters’ KPIs, top churn risks, and 3 slide headlines. Book 30 minutes with me tomorrow for review. Flag blockers by EOD. Thanks! Calendar triage script (EA → requester): “Thanks for reaching out. [Executive] is heads-down on a strategic deliverable this morning. Can we convert this to an async update or land in [next 30-min slot], or would [Name] on the team be the right approver? If this is time-sensitive, reply here with the decision needed and latest acceptable time.”

U.S. GEO rhythm: overlap windows and async handoffs

Recommended overlap windows for distributed U.S. teams: cross-coast core 12–4 PM ET (9 AM–1 PM PT). Meeting windows many U.S. teams adopt: Mon–Thu 12–4 PM ET for cross-functional calls; 8–11 AM local for deep work; 4–5 PM ET for West Coast catch-ups; protect Friday after 2 PM local for wrap and planning. Industry coverage from Microsoft’s Work Trend Index (https://www.microsoft.com/en-us/worklab) and HBR’s guidance on timeboxing and deep work (see links above) both note persistent meeting density and the value of scheduling protected focus time. Async handoff template (time-zone friendly): Subject: Async handoff: [Project/Task]: due [Day, Time, Timezone] Context: [2–3 sentences]. Definition of done: [bullet list or 3–5 checks]. Attachments/links: [docs]. Next touchpoint: I’ll review between [time window]; ping only if blocked >15 minutes or if decision >$X costs.

Delegation matrix for high-sensitivity items (example thresholds)

SOP checklist for redaction and secure handoffs

• Redact PII/financials unless strictly required; share via permissioned docs, not attachments.
• Use SSO + 2FA everywhere; store credentials only in a password manager.
• Apply least-privilege access; set expirations on shared links; enable audit logs.
• Watermark or label sensitive drafts; use version control in your doc suite.
• Define escalation paths (what, when, how); document in the EA playbook.
• Quarterly access review: remove stale permissions; rotate service passwords every 90 days (or per policy). See practices in Remote Executive Assistant: How It Works and Why It Often Works Better.

Get an executive assistant quote today.

Part-time or full-time support for calendar, inbox, travel, vendor follow-up, and personal logistics. Tell us what you need and we will scope the right plan.

Request quote

Professionals from top brands trust Aurora

KPI tracker (simple template) and cadence

How to use & sample benchmarks: Start with a baseline week (no changes). In Month 1, many executives aim to reclaim 3–8 hours/week and complete 1–3 '1's per week; treat these as illustrative, not guaranteed. Review the tracker in a 10-minute weekly standup, then adjust buffers, delegation, and meeting rules accordingly.

Sample 1-3-5 daily templates by U.S. executive role

Micro-case: from fragmented calendar to predictable '1' in 10 business days

In an anonymized Aurora pilot with a Series B SaaS CRO in New York (EA in Austin), the EA implemented nightly 1-3-5 drafts and protected an 8:30–11:00 AM ET focus block with 15-minute buffers. Over the first two weeks, calendar analytics showed multiple meetings either declined or converted to async updates, and the CRO completed high-leverage '1's (pricing committee deck; revised enterprise narrative) while the EA closed a majority of medium tasks (briefs, data pulls, vendor SOWs). The CRO kept ownership of the strategic narrative: Aurora handled planning, gatekeeping, and follow-through. As one Aurora client put it: “My mornings finally belong to the work only I can do.”

Onboarding timeline (Day 0–30) with checkpoints

1. 1Day 0–3: Kickoff & access: define success criteria; share calendars/inboxes; confirm tool access (SSO/2FA); align on 'big/medium/small' sizing. Permissions: calendar read/write; email delegate/send-as; Slack/Teams; doc drive (SharePoint/Drive) with least-privilege; project tracker (contributor); finance tools (requester-only); password manager seat. Success signals: an approved 1-3-5 draft and first protected '1' block on the calendar. See scope cues in What Does an Executive Assistant Do? The Complete 2026 Guide.
2. 2Day 4–10: Shadowing & low-risk delegation: EA drafts nightly 1-3-5; owns small tasks (scheduling, follow-ups); prepares briefs for two medium tasks. Success signals: at least one '1' completed; 3–5 smalls closed by EA per day; calendar holds respected.
3. 3Day 11–20: Expanded scope: EA converts medium tasks into tickets with due dates; triages inbound; enforces buffers; runs the KPI tracker. Success signals: meetings pruned or converted to async; weekly KPI tracker populated; fewer context switches.
4. 4Day 21–30: Operating cadence: add a 10-minute weekly review; EA produces a 'wins' report and maintains SOPs/escalation paths. Success signals: predictable '1' throughput; hours reclaimed tracked; confident delegation of higher-sensitivity items. For hiring steps, see How to Hire an Executive Assistant Who Actually Frees Up Your Time.

Day 0 access checklist (set it once, document it)

• Grant calendar read/write + meeting delegation; define decline/convert rules.
• Enable email delegate + send-as with approved templates and signature.
• Add EA to doc repositories with least-privilege (read by default; write on shared team folders).
• Provide contributor access to Asana/Jira/Notion; define ticket naming and labels for 1-3-5 items.
• Issue a password manager seat; enable SSO + 2FA across tools; share vault groups, not passwords in chat.
• Grant requester-only roles in finance tools (expenses/POs); no card numbers in plaintext; use secure forms.
• Create a security page in your internal wiki: NDAs on file, escalation paths, and SOP index.

Risk-mitigation checklist (first 30 days)

• Document the delegation matrix with thresholds; review weekly for adjustments.
• Confirm 2FA on all accounts; audit log visibility for calendar/docs; enable device encryption.
• Rotate shared service passwords after 30 days and then quarterly; remove stale access when roles change.
• Run a 15-minute tabletop: simulate a sensitive handoff (e.g., contract redline) and validate escalation timing.
• Track KPI definitions in the SOP; do a quick calibration every Friday to keep metrics consistent.

Security practices that enable confident delegation

• Mutual NDAs and confidentiality clauses in MSAs/SOWs.
• Background checks for assistants and core staff.
• Two-factor authentication (2FA) and SSO where available; least-privilege, role-based access.
• Encrypted file access and secure password managers; audited access logs.
• Documented SOPs and clear escalation paths (what to escalate, when, and how).
• U.S.-calibrated communication norms (tone, timezones, holidays) and executive discretion training.
• We avoid absolute guarantees; instead, we rely on tested policies, tooling, and oversight. See practices in Remote Executive Assistant: How It Works and Why It Often Works Better.

Implementation checklist + next step (two-week pilot)

1. 1Decide when to plan: EA drafts nightly; you approve in the morning (30–90 seconds).
2. 2Block your daily '1' (2–4 hours) with 15–30 minute buffers; empower your EA to gatekeep.
3. 3Create a one-page delegation matrix (use the role templates and 15 Tasks Every Executive Should Delegate to an EA Immediately).
4. 4Adopt the KPI tracker; review it in a 10-minute weekly standup using the methods above.
5. 5If you’re evaluating Aurora, skim packages in Executive Assistant Pricing Guide: What You Are Really Paying For. Many teams start with a two-week pilot of 10–20 hours, then scale to 40–80 hours/month based on fit and ROI. For impact measurement ideas, see The ROI of an Executive Assistant: A Better Way to Measure Return.

Ready to see it in your world? Request a 15-minute onboarding consult and a two-week pilot. Start with How to Hire an Executive Assistant Who Actually Frees Up Your Time, review options in Executive Assistant Pricing Guide: What You Are Really Paying For, and browse our methodology in Remote Executive Assistant: How It Works and Why It Often Works Better. We’ll set up your nightly 1-3-5, protect your '1', and measure the wins.