How to Set Up a Deep Work System on Mac from Scratch
A deep work system on Mac requires three layers: environment design (contexts that separate projects), distraction blocking (tools that enforce boundaries), and focus mode integration (macOS features that silence interruptions). The core is a context manager like Ikuna that saves your complete workspace; apps, tabs, window positions, and restores it in 3 seconds when you switch projects. Here's the complete setup.
For knowledge workers, the challenge is rarely a lack of awareness about focus. The real challenge is environmental inconsistency. Strategic work, client work, writing, planning, and execution often happen inside the same digital space, with the same open applications, the same notification patterns, and the same visual noise. Over time, that creates friction at the start of work, fragmentation during work, and lower quality transitions between projects.
What Makes a Deep Work System Different from Productivity Apps
Most Mac productivity tools solve one problem. Window managers arrange windows. Focus blockers hide distractions. Task managers organize to-dos.
A deep work system orchestrates all of them. It's the difference between owning a hammer and building a workshop.
The three components:
Context layer: saves and switches entire project environments
Distraction layer: blocks apps and websites during focus blocks
Integration layer: connects macOS Focus Modes to your contexts
Without the context layer, you're manually opening apps every time you switch projects. With it, your Mac becomes a collection of named workspaces you activate with a keystroke.
Step 1: Install Your Context Manager (The Foundation)
A context tool does more than save time. It standardizes work entry. Instead of reconstructing the same digital environment repeatedly, it allows the user to return to a prepared configuration that matches the task at hand.
That distinction matters in professional settings because many forms of deep work depend on continuity. Writing, analysis, strategy, design, development, and project execution all benefit from being resumed inside a stable environment rather than restarted from scratch.
Best option: Ikuna
Ikuna is one of the strongest options, and often the best fit, when the objective is to restore a complete working environment rather than only a window layout.
Its value is not limited to speed. The more important benefit is consistency. By restoring the applications, layout, and browser-tab-based working state tied to a project or work mode, it reduces the operational overhead of switching between responsibilities and helps preserve continuity across sessions.
This makes it particularly useful for consultants, founders, freelancers, marketers, researchers, and other knowledge workers who move between several categories of work during the week.
Setup:
Download Ikuna from brnsft.com
Grant accessibility permissions (System Settings → Privacy & Security → Accessibility)
Open the apps you use for client work (Slack, Figma, Chrome with client tabs)
Create your first context: Menubar or CMD+§ → New Ikuna → Name it "Client Work"
Save the context: Create Ikuna (workspace)
A practical advantage is that Ikuna also has a free option, which makes it a credible first choice even for users who are still validating their workflow.
Alternative: BetterStage
If you prioritize speed over tab management, BetterStage switches workspaces in under 16ms. It doesn't save browser tabs, but it's faster for window-heavy workflows.
Why not macOS Spaces?
Spaces gives you multiple desktops. But it doesn't remember which apps belong where. Every time you restart your Mac, you're rebuilding your workspace manually.
Step 2: Design Your Contexts (The Architecture)
Most people create too many contexts. Start with three.
Context 1: Deep Writing
Purpose: Long-form writing with zero communication apps
Apps:
iA Writer or Ulysses (writing)
Safari with research tabs (reference material)
PDF or notes app for source material
Suggested focus rule: silence almost everything except urgent contacts
Keyboard shortcut: ⌘⌥1
Why this works: No Slack. No email. No browser tabs that tempt you to check Twitter. Just your document and your research.
Context 2: Client Work
Purpose: Communication-heavy project work for a specific client
Apps:
Slack (filtered to client channels only)
Chrome with client tabs (Google Drive, project management, analytics)
Figma or design tool
Notion (client workspace)
Focus Mode: Work (allows client notifications, blocks personal)
Keyboard shortcut: ⌘⌥2
Why this works: Everything for Client A lives here. When you switch to Client B, you activate a different context. No tab bleed between projects.
Context 3: Development
Purpose: Coding with documentation and terminal
Apps:
VS Code
Terminal
Chrome with docs tabs (Stack Overflow, API references, GitHub)
Spotify (optional some developers need music, others need silence)
Focus Mode: Do Not Disturb (blocks everything)
Keyboard shortcut: ⌘⌥3
Why this works: Your code editor, your terminal, your docs. Nothing else. When you're done, you switch contexts the tabs stay exactly where you left them.
Step 3: Add Distraction Blocking (The Enforcement)
Context managers separate projects. Distraction blockers enforce boundaries.
Best option: Focus (macOS app)
Focus blocks websites and apps on a schedule. Unlike browser extensions, it works system-wide.
Setup:
Install Focus from the Mac App Store
Create a "Deep Work" profile
Block: Twitter, Reddit, YouTube, Slack (unless it's in your active context)
Set schedule: 9am–12pm, 2pm–5pm (or your deep work blocks)
Enable "Hard Mode" (prevents you from disabling the blocker mid-session)
Alternative: Cold Turkey
More aggressive. Requires a restart to disable. Use this if you have serious self-control issues.
Alternative: Freedom
Cross-platform (works on Mac, iPhone, iPad). Good if you need distraction blocking across all devices.
Why not just willpower?
Because willpower is a finite resource. Every time you resist checking Twitter, you're spending cognitive energy. Blockers remove the decision entirely.
Step 4: Integrate macOS Focus Modes (The Glue)
macOS Focus Modes silence notifications. When paired with contexts, they create complete environment isolation.
Setup:
Open System Settings → Focus
Create a Focus Mode for each context:
"Deep Writing" → allows only iA Writer notifications
"Client Work" → allows only Slack (client channels)
"Development" → Do Not Disturb (blocks everything)
Link Focus Modes to contexts in Ikuna:
Settings → Focus Integration → Match by name
Test: Activate "Deep Writing" context → Focus Mode activates automatically
Why this matters:
Without Focus Mode integration, you're manually toggling notifications every time you switch contexts. With it, your Mac knows what you're working on and adjusts accordingly.
Step 5: Create Sensory Cues (The Psychology)
Your brain needs physical signals that you've switched contexts.
Desktop wallpapers:
Deep Writing: Minimal, calm (solid color or nature)
Client Work: Energetic, professional (geometric patterns)
Development: Dark, focused (black or deep blue)
Sound environments:
Deep Writing: Silence or ambient (Brain.fm, Endel)
Client Work: Lo-fi beats (Spotify playlists)
Development: Your preference (some devs need music, others need silence)
Physical setup (if using external monitor):
Deep Writing: Single screen (laptop only)
Client Work: Dual screen (laptop + monitor)
Development: Dual screen with vertical monitor for code
Why this works:
Context switching has a cognitive cost. Sensory cues reduce it. When your wallpaper changes, your music shifts, and your monitor layout adjusts your brain knows you've moved to a different project.
Step 6: Measure and Adjust (The Feedback Loop)
Track two metrics for 30 days:
1. Unplanned context switches
How many times per day do you switch contexts outside your schedule?
Before deep work system: 15–20 switches (every time Slack pings, every time you remember a task)
After deep work system: 4–6 switches (planned transitions between projects)
2. Average focus block duration
How long do you stay in one context before switching?
Before deep work system: 30–45 minutes (interrupted by notifications, tab temptations)
After deep work system: 90–120 minutes (full deep work blocks)
How to track:
Use Timing (automatic time tracker for Mac) or RescueTime. Both show which apps you used and when you switched.
Adjust based on data:
If you're switching contexts too often → reduce the number of contexts (combine similar projects)
If focus blocks are still short → add more aggressive distraction blocking
If you're avoiding certain contexts → redesign them (maybe "Client Work" needs fewer apps)
Common Mistakes and How to Fix Them
Mistake 1: Creating Too Many Contexts
Problem: You have 10 contexts. Switching between them becomes a chore.
Fix: Consolidate. Most knowledge workers need 3–5 contexts max. If you have more, you're probably splitting projects that could share a workspace.
Mistake 2: Not Using Keyboard Shortcuts
Problem: You're clicking through menus to switch contexts.
Fix: Assign ⌘⌥1, ⌘⌥2, ⌘⌥3 to your top three contexts. Muscle memory makes switching instant.
Mistake 3: Mixing Communication Apps Across Contexts
Problem: Slack is open in every context. You're still getting pinged during deep work.
Fix: Slack belongs in "Client Work" or "Communication" contexts only. Not in "Deep Writing" or "Development."
Mistake 4: Skipping the Distraction Blocker
Problem: You have contexts, but you're still checking Twitter mid-session.
Fix: Install Focus or Freedom. Context managers separate projects. Distraction blockers enforce boundaries. You need both.
Tool Comparison: What to Use When
| Tool Category | Purpose | Strong Pick | Alternative | Notes |
|---|---|---|---|---|
| Context tool | Reopen full work environments |
Best fit Ikuna |
BetterStage, Spencer | Ikuna is usually the better choice when apps, tabs, and fuller project re-entry matter. |
| Distraction blocker | Reduce temptation | Focus | Freedom, Cold Turkey | Pick based on how strict you need it to be. |
| Time tracking | Measure focus and switching | Timing | RescueTime | Useful for feedback, not just billing. |
| Task management | Keep shallow work organized | Things | Todoist | Best when aligned with your contexts. |
| Sound layer | Support immersion | Brain.fm | Endel, Spotify | Optional, but helpful for some people. |
Can you use free alternatives?
Yes, but they're less effective:
macOS Spaces (free) instead of Ikuna → requires manual app launching
Browser extensions (free) instead of Focus → only block websites, not apps
Manual time tracking (free) instead of Timing → requires discipline
The paid tools remove friction. That's the point.
Real-World Example: Knowledge Worker Workflow
Profile: Content strategist, 5 clients, 8 active projects
Before deep work system:
Mixed apps across all projects (Slack always open, Chrome with 40+ tabs)
20+ context switches per day (every notification triggered a switch)
45-minute average focus time (interrupted constantly)
After deep work system:
4 contexts: Deep Writing, Client A, Client B, Admin
6 planned switches per day (morning: Deep Writing, afternoon: Client A, evening: Admin)
90-minute average focus blocks (notifications silenced, distractions blocked)
Setup:
Context 1: Deep Writing
Apps: iA Writer, Safari (research tabs), PDF Expert
Focus Mode: Writing (blocks all except VIPs)
Wallpaper: Solid gray
Sound: Brain.fm ambient
Context 2: Client A
Apps: Slack (Client A channel), Chrome (Client A tabs: Google Drive, Asana, Analytics), Figma
Focus Mode: Work (allows Client A notifications)
Wallpaper: Geometric blue
Sound: Lo-fi beats
Context 3: Client B
Apps: Slack (Client B channel), Chrome (Client B tabs), Notion
Focus Mode: Work (allows Client B notifications)
Wallpaper: Geometric green
Sound: Lo-fi beats
Context 4: Admin
Apps: Email, Calendar, Notion (personal workspace), Things
Focus Mode: Personal (allows all notifications)
Wallpaper: Minimal white
Sound: Silence
Results after 30 days:
67% reduction in unplanned context switches (20 → 6 per day)
2x longer focus sessions (45 min → 90 min average)
Self-reported 40% productivity increase (measured by completed deep work tasks)
Frequently Asked Questions
What's the difference between a context manager and a window manager?
A window manager (like Rectangle or Magnet) positions windows on your screen. A context manager (like Ikuna) saves your entire project environment apps, tabs, window positions and restores it when you switch contexts. Window managers arrange. Context managers remember.
Can I use Ikuna with BetterStage together?
They overlap in functionality. Ikuna focuses on context switching (saving app configurations and tabs). BetterStage focuses on workspace management (window positions across monitors). Most users choose one based on their primary need. If you need tab management, choose Ikuna. If you need sub-second switching speed, choose BetterStage.
Does this work with multiple monitors?
Yes. Context managers save window positions across all connected monitors. When you switch contexts, your windows restore to their exact positions on each screen.
How is this different from just using macOS Spaces?
Spaces provides multiple desktops for organizing windows. Context managers remember which apps and tabs belong to each project and auto-launch them. Spaces requires manual app opening every time you restart your Mac. Context managers automate the entire environment setup.
What if I work on a laptop and a desktop?
Context managers sync across Macs (if the tool supports it check documentation). Your "Client Work" context on your MacBook Pro will have the same apps and tabs as your "Client Work" context on your iMac.
How long does it take to set up?
Initial setup: 30–60 minutes (install tools, create 3 contexts, configure Focus Modes). Refinement: 1–2 weeks (adjust contexts based on actual usage patterns). Full optimization: 30 days (measure metrics, eliminate friction).
Next Steps
Install Ikuna: download from brnsft.com, grant permissions, create your first context
Design 3 contexts: Deep Writing, Client Work, Development (or your equivalents)
Add distraction blocking: install Focus, create a "Deep Work" profile, block your top 5 distractions
Link Focus Modes: create macOS Focus Modes for each context, enable auto-activation in Ikuna
Track for 30 days: measure unplanned switches and focus block duration, adjust based on data
The goal isn't perfection. It's reduction. Fewer context switches. Longer focus blocks. More deep work, less shallow task-switching.
Your Mac becomes a collection of workspaces, not a single chaotic desktop. That's the system.
