Four Hours Of Overlap Is Plenty If You Spend It On The Right Things

Your team spans two or three time zones and you get about four hours where everybody is awake at once. Those four hours are currently full of standups, status calls and demos, and the actual hard conversations keep getting pushed to next week.

Four hours of overlap is plenty for a distributed team, as long as you spend it only on the things that genuinely need people talking at the same time: decisions, disagreements and the first draft of a plan. Everything else, including status, reviews and most demos, works better written down. The problem in most teams is not the size of the window. It is what is sitting in it.

The three things that need live time

Be strict about this list. If a meeting is not one of these, it should not be in the overlap.

• Decisions with real disagreement. When two people want different things and both have reasons, writing gets slow and tense. Ten minutes of talking beats two days of threads.
• The first draft of a plan. Going from nothing to a rough shape is genuinely faster out loud. Once there is a shape, refining it is a writing job.
• Anything with feelings in it. Feedback, a difficult client, someone who is unhappy. Text makes these worse, reliably.

That is the whole list. Notice what is not on it.

What to push out of the window

Status is the biggest offender. A daily standup where everyone says what they did is a report being read aloud. Write it down instead, at a fixed time, in a fixed place, in the same format each day.

Reviews are next. Code review, document review, design review: all better asynchronous, because the reviewer can take the time they need and the record survives.

Demos usually work as a recording. A five minute video that people watch when they are fresh beats a live demo that half the team attends at ten at night.

Information sharing is the third. If the purpose is that people should know a thing, the meeting is a slow way to tell them.

How to protect the window

Knowing what belongs in the overlap is easy. Keeping it clear is not, because meetings expand to fill available time. Where the window sits at all is a handoff question, and Kerala and Gulf teams have a working pattern for it.

A few rules that hold up:

• Default to no meeting. Anyone booking overlap time has to say which of the three categories it is. If they cannot, it goes in writing.
• Cap the total. Decide that no more than half the overlap is bookable. The rest is for working together on the same thing, or for nothing at all. Overlap is capacity like any other, and it thins quickly when half the team is part time.
• No status in the window, ever. This is the one exception you should not make. Once one status meeting is allowed back in, the rest follow.
• End early when the decision is made. A thirty minute slot that finishes in eleven minutes gives the time back to everybody.

Make the written half actually work

Pushing things out of the overlap only helps if the asynchronous side is good. Otherwise you have just made people wait longer.

Three things carry most of that load. A single place where the current state of work lives, so nobody has to ask. A habit of writing decisions down with the reasoning, not just the outcome. And clear ownership, so a written question has a named person to answer it rather than sitting in a channel.

This is where the shape of your tools matters. SicherOne keeps project records and HR records on one set of data, so who owns a task, who is on leave and what changed sit together rather than in three places. When somebody in the other time zone opens it at the start of their day, the answer to "what happened while I was asleep" is in one view rather than reconstructed from messages.

The overlap is also for being human

One caution. If you strip the overlap down to pure decision making, you get an efficient team that does not particularly like each other.

Leave some of it unstructured. A weekly half hour with no agenda. Time where people are simply available. This is not waste. Distributed teams lose the accidental conversation that offices provide for free, and something has to replace it. The loss is sharpest when half the team is on site and half is remote.

A test for next week

Look at every meeting in your overlap window and label each one: decision, first draft of a plan, feelings, or none of the above. Count the hours in the last category.

That number is how much of your scarcest resource you are currently spending on things that could have been written down.