What is maker schedule productivity?

Example: You are a software engineer with a four-hour morning block reserved for deep coding. At 9:47, a colleague messages you about a non-urgent question. You glance at it — just to see what it says. The question is simple, and you answer in two minutes. But when you turn back to your editor, the mental model you had been constructing — the full architecture of the module you were building, its edge cases, its interactions with three other components — is gone. You stare at the screen. You re-read the last function you wrote. You try to recall where you were headed. Twenty-three minutes later, you are back in the flow of the work. A two-minute interruption cost twenty-five minutes of productive time. By noon, you have had four such interruptions. Your four-hour block yielded approximately ninety minutes of actual deep work. The remaining one hundred fifty minutes were spent recovering from interruptions that each felt trivially short. The math is brutal, and it is invisible to anyone who measures only the duration of the interruption rather than the cost of the context switch.

This concept is part of Time Systems in the How to Think curriculum.