90-Minute Deep Work Blocks for Multiple Projects: Exact System to Maintain Focus and Avoid Burnout

The 90-minute deep work technique leverages ultradian rhythms—natural 90-120 minute cycles of high and low cognitive energy—to maximize focus on complex tasks. For professionals juggling multiple projects, this method prevents fragmented attention and reduces the mental cost of context-switching. Here’s how to implement it with precision:

Step 1: Assign 90-Minute Blocks to High-Impact Projects

Start by identifying which projects require deep work. Use the Eisenhower Matrix to classify tasks by urgency and importance, then allocate blocks accordingly. Example for a freelance designer with three clients:

• Client A (urgent + important): 2 blocks/day (e.g., 9:00–10:30 AM and 2:30–4:00 PM). Task: Redesign e-commerce homepage.
• Client B (important, not urgent): 1 block/day (e.g., 11:00 AM–12:30 PM). Task: Draft brand guidelines.
• Client C (urgent, not important): 30-minute slot (e.g., 4:30 PM). Task: Quick social media graphics.
• Admin: Grouped into a 45-minute block (e.g., 5:00 PM). Tasks: Invoices, emails.

Key rule: If a task doesn’t justify a 90-minute block, batch it or delegate it. This ensures deep work time isn’t diluted by shallow tasks.

Step 2: Structure Each Block for Maximum Output

Divide the 90 minutes into phases to sustain energy and focus:

• 0–10 minutes: Define the goal. Example: ‘Complete wireframes for Client A’s checkout flow.’ Write it on paper or a sticky note.
• 10–70 minutes: Deep work. Silence notifications, close unrelated tabs, and use tools like Cold Turkey to block distractions. If working in a team, set an ‘emergency’ Slack channel (e.g., #urgent-only).
• 70–80 minutes: Review progress. Adjust if off-track (e.g., ‘Need client feedback on color palette—add to next block’s agenda.’).
• 80–90 minutes: Wrap up. Document next steps (e.g., ‘Pending: Client A’s approval on wireframes’) and reset your workspace for the next block.

Pro tip: If 90 minutes feels too long, start with 60-minute blocks and gradually increase. The goal is to match your natural rhythm, not force an arbitrary duration.

Step 3: Minimize Context-Switching Costs

Switching between projects drains mental energy. Reduce friction with these tactics:

Group Similar Tasks

Schedule blocks requiring similar skills consecutively. Example for a developer:

• 9:00–10:30 AM: Debug API for Client A (coding).
• 10:45 AM–12:15 PM: Write documentation for Client B (writing).
• 1:00–2:30 PM: Design database schema for Client C (analytical).

Why it works: Your brain stays in ‘coding mode’ for the first two blocks, reducing the need to ‘reload’ context.

Use Active Transitions

Between blocks, reset your mind with a 15–30 minute break. Options:

• Physical: Walk, stretch, or do breathing exercises (e.g., 4-7-8 technique).
• Environmental: Move to a different space (e.g., from desk to couch) or step outside.
• Mechanical: Tidy your desk, file documents, or make a non-work call.

Avoid: Checking emails or social media—these create new mental loops.

Document Project Status

At the end of each block, note:

• What you accomplished: ‘Finished wireframes for Client A’s checkout flow.’
• Next steps: ‘Need client feedback on color palette.’
• Roadblocks: ‘Pending: Client B’s content for homepage.’

Store these notes in a visible place (e.g., a project management app or notebook). Tag them by project for quick retrieval. For a system to separate contexts without losing the big picture, see Bullet Journal for Multiple Jobs: Exact System to Separate Contexts Without Losing the Big Picture.

Step 4: Real-World Example (Freelance Developer)

Scenario: A developer managing an app (Client A), a website (Client B), and a personal course. Here’s their day:

• 7:30–9:00 AM: App (Client A). Task: Implement payment gateway. Result: Code deployed for testing.
• 9:00–9:30 AM: Break + urgent emails.
• 9:30–11:00 AM: Personal course. Task: Record lesson 3. Result: Video edited and uploaded.
• 11:00–11:30 AM: Walk + call with Client B to clarify requirements.
• 11:30 AM–1:00 PM: Website (Client B). Task: Design homepage. Result: Mockup approved.
• 1:00–2:30 PM: Lunch (no screens).
• 2:30–4:00 PM: App (Client A). Task: Fix bugs. Result: 5/7 bugs resolved.
• 4:00–4:30 PM: Snack + review pending tasks.
• 4:30–6:00 PM: Personal course. Task: Write script for lesson 4. Result: Script completed.

Key takeaways:

• Grouped similar tasks (e.g., two app blocks) to reduce context-switching.
• Used active transitions (walks, calls) to reset focus.
• Documented progress after each block to avoid rework.

Step 5: Avoid Common Mistakes

Mistake 1: Skipping Preparation

Problem: Wasting the first 10–15 minutes deciding what to do. Solution: Define the block’s goal in one sentence before starting (e.g., ‘Draft proposal for Client X’). If you can’t summarize it, the task is too vague.

Mistake 2: Ignoring Fatigue Signals

Problem: Forcing focus during low-energy periods (e.g., post-lunch). Solution: Schedule demanding blocks during peak hours (e.g., morning). Use afternoon blocks for shallow tasks like emails or admin. For strategies to avoid procrastination, see Parkinson's Law for managing multiple jobs and avoiding procrastination: a practical guide.

Mistake 3: Multitasking Within a Block

Problem: Trying to work on two projects simultaneously. Solution: If an urgent task arises, jot it down on a ‘pending’ list and address it in its assigned block. Use the two-minute rule: handle interruptions under two minutes immediately; postpone longer ones.

Tools to Implement the System

Calendars: Block 90-minute slots in Google Calendar or Outlook. Use colors to differentiate projects (e.g., blue for Client A, green for Client B).

Task Managers: Organize tasks by project and priority. For example, use the Critical Power List method to identify high-impact tasks for each block. Learn how in Critical Power List: How to Identify, Prioritize, and Execute Critical Tasks (Exact Steps for Freelancers).

Distraction Blockers: Tools like Freedom or Cold Turkey to block social media and unrelated websites during blocks.

Foco: If you need a single tool to manage multiple projects, Foco lets you create color-coded project containers (e.g., red for Client A, blue for Client B). Use Panorama mode to see all tasks at once or Focus mode to concentrate on one project. The Calendar view syncs with Google Calendar/Outlook to avoid scheduling conflicts, while voice capture lets you log tasks hands-free between blocks. For freelancers using multiple apps (e.g., Notion, GitHub, Jira), Foco Plus unifies tasks without migrating data. See How to Unify Tasks from Multiple Apps in One Place Without Migrating Data: A Practical Guide with Foco Plus.

Deep work isn’t about working longer—it’s about working smarter in focused bursts, with systems that minimize friction between projects.

FAQ

FAQ

How do I handle interruptions during a 90-minute block?

Use the two-minute rule: if the interruption takes less than two minutes, handle it immediately. For longer interruptions, jot it down on a ‘pending’ list and return to it in its assigned block. Communicate your focus time to colleagues (e.g., ‘I’m in deep work until 10:30 AM—use #urgent for emergencies’).

What if a project requires more than 90 minutes?

Break it into sub-tasks. For example, if designing a website takes 4 hours, split it into: ‘Block 1: Wireframes’ and ‘Block 2: High-fidelity mockups.’ Document progress after each block to avoid rework.

Can I use this technique with the Pomodoro method?

Yes, but adjust the timing. Use 90-minute blocks for deep work and 25-minute Pomodoros for shallow tasks (e.g., emails). Example: ‘9:00–10:30 AM: Deep work block (Client A)’ followed by ‘10:45–11:10 AM: Pomodoro for emails.’

How do I track progress across multiple projects?

Use a task manager to log completed tasks and next steps after each block. In Foco, the List view groups tasks by date (e.g., ‘Today,’ ‘This Week’), while the Kanban view shows progress in columns (e.g., ‘To Do,’ ‘Doing,’ ‘Done’).

What if I can’t finish a task in 90 minutes?

Note what’s left and schedule it for the next block. Example: ‘Block 1: Drafted 3/5 sections of the report—next block: finish sections 4–5.’ Avoid extending the block; stick to the time limit to prevent burnout.