Design your first week in blocks
A practical guide to starting with contextual time-blocking without falling into system perfectionism. Three steps, five templates, one week.
The most common trap when starting any productivity system is wanting to design it perfectly before using it. You spend three hours designing the system to manage the three hours you need to do the actual work.
This guide is designed to avoid that trap. You’re not going to design the perfect week. You’re going to design a sufficient week and use it to learn.
Before opening the app
There are two questions worth answering before touching the keyboard:
What types of work do you do regularly?
I’m not talking about specific tasks. I’m talking about categories of work. For most knowledge workers, there are between three and six categories:
- Deep work (code, writing, analysis, design — whatever requires sustained focus)
- Communication (email, Slack, informal meetings)
- Formal meetings
- Planning and review
- Admin and management (expenses, bureaucracy, forms)
- Free time or recovery
When do you have the most energy?
Your calendar should reflect your biology, not the other way around. If your concentration peak is between 9 and 12, that time is for deep work. If you struggle after lunch, that’s when meetings or admin go. There’s no universally correct answer.
With those two answers, you have the raw material for your templates.
Step 1: Create five base templates
No more than five. Five is enough to start and not too many to manage.
Template 1: Deep work
This is the most important one. Configure it carefully.
- Duration: 90-120 minutes (enough to enter real focus)
- Color: choose one that feels “serious” — in ZexTime, peach or mauve work well
- Priority: high
- Habits: no distractions (notifications), water on the desk, review tasks at the start
- Pomodoro: 25/5 or 50/10 depending on your preference
- Default tasks: leave 2-3 slots for the specific tasks of each instance
Template 2: Email and communication
- Duration: 30-45 minutes
- Habits: quick or deferred response (don’t mix), archive what requires no action
- Frequency: maximum twice per day. More than that and email starts managing your calendar.
Template 3: Meetings
If you have a recurring type of meeting, create a template for it. If you have multiple types (1:1, sprint planning, review), create a template for each.
- Habits: prepare agenda beforehand, notes during, actions at close
- Linked notes: the meeting document, the agenda
Template 4: Planning and review
This is the most ignored template and the most important for the system to work.
- Duration: 30 minutes
- Timing: end of day or first thing in the morning
- Tasks: review what was left pending yesterday, configure tomorrow’s blocks, update tasks in relevant blocks
Template 5: Free time / recovery
Yes, this is also a block. A block with no tasks is an honest block. Empty slots in the agenda are part of the agenda.
Step 2: Place blocks in the day
Take tomorrow. Not the whole week. Tomorrow.
- Mark your fixed constraints (already-called meetings, commitments).
- Place the deep work block in your best energy window.
- Place communication blocks outside that window.
- Close the day with a 30-minute planning block.
- Leave real gaps between blocks (the buffer is not optional).
The resulting day will probably have 4-5 blocks. That’s enough. A day with 8 tight blocks is a poorly planned day.
Step 3: Use Focus mode
This is where the system is put to the test.
When you reach the first block of the day, open it in Focus mode. Read the tasks. Activate the habits. Start the Pomodoro.
Don’t open email until you reach the communication block. Don’t check Slack until then. If something urgent comes up, note it in the planning block’s tasks and continue.
When you finish the block, mark it as complete. ZexTime will save an instance with the state of the tasks and habits from that session.
The learning week
After your first week using the system, set aside 30 minutes for a review. Ask yourself:
- How many blocks did I complete vs. what I planned?
- Which blocks were interrupted, and why?
- What tasks did I end up doing outside their assigned block?
- Which templates worked well as defined? Which need adjustment?
Don’t expect the first week to go perfectly. Expect to learn what needs adjusting. That’s the real goal of the first week.
What not to do
Don’t try to capture everything. If you have a task that doesn’t fit any block, create a generic “Misc” template and put it there. Don’t block time to think about where each task goes.
Don’t make blocks too short. A 20-minute block doesn’t give time to enter context. If you think something “only takes 15 minutes,” it probably takes 40 including the setup.
Don’t block 100% of your day. Leave at least 20% without assigned blocks. Interruptions are inevitable. If your schedule has no margin, any unexpected event breaks everything.
Contextual time-blocking isn’t a system that works from day one. It’s a system that improves with use, because every week you learn something about how you actually work. After four weeks, you’ll have a schedule that is honest with yourself about what you can do in a day.
No task list achieves that.
Also read: What is contextual time-blocking?