Module 3: Design Your Week
A week is a container with fixed walls. This module measures your real capacity, gives each weekday a job, and installs the two structures that protect deep work: power blocks and batching.
The week container
There are 168 hours in a week. Subtract sleep (56), meals and life (about 25), and family and rest time, and most founders have 40–55 honest work hours — not the 70 they tell themselves. The Container is your real weekly work capacity, counted honestly. Plans built for a 70-hour container collapse by Wednesday; plans built for a 45-hour container actually happen.
Do the subtraction on paper: 168 minus sleep, minus non-negotiable life (school runs, workouts, dinner with family), minus real rest. What's left is the container. Then protect a margin — plan to use 80% of it, because weeks leak. A 50-hour container means 40 planned hours. The unplanned 10 aren't laziness; they're the overflow valve that keeps one bad Tuesday from sinking the week.
This number also sets your pricing and your promises. If your container is 40 hours and client work needs 25, you have 15 for building the business — not 30. Every overcommitment you've ever made was a container you never measured. Write your number down. You'll use it in the weekly template at the end of this module.
The week container — 168 hours, counted honestly
Give each weekday a job
Context-switching is a tax you pay every time your brain changes modes. A day split between sales calls, writing, bookkeeping, and support tickets is four shallow days in a trench coat. Anchor days fix this: each weekday gets one main job, and similar work lives together.
A common founder map looks like this:
- Monday — Money and planning: review the week, invoices, pipeline, Big Three for the week.
- Tuesday / Wednesday — Creation: the deep work. Content, product, writing. Meeting-free.
- Thursday — People: calls, meetings, interviews, client work. All of them, one day.
- Friday — Review and close: the Friday Reset (Module 5), loose ends, admin batch.
Yours will differ — a coach might anchor client sessions, a maker might anchor shipping. The rules: one job per day, one fully meeting-free day per week, and admin rides along with Friday instead of leaking into every day. When someone asks for a call, you don't check your calendar — you check your anchor map. "I do calls on Thursdays" is a complete sentence.
One job per day
Give each weekday a job
Build brief
Sketch your anchor days: which weekday gets which job? Which day will be your meeting-free day?
Saved
Power blocks
The Power Block is a 90-minute stretch of uninterrupted work on exactly one outcome. Ninety minutes because it's long enough to do real thinking and short enough to survive a normal day. One outcome because multitasking inside the block defeats the point. Uninterrupted means: phone in another room, inbox closed, door shut or headphones on.
Schedule power blocks at your peak energy — for most people that's the first 90 minutes of the workday, before email, before news, before the world gets a vote. Two power blocks a day is a heavy, excellent day. One is a fine day. Three is a fantasy for most founders; don't plan three.
Treat a power block like a client meeting with your most important client — you. You wouldn't cancel on a paying client to "quickly check" something. Give the block the same standing: it moves only for genuine emergencies, and a rescheduled block gets a new time the same day, not a vague "later." Three focused hours beat ten fragmented ones. Every time.
Ninety minutes, one outcome
How many power blocks
Build brief
When is your peak energy each day? Which two 90-minute windows will you protect as Power Blocks?
Saved
Batch the small stuff
Small tasks aren't the enemy — small tasks scattered across the day are. Batching gathers similar chores into one container so they cost one context-switch instead of ten. Email twice a day (late morning, late afternoon), never first thing. Invoices and bookkeeping in one Friday slot. Errands in one trip. Social media in one 20-minute window, if it earns one at all.
Meetings need their own rules, because they expand to fill every calendar: 25 minutes default instead of 30, 50 instead of 60 — the leftover minutes become your buffer. No agenda in the invite, no meeting. And keep one day meeting-free (your creation anchor day) so there's always somewhere for deep work to live.
The weekly template below is where all of this lands. Fill it once, then reuse it every Sunday with small edits. A designed week isn't rigid — it's a default. Defaults beat decisions.
One context-switch, not ten
Scattered vs. batched
| Task | Scattered | Batched |
|---|---|---|
| All day | Twice a day, never first thing | |
| Invoices | Whenever | One Friday slot |
| Meetings | 30 and 60 minutes | 25 and 50, with an agenda |
| Social media | Whenever | One 20-minute window, if it earns one |
WEEKLY PLANNING TEMPLATE Copy this into your notes app every Sunday. MY WEEKLY CAPACITY: ___ honest work hours this week WEEKLY OUTCOMES (2-3 finished results): 1. 2. 3. ANCHOR MAP: Mon (money + planning): Power block ___ | Afternoon: ___ Tue (creation): Power blocks ___ and ___ | No meetings Wed (creation): Power blocks ___ and ___ Thu (people): Calls/meetings between ___ and ___ Fri (review + close): Friday Reset at ___ | Admin batch BATCHES: Email: ___ and ___ daily | Invoices: Fri ___ | Errands: ___ MEETING-FREE DAY: ___ DEFAULT NOS THIS WEEK: 1. ___ 2. ___ 3. ___
Week template
Mon: ___ Tue: ___ Wed: ___ Thu: ___ Fri: ___ Protected blocks: ___
Priya is a freelance consultant. She does client calls scattered across Monday, Tuesday, and Wednesday, answers email all day, and tries to write proposals "in between." She's exhausted and behind. What's the single best structural fix?