How to Actually Use a Calendar for Project Management (Without Losing Your Mind)

Most advice about planning projects on a calendar is either too rigid or too loose. Here's the approach I landed on after two years of mistakes.

I used to keep projects in one app and my calendar in another, and the result was that neither reflected reality.

The task app said I had 23 things to do this week. The calendar said I had 14 hours of free time. These two numbers implied I could do a task every 40 minutes, which was absurd for any task worth having.

For two years I tried to fix this from the task side — better estimation, better prioritization, tighter weekly reviews. What actually worked was approaching it from the calendar side. I stopped treating the calendar as a record of meetings and started treating it as the plan.

This post is the specific system I use, why each piece exists, and the mistakes I made before landing on it.

The core idea

Your calendar is the only document that has limits. A task list can have 500 items; a week has 40 useful hours. The mismatch between those numbers is the entire planning problem.

Most productivity systems ignore this and let the list grow. When the list gets overwhelming, you feel bad, then you "prioritize" — meaning you pick the three things you'll probably do and ignore the rest.

The alternative is to move tasks onto the calendar as time blocks. Not every task — that's called "time blocking," and I don't recommend it in its pure form. Something lighter:

Blocks for work that will take an hour or more. Lists for everything else.

A block for "draft the Q2 proposal" because it's 3 hours. A checkbox item for "reply to Mia about the logo" because it's 4 minutes. If you try to calendar the small stuff, you'll spend more time scheduling than doing. If you try to list the big stuff, the list lies about your capacity.

Step 1: separate the two types of tasks

Every Monday, I go through incoming tasks and split them:

Deep blocks: anything that needs continuous focus, usually over 45 minutes. "Write the report." "Research competitors." "Review design mocks."
Shallow items: small administrative or communication tasks. "Send the invoice." "Book the flight." "Follow up with Hana."

Deep blocks become calendar events. Shallow items stay in a plain checklist.

The trap here is calling a shallow task "deep" to make yourself feel important. I catch myself doing this. A useful heuristic: if the task wouldn't be on the calendar of a person whose job you'd want, it's shallow.

Step 2: stop planning on Monday morning

I used to plan the week at 9am Monday. This is the worst possible time.

By 9am Monday your brain is in reactive mode, inbox is loud, and the weekend has just ended. You will underestimate the week and overcommit.

Plan on Friday afternoon instead. The week is fading. You know what rolled over. You have emotional distance from next week because it still feels abstract. You'll make better choices about it.

If Friday doesn't work for you, Sunday evening is second best. Monday morning is last.

Step 3: calendar the blocks first, meetings second

Here's where most people mess up. They let meetings fill the calendar first, then try to squeeze deep work into the gaps. The gaps are always too small and poorly shaped.

Reverse the order. On Friday, place your 3-4 deep blocks for next week first. 2-hour chunks, ideally mornings. Then accept meetings only into the gaps.

This is hard socially. "I can do Tuesday 10am or Thursday 2pm" is a much less helpful answer than "I have six open slots this week." But the social cost is fake — people don't actually judge you for constraints when you're delivering work.

The rule I use: no meeting in the first 2 hours of the day, at least 2 days per week. Those mornings are for the work that actually moves the project.

Step 4: durations, honest ones

After a deep block finishes, write down how long it actually took. Not in the task tool — in the calendar event itself. Rename the event from "Draft proposal (2h)" to "Draft proposal (took 3h 20m)."

Do this for three weeks and you'll have calibrated estimates. Before I did this, I was off by 1.5x on average. After three weeks I was within 15% on familiar work. Still off on unfamiliar work, but at least I knew I was off.

This is the single highest-leverage habit in this entire post. If you skip everything else, do this.

Step 5: the mid-week repair

Something will always break the plan. A ticket escalates. A client wants a meeting. A family thing comes up.

By Wednesday, the Friday plan is usually 20-40% wrong. Don't rebuild the whole week — that's wasted work. Do a small repair:

Pull up the rest of the week
Ask: which blocks are still realistic?
Move or drop the ones that aren't
If you drop a block, decide right now where it goes (next week? deleted?)

The whole thing takes 10 minutes on Wednesday afternoon. It prevents the Friday feeling of "I didn't get anything done this week."

Step 6: tools

A specific opinionated setup that works:

Google Calendar for the actual blocks and meetings. It has the best sharing and the best notifications, which matters more than any fancy feature.
A task tool that reads/writes Google Calendar so your shallow tasks with due dates also show up in the calendar without double-entry. I use Sodot (bias noted — I build it). Other options: TickTick, Akiflow, Reclaim.
A plain-text weekly review doc. The calendar shows what happened; the doc is where you notice patterns over months.

Why having task tool → calendar sync matters: when I drag a task card from Monday to Wednesday, the calendar event should move too. And vice versa. Without this, you'll maintain two systems and eventually give up.

Sodot, Akiflow, and Reclaim all handle this. TickTick has it on a paid plan. Todoist has calendar subscription (one-way, read-only) which is not enough. Asana's calendar integration is surprisingly weak.

Step 7: the weekly review (quick version)

Fifteen minutes every Friday. Three questions:

What did I actually finish this week? (write the 3-5 real wins)
What rolled over, and why? (be honest — bad estimate? interruption? lost interest?)
What's the 1 thing next week must ship? (if you do nothing else, what's the one?)

That's it. No templates, no Notion pages with 14 subheadings. Three questions, written anywhere.

The questions matter more than the format. If you keep doing this, you'll notice patterns: the kind of task that always rolls over, the day of the week when you lose focus, the type of meeting that drains three hours for no reason.

Mistakes I made

A list of things I tried that did not work, so you can skip them:

Rigid time blocking the whole day. Too brittle. Doesn't survive a 20-minute interruption. I did this for two weeks and hated every day.
Separate tools for work and personal. You have one brain and one 24-hour day. Use one calendar.
Over-tagging in the task tool. I had 14 labels once. I used 3. The other 11 were planning overhead.
Quarterly OKRs imposed from above. Works in large orgs, doesn't for small teams or solos. The honest weekly review beats formal OKRs in my experience.
"Themed days" (Monday for meetings, Tuesday for deep work, etc.) Sounds nice in blog posts. Collapses the first time reality disagrees.

The one principle

If you take one thing from this post: track durations honestly, plan from the calendar, and keep the shallow list separate.

Everything else is tactical variation. You'll develop your own version. Mine took two years. Yours might take six months if you avoid my mistakes.

— JP

Last updated: April 15, 2026.