A developer's calendar: mornings with no meetings

Maker schedule and manager schedule are two incompatible ways of relating to time. A manager's calendar lives in hourly blocks, and a meeting sandwiched between meetings is no big deal. A developer's — or any maker's — calendar needs uninterrupted stretches, because ramping into a hard problem alone takes twenty to thirty minutes.

A typical scenario

Klára, a developer, has a free morning on her calendar, except for one thirty-minute meeting at 10:30. It looks harmless — but in reality she's reluctant to dive deep into a hard problem, knowing a notification will pull her out in an hour and a half. The result: she spends the morning skimming the surface of the task, and real work only starts after lunch, once she's sure she'll have peace.

When the team instead agrees on a clear meeting window — say, 1 to 3 in the afternoon — and keeps mornings free across the board, Klára knows nobody will interrupt her. She dives into the hard problem first thing in the morning and has it done by 2 p.m. — work that would otherwise have taken a whole day shattered by meetings.

How to do it

1. Agree on a shared meeting window as a team — say, 1:00 to 3:00 p.m. — and set the rule that meetings outside that window only happen in exceptional cases, scheduled well in advance.
2. The rest of the day, typically the morning, is reserved for focused work — writing code, solving hard problems, anything that needs uninterrupted stretches of time.
3. Block your morning slots directly on your calendar as Busy (or a similar status), so it's visible to colleagues who might otherwise auto-schedule a meeting by searching for an open slot.
4. Push standups or other short recurring meetings to the edge of the block — ideally right before lunch — instead of the middle of the morning, where they'd split a focused block into two unusable halves.
5. If a team-wide agreement doesn't happen right away, start with yourself — a blocked calendar works even individually, just with less certainty that others will respect it.

The best tools

• Time blocking directly on the calendar (Google Calendar, Outlook) — a basic, built-in feature; you just need to use it consistently.
• Shared team working hours (availability settings in Google Calendar or Outlook) — limits automatic meeting suggestions outside the agreed window.
• Focus mode in the operating system or a communication tool — mutes notifications for the duration of the block, so even chat can't break it.
• Meeting-scheduling tools (Calendly and similar), configured to offer slots only in the agreed window — keeps meetings from outside the team confined to the same hours.

What you get out of it

• Time: instead of a scattered morning where real work only fits into an hour, you get two to three hours of uninterrupted productivity a day.
• Better quality work: hard problems need a ramp-up — without interruptions you can go deeper, and solutions tend to be better.
• Less context switching: every pull-out from focused work costs tens of minutes to re-settle into, even if the interruption itself was brief.
• Predictability for the whole team: when everyone knows the shared meeting window, scheduling gets easier for everyone, not just you.

Pro tip

If a team-wide agreement can't be pushed through right away, try it for just two days a week first — it's an easier sell, and once the team sees the difference in output, extending it to the full week usually gets easy.