How to write a good to-do list

1. Choose your tool: Whatever you’ll actually use daily (phone app, notebook, computer)
2. Create 5 core lists: Inbox, Today, Next, Waiting, Someday (plus Done if you like reviewing wins)
3. Brain-dump everything: 15 minutes, get everything out of your head into Inbox
4. Process 5 items: Turn vague items into specific next actions, move to appropriate lists
5. Pick Today 3: Choose 1 keystone + 2 supporting tasks
6. Set up reminders: Daily 5-min review + Weekly 20-min planning; add calendar blocks for any deep work that must actually happen

7-Day Checkpoint

Expected outcomes:

• Inbox processed most days
• Roughly half of planned daily tasks completed
• Feeling a bit less scattered
• Fewer “oh no, I forgot” moments

If you’re not seeing this: You’re probably overstuffing Today. Cut your daily list in half. See the Overstuffed Today List pitfall for recovery ideas.

14-Day Checkpoint

Expected outcomes:

• Daily review feels easier (attached to an existing habit)
• Most days you finish what you planned
• Weekly review completed at least once
• Projects are moving forward with small steps

If you’re not seeing this: Focus on habit formation. Attach reviews to something you already do daily.

30-Day Checkpoint

Expected outcomes:

• System feels more natural, not forced
• Stress levels somewhat lower
• Completing more important work, less busywork
• Some time for strategic thinking (not just reactive work)
• Reliable follow-through on most commitments

If you’re not seeing this: The system may not fit your work style. Adapt it rather than abandon it. Review the Simple Structure section to customize the system for your needs.

Problem: “I keep forgetting to check my lists”

Solutions:

• Set phone notification for same time daily
• Put task list next to something you check obsessively (coffee machine, bathroom mirror)
• Start smaller: just one daily check instead of multiple
• Use widget/shortcut on phone home screen

Problem: “Everything still feels urgent”

Solutions:

• Audit your “urgent” items: what percentage have real external deadlines?
• Practice the 24-hour rule: “What happens if this waits one day?”
• Block 2 hours/week for important-not-urgent work
• Ask boss/client: “What’s the real deadline for this?”

Problem: “I’m still overwhelmed”

Solutions:

• Cut Today list in half for one week
• Are you saying yes to too much? Practice: “Let me check my commitments and get back to you”
• Delegate one task per week
• Archive or delete Someday items that have not mattered for 3+ months

Also review prioritization frameworks to help manage competing demands.

Problem: “Tasks are taking longer than expected”

Solutions:

• Track actual vs estimated time for 1 week
• Multiply your estimates by 1.5x (most people underestimate)
• Break large tasks into smaller pieces
• Account for interruptions and context switching

Problem: “I keep switching tools”

Solutions:

• 90-day moratorium on new productivity apps
• Focus on building the habit, not perfecting the tool
• Remember: the best system is the one you actually use
• Ask: “Am I avoiding work by reorganizing?”

For Different Work Styles

If you’re a Manager:

• Add @delegate tags to identify tasks others can do
• Create “Team Blockers” list for things your reports are waiting on
• Weekly team priorities shared in advance

If you’re Creative/Freelance:

• Add energy tags: creative admin client-work
• Create “Inspiration” list for ideas that strike randomly
• Block creative time during your peak energy hours

If you’re a Student:

• Add course tags: @history @math
• Create “Study” vs “Admin” vs “Social” task types
• Plan around class schedule and deadlines

If you work in Sprints/Agile:

• Weekly review = Sprint planning input
• Tag tasks by sprint: sprint-15
• Separate list for “Backlog” items

30 Days: “System Working Well”

• Most planned tasks finished on typical days
• Inbox cleared several times per week
• Weekly review happens more often than not
• Projects have clear next actions
• Stress level lower than when you started

60 Days: “System Optimized”

• System feels natural, not forced
• Enough time for strategic/creative work
• Commitments and deadlines are mostly on track
• Can quickly explain priorities to anyone who asks

90 Days: “System Mature”

• Adjust the system easily as work changes
• Balance urgent and important work without constant stress
• Complete significant projects while maintaining daily operations
• Feel in control of your work and life

Score 5-10: You need a system overhaul. Start with the Quick Start section.

Score 11-18: Your system needs refinement. Review the areas where you scored 1-2 and focus on those specific sections.

Score 19-25: You’re doing well. Explore the Prioritizing and Projects sections for advanced techniques.

• Missing deadlines or appointments at least once a week
• Waking up at 3 AM remembering forgotten tasks
• Constantly apologizing for delayed responses or deliverables
• Feeling overwhelmed despite working constantly
• Tasks sitting untouched for weeks or months
• Using “I forgot” or “It slipped my mind” regularly
• Your inbox has become your de facto task list

If several apply to you: This guide should help you regain control over the next few weeks. Start with the Quick Start guide for immediate implementation.

1. Clarity

Items are specific, visible next actions.

2. Focus

You can see a tiny list of what matters today.

Example “Today 3”:

3. Progress

Big projects move via small steps.

Project: “Launch Q4 campaign”

Next actions:

• Collect last year’s CTR/CPA into one sheet
• Draft campaign brief v1
• DM design to confirm ad sizes

4. Measurable Success

Lightweight metrics can help you see if your system is working:

• Daily completion rate: Did you finish most of what you planned?
• Stress check: Do you feel calmer because everything is captured?
• Dropped balls: Are important items slipping?
• Weekly project momentum: Did each project move at least one step?
• Planning time: Can you review and plan in under 10 minutes?

Track for a couple of weeks to see your baseline, then adjust.

5. Team Collaboration

Handle shared work effectively:

• Delegation notation: “Review sales deck → delegate slides 4-6 to Marcus by Wed”
• Accountability tags: Use @waiting-for-[name] to track delegated items
• Shared visibility: Keep team tasks in shared channels/boards when possible
• Check-in rhythm: Weekly 1-on-1s to review mutual commitments

Example team task:

6. Cognitive Load Management

Your system should free your mind, not burden it:

• External brain: Everything captured = nothing to remember
• Decision fatigue reduction: Pre-decided “next actions” eliminate daily planning paralysis
• Context preservation: Tags and notes maintain task context across time
• Mental energy savings: Less mental overhead from trying to remember everything

The goal: Your mind is for having ideas, not holding them.

Without These Principles

Real consequences of a poor system:

• Project delays: “The launch slipped 3 weeks because we forgot the compliance review”
• Relationship damage: “Client lost trust after the third missed deadline”
• Burnout symptoms: Working 60+ hours but feeling unproductive
• Career stagnation: Seen as “unreliable” despite working hard
• Constant firefighting: Every day is crisis mode, no time for strategic work

The cost: One dropped ball can undo weeks of good work. A good system prevents this. Start by learning to write clear, actionable tasks in the Task Anatomy section, then establish consistent habits in Daily & Weekly Rhythm.

T-shirt sizing for quick estimates:

Pomodoro units: Estimate in 25-minute blocks (1 pomo, 2 pomos, etc.). The 25-minute block is Francesco Cirillo’s, from the Pomodoro Technique.

Accuracy tip: Track actual vs. estimated for 2 weeks, then multiply estimates by your personal correction factor (usually 1.3-1.5x).

• Blocked by person: “→waiting-Ana” (needs Ana’s input first)
• Blocked by task: “→after-deploy” (can only do after deployment)
• Blocks others: “blocker-for-team” (team is waiting on this)
• Sequential chain: “1/3→” (first of three sequential steps)

Example:

Energy levels for optimal scheduling:

• high-focus Deep thinking, complex problems, creative work (morning)
• medium-energy Regular work, meetings, standard tasks (midday)
• low-energy Admin, email, simple updates, filing (afternoon slump)
• creative Brainstorming, design, writing (whenever inspired)
• social Calls, meetings, collaboration (when energized)

Batch similar tasks: Group all @phone calls, all low-energy admin, etc.

Keep tags lightweight: Start with 3-5 labels you actually use, such as @phone, @laptop, high-focus, and low-energy. Add more only when they make choosing the next task faster.

Meeting Prep:

Report Writing:

Code Review:

Client Communication:

Planning Tasks:

Red flag: If Next has 50+ items, you’re using it as storage, not active inventory. This is often a sign of the overstuffed system pitfall.

From scattered notes/emails/sticky notes:

1. Set 25-min timer, gather everything into one document
2. Dump all items into Inbox (don’t judge, just capture)
3. Process 10 items per day until clear

From multiple apps (Trello + Notion + Notes):

1. Pick ONE as primary (others become reference-only)
2. Export/copy all active tasks to new Inbox
3. Set old apps to read-only for 30 days, then delete

From complex project management (Jira/Asana):

1. Keep PM tool for team collaboration
2. Extract YOUR next actions to personal system
3. Weekly sync: personal system → PM tool updates

Warning: Don’t migrate everything at once. Start with current/urgent, add rest gradually.

Weekly (Friday PM):

• Move completed tasks older than 7 days to archive
• Export accomplishments to a “Wins” document

Monthly:

• Review Someday list, delete 20% that no longer excite you
• Archive Waiting items with no response after 30 days

Quarterly:

• Export full task history to CSV/PDF for records
• Delete archived items older than 90 days
• Keep only: completed projects summary, key decisions, lessons learned

What to keep forever: Major project completions, annual reviews, “this saved the day” solutions

• Projects audit: Which are actually dead? Archive or revive with next actions
• Someday pruning: Delete bottom 20% you’ll never do
• Metrics review: Calculate completion rate, identify patterns
• System tune-up: What friction points need fixing?
• Next month setup: Add recurring tasks, birthdays, deadlines

Output: Monthly accomplishments list + 3 focus areas for next month

• Big picture: Review annual goals, adjust quarterly targets
• Project pipeline: What big initiatives start this quarter?
• Capacity planning: Block time for deep work, vacation, learning
• Relationship review: Who needs more attention? Schedule check-ins
• System overhaul: Major changes needed? New tools? New workflows?

Output: Quarterly OKRs (objectives and key results, invented by Andy Grove at Intel and carried to Google by John Doerr) + project roadmap + calendar blocks

Morning stack:

• Pour coffee → Open task app → Review Today list (2 min)
• First sip → Pick #1 priority → Move to top

Commute stack:

• Sit on train/bus → Process Inbox on phone (5 min)
• Before arriving → Set Today’s keystone task

Lunch stack:

• After eating → Check off morning completions (1 min)
• Before returning → Adjust afternoon priorities

Shutdown stack:

• Close laptop → Capture new tasks in Inbox (3 min)
• Before leaving → Set tomorrow’s first task

Success tip: Start with ONE stack for 2 weeks, then add another.

Source: Stacking was BJ Fogg’s idea first, as the “anchoring” step in Tiny Habits. James Clear’s write-up of the formula (“After [current habit], I will [new habit]”) credits Fogg and is the shortest way in.

Travel/Conference:

• Pre-trip: Clear Inbox, set out-of-office tasks
• During: Capture only, don’t process
• Return: Block 2 hours for catch-up processing

Illness (You or Family):

• Immediate: Push all tasks +3 days automatically
• Delegate or delete non-critical items
• Recovery: Start with 50% capacity for first week back

Crisis Mode:

• Create “Crisis” list, move everything else to “Paused”
• Daily tasks = crisis items only
• Post-crisis: Schedule recovery review to reprioritize

System Breakdown (Stopped Using It):

• Don’t guilt yourself, just restart
• Archive everything older than 2 weeks
• Start fresh with today’s actual priorities
• Reduce to 3 lists only: Today, Next, Done

Daily Metrics (Track in habit tracker or journal):

• Completion rate: Today tasks completed ÷ planned (aim for “most days”)
• Inbox zero: Yes/No (aim for several times per week)
• Keystone done: Yes/No (aim to finish the big one more often than not)

Weekly Metrics:

• Tasks completed: Total count (establish your baseline)
• Average task age: Days from creation to done (keep it reasonable for your work)
• Project progress: Projects with movement (aim for each active project to advance)

Monthly Metrics:

• System usage: Days with review done ÷ total (notice trends)
• Someday promotion: Items moved to active (a couple per month is healthy)
• Stress level: 1-10 scale (watch for gradual decline)

Simple tracking: Use a spreadsheet or tally marks in a notebook. Review trends, not daily fluctuations. If your metrics are concerning, check the Common Pitfalls section for specific recovery strategies.

If it takes less than 2 minutes, do it now. Otherwise, capture it.

• Do now: Reply “Got it, will review by EOD”
• Do now: Add meeting to calendar
• Capture: “Review 15-page proposal and provide feedback”
• Capture: “Research competitor pricing models”

This prevents small tasks from clogging your system.

Source: The two-minute rule is David Allen’s, from Getting Things Done. He explains the reasoning himself: if an action takes less time to finish than to file and revisit, finish it.

Daily prioritization in 30 seconds:

• Must (Today): External deadlines, blockers for others, promises made
  Examples: Send contract to Acme by 5pm; fix signup bug blocking launch; call mom (her birthday)
• Should (This Week): Important but flexible, moving projects forward
  Examples: Draft Q4 roadmap; review team proposals; book dentist appointment
• Could (Whenever): Nice to have, personal growth, exploration
  Examples: Try new productivity app; read industry report; organize desk drawer

Rule: Maximum 2 “Must” items per day. Everything else is negotiable. This connects directly to the capacity limits discussed in the Simple Structure section.

Source: Must / Should / Could is MoSCoW prioritisation with the fourth bucket dropped, as the Agile Business Consortium documents it for DSDM. That fourth bucket is “Won’t have, this time”, and it is worth borrowing on days when you need to say no on the record.

Eisenhower Matrix (Urgent vs Important)

Use when: Feeling overwhelmed by competing demands

Source: The name traces to a line Eisenhower quoted in his address of 19 August 1954 in Evanston, Illinois: “I have two kinds of problems, the urgent and the important. The urgent are not important, and the important are never urgent.” He was quoting a college president; the four-box grid came later.

RICE Scoring (Data-Driven Priority)

• Reach: How many people/projects affected? (1-10)
• Impact: How much value created? (1-10)
• Confidence: How sure are you? (0.5, 0.8, 1.0)
• Effort: Person-hours required (actual number)

Example: “Automate weekly reports”

Use when: Choosing between multiple project ideas

Source: RICE was built by Sean McBride on Intercom’s product team and published in the original 2018 write-up. The scales above are simplified for a personal list; Intercom counts Reach as people affected per period, scores Impact on a fixed 0.25 to 3 scale, and states Confidence as a percentage.

ICE Framework (Quick Scoring)

• Impact: How much will this move the needle?
• Confidence: How sure are you it’ll work?
• Ease: How easy is it to implement?

Scores: Higher scores go first; use as a quick sort rather than a strict rule.

Use when: Need quick prioritization without detailed analysis

Source: ICE predates RICE and is credited to Sean Ellis, who used it to rank growth experiments quickly enough that the ranking never became the work.

The Stakeholder Matrix

• Boss priorities: Tag with @boss - Do first, communicate progress
• Customer/Client: Tag with @client - Set clear expectations, never surprise
• Team dependencies: Tag with @blocker - Unblock others before own work
• Personal goals: Tag with @growth - Schedule during high-energy times

Conflict Resolution Script:

“I have conflicting priorities from you and [other stakeholder]. Both are marked urgent. Which should I complete first, or can we find someone to help with one?”

Managing Up: Send weekly priority list to manager: “Planning to focus on X, Y, Z this week. Any concerns?”

When to Reprioritize

• Emergency/Fire: Stop everything, communicate impact, reschedule displaced work
• New urgent request: Assess against current “Must” items, negotiate trade-offs
• Energy crash: Swap high-focus task for low-energy admin immediately
• Blocked/Waiting: Move to next priority, set reminder to check blocker
• Ahead of schedule: Pull from “Should” list, not “Could” (maintain momentum)

The 3-Question Filter for New Requests

1. What breaks if this waits 24 hours? (If nothing, it’s not urgent)
2. Am I the only one who can do this? (If no, delegate)
3. What won’t get done if I do this? (Make the trade-off explicit)

Document shifts: “Pushed [task] to tomorrow due to [urgent issue]” - maintains accountability

Scenario 1: Everything is “Urgent”

Situation: Boss wants report, client wants proposal, team needs code review - all “by EOD”

Resolution:

1. List all three with realistic time estimates
2. Send to boss: “I have 6 hours of ‘urgent’ work and 3 hours until EOD. What’s the priority order?”
3. Propose: “I can do X today, Y by noon tomorrow, and delegate Z to [teammate]”
4. Document decision in email for CYA

Scenario 2: Personal vs Professional

Situation: Important work deadline same day as kid’s recital

Resolution:

• Non-negotiable personal? Communicate early, offer alternative (work early/late/weekend)
• Flexible personal? Propose splitting difference (attend part, watch recording)
• Key principle: Set boundaries early, deliver on adjusted commitments

Scenario 3: Perfectionism Paralysis

Situation: Spending too long perfecting low-priority tasks

Resolution:

• Set quality levels: “Must” = 90% quality, “Should” = 70%, “Could” = 50%
• Use timebox: “I’ll spend max 30 min on this”
• Ask: “What’s the minimum viable version?”
• Remember: Done > Perfect for most tasks

Map Your Energy to Task Types

Track for 1 week: Note your energy (1-10) hourly. Match tasks to your personal rhythm.

Example optimization: “Moved coding from 2 PM to 9 AM and it felt easier.” Use this awareness in your daily rhythm and when writing tasks with appropriate energy tags.

1. Define the outcome: What does “done” look like? Be specific.
2. Identify milestones: 3-5 major checkpoints toward completion
3. Map dependencies: What must happen before what?
4. Create next actions: Break each milestone into 2-5 concrete tasks
5. Assess risks: What could block progress? Plan mitigations.

Product Launch

Milestones:

• Market research complete
• MVP developed and tested
• Go-to-market plan approved
• Launch campaign executed
• Post-launch metrics reviewed

Next actions for milestone 1:

Event Planning

Milestones:

• Venue booked and confirmed
• Speaker lineup finalized
• Registration system live
• Event executed successfully
• Follow-up completed

Dependencies example: Can’t send invites → until speakers confirmed → until venue booked

Research Paper/Report

Milestones:

• Research questions defined
• Literature review completed
• Data collected and analyzed
• First draft written
• Final version published/submitted

Parallel vs Sequential: Literature review + data collection can happen simultaneously

A good milestone is:

• Measurable: “Demo ready for stakeholders” not “Make progress on demo”
• Meaningful: Represents genuine project progress
• Memorable: Easy to communicate to others
• Motivating: Feels like an accomplishment when reached

Milestone spacing: 1-3 weeks apart. Closer for urgent projects, further for long-term initiatives.

Visual tracking: Use progress bars, kanban boards, or simple checklists to show milestone completion.

Tasks You Can Do Simultaneously

• Research + initial outreach (while researching, start building contact list)
• Writing + gathering feedback (share draft sections as you complete them)
• Development + testing (test components as they’re built)
• Content creation + design work (writer and designer work on different sections)

Tasks That Must Be Sequential

• Requirements gathering → design → development
• Data collection → analysis → conclusions
• Budget approval → vendor selection → project kickoff
• Legal review → contract signing → project start

Time-saving tip: Look for 80% completion points where you can start the next sequential task. This approach prevents the bottlenecks that lead to project delays.

Common Project Risks

• People risk: Key person unavailable/leaves
  Mitigation: Cross-train team members, document critical knowledge
• Technical risk: Solution doesn’t work as expected
  Mitigation: Build prototype early, have backup approaches
• Timeline risk: Tasks take longer than estimated
  Mitigation: Add 25% buffer time, identify which tasks can be cut
• Budget risk: Costs exceed expectations
  Mitigation: Get fixed quotes, have contingency fund
• Stakeholder risk: Requirements change mid-project
  Mitigation: Document decisions, establish change control process

Risk planning: For each milestone, ask “What could go wrong?” and “How would we recover?” Good risk planning also requires effective priority management when problems arise.

Outcome: 15-minute presentation delivered to executive team showcasing Q4 results and Q1 priorities

Milestones:

1. Content outline approved by manager
2. Data compiled and validated
3. Slides completed and rehearsed
4. Presentation delivered successfully

Next actions:

Risks & Mitigations:

• Risk: Ana doesn’t provide budget data → Mitigation: Use Q3 data + 10% estimate
• Risk: Presentation runs long → Mitigation: Prepare 10min version with backup slides

Notice how each task follows the anatomy guidelines with clear actions and context. Incorporate these into your weekly review to ensure steady progress.

1. Vague Items (The “Someday Disease”)

Warning signs: Tasks sitting untouched for weeks, “I don’t know where to start” feeling

Examples:

Recovery strategy:

1. Set 15-min timer for “vague task archaeology”
2. For each vague item, ask: “What would I do in the next 30 minutes if I had to start this right now?”
3. Rewrite with that specific action
4. If you can’t make it specific, move to Someday or delete

2. Overstuffed Today List (The “Optimism Trap”)

Warning signs: Completing <50% of daily tasks, constant feelings of failure, rolling tasks forward daily

Early warning signs: Adding “just one more” task to today, estimating tasks at your best-case speed

Recovery strategy:

1. Immediate: Move everything except 2-3 “Must do” items to Next
2. Track for 1 week: How many tasks do you actually complete daily?
3. Set your ceiling: That number is your maximum daily capacity
4. Buffer rule: Plan for 75% of your capacity (life happens)

Accountability mechanism: Tell someone your daily plan and report completion rate

3. Fake Deadlines (The “Urgency Addiction”)

Warning signs: Everything feels urgent, using “deadlines” to motivate yourself, constantly missing self-imposed dates

Early warning signs: Adding dates to tasks that don’t actually have real consequences

Recovery strategy:

1. Audit all dates: For each deadline, ask “What happens if this is late by 1 day? 1 week?”
2. Keep only real deadlines: External commitments, legal requirements, event dates
3. Replace fake deadlines with goals: “Ideally by Friday” instead of “Due Friday”
4. Use constraints instead: “Before vacation” or “While Sarah is available”

Accountability mechanism: Share your real deadlines with stakeholders for external pressure

4. Tool Hopping (The “Perfect System” Myth)

Warning signs: Changing apps every 2-3 months, spending more time setting up than using, having tasks scattered across multiple systems

Early warning signs: Reading productivity blogs obsessively, excitement about new features over actual task completion

Recovery strategy:

1. Declare a moratorium: No new productivity tools for 90 days
2. Consolidate everything: Into ONE system, even if it’s imperfect
3. Focus on habits, not tools: Master daily/weekly review first
4. The 80% rule: If your current tool does 80% of what you need, it’s good enough

Accountability mechanism: Ask a friend to call you out if you mention trying a new productivity app. Instead, focus on mastering the daily and weekly rhythm with your current tool.

5. Review Avoidance (The “Set and Forget” Problem)

Warning signs: Tasks getting stale, losing sight of bigger goals, reactive rather than proactive work

Early warning signs: Skipping weekly review “just this once,” feeling overwhelmed despite having a system

Recovery strategy:

1. Start micro: 5-minute daily check-in instead of ambitious weekly review
2. Attach to existing habit: Review during morning coffee or evening commute
3. Make it enjoyable: Nice location, favorite drink, reward after completion
4. Track the streak: Mark calendar days when you do your review

Accountability mechanism: Weekly check-in text with accountability partner

Case Study 1: Sarah, Marketing Manager

Problem: Had 47 items in “Today” list, completing only 3-5 daily, felt constantly behind

Solution:

1. Moved 40 items to Next, kept only 5 real priorities
2. Tracked actual completion for 2 weeks: averaged 4 tasks/day
3. Set new rule: maximum 4 items in Today
4. Added buffer: only planned 3 tasks, leaving 1 slot for urgent issues

Result: Completion rate improved, stress decreased, more time for strategic work

Case Study 2: Marcus, Freelance Developer

Problem: Used 5 different task apps, constantly migrating data, spent 2 hours/week on “system maintenance”

Solution:

1. Chose simplest tool (Apple Notes), moved everything there
2. Deleted other apps, exported data to read-only format
3. 90-day moratorium on new productivity tools
4. Focused on building daily review habit instead

Result: Freed up extra time for billable work, used one consistent system for months

Case Study 3: Alex, Startup Founder

Problem: Everything felt urgent, missed important but non-urgent strategic work, constant firefighting mode

Solution:

1. Audited all “urgent” items: only 30% had real external deadlines
2. Removed fake deadlines, added to weekly/monthly goals instead
3. Created “Strategic Time” block: 2 hours/week for important-not-urgent work
4. Weekly review to ensure strategic items got attention

Result: Noticeable reduction in “fire drills,” completed Q4 strategic planning on time, team stress decreased. Alex learned to apply the Must/Should/Could framework and broke down strategic work using the project methodology.