Home Consulting FrameworksTime Blocking

Building

Time Blocking

Reserve deep-work blocks before reactive meetings fill the calendar.

Building1,603 words·By Sufi Khan Sulaiman

Table of Contents

1. History & Origins
2. Core Concept
3. B2B Application Guide
4. Step-by-Step Implementation
5. Common Pitfalls & How to Avoid Them
6. Extended Real-World Example
7. Measuring Success

History & Origins

Time Blocking has roots in productivity literature from the early 20th century, but it was popularised for knowledge work by Cal Newport in his 2016 book 'Deep Work.' Newport argued that the ability to focus without distraction is a competitive advantage in the modern economy, and that protecting deep-work blocks from reactive meetings is the mechanism. The technique was adopted by executives, engineers, and creative professionals as a way to make time allocation visible and defend strategic work from context-switching. Time Blocking is now a standard practice in engineering leadership, product management, and executive coaching, particularly for roles where reactive work constantly threatens to crowd out the strategic work that compounds. Newport developed the framework in response to the rise of open offices, constant connectivity, and meeting culture, which had eroded the ability to do focused, cognitively demanding work. His contribution was distinguishing between deep work (cognitively demanding, high-value, requires focus) and shallow work (logistical, low-value, tolerant of interruption), and arguing that the ability to do deep work is a skill that must be protected and practised. The framework is complementary to the Eisenhower Matrix (which prioritises tasks) and to the 12-Week Year (which compresses execution), and it is particularly valuable for roles where the deep work that compounds is constantly threatened by the reactive work that screams.

Core Concept

Time Blocking reserves fixed calendar blocks for specific work types, protecting deep work from reactive context-switching. The framework audits where time actually goes, then blocks deep work (architecture, analysis, writing) before reactive work (meetings, email, tickets) fills the week. The key principle is that time is a zero-sum resource: if you don't block it deliberately, reactive work will consume it. The framework makes time allocation visible and measurable, so leadership can see whether deep work is being defended or eroded. The weekly actual-versus-planned audit is the feedback loop that turns time blocking from a good intention into a measured practice. The framework also distinguishes between deep work (cognitively demanding, high-value, requires uninterrupted focus) and shallow work (logistical, low-value, tolerant of interruption), and argues that the deep work is where strategic value is created. The key insight is that context-switching has a hidden cost: each interruption (a meeting, a Slack message, a ticket) doesn't just consume the time of the interruption, but also the recovery time to return to the deep-work state, which can be 15-30 minutes per interruption. Time Blocking eliminates this cost by creating uninterrupted blocks where the deep-work state is maintained for hours.

B2B Application Guide

In B2B companies, Time Blocking protects the deep work that compounds: architecture, tech-debt paydown, vendor evaluation, BOM analysis. Mornings are blocked for architecture and design; afternoons are open for review, planning, and 1:1s. The framework ensures the important work gets done alongside the urgent, rather than being perpetually deferred. For inventory and supply-chain leaders, blocked analysis time keeps forecasting, safety-stock, and BOM reviews on cadence instead of reactive, which stabilises service levels and carrying cost without adding headcount. For technology selection, it protects the architecture and evaluation work that compounds from being deferred by reactive tickets, so opex funds decisions rather than firefighting. For merchandising, blocked analysis time keeps assortment reviews, margin analysis, and vendor negotiations on cadence rather than reactive. For hiring, blocked time keeps the interview cadence consistent, so hiring doesn't drift when reactive work spikes. For vendor management, blocked time keeps the vendor reviews and contract negotiations on cadence, so vendor performance doesn't erode silently. The framework also disciplines meeting culture: by blocking deep-work time, the team creates a natural constraint on meeting proliferation, because the deep-work blocks are defended and meetings are pushed into the remaining time.

Time Blocking framework graphic — Sufi Khan Sulaiman — Time Blocking — Sufi Khan Sulaiman

Step-by-Step Implementation

Step 1: Audit the current week. Track where time actually goes for one week, categorising into deep work, shallow work, meetings, and reactive work. Step 2: Identify the deep-work priorities. List the cognitively demanding, high-value tasks that need protected time (architecture, analysis, writing, evaluation). Step 3: Block the deep-work time. Reserve fixed calendar blocks for deep work, ideally in the morning when cognitive energy is highest. Block 2-4 hours per day. Step 4: Defend the blocks. Set a calendar rule (no meetings during deep-work blocks without explicit approval) and communicate it to the team. Step 5: Schedule shallow work in the remaining time. Meetings, email, reviews, and 1:1s go in the afternoon blocks. Step 6: Audit weekly. At week end, compare the actual time in each category to the planned blocks, and adjust. Step 7: Adjust the blocks. If the deep-work blocks are being eroded, strengthen the defense (tighter calendar rules, earlier blocks, fewer meetings). Step 8: Review monthly. Assess whether the deep-work blocks are producing the intended outcomes (architecture shipped, analysis completed, evaluations done). Step 9: Make it a team practice. Encourage the team to block their own deep-work time, so the culture supports focused work rather than constant availability.

Common Pitfalls & How to Avoid Them

Pitfall 1: Not auditing first. The blocks are set without knowing where time actually goes, so the blocks are unrealistic. Avoid by auditing the current week before blocking. Pitfall 2: Not defending the blocks. The blocks are set but meetings are accepted during them, eroding the deep-work time. Avoid by a calendar rule and team communication. Pitfall 3: Blocking too little. The deep-work blocks are too short (1 hour) to reach the deep-work state. Avoid by blocking 2-4 hours per day. Pitfall 4: Not auditing weekly. The blocks are set and never reviewed, so erosion isn't detected. Avoid by a weekly actual-versus-planned audit. Pitfall 5: Blocking the wrong time. Deep work is blocked in the afternoon when cognitive energy is low, reducing the quality of the work. Avoid by blocking the morning for deep work. Pitfall 6: Not making it a team practice. The individual blocks their time, but the team culture doesn't support it, and the blocks are eroded by team expectations of constant availability. Avoid by encouraging the team to block their own deep-work time.

Extended Real-World Example

A VP of Technology blocked mornings (8:00-12:00) for architecture and deep work, and afternoons (13:00-17:00) for review, planning, and 1:1s. The blocks were defended from meetings by a calendar rule: no meetings before 12:00 without explicit approval. The result: the replatform architecture was designed in the morning blocks, and the review and people work happened in the afternoon blocks. The actual-versus-planned time audit showed 60% deep work, up from 30% before blocking, and the architecture shipped on schedule because it was defended rather than squeezed between meetings. The weekly audit also surfaced when the blocks were eroded, so the calendar rule was reinforced before context-switching silently inflated opex. Over 16 weeks, the Time Blocking practice produced a measurable shift in the VP's output. Week 1 audit: deep work 30%, shallow work 25%, meetings 35%, reactive 10%. The deep-work percentage was low because mornings were filled with meetings. The calendar rule was set: no meetings before 12:00 without explicit approval. Week 4 audit: deep work 50%, shallow work 20%, meetings 20%, reactive 10%. The morning blocks were being defended, and the replatform architecture was progressing. Week 8 audit: deep work 60%, shallow work 15%, meetings 15%, reactive 10%. The deep-work percentage had doubled, and the architecture was 70% complete. Week 12 audit: deep work 62%, shallow work 15%, meetings 13%, reactive 10%. The architecture shipped, and the VP began a new deep-work initiative (a vendor evaluation for a commerce platform replacement). Week 16 audit: deep work 60%, shallow work 15%, meetings 15%, reactive 10%. The vendor evaluation was complete, and the VP had produced two major strategic deliverables (the architecture and the vendor evaluation) in 16 weeks, compared to one in the previous 16 weeks. The afternoon blocks were used for review, planning, and 1:1s, and the team reported that the VP was more available for people work in the afternoon because the deep work was done in the morning. The weekly audit also caught erosion: in week 6, a board meeting was scheduled in the morning block, and the deep-work percentage dropped to 45%. The VP moved the board meeting to the afternoon in future weeks, and the deep-work percentage recovered. The Time Blocking practice was extended to the team: the engineering leads blocked their own morning deep-work blocks, and the team culture shifted to support focused work rather than constant availability. The result: the team's output increased measurably (architecture shipped on time, vendor evaluation completed, tech-debt paydown accelerated), and the VP's strategic deliverables doubled, because the deep-work time was defended rather than squeezed between meetings.

Measuring Success

Time Blocking success is measured by the deep-work percentage (the percentage of time spent in deep work, which should be trending up) and the deep-work output (the strategic deliverables produced in the deep-work blocks, which should be increasing). The key indicators are: deep-work percentage (should trend toward 50-60% for knowledge-work roles), block defense rate (the percentage of deep-work blocks that were not eroded by meetings, which should be high), and deep-work output (the number of strategic deliverables produced, which should be increasing). In practice, these are tracked by the weekly actual-versus-planned audit. The ultimate test is whether the deep-work blocks are producing strategic deliverables that wouldn't have been produced without the blocks: are the architecture, analysis, and evaluation work shipping on schedule, and is the quality higher than when the work was squeezed between meetings? If the deep-work percentage is rising but the output isn't increasing, the deep work may be mis-prioritised. If the block defense rate is low, the calendar rule isn't being enforced, and the blocks are being eroded. A healthy Time Blocking practice produces a deep-work percentage of 50-60%, a block defense rate above 80%, and an increasing output of strategic deliverables.

Framework Visualizations

Data-driven graphics showing how Time Blocking is applied to real B2B data.

Day blocks