The calendar lie for engineers
A ninety-minute slot on the calendar is not ninety minutes of lost coding. It is ninety minutes plus the shallow hour before it, when you avoid starting anything that might be interrupted, plus the rebuild after, when you reopen the branch and reread your own notes.
Teams measure meeting load by scheduled time. Throughput dies in the unscheduled margins around those blocks.
Example: three calls and a "free" afternoon
Example: Standup at 10:00, design review at 11:30, planning at 14:00. The afternoon looks open.
In practice, 09:00-09:45 is too short to enter debug mode. 11:00-11:25 is spent preparing screenshots for review. 13:00-13:45 is lunch plus Slack catch-up from the morning threads. After planning at 15:00, energy is low and the branch from yesterday feels stale.
The calendar recorded three hours of meetings. The day lost one meaningful composition window.
Depth work needs contiguous time, not fragments
Feature work and debugging share a long setup cost: branch, tests, mental model, reproduce steps. Fragments produce motion - comments, small fixes, ticket updates - without integration.
That motion reads as progress in standup. It is often busy work on the second ledger: nothing a reviewer can merge end-to-end.
Batch coordination like you batch deploys
Treat reviews, standups, and stakeholder syncs as a coordination cluster when you can. Put them adjacent with a shared prep window, then defend a contiguous block on the other side of the day.
When clustering is impossible, name the day type honestly: coordination day, not feature day. Plan one small finishable slice instead of a heroic feature.
Async-first decisions reduce reload tax
Decisions captured in tickets survive the meeting. Decisions that exist only in spoken memory force another meeting when half the team was not in the room.
Climb the async ladder from treat meetings as a last resort before booking engineering time.
Managers: throughput is a system metric
Counting meetings attended rewards availability. Counting merged, integrated outcomes rewards throughput.
If your team is "busy" in calls and slow in delivery, the fix is fewer calls with better residue, not longer evenings.
Green CI is not the same as finished
Passing checks on a branch still in review is not throughput. It is a checkpoint. See green CI is not finished work.
Protect edges for the team, not only for yourself
Team norms matter: no-meeting mornings, written briefs required before live time, default recording for optional attendees in other zones.
Individual calendar blocks fail when culture treats every ping as urgent.
Engineering throughput is fragile. Meetings are expensive inventory. Spend them where live conversation is the only path, and protect the contiguous hours that actually ship software.
Example: prep hour invisible
Example: Design review at 11:00; engineer gathers screenshots and data from 10:00-10:45. Calendar shows one meeting; cost was meeting plus prep plus aborted morning start.
No-meeting block team norm
Team agrees two mornings without meetings; violations require async brief first. Norm belongs in onboarding doc, not oral tradition.
Async brief before live time
Require written brief for meetings over thirty minutes: decision needed, options, links. Decline if brief missing - see when a remote team needs a meeting.
Example: recurring sync without agenda
Example: Weekly sync becomes status round robin that could be a doc. Cancel or replace with written update until agenda exists.
Cost language for leadership
Express cost as person-hours times attendee count compared to feature estimate. Leaders understand tradeoffs in person-hours language.
Protect tomorrow morning
Late evening meetings for one zone steal next-day depth for another. Rotate bad slots across regions when global.
Review and merge still work
After meeting-heavy days, schedule integration window - plan developer day with review and feature work - instead of pretending meetings were the work.
Tradeoff: inclusion vs depth
Recordings help optional attendees; they do not replace documented decisions. Absent engineers need written outcomes, not hour-long replay guilt.
Meetings buy conversation; throughput requires integration. Spend meeting inventory sparingly and recover contiguous time deliberately.
Example: standup that becomes design meeting
Example: Fifteen-minute standup expands into forty-minute whiteboard for whole team. Move design questions to ticket and scheduled workshop; protect standup boundary.
Post-meeting residue rule
No meeting ends without owner and next step in writing within one hour - otherwise the meeting tax repeats tomorrow.
Recovery block on calendar
After three hours of calls, book thirty minutes labeled recovery before starting feature work; prevents fake depth in the afternoon.
Tradeoff: social bonding
Some meetings build trust; batch social time separately from decision meetings so neither steals composition windows by accident.
Link context switching
Each meeting is a mode switch with reload cost - see real cost of context switching when measuring true calendar damage.
Manager metric
Track merged outcomes per engineer per week alongside meeting hours; divergence signals meeting load problem, not laziness.
Engineering organizations that protect contiguous maker time ship more with fewer heroics. Meetings are a tool; throughput is the outcome worth measuring.
Example: calendar tetris
Example: A ninety-minute hole between meetings looks usable for coding. In practice it is prep for the next call, Slack from the last call, and insufficient time to reload debug context. Honest planning marks that hole as coordination residue, not feature capacity.
Decision rules before accepting invites
- Is the decision already documented elsewhere?
- Can async comments resolve it within one business day?
- Does this require real-time whiteboard or is that habit?
- Who is optional versus required?
If 1 and 2 are yes, decline with link to ticket. If 3 is no, propose written options first.
Example: weekly leadership sync
Example: Leadership sync repeats status available in project board. Engineer attendance costs four person-hours weekly with zero new decisions. Replace with written summary; keep live meeting only when escalation list is non-empty.
Protect the team edge, not only your edge
Individual focus blocks fail when teammates ping through them. Team norms - no-meeting mornings, brief-required invites - matter more than personal calendar color.
Finish line after meeting-heavy days
End with integration checklist: open PRs reviewed, merge queue addressed, tomorrow's first action written. Meetings without residue become repeat meetings; see when a remote team needs a meeting for tighter criteria.
Throughput recovers when meetings produce artifacts and contiguous maker time is defended as deliberately as production uptime.
Closing rule
If a meeting did not change a ticket, document, or calendar, it was optional social time - schedule it honestly next time instead of taxing maker hours by surprise.