Should we align the team's hours with the client's?

Partly, and the important thing is to decide which side carries the gap rather than letting it distribute by default. Total alignment transfers the whole constraint onto the local team and is paid for in turnover. A defined, protected shared window with the rest of the day organised around autonomy costs less and lasts longer.

How do you keep cohesion when part of the team works late?

Not by adding social occasions outside working hours, which fall precisely on the people already most constrained. What works is placing team rituals inside the shared local working day, and never making important information depend on an informal moment part of the team cannot attend.

Does remote working solve the problem?

It makes it bearable and worsens it at the same time. Working from home removes the late-evening commute, which genuinely matters. But it also removes the last marker separating the working day from the rest, and the stretched days become invisible to the manager. The two subjects have to be handled together.

Managing a team on a shifted schedule | ABP Consulting Maurice

Q: How do you stop meetings swallowing the shared window?

By treating the window as a scarce resource and stating explicitly what has a right to it. One simple, effective rule: put in it only what requires a real-time exchange — a decision, a trade-off, a complex explanation. Anything that can be written is written, and read during the hours the other team is not there.

A team in Ébène starts at ten because its European client starts at eight. Another finishes at eleven at night because it serves a US time zone. A third lives on two windows, India in the morning and Europe in the afternoon, which leaves two hours in the middle when work can actually happen.

That is ordinary life across a substantial part of Mauritian service activity, and most managers treat it as an organisational constraint. It is not one. It is a decision constraint, and that shift changes everything about what needs doing.

What the gap actually costs

Fatigue is visible, so it gets talked about. It is not the main cost.

The main cost is waiting. In a team that shares its hours with its client, a question is asked and settled within the minute. In a team whose shared window is three hours, a question arriving after the window stays open until the next day. The work does not stop: it proceeds meanwhile, on an assumption, and sometimes has to be redone.

Multiply that by the number of questions in an ordinary day and you have the real cost of the gap. It appears in no dashboard, because it takes the form of work redone rather than work not done.

The first decision is not a rota

Hence the most useful conclusion in the whole subject: before building a schedule, a manager working across time zones has to draw up a list.

Which decisions get taken without them, and without the client?

The exercise is uncomfortable because it forces you to name thresholds: up to what value, up to what deviation from the specification, up to what consequence for the end client. It is uncomfortable too because it exposes that some decisions have always travelled upwards for no real reason, out of habit.

The four levels of delegation worked on in the manager-leader toolkit are the instrument for building that list.

But there is no alternative. A team without that list waits, and waiting is exactly what the gap makes expensive. A team that has it works while the other sleeps, which is the only genuine advantage of the arrangement.

Protecting the shared window

Overlapping hours have an unfortunate property: they fill themselves. Since it is the one moment when everybody is available, every meeting settles there, and the window becomes the worst time of day to produce anything.

The rule that works is a simple filter. Put in it only what requires a real-time exchange: a decision to be taken together, a trade-off, a complex explanation where the questions arrive as you go. Everything else — progress, information, sign-off on a compliant deliverable — is written, and read during the hours the other team is not there.

The corollary is worth saying: the written record is the most profitable management tool a time-shifted team has. It works through the other side’s night. A manager who spends fifteen minutes at the end of the local day writing what was decided and what is waiting on an answer buys a full cycle of advance.

Who carries the gap

Here is where teams degrade quietly. The burden of a shifted schedule never distributes itself: it falls on the people who agree, and the people who agree are usually the most committed, the youngest, or those with the least means to refuse.

After a year, two or three people are covering every late meeting. They do not complain — that is the mechanism itself — and then they leave.

Three rules are enough to prevent it, provided they are written down. An explicit rotation of the uncomfortable slots. A ceiling: nobody takes more than a set number of out-of-hours meetings per month. And time back that does not have to be asked for, because what has to be asked for is not asked for by the people who need it most.

The warning sign

There is only one to watch, and it is easy to miss: the late meeting that becomes normal without ever having been decided.

It starts as a justified exception — a launch, a crisis, an important client. Then the slot stays in the calendar because it is convenient for the other side. Six months later it is part of the job, with no conversation having taken place and with it appearing in nobody’s job description.

Where the team is multilingual as well, the two subjects compound and are best handled together.

The question to ask every three months is therefore precise: which out-of-hours meetings exist today, and which of them was ever actually decided? The gap between the two lists is the measure of the drift.

When the client sets your day: managing on a shifted schedule