What is context switching costs productivity?

Context switching costs productivity is a concept in personal epistemology: Schedule transition time between different types of work to reduce context-switching costs.

Example: You finish a 60-minute product strategy call at 11:00 and your calendar shows a deep coding block starting immediately. You open your IDE, stare at the function you were writing yesterday, and realize you cannot remember what it was supposed to do. Your head is still in the strategy call — replaying something the VP said about Q3 priorities, wondering if you should have pushed back harder on the roadmap, composing a follow-up email you haven't sent yet. Twenty minutes pass before you even locate the right file. Another ten before you understand your own code. By 11:30, you have thirty minutes of real focus before your next meeting. The coding block was 90 minutes on paper. It was 30 minutes in practice. The other 60 minutes were consumed by an invisible tax: the cost of switching from one cognitive context to another with no transition time. A ten-minute buffer between the call and the coding block — time to close the strategy conversation mentally, jot down the follow-up email, take a short walk, and deliberately reload the coding context — would have saved 50 minutes of productive work.

This concept is part of Phase 42 (Time Systems) in the How to Think curriculum, which builds the epistemic infrastructure for time systems.