Dump everything that could claim your attention into one visible list: meetings, obligations, ideas, and lurking requests. Do not analyze yet; collecting before judging lowers anxiety and prevents bias. A single container reduces friction later when scoring and avoids forgetting quiet, important tasks that never shout.
Use quick numbers or dots for impact, urgency, effort, and energy fit, then compute a rough priority by multiplying benefits and dividing by cost. Keep it approximate to stay fast. The goal is comparative clarity, not precision. Share which axis surprises you most once everything is visible.
Pick a realistic slate: one significant outcome, three medium movers, and five micro‑wins if capacity allows. Reserve time boxes, account for meetings, and mark a protected deep‑work window. Confirm logistics and dependencies before starting to avoid avoidable stalls, then honor the plan through gentle, accountable check‑ins.
Decide how many unplanned requests you can absorb today without sacrificing deep work, then reserve small, explicit windows to address them. When a new request appears, compare it to your budget and swap intentionally if necessary. This transparency teaches others your capacity, reducing reactive yeses and quiet resentment.
Pause at pre‑scheduled times, review your slate, and quickly re‑score candidates against impact and cost. Confirm whether any stakeholder information changed. Protect the day from whiplash by limiting changes to explicit checkpoints. If you must pivot mid‑block, capture a restart note to minimize re‑entry waste later.
Use three questions: What outcome is threatened, what is the latest responsible moment to act, and what can safely wait? Ask requestors for evidence and scope. This respectful script turns panic into parameters, enabling principled swaps rather than chaotic reshuffles that leave everyone disappointed and behind.
All Rights Reserved.