Thrashing (Over-Scheduling)

A computing term for when a system spends more time switching between tasks than doing actual work—the processor is 'busy' but producing nothing because context-switching overhead consumes all available capacity. In organizations: when people have so many concurrent priorities that they spend more time in meetings about work than doing work, more time switching contexts than thinking deeply, and more time managing their task list than completing tasks. Thrashing is the systemic result of exceeding human channel capacity with simultaneous demands.

When to use it

When teams are busy but nothing is getting finished; when adding more tasks is slowing overall throughput; when context-switching costs are consuming productive capacity; when calendar density has increased but output quality has declined.

How it can help

Diagnose thrashing by tracking the ratio of productive work time to coordination/switching time. If meetings, email, context-switching, and task management consume more than 50% of the day, you're thrashing. The fix isn't better time management—it's reducing concurrent commitments. Work-in-progress limits (from kanban), focus days (no-meeting blocks), and ruthless prioritization (doing fewer things) address thrashing at the systemic level. The counterintuitive solution: doing fewer things simultaneously produces more total output because it eliminates switching overhead.