How to Use GTD for Multiple Jobs Without Burning Out: A Practical Guide with Real Examples

If you juggle multiple jobs, clients, or projects at once, you know how quickly things can spiral out of control. Tasks pile up, deadlines overlap, and the feeling of always running—but never making progress—becomes exhausting. This is where David Allen’s GTD (Getting Things Done) method can be your best ally. But how do you use GTD for multiple jobs without your system collapsing under its own weight? This guide explains it with concrete steps, real-world examples, and key adaptations to keep things manageable without drowning in processes.

Why GTD Works for Multiple Jobs (and Where It Often Fails)

GTD is built on a simple principle: free your mind from remembering tasks so you can focus on executing them. Its five-step workflow—capture, clarify, organize, reflect, and engage—is universal, but when you manage multiple jobs, specific challenges arise:

• Capture becomes chaotic: Where do you jot down a task if you’re not sure which job it belongs to?
• Prioritization gets complicated: What’s urgent when everything seems urgent?
• The weekly review drags on: Reviewing 10 projects in one sitting can take hours.
• Contexts blur together: How do you separate tasks that require deep focus from those you can do during a coffee break with a client?

The most common mistake is trying to apply GTD identically to each job, as if they were isolated silos. In reality, you need a system that lets you see the big picture (to prioritize) while also isolating each project when you need to focus on it. This is where most tools fall short: they either show you everything jumbled together or force you to switch between tabs to view each job separately.

How to Use GTD for Multiple Jobs: Step-by-Step with Examples

In GTD, capture should be immediate and frictionless. When managing multiple jobs, this means:

• Using a single inbox for all tasks, regardless of their origin. Example: An email from a client, an idea for a personal project, and an overdue invoice all go to the same place.
• Assigning a visual identifier to each job (like a color or tag) so you can recognize at a glance what each task belongs to. For example, blue for Client A, green for your personal project, and red for administrative tasks.
• Including minimal context in the capture: Is this a task that requires deep focus? Do you need to be in the office? Does it depend on someone else?

Real-world example: Imagine you dictate via voice, "Call María to review the contract for Client X—it’s urgent, and I need the document she sent yesterday." A good capture should include:

• Title: Review contract with María (Client X).
• Color or tag: Blue (associated with Client X).
• Priority: Urgent.
• Context: Call (requires a phone).
• Attached note: María’s document (so you don’t waste time looking for it later).

In this step, you process each task in your inbox to decide if it’s actionable. With multiple jobs, add these key questions:

• Which job does this belong to? If it’s unclear, create a temporary category like "Unassigned" to revisit later.
• Is this a task or a project? In GTD, a project is any outcome that requires more than one step. Example: "Prepare proposal for Client Y" is a project; "Draft the proposal introduction" is a task.
• Can I delegate it? If you work with teams or collaborators, assign the task to the right person within that job.

Example: You receive an email with the subject "Changes to the design for Project Z." When clarifying it, you determine:

• Is it actionable? Yes.
• Job: Project Z (purple color).
• Type: Project (because it requires coordinating with the designer, reviewing feedback, and approving changes).
• Next action: Schedule a meeting with the designer (specific task).

GTD suggests organizing tasks into lists based on their context (e.g., "Calls," "At the office"). With multiple jobs, you can adapt this in two ways:

• Lists by job: Create a list for each project or client, but keep a global view that groups them. Example: "Client A - Pending," "Personal Project - Ideas," "Admin - Invoices."
• Lists by task type: Group similar actions regardless of the job. Example: "Calls," "Meetings," "2-Minute Tasks." This helps you make the most of downtime (like waiting in a meeting room) to tackle what you can.

The key is to avoid fragmentation. If you have too many lists, you’ll lose the big picture; if you have too few, you’ll drown in details. A good balance is to combine both strategies: lists by job for specifics and lists by context for cross-cutting tasks.

The weekly review is the heart of GTD, but with multiple jobs, it can become endless. To optimize it:

• Divide the review into blocks: Spend 20-30 minutes per job instead of trying to review everything at once. Use a timer to stay focused.
• Prioritize by impact: Start with the jobs that generate the most income or have imminent deadlines. Ask yourself: What three things, if I don’t do them this week, will have serious consequences?
• Clear out the obsolete: Delete or archive tasks that are no longer relevant. With multiple jobs, it’s easy to accumulate "ghost tasks" that never get done.

Example of a weekly review:

• Monday 9:00 - 9:30 AM: Review Client A (this week’s deadlines, delegated tasks, blockers).
• Monday 9:30 - 10:00 AM: Review personal project (progress, new ideas, resources needed).
• Tuesday 6:00 - 6:30 PM: Review administrative tasks (invoices, errands, reminders).

With multiple jobs, the biggest challenge is deciding what to focus on. GTD suggests using four criteria:

• Context: What can you do right now with the resources available? (Example: If you’re in the office, prioritize tasks that require your computer.)
• Time available: Do you have 5 minutes or 2 hours? Use gaps for quick tasks.
• Energy: Are you fresh or exhausted? Save tasks that require deep focus for your high-energy moments.
• Priority: What will have consequences if you don’t do it today?

Practical example: It’s 11:00 AM, you have a meeting in 30 minutes, and you’re feeling energized. Your task list includes:

• Draft report for Client A (requires focus, 1 hour).
• Call the supplier to confirm delivery (5 minutes, urgent).
• Review feedback for personal project (can wait).

The decision: Call the supplier (urgent and quick), then use the remaining 25 minutes to make progress on the report (high focus, but limited time).

Common Mistakes When Using GTD for Multiple Jobs (and How to Avoid Them)

• Creating too many lists: If you have 20 lists, one for every subtask, you’ll lose the big picture. Solution: Group by main jobs and use tags for cross-cutting tasks.
• Not assigning colors or identifiers: Without a visual system, you’ll mix up tasks from different jobs. Solution: Use colors, icons, or prefixes in titles (e.g., [CLIENT A] Review contract).
• Skipping the daily review: With multiple jobs, priorities change fast. Solution: Spend 5 minutes a day reviewing only urgent tasks or those with near deadlines.
• Mixing personal and professional: While GTD allows you to manage everything in one system, with multiple jobs, it’s helpful to separate work from personal tasks to avoid distractions. Solution: Use separate categories or spaces within your tool.

How to Adapt GTD in Foco for Managing Multiple Jobs Without Overwhelm

If you already use GTD for multiple jobs, you know that the tool you choose can make the difference between a smooth system and one that wastes more time than it saves. Foco is designed to address the pain points of GTD when managing multiple projects:

• Jobs as containers: Each job (client, project, or area) is an independent space with its own name and color. This way, a task for Client A will always appear in blue, no matter which view you’re in.
• Panorama vs. Focus mode: In Panorama mode, you see all tasks from all jobs at once, each with its color, to prioritize globally. If you need to focus on a single job, switch to Focus mode, and the board automatically filters to show only that project’s tasks.
• Smart voice capture: Dictate a task like "Meeting with the design team for Project Z on Thursday at 10 AM—it’s important and will take 1 hour," and Foco automatically detects the date, time, priority, and duration, creating the task already organized. If you dictate multiple tasks in a row (Burst mode), it separates them in real time and shows them to you for review before saving.
• Flexible views: Use the List view to group tasks by date (Today, This Week, Later) and see what needs immediate attention. Switch to Kanban to organize by status (To Do, Doing, Done) or to Calendar to see deadlines and meetings alongside your tasks.
• Integrations with work tools: If you use Notion, GitHub, Jira, or Asana, Foco can automatically pull in tasks assigned to you in those platforms, so you don’t have to capture them manually. When you mark a task as done in Foco, you can set it up to complete it in the source tool as well (e.g., close an issue in GitHub).

Example workflow in Foco:

• Capture via voice: "Call Luis to confirm the budget for Client B—urgent, tomorrow at 9 AM." Foco creates the task with Client B’s color, urgent priority, and a reminder for tomorrow.
• Organize: In List view, you see the task appears under "Today" (due to the reminder). In Kanban, you drag it to the "Doing" column when you start the call.
• Review: In Panorama mode, you see all your tasks for the week, each with its color. Filter by Client B (Focus mode) to see only their tasks and plan your day.
• Engage: Use the Calendar view to see the call with Luis alongside other meetings and tasks for the day.

Foco isn’t a tool built exclusively for GTD, but its design solves the areas where the method often struggles with multiple jobs: fragmentation, lack of visual context, and information overload. If you already use GTD, try adapting it in Foco to see how it simplifies management without losing flexibility. If you haven’t started yet, this guide gives you the steps to begin, with or without a tool.