Key stats
- 3 measures: meeting hours, longest focus block, and decision share
- 2 time costs beyond the call: preparation and recovery
- 2 async formats: a written decision update and a short recorded demonstration
- 1 calendar change per monthly review
Key takeaways
- Count preparation and recovery time, not only the minutes spent in the call.
- Measure meeting load for engineers who build and review, not only for managers.
- Retire recurring series that produced no decision in the last month.
- Protect one long focus block per day and check whether it survives the week.
- Change one series at a time and compare the result with delivery measures.
Question and scope
This report examines meeting load as a coordination cost in distributed offshore delivery. The unit is one recurring meeting attended by an engineer, together with the preparation and recovery time it requires. The scope covers standups, planning sessions, reviews, and status calls shared by an offshore pod and a buyer. It excludes one-off workshops and incident bridges, which are judged by a different standard.
The question is whether a team can see the cost of its calendar before the cost shows up as slow delivery. A pod can look responsive while its engineers spend the quiet hours in calls. The report treats calendar time as a finite delivery resource rather than a neutral container for decisions. It looks for a review routine that protects focus without hiding coordination.
Define meeting load
Meeting load is not only the hours in calls. It includes the context switch before a call and the recovery time after one, which are larger when the meeting interrupts a block of technical work. A thirty-minute status call in the middle of a debugging session can cost far more than thirty minutes. Record the meeting length and the time of day together.
Load also depends on the role. A pod lead may attend eight calls a day and still protect the team's focus, while an engineer who attends two scattered calls loses the morning. Measure the load for the people who build and review, not only for the manager. The average across the group hides the engineer whose calendar is fragmented. Report the calendar by role so the review can protect the people who do the technical work.
Where the cost appears
The first cost is fragmented focus. An engineer with a free hour between calls will avoid starting a deep task, because the interruption is predictable. That behavior is rational and largely invisible in a timesheet. The work moves to the end of the day, which is often the buyer's night and the offshore team's late evening. Track the longest free block in the working day, because that block is where difficult work actually happens.
The second cost is preparation debt. A recurring meeting with no agenda still requires someone to gather status and context. When that work is done just before the call, it displaces review or testing. The meeting then reports progress rather than changing a decision, and the preparation cost buys nothing for the delivery. A meeting that needs an hour of preparation should show the decision that justified the hour.
Recurring meetings and agenda debt
Every recurring meeting should have a purpose, an owner, and a decision it supports. A meeting that only shares information can usually become a written update. Review the calendar quarterly and ask which decisions the series produced in the last month. A series with no decisions is agenda debt, even when attendance is high. Write the purpose in the calendar entry so a new attendee can decide whether the series is relevant.
Cut or shorten one series at a time and observe the effect. Removing a status call may reveal that the written update is missing a decision, which is useful information. Keep the meeting if it is the only place where a real negotiation happens. The review should record the decision, not just the new calendar. Give the change four weeks before judging it, because one week is usually a holiday or a release anomaly.
Async alternatives
A written update works when the information is stable and the audience can read it on its own schedule. Include the decision, the evidence, and the question that still needs an answer. A thread that only lists activity is not a substitute for a decision meeting. The format matters less than whether a reader can act without asking for context.
Use short recordings for demonstrations that would otherwise require a live screen share across time zones. Keep them under a few minutes and pair them with a written summary. The recording lets the offshore team watch during its own hours and preserves the demonstration for later review. A long recording with no summary simply moves the meeting cost to the viewer.
What to measure
Measure the number of meeting hours per engineer per week and the longest uninterrupted block in a typical day. Add the share of recurring meetings that produced a decision in the last month. The first two measures show the cost, and the third shows whether the cost buys coordination. Report the distribution rather than the team average, because fragmentation is uneven.
Track the meetings that cross the offshore team's evening or the buyer's early morning. Those calls carry a higher personal cost and deserve an explicit reason. Record whether attendance is required or optional, and whether a written alternative exists. The measure should support a scheduling decision, not a judgment about commitment. Rotate the inconvenient slot between both sides so the burden does not always fall on the same time zone.
A monthly review protocol
Review the recurring calendar once a month with the pod lead and one engineer. List each series, its owner, its decision output, and its attendee count. Mark the series that produced no decision and the ones that fall outside comfortable hours. Pick one series to shorten, convert, or cancel for the next month. Use the existing service review rather than creating another meeting to discuss meetings.
Record the change and its effect on the delivery measures you already track, such as review latency or completed tickets. Do not add a new meeting to review the meetings; use an existing service review. The protocol should take less than an hour and end with one calendar change. A monthly habit is more sustainable than a large annual cleanup.
Limits of the signal
Fewer meetings are not automatically better. A team with no shared time may miss the negotiation that prevents a costly misunderstanding. The measure should be read beside delivery time and rework, not as a target on its own. A calendar with protected focus and a few decisive calls is the goal, not an empty calendar. Protect a small number of live decisions and make the rest written, rather than removing all shared time.
The data is also easy to distort. An engineer may block focus time on the calendar while still answering chat, or attend a call without participating. Use the calendar as a starting point and ask the team what the blocks feel like. The review should combine the numbers with a short conversation about the week. Ask two engineers how the calendar felt during the week and compare that with the measured blocks.
From calendar to working agreement
Write the meeting expectations into the working agreement so they survive a change of pod lead. Name the protected focus block, the decision-oriented series, and the written format for status. State which calls are optional and which require attendance. A written expectation prevents the calendar from slowly returning to its previous shape. Include the review date so the list is treated as a living document rather than a rule carved in stone.
Review the agreement when the delivery model changes, such as a new time zone or a new service. Add the meetings that the change requires and remove the ones it makes redundant. Keep the list short enough that an engineer can read it in a minute. The calendar should follow the work, not the other way around. Assign the review to the pod lead and put the date in the service calendar.
Reporting the result
Report the meeting hours, the longest focus block, and the decision share for recurring series. Add the one calendar change made during the month and its observed effect. Keep the per-person detail private and report the distribution in ranges. The buyer needs to see the coordination cost without turning the report into an attendance audit. Keep individual calendars out of the buyer report and show ranges that protect the team.
Review the result at the next service meeting and decide whether to keep the change. If the delivery measures improved, document the new expectation in the working agreement. If not, restore the meeting or try a different format. The record of these small experiments is more useful than a one-time instruction to meet less. Record the change in the working agreement so the next pod inherits the lesson instead of repeating it.
Evidence table
| Signal | What to inspect | Owner |
|---|---|---|
| Outcome | Acceptance evidence for the bounded task | Task reviewer |
| Control | Access, test, and approval boundary | Internal owner |
| Handoff | Open risks and next decision | Next owner |
Good distributed work is observable at the handoff: the result, evidence, limitations, and next owner are explicit.
Frequently asked questions
Is a daily standup always worth the cost?
Only if it changes a decision or unblocks work. If it is a status round, a written update usually serves the same purpose without fragmenting the morning.
How do we include the buyer without late-night calls?
Use a written decision update, a short recording, and a smaller number of live calls at a time that rotates fairly. Record which decisions actually need live discussion.
What is a healthy amount of meeting time?
There is no universal number. Track the focus block and the decision output, then reduce the series that consume time without producing a decision.
