A week is not five identical days
Weekly planning fails when you copy Monday's optimism onto Tuesday through Friday without counting meetings, recovery, or the admin that never fits on a sticky note. A finishable week has a small set of outcomes, honest meeting capacity, optional theme days, buffers for slip, and a Friday shutdown that makes Monday start from writing, not memory.
Daily rhythm lives in structure a remote workday. Focus at home: protect focus when you work from home. Block math: Pomodoro Planner.
Step 1: Count real capacity
Before you assign work, subtract what the calendar already spent.
| Input | How to estimate |
|---|---|
| Fixed meetings | Count hours from the calendar, include prep |
| Message debt | 30 to 60 minutes per day if clients or on-call |
| Admin | Invoicing, expenses, scheduling (often Friday) |
| Deep work ceiling | Rarely more than 3 to 4 hours per day on meeting-heavy weeks |
Rule of thumb: If more than half the week is in meetings, plan one Primary outcome for the whole week, not five.
Use the Pomodoro Planner to see how many focus blocks remain after you block meetings on the clock.
Step 2: Pick one to three weekly outcomes
Weekly outcomes are evidence, not intentions.
| Good weekly outcome | Bad weekly outcome |
|---|---|
| "Staging deploy of feature X with demo script" | "Work on feature X" |
| "Client proposal sent with pricing options" | "Catch up on email" |
| "Close three tickets from the release checklist" | "Be productive" |
Write each outcome so someone else could verify it Friday afternoon. If verification is fuzzy, shrink the outcome until it is testable.
Step 3: Theme days (optional but powerful)
Theme days reduce switching cost. They are not rigid law. They are a default you break on purpose.
| Day | Theme | Typical work |
|---|---|---|
| Monday | Plan + start | Weekly plan, first deep block on Primary |
| Tuesday | Deep | Primary only in the morning |
| Wednesday | Collide | Meetings, collaboration, reviews |
| Thursday | Deep | Primary or secondary |
| Friday | Close | Ship, admin, shutdown, Monday first move |
If Wednesday is always meeting-heavy, protect Tuesday and Thursday mornings for deep work and stop pretending Monday will carry the week alone.
Step 4: Buffers for slip
Plans break. Buffers are empty-ish blocks you do not fill until Thursday.
| Buffer type | Size | Use |
|---|---|---|
| Daily | 30 to 45 minutes | Overrun, urgent client reply |
| Weekly | Half of Friday afternoon | Finish Primary or honest wrap-up |
| Emotional | One "salvage" block midweek | Replan after a bad morning |
If buffers stay empty, bank them as early finish or learning, not as permission to add scope midweek.
Step 5: Daily five-line plan still matters
The week sets direction; each morning sets the day. Before the first focus block:
- Primary: today's slice of the weekly outcome
- Secondary: if Primary finishes early
- If time: optional
- Waiting on: others or systems
- First move: smallest physical action
Template: daily work plan.
Worked week example
Person: Solo contractor, mixed client delivery and product work.
Weekly outcomes:
- Ship revised onboarding copy to staging (Client A)
- Send fixed-fee quote for Q4 project (Client B)
- Close personal admin: Q3 expenses filed
Calendar reality: Client A call Tuesday 10:00, internal review Wednesday 14:00, dentist Thursday 11:00.
| Day | Plan |
|---|---|
| Monday | AM: draft onboarding sections 1–2 (Primary). PM: message sweep + weekly plan posted to client channel |
| Tuesday | AM: finish section 3 before call. Call 10:00. PM: apply call notes, one 40m block |
| Wednesday | AM: deep polish + paste to staging. PM: review meeting; buffer 30m after |
| Thursday | AM: dentist. PM: Client B quote outline (Secondary becomes Primary for the day) |
| Friday | AM: finalize quote + send. PM: expenses, weekly Done/Open/Blocked, Monday first move |
Friday shutdown (ten minutes):
Done this week
- Onboarding copy on staging (link); Client B quote sent
Open
- Client A feedback expected Monday
Blocked
- None
Monday first move
- Pull Client A comments from shared doc; list edits as ticketsStatus format detail: end-of-day status update.
Meeting budget for the week
| If you run the team | If you are IC |
|---|---|
| Cap recurring syncs at one short slot | Decline optional meetings without agenda |
| Require written pre-read | Batch 1:1s on one day if possible |
| Replace one standing meeting with async for two weeks | Protect two mornings as meeting-free |
Async defaults for distributed teams: async communication for distributed teams.
When the week goes wrong (midweek replan)
Wednesday is when optimistic Monday plans meet reality. Do not wait for Friday to admit slip.
- Cross out outcomes that are no longer possible without heroics
- Pick one salvage outcome for the rest of the week
- Move waiting-on items to Blocked with an owner, or delete them
- Protect one deep block in the next 48 hours for the salvage outcome
- Tell stakeholders in writing if a client deadline moved
An honest midweek note beats a heroic weekend. Clients remember reliability more than late-night effort.
| Signal | Response |
|---|---|
| Primary untouched by Wednesday noon | Halve scope or renegotiate date today |
| Calendar gained three "urgent" meetings | Drop If-time work; keep one deep morning |
| Energy crash after bad sleep | Two short blocks + admin, not a fantasy catch-up list |
| Waiting-on cleared early | Promote Secondary, do not invent busywork |
Weekly review (fifteen minutes, Friday)
- Did the weekly outcomes finish or shrink honestly?
- Which meetings earned their time?
- Where did buffers save the week?
- What waiting items never got done (delete or schedule)?
If you finished zero weekly outcomes but felt busy, your tasks were still topics. Rename them until they are verifiable.
Tradeoffs
| Pressure | Cut first | Protect |
|---|---|---|
| New midweek "urgent" | Optional tasks | Weekly Primary |
| Perfect theme days | Rigidity | Two deep mornings |
| Client scope creep | Silent yes | Renegotiate deadline in writing |
| Weekend catch-up habit | Extra blocks Sunday | Friday buffer + smaller Primary |
What to refuse
- Five big outcomes on a ten-meeting week
- Planning the week without looking at the calendar first
- Ending Friday without Monday's first move written
- Treating every day as interchangeable
- Skipping shutdown because "you will remember"
A finishable week is a small promise kept. Count capacity, name verifiable outcomes, theme when it helps, keep buffers empty on purpose, and close Friday so Monday starts from a note, not from dread.