Time blocking has a reputation problem. Productivity writers recommend it relentlessly, people try it, it does not work the way they expected, and they conclude either that they are bad at time blocking or that time blocking is overrated. Usually neither is true. The failure has a specific cause.
The Core Failure: Blocks Without Defense
Time blocking fails when blocks get created but not defended. Creating the block is the easy part — you open your calendar, drag out a two-hour rectangle, and feel a small hit of organizational satisfaction. The hard part is what happens when someone requests a meeting in that slot, or when something urgent comes up, or when the block arrives and you are not in the mood.
If the block is treated as optional — if it moves every time something else comes up — it is not time blocking. It is wishful scheduling.
The Psychological Asymmetry
Here is the root of the problem: meeting requests feel like obligations. Your own blocks feel negotiable. When a colleague asks for a meeting, there is social weight behind the request. Declining requires a reason. When your own "deep work" block comes up against that request, it has no social weight at all — just your own preference.
The fix is to treat your own blocks as real appointments with the same weight as external meetings. Not as a motivational affirmation, but as a literal operational choice: when someone asks for that time, you say you have a conflict. You are not lying. You do have a conflict. It is with yourself.
Your calendar does not know the difference between an external meeting and your own block. That equivalence is the whole point.
The Second Failure: Over-Blocking with No Buffer
The second most common failure: people block every hour of their day with perfectly planned work, leaving no buffer. Then one task takes longer than expected, and the cascade begins. A calendar with no slack has no resilience. Build in buffer blocks — unplanned time that can absorb overruns. If nothing overruns, the buffer becomes a bonus.
The Third Failure: Blocking Tasks Instead of Work Types
Blocking specific tasks ("write Q2 report") sets you up for failure if that task is not the right energy for the moment. Blocking work types ("deep focus — writing or analysis") gives you flexibility within the protected time. You show up to the block and choose the right task from your type category, instead of being locked into one thing that may not fit the day.
The One Thing That Makes It Stick
Track whether you actually kept your blocks. This is the single most effective intervention. Not as a guilt mechanism — as information. A weekly review that asks "how many of my blocks did I actually protect?" tells you where the leakage is. Blocks that consistently get overridden by meeting requests need to move to better-protected times. Blocks you consistently skip yourself need to be either eliminated or renegotiated with yourself.
Tempo's layer tracking gives you this data automatically. If your "Focus" layer is consistently thinner than scheduled, the pattern is visible. That visibility is the starting point for changing it.