GTD for Multiple Projects: The Exact System to Separate, Prioritize, and Execute Without Overwhelm

GTD (Getting Things Done) was designed for a single stream of work, not the reality of managing three clients, two courses, and personal life simultaneously. The classic method fails when projects blend into a single chaotic list, dependencies between tasks aren’t visible, and the weekly review becomes a 3-hour marathon. This guide adapts GTD for multiple projects with exact workflows, tools, and rules to separate contexts, prioritize ruthlessly, and execute without losing the big picture.

Why Classic GTD Fails with Multiple Projects (and How to Fix It)

• Problem 1: The inbox becomes a dumping ground. Capturing tasks from five projects in one place forces you to sort them later—a waste of time. Fix: Use separate inboxes by project (e.g., |Client A|, |Course X|, |Home|). When processing, you already know where each task belongs.
• Problem 2: Projects blend in lists. GTD groups actions by context (e.g., |Calls|), but if two projects require similar actions, you’ll mix them up. Fix: Add visual identifiers (colors, labels) per project. Example: All |Client A| tasks in blue, |Course X| in green.
• Problem 3: The weekly review is exhausting. Reviewing 20 projects in one sitting is unrealistic. Fix: Split the review into micro-sessions (e.g., 15 minutes/day for a different project) or prioritize by urgency using the Eisenhower Matrix.
• Problem 4: Dependencies aren’t visible. If a task in |Project A| blocks |Project B|, classic GTD doesn’t reflect this. Fix: Create a dependency map (a table or diagram) and review it weekly. Example: |Project A: Task 3 → Project B: Task 1|.

The GTD Workflow for Multiple Projects: Step-by-Step

1. Capture: How to Ensure Nothing Slips Through

• Rule 1: Assign a project at capture. Never write |Buy materials|. Instead, write |Project Z: Buy materials for prototype|. If unsure, file it in a |No Project| folder and review weekly.
• Rule 2: Use quick-capture tools. Voice commands (e.g., |Hey Siri, add task to Project X: Call Juan|), mobile widgets, or a physical notebook. Example: A freelancer dictates |Client A: Draft proposal (due Friday)| while walking to a meeting.
• Rule 3: Capture non-tasks too. Ideas (|Idea: Use Client B’s case study for Course X|), references (|Article: GTD for freelancers|), and blockers (|Blocker: Waiting for María’s feedback on Project A|).

2. Process: Turn Chaos into Clear Actions

• Filter 1: Which project? If unclear, file in |No Project|. Example: |Research automation tools| could belong to |Client A| or |Course X|—decide later.
• Filter 2: Is it actionable? If not, classify as reference (e.g., |Article on Python libraries|), someday/maybe (e.g., |Learn Photoshop for Course Y|), or trash.
• Filter 3: What’s the next physical action? GTD requires concrete steps. Instead of |Work on report|, write |Draft introduction for Client A’s report (max 500 words)|. If it takes <2 minutes, do it now.

3. Organize: Structure Projects Without Losing Your Mind

• Lists by project + context. Replace the single |Next Actions| list with one per project (e.g., |Next Actions - Client A|, |Next Actions - Course X|). Within each, group by context (|Calls|, |Computer|, |Errands|).
• Calendar for time-specific actions. Use it only for tasks with fixed times. Color-code by project (e.g., |Client A| in blue, |Course X| in green). Example: |Client A: Meeting at 10 AM| (blue), |Course X: Lecture at 2 PM| (green).
• “Waiting For” lists per project. Track delegated tasks. Example: |Waiting For - Client A: Luis’s feedback on budget|. Review weekly to follow up.
• Tagging for cross-project filtering. Use tags like |#urgent|, |#blocked|, or |#highenergy|. Example: Filter by |#highenergy| to pick quick tasks when you’re tired.

4. Review: Stay in Control Without Burning Out

• Split the review into days. Dedicate 20 minutes/day to a different project. Example: Monday for |Work|, Tuesday for |Studies|, Wednesday for |Home|. Use a checklist per project: What progress was made? What’s blocked? What’s next?
• Review dependencies. Check if |Project A| tasks block |Project B|. Example: |Project A: Task 3 must finish before Project B: Task 1|.
• Archive the irrelevant. If a project lingers in |Someday/Maybe| for 3+ months, ask: Do I really need this? If not, archive or delete it.

5. Do: Choose What to Tackle First

• Rule 1: Context. If you’re at the office, filter |Client A| tasks with the |Computer| context. At home, pick |Home Project| tasks with the |Household| context.
• Rule 2: Time available. Use the 2-minute rule (do it now if <2 minutes) and the 20/80 rule (pick a task that gives 80% of the result in 20% of the time). Example: If you have 20 minutes, choose |Client A: Send invoice| over |Client B: Write 1,000-word report|.
• Rule 3: Energy. If exhausted, pick mechanical tasks (e.g., |Organize files for Project X|). If fresh, tackle creative tasks (e.g., |Design Course Y presentation|).
• Rule 4: Priority. Use the Eisenhower Matrix to classify tasks. Focus on urgent and important first. Example: |Client A: Fix critical bug (due today)| > |Course X: Read optional article|.

Tools for GTD with Multiple Projects: What Works (and What Doesn’t)

• Must-have features:
• - Project separation. View tasks for one project in isolation (to focus) or all together (to maintain perspective). Example: Toggle between |Client A| and |All Projects| views.
• - Visual identifiers. Colors, labels, or icons to distinguish projects at a glance. Example: |Client A| tasks in blue, |Course X| in green.
• - Flexible views. List, kanban, or calendar to adapt to workflows. Example: Use kanban for |Project A| (columns: |To Do|, |Doing|, |Done|) and calendar for |Course X| (deadlines).
• - Quick capture. Add tasks via mobile, widget, voice, or email. Example: Dictate |Client A: Call Juan about contract (urgent)| while driving.
• - Calendar integration. See events and tasks in one place without mixing contexts. Example: |Client A: Meeting at 10 AM| (blue) + |Course X: Lecture at 2 PM| (green).

Real Example: A Day with GTD for Multiple Projects

Scenario: You’re a freelancer with two clients, taking an online course, and managing household tasks. Here’s how GTD works on a Tuesday:

• 7:00 AM - Capture. Check inbox and add: |Client A: Send report draft (today)|, |Course X: Watch lesson 3 (tomorrow)|, |Home: Buy milk (today)|.
• 8:00 AM - Process. Classify tasks: |Client A| → |Next Actions - Client A| (context: |Computer|), |Course X| → |Next Actions - Course X| (context: |Computer|), |Home| → |Errands|.
• 9:00 AM - Quick review. Check calendar: |Client B: Meeting at 10 AM|. Add task: |Prepare talking points for Client B meeting| (context: |Computer|).
• 10:00 AM - Do. During the meeting, capture notes and add: |Client B: Send signed contract (urgent)|.
• 12:00 PM - Break. Process the contract task: → |Next Actions - Client B| (high priority).
• 2:00 PM - Work block. Filter by |Computer| and high priority. Pick |Client A: Send draft| and |Client B: Send contract|.
• 5:00 PM - Wrap-up. Check |Errands| list and buy milk. Mark task as done.

How to Avoid Burnout When Everything Feels Urgent

• The 1-3-5 rule. Each day, complete 1 big task, 3 medium tasks, and 5 small tasks. Example: |Big: Draft Client A’s report|, |Medium: Watch Course X lesson|, |Small: Buy milk, reply to 3 emails|.
• Buffer time. Leave 20% of your day unplanned for unexpected tasks. Example: If you work 8 hours, block 6.4 hours for tasks and 1.6 hours for surprises.
• Digital detox. Schedule notification-free blocks (e.g., 9:00-11:00 AM) for deep work. Example: Silence Slack and email to focus on |Client A’s report|.
• Meetings with yourself. Weekly, ask: Which projects stress me out? Can I delegate anything? Do deadlines need adjusting? Example: If |Course X| feels overwhelming, negotiate a 1-week extension.
• Embrace “good enough.” With multiple projects, perfection is impossible. Focus on progress. Example: Send |Client A’s report| as a draft instead of waiting for it to be flawless.

GTD for multiple projects isn’t about doing more—it’s about doing the right thing at the right time, in the right context, without burning out.

Applying GTD for Multiple Projects: A Tool That Adapts to You

GTD with multiple projects requires a tool that separates contexts without losing the big picture. For example, Foco lets you create a container for each project (e.g., |Client A|, |Course X|, |Home|), each with a unique color. In Panorama mode, you see all tasks color-coded by project. In Foco mode, you filter to see only |Client A| tasks, eliminating distractions. Use the List view to group tasks by date (|Today|, |This Week|, |Later|) or the Kanban view to drag tasks between columns (e.g., |To Do|, |Doing|, |Done|). For time-sensitive tasks, the Calendar view shows deadlines and meetings in one place. Capture tasks via voice (e.g., |Client A: Call Juan about contract|), and Foco transcribes it, detects deadlines, and assigns it to the right project. If you’re managing tasks from Notion, GitHub, or Asana, Foco’s Plus plan connects to these tools and imports tasks automatically, keeping everything in one place without manual entry.

FAQ

FAQ

How do I handle tasks that belong to multiple projects?

Tag them with both project labels (e.g., |#ClientA #CourseX|) and add a note explaining the overlap. Example: |Write case study (for Client A and Course X)|. Review these tasks during both project reviews.

What’s the best way to prioritize tasks across 5+ projects?

Use the Eisenhower Matrix to classify tasks by urgency/importance. Focus on urgent and important first. For cross-project conflicts, ask: Which task has the earliest deadline? Which blocks the most other tasks? Example: |Client A: Fix critical bug (due today)| > |Course X: Read optional article|.

How often should I review projects with dependencies?

Review dependencies daily if they’re time-sensitive (e.g., |Project A: Task 3 → Project B: Task 1|). For long-term dependencies, check weekly. Example: If |Project A|’s deliverable is due Friday and blocks |Project B|, review it Monday and Wednesday.

What’s the minimum viable GTD setup for someone with 3 projects?

Three inboxes (one per project), a |Next Actions| list per project, a |Waiting For| list per project, and a calendar with color-coded events. Example: Use a tool like Foco to create containers for |Client A|, |Course X|, and |Home|, then filter tasks by project or view all together.

How do I prevent the weekly review from taking 3+ hours?

Split it into 15-minute daily micro-reviews (e.g., Monday for |Client A|, Tuesday for |Course X|). Use a checklist per project: What’s done? What’s blocked? What’s next? Example: On Monday, review |Client A|’s tasks, update the |Next Actions| list, and archive completed items.