Field note · 18 January 2026
Operating review cadence in Thailand
Imported operating-review rituals often assume a US Monday. That assumption collides with Thai public holidays, a Saturday–Sunday weekend that still includes a lot of marketplace volume, and regional teams whose “week” closes in Singapore time.
Close the week on Sunday night ICT
If your app takes money on Saturday, a Friday close lies to you. We ask teams to freeze the operating week at Sunday 23:59 Indochina Time and to timestamp the appendix with that freeze. Analysts who pull “last 7 days” from a tool default will silently drift. Write the freeze in the metric dictionary so it survives staff changes.
Hold the review on Thursday
Monday mornings in Bangkok are when people catch up on messages, not when they read a nine-page pack. Several of our alumni moved the operating review to Thursday afternoon. Pre-reads go out Wednesday. Exceptions that need a product change still have Friday to land a ticket before the weekend. The board pack, if one is due, can borrow the same spine without a Sunday scramble.
Holidays are not footnotes
Songkran, Chinese New Year, and the long early-December birthdays will wreck any week-on-week chart that pretends they are ordinary. Annotate them on the commercial bridge, not in a footnote on slide 19. If your comparison period includes a holiday and this year does not, say so in the spine paragraph. Boards in Thailand already know the calendar; they punish packs that pretend otherwise.
Remote SEA groups
If part of the team sits in Jakarta or Manila, publish the freeze timezone explicitly. “Week 32” without a timezone is how two honest dashboards disagree. We would rather you pick ICT and make Singapore adjust than run two dictionaries.
Cadence is unglamorous. It is also the difference between an operating review and a recurring status theatre. The Weekly Operating Reviews programme is mostly this: freeze, agenda, exception rules, and the holiday list taped to the dictionary.