Operator
Built for a moving date
The countdown asset says three days to go, and nobody in the building can tell you what day it is counting to.
Eid is expected in the last days of this month. Whether it arrives on one day or the next depends on an announcement made the evening before, and that announcement can leave Saudi Arabia and Egypt a day apart. Two markets, one plan, two different mornings.
Every tool in the stack wants a date. The email platform wants a send date. The media plan has a flight end date. The countdown was built with the number burned into the artwork, from a playbook written where next year's holidays are already printed.
So the same three things break every year, in the same order. The greeting lands a day early in one market and a day late in the other. The promotion expires at midnight while half the region is still fasting. The countdown says one day to go on the morning of the holiday, and it stays up, because it is a scheduled post and the only person who could take it down is sitting with her family.
The artwork was never the problem. It was hanging next to a switch with nobody standing at it.
The accounts that get through the week have three things in place before the last stretch. Two versions of everything, approved while approval is still cheap. A written rule saying which announcement each market follows, so the argument happens now rather than at midnight in a group chat. And somebody who has the access and is genuinely awake when the announcement comes, which is a rota, not a good intention.
In a fixed calendar the plan is a date. In a lunar month the plan is a decision about who flips the switch.