Multi-Account Management: Context Switching as a Skill

This year I went from managing one account to three. The naive approach — keeping everything in my head and switching between contexts throughout the day — lasted about two weeks before I started dropping balls.

Context switching isn't just a developer problem. PMs who manage multiple accounts need systems to prevent cognitive overload.

My system

Time blocking by account. Monday and Wednesday mornings are Account A. Tuesday and Thursday mornings are Account B. Account C gets Friday and overflow slots. Afternoons are cross-account work and stakeholder communication. This isn't rigid — emergencies break the pattern — but it gives me a default that prevents constant context switching.

Account-specific journals. I keep a running document per account with three sections: current state, this week's priorities, and open risks. Before every account meeting, I spend 5 minutes reading my journal. It takes me from cold to warm in the time it takes to brew coffee.

Separate notification channels. Each account has its own Slack workspace or channel group. I mute all accounts except the one I'm focused on during time blocks. The urge to check other accounts is strong. Resist it.

Delegation with context. My tech leads own the day-to-day execution for each account. I own cross-account strategy, escalations, and stakeholder relationships. If I'm doing work a tech lead should be doing, something is wrong with my delegation.

The trap

The dangerous moment is when all three accounts need you urgently on the same day. This happens about once a month. The answer isn't working three times harder — it's triaging ruthlessly. Which fire causes the most damage if left for 4 hours? Handle that one. Delegate or defer the others.

What I learned

Multi-account management isn't about being busier. It's about being more disciplined with your attention. Your brain is single-threaded. Build systems that respect that limitation.