How an APAC-EU Engineering Team Killed the Morning Catchup Meeting (Composite)

This post describes a hypothetical scenario based on common patterns we observe in distributed engineering teams. It is not a specific customer. Details have been generalized, and the outcomes are framed in directional terms rather than as precise measurements.

The team in this composite is a 25-engineer infrastructure team split between Singapore and Berlin — twelve engineers in Singapore, thirteen in Berlin, a six-to-seven-hour offset depending on the season. At the start of the scenario, the team had a daily 4pm Singapore / 10am Berlin catchup meeting, which existed because the Berlin engineers needed to know what had happened in Singapore overnight, and Singapore engineers needed to brief Berlin before they signed off.

The structural problem

The meeting was working — barely. Singapore engineers were tired at 4pm; Berlin engineers were not yet fully online at 10am. The meeting drifted to 45 minutes most days. The record of what was said evaporated within the hour, which meant a Berlin engineer who needed the context the next morning had to either watch a recording or ping a Singapore engineer who had already gone offline.

The team had been told repeatedly to "fix async" and had tried twice — once with a Slack channel that nobody maintained after the first week, and once with a Notion page that nobody opened. The pattern was that the catchup meeting absorbed the urgency, and there was no consequence for not also maintaining the written layer.

The intervention

The team rolled out structured wraps at end-of-shift for both regions. Singapore engineers wrote wraps before signing off. Berlin engineers read the Singapore wraps as part of their morning ramp. The Representative answered questions during the Berlin morning when a wrap was unclear or when context was missing. The catchup meeting was kept for two weeks as a safety net, then trimmed to twice a week, then to once a week, then retired.

The directional results

Three months after rollout, the team reported the following directional outcomes. The morning catchup meeting was gone. The Berlin engineers' morning ramp time dropped from roughly 40 minutes (reading scrollback, scheduling clarifying calls during the overlap) to under 15 minutes (reading wraps, querying the Representative). The Singapore engineers stopped staying online past their normal end-of-shift to attend the meeting, recovering an hour per day on average. The team kept a weekly one-hour all-hands during the overlap for higher-bandwidth conversation — strategy, retros, planning — but the daily catchup was retired.

The friction the team did not anticipate was the senior-engineer holdouts. Two senior Singapore engineers had been the highest-bandwidth speakers in the catchup meeting; they were used to delivering context verbally and had to learn to write it instead. They took about two months to adopt the wrap pattern reliably. The team's lead made wrap-writing an explicit performance expectation, which helped.

What the team would do differently

The retrospective surfaced three lessons. First, the catchup meeting absorbed the urgency and was the reason previous async attempts had failed — to make async stick, the synchronous fallback had to be reduced, not just supplemented. Second, the Berlin engineers needed an explicit habit of querying the Representative; the team built that into the start-of-shift ritual. Third, the weekly all-hands during the overlap is worth keeping; killing every synchronous meeting is over-correction, not optimization.

Frequently asked questions

Is this a real team?

No. This is a composite based on common patterns we observe in APAC-EU engineering teams. The structural pattern — narrow overlap, daily catchup as a load-bearing failure mode, async only sticks when the synchronous fallback is deliberately reduced — is what we see consistently.

Does this work for other long-offset geometries?

Yes, the same pattern applies to APAC-US West Coast, APAC-EU East, and other six-to-ten-hour offsets. The geometry detail matters less than the principle: the asynchronous layer has to be where the work happens, not a parallel record.

What about the weekly all-hands? Why keep it?

Some conversations are genuinely higher-bandwidth when synchronous — strategy, retros, planning conversations that benefit from real-time exchange. The teams that try to push all of these into async tend to over-correct and end up with worse decisions. A single weekly synchronous meeting in the overlap is the typical resting state.