How do I practice protect maker time?

At the end of the block, count the interruptions and estimate the total recovery time (use twenty-three minutes per interruption as your baseline, adjusting based on the complexity of what you were doing). Calculate the ratio of actual deep work time to total block time. At the end of the week, you will have five data points. Average them. This number — your maker-time efficiency ratio — tells you what percentage of your intended deep work time actually produces deep work. Most people discover this number is between thirty and fifty percent. That discovery is the motivation for every protection strategy this lesson teaches.

Common pitfall: Two complementary failures bracket this lesson. The first is undefended maker time — blocking time on a calendar but treating the block as a suggestion rather than a commitment. This person has "focus time" on their schedule, but they answer messages during it, accept meeting invitations that overlap it, and allow colleagues to interrupt it because refusing feels rude. The block exists in name only. It provides no protection because it carries no enforcement. The second failure is fortress mode — defending maker time so aggressively that collaboration, relationships, and responsiveness suffer. This person closes every channel, ignores every request, and treats any interruption as a personal affront. They produce excellent deep work in isolation and gradually become someone that nobody can work with, plan around, or rely on for timely responses. The mature position is defended but not fortified: clear boundaries with clear availability, protected blocks with defined response windows, and the social skill to maintain both without either collapsing into the other.

This practice connects to Time Systems — building it as a repeatable habit compounds over time.