Three Deep Days, Two Meeting Days: the calendar rule that saved my mornings
How I protected focused work by consolidating meetings into two days a week—how I set it up, the pushback I faced in Indian companies, and the tradeoffs that stuck.
Written by: Rohan Deshpande
It started on a Tuesday at 9:05. My calendar was full. My inbox had eight threads marked “urgent.” I had promised a rewrite of a critical backend job that afternoon. By 11:30 I’d switched tabs eleven times, answered a meeting chat, and written 50 lines of code that needed a complete rework. I left at 8 pm with nothing merged and a headache.
That was the last week I treated every weekday as equal.
I now split my workweek into three “deep days” and two “meeting days.” Monday–Wednesday are for focus; Thursday–Friday are for sync, reviews, and meetings. It’s simple on paper. In practice I had to renegotiate calendars, teach teammates a small ritual, and accept real tradeoffs. It’s the clearest productivity change I’ve kept for over a year.
Why three deep days I tried single deep blocks before. They helped, but one day wasn’t enough: interruptions on other days bled into the deep day, context switched, and progress stalled. Full-week meeting-free experiments failed when client or cross‑team syncs moved to the only quiet day left.
Three consecutive days buy two things that matter for engineering work:
- Momentum. Complex features need uninterrupted stretches of 90–180 minutes across multiple days. Monday–Wednesday gives me that continuity.
- Predictability. Teammates know when I’ll be available for quick clarifications (Thursday–Friday), so fewer ad‑hoc pings happen midweek.
How I made it real (the exact rules I use) I don’t “try harder” — I change the defaults and make work follow the rule.
- Block the calendar, visibly I create recurring events:
- “Deep Work (Busy)” Mon–Wed 09:00–13:00 and 14:00–17:00.
- “DM Hours” Mon–Wed 17:00–18:00. Calendar invites are public to my org. I mark them as Busy, not Free. This means meeting invites get auto-placed to Thursday/Friday or bounced back with a suggested time.
-
An explicit async ritual At 08:45 on deep days I post a one‑line “today’s focus” in our team Slack thread: what I’ll ship before DM hours. It makes me accountable and reduces “ping me if…” messages. If I need a review, I request it by noon; otherwise, I wait.
-
Stop-the-bleed rules for teammates
- Urgent? Use “ESCALATE” in the channel title and ping only one lead.
- Need a decision that blocks me? Book 15 minutes on Thursdays; I’ll prioritize it.
- Technical enablers
- I consolidate CI-heavy tasks to run overnight or on Thursday so my deep work stays local.
- For cross-timezone meetings (we have US overlaps), we reserve one slot on Friday mornings and an asynchronous recording policy for anyone who can’t attend.
The first month felt bureaucratic. People asked for exceptions. I gave many. Then I handed out exactly two exceptions per week to myself. That cap forced judgment. If it truly mattered, I used an exception; otherwise I absorbed the delay and continued my deep block.
What actually improved
- I ship medium-sized features faster. The rewrite that used to take two weeks of interrupted afternoons now ships in seven focused days.
- My afternoons stopped being a slugfest. I end deep days with a clear handoff note and fewer half-finished PRs.
- Meetings got better. When you cluster meetings, they’re shorter and more to-the-point — you only bring what’s actionable that day.
Real constraint I hit: Indian meeting culture and “the urgent” This is not magic. In Indian companies where managers (or clients) expect immediate availability, the rule required explicit negotiation. Two concrete failures taught me a lot:
-
The first quarter I tried this at a mid-sized Bengaluru startup, I lost a product demo because a cross-team meeting was scheduled for Wednesday morning by a manager who assumed everyone was “available.” My calendar blocked it, but they assumed the calendar was “advice.” I escalated. It led to a short, awkward 1:1 with the manager where I explained the structure and why it mattered. It fixed the problem for my team but cost political capital.
-
During our one on‑call month, deep days evaporated. Critical incident handling forced context switches and the rule felt fragile. I’d bank deep time before on-call weeks and accept a productivity drop during those rotations.
Those failures changed how I run the rule: don’t demand, explain. I run a 10‑minute onboarding for new teammates and managers explaining why I block my calendar and how to work with it. I also reserve one “flex slot” each week for truly emergent cross-team discussions.
Tradeoffs I accepted
- You’ll lose some responsiveness. I used to answer every small request in 10 minutes. Now some things take 48 hours.
- Some meetings move to Friday afternoons — which can feel like a sprint finish. I learned to keep Fridays low-energy: no heads-down coding, only reviews, demos, and planning.
- On-call and client-facing roles may need a modified version. This rule works best for product engineers who own features and need extended focus.
A small, testable way to try it tomorrow Block two consecutive 3-hour slots tomorrow morning. Tell your team in one short message what you’re protecting and where to put urgent flags. Let one meeting get auto-rescheduled. See how many interruptions you prevent.
What I walked away with I stopped treating focus like a moral victory and started treating it as a shared calendar contract. Deep work is quieter when you make it visible and give people a clear alternative for urgent asks. It didn’t remove meetings — it made them less destructive. It cost a little upfront politicking in Indian orgs, but the payoff was predictable stretches of real progress.