There was a small communication failure incident: not telling me about a judgment call, in all the excitement, and when we didn't have comms as it was happening. (I have a few other stories about comms there, for another time) We addressed that oops constructively, as soon as it was realized. But that's not the problem I meant to highlight.
The problem I meant to highlight was that there can be surprising local resistance to something like UTC time, from people who aren't IT nerds. In this case, resistance to something we didn't even think they'd see during boot. And that prompts thinking about other ways there might be resistance, and what might happen due to resistance.
The factory manager and staff have their own way of doing things, and part of working well with them is figuring out what that is. Especially when you'll be thousands of miles away if problems come up. It turns out some things were intuitive, and some things weren't.
The people on the ground made a judgment call that this wasn't the thing to communicate harder or spend political capital on, and I support them making that call.
