Table of contents
Research context
This protocol asks how much of an offshore engineer's working week goes to meetings with the client and what those meetings displace. The unit is one engineer-week, with time classified into scheduled meetings, ad hoc calls, waiting for a meeting, and focused delivery work. The study measures the share of paid hours in each class. It does not judge whether a meeting was necessary.
A meeting count alone does not show the cost. Two thirty-minute calls can fragment a morning more than one hour-long review, because each interruption requires context to rebuild. The protocol should record the gaps around meetings as well as their duration. Fragmentation is part of the time-use picture.
Set the scope to one offshore team, one client, and one standard working week. Record the contractual hours, the time zone difference, and the meeting policy at the start. If the meeting policy changes during the window, keep the earlier definition for the full sample or analyze the change as a separate period. A new daily stand-up can look like more collaboration when it is only a different schedule.
Record whether the engineer was expected to prepare for the meeting. Preparation can take longer than the call and rarely appears on a calendar. Ask the engineer for an estimate of preparation time each day and record it as a separate class. A meeting that looks short may carry a hidden hour of work.
Define a meeting as a synchronous conversation with a client participant, whether scheduled or ad hoc. Define waiting time as the gap between a meeting's scheduled start and the resumption of focused work. Define focused delivery as time on a ticket, a review, or a test with no client call in progress. Each definition needs a positive and a boundary example.
Separate recurring meetings from one-off meetings. A daily stand-up is a standing cost that can be planned, while an ad hoc escalation is a disruption. Report the two categories separately and note the recurrence pattern. The owner can then decide whether the standing cost is earning its place.
Record the engineer, the week, the total paid hours, the minutes in each class, and the number of meetings. Add the meeting purpose, the number of attendees, and whether the engineer spoke or only listened. Keep the calendar export and the ticket activity together. A second reviewer should be able to reconstruct the week from the two sources.
Look at the distribution, not only the average. One engineer with a heavy client-facing role can raise the team average while the rest of the team has little meeting load. Report the median and the range by engineer role. A role-based view is more actionable than a single team number.
Practical application
Report the number of engineer-weeks, the median share of time in client meetings, the median share in ad hoc calls, and the median share in focused work. Show the counts by meeting purpose and by team. Present the share of meetings with more than five attendees and the share where the engineer had no speaking role. Use the same denominator for every rate.
Record the meeting owner and the decision each meeting is meant to produce. A meeting without a decision is a candidate for a written update. If a meeting produces decisions that are not recorded, the cost is likely to repeat. The owner field turns the time-use data into a governance question.
Inspect the weeks with the highest meeting load and describe what was displaced without naming the engineer. A cluster of status meetings may point to a reporting habit that could be replaced by a written update. A cluster of ad hoc calls may point to an unclear escalation path. Compare the result with the delivery output for the same weeks, but do not claim that one caused the other.
Ask the client which meetings they consider essential and which they attend out of habit. The answer may differ from the offshore team's assumption. Record both views and compare them with the time data. A short conversation can remove a recurring call without any policy change.
The record cannot show whether a meeting prevented a misunderstanding or whether the engineer was distracted. It can show only the time allocated and the calendar evidence. Meeting load is not proof of poor focus, because some collaboration is necessary. The protocol also cannot capture interruptions that were never added to a calendar.
Do not treat focused work as automatically productive. A long block of uninterrupted time can still be spent on the wrong task. Pair the time-use data with the delivery result for the same week, but describe the relationship carefully. The protocol measures allocation, not output.
Give the result to the delivery lead and the client owner and ask them to choose one observable change. The change might be a meeting budget, a written status update, a named decision channel, or a no-meeting block for delivery work. Record the owner, the effective date, and the measure that will show whether the change worked. Repeat the protocol with the same definitions and compare the same fields.
A useful additional view is the time from a meeting to the first related code or ticket update. A meeting that produces no follow-up may have been informational, which is not necessarily bad. A meeting that produces a decision but no recorded action is a gap. Report the follow-up rate for meetings that were meant to decide something.
Operating controls
Check the meeting load during a release week separately from a normal week. Release weeks often add coordination calls that do not reflect the steady state. Mixing them into one average hides the peak. Report both so the owner can plan for the release rhythm.
Close with one change to the meeting pattern and a date to re-measure. The change might be a written status update, a named decision channel, or a no-meeting block. Record the owner and the expected effect. Repeat the protocol with the same definitions and compare the same fields.
Record the start time of the engineer's first deep-work block and whether a meeting interrupted it. A week with the same meeting hours can feel very different if the calls are scattered across the morning. Report the number of days with a block of at least two uninterrupted hours. That field is often more useful to the team than the total meeting share.
Check whether the engineer is expected to attend meetings outside contractual hours. A late call that repeats every week is a schedule design problem, not a one-off. Record the after-hours minutes and whether time off in lieu was given. The owner should see the cost before it becomes a retention issue.
Ask the client which decisions could move to a written comment or a short recorded update. A decision that needs discussion should stay a meeting, while a status report can usually be written. Record the candidate meetings and the client's response. A small change in format can free a meaningful block of delivery time.
Compare the meeting load of engineers who joined recently with those who have been on the engagement for a year. A new engineer often attends more calls to learn context, while a senior engineer may attend more to make decisions. Report the groups separately so the average does not hide either pattern. The onboarding plan can then set an explicit meeting budget.
Ask whether the client records meetings and shares the notes with people who could not attend. A good record can replace attendance for some participants, but only if the decision and the owner are written down. Sample a few meeting notes and check for those fields. A note that summarizes discussion without decisions will not reduce the call load, so the note template should require a decision and an owner field.
Sources
Frequently asked questions
What should happen first?
Begin with a bounded ticket, approved access, explicit acceptance evidence, and a named reviewer.
Who approves production changes?
The client's technical owner keeps final merge and release authority.
Related research
How long does a new offshore engineer take to make a first production change?
How often does an offshore estimate change after refinement?
