What switching actually costs

Work that needs thinking is different from work that needs doing. Answering messages can be done in fragments. Writing, analysing, designing and debugging cannot, and treating them the same is why some tasks take all day and still feel unfinished.

Getting into a piece of work takes time. You have to load the context: what you were doing, what you had decided, what comes next. That loading is real and it costs minutes, not seconds.

Every interruption makes you pay it again. A message that takes thirty seconds to answer does not cost thirty seconds. It costs thirty seconds plus the reloading, and the reloading is usually longer than the interruption.

Six interruptions in two hours can consume most of the two hours, and nothing on your calendar records it. This is why a day can feel completely full and produce nothing you can point at.

The residue is worse than the interruption. After switching back, part of your attention stays with the thing you just left. You are working, but at reduced capacity, and you do not notice because it still feels like working.

Which means the target is not more hours. It is fewer, longer, uninterrupted pieces. Two protected hours produce more than six fragmented ones, and the six leave you more tired.

And some work genuinely does not need protection. Replying, filing, routine admin: do those in the gaps. The mistake is treating everything as the same kind of work and then wondering why the hard thing never progresses.