Best overlap: 10:00 AM to 6:00 PM in Melbourne is 8:00 AM to 4:00 PM in Manila.
Book within 10:00 AM to 6:00 PM Melbourne time (8:00 AM to 4:00 PM in Manila) and both teams will be at work. This is one of the easier pairings: 8 hours of shared time means flexible, low-stress scheduling. Daylight saving complicates things slightly: Melbourne observes it, Manila doesn't, so the difference flexes by an hour part of the year.
| Local time | 12am | 1am | 2am | 3am | 4am | 5am | 6am | 7am | 8am | 9am | 10am | 11am | 12pm | 1pm | 2pm | 3pm | 4pm | 5pm | 6pm | 7pm | 8pm | 9pm | 10pm | 11pm |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Melbourne Australia/Melbourne | ||||||||||||||||||||||||
Manila Asia/Manila |
Most distributed teams either keep the daily standup and exclude someone, or kill it and lose the rhythm. There is a better third option. Here is how to redesign the daily standup so it works across nine time zones. -
The Philippines sits 12 to 16 hours ahead of the US and never changes its clocks. Exact overlap windows for every US coast, the tomorrow problem, and a rotation rule that works for product and BPO teams. -
24/7 support sounds great until a P1 ticket falls into the gap between Manila signing off and Dublin signing on. Here is how to design a follow-the-sun support model that actually catches tickets at the boundary. -