Skip to content
How to ThinkIn the Age of AI

Keep a Waiting For list with delegation date and expected…

Maintain a separate Waiting For list tracking items delegated to others with delegation date and expected completion date, reviewing it weekly to follow up on overdue items.

When This Fires

  • When delegating any task or request to another person
  • During weekly review when checking on delegated items
  • When you realize you've been waiting for something but can't remember when you asked or when it was due
  • Complements Organize actions by execution context… (context lists) as a parallel tracking system for items you can't act on yourself

Common Failure Mode

Mental tracking of delegated items: "I'll remember to follow up with Sarah." You won't — or you will, but at a random time that's either too early (annoying) or too late (past the deadline). The Waiting For list replaces unreliable mental tracking with systematic external tracking that fires reminders at the right time.

The Protocol

(1) Every time you delegate a task or make a request that requires someone else's action, add it to your Waiting For list with three fields: What (the specific deliverable), Who (the person responsible), Dates (delegation date + expected completion date). (2) During weekly review, scan the entire Waiting For list. For each item: past expected date → follow up today. Approaching expected date → verify it's on track. Well before expected date → no action needed. (3) When following up, reference the specific item and dates: "Hi Sarah, I sent the timeline request on March 5 — are we on track for the March 15 delivery?" (4) When the item is delivered, remove it from the list and process the deliverable. (5) If you find yourself with 20+ items on the Waiting For list, you may be delegating faster than others can deliver — reduce delegation rate or increase follow-up frequency.