Communication Is Not Coordination
Many astronomical observatories (both pros and amateurs) coordinate their nightly operations through tools like Slack, Discord, or long email threads. These tools are convenient and familiar, especially for distributed teams. They lower the barrier to communication and make it easy to keep everyone loosely aligned. The difficulty is not that these tools are inadequate. It is that they are structurally detached from the systems they are meant to coordinate.
A telescope slews. An instrument warms up. A user takes over a camera. A sequence is paused because of weather. The operational state evolves inside control software, while the discussion about that state unfolds elsewhere — in chat messages or inboxes.
Over time, the link between communication and operation becomes implicit. Someone writes “camera ready.” Someone else answers “starting sequence.” The system itself continues independently. The coherence of the whole depends on people remembering what was said, interpreting it correctly, and translating it back into actions.
Email often becomes the official memory of these decisions. Chat holds the real-time flow. The control system holds the technical state. None of them contains the complete picture.
When Operations Scale
To compensate, teams create small bridges. They paste logs into Slack. They send screenshots of control panels. They write nightly summaries. Sometimes they build small bots to mirror partial information from the control layer into the communication layer.
These hooks help, but they are always incomplete and require maintenance. They age. They break. They drift out of sync.
For small, stable teams, this separation can work reasonably well. People know each other. They share context. They notice inconsistencies early. But as operations become more distributed — remote users, shared facilities, multiple institutions — the reliance on informal synchronization becomes fragile.The question is not whether Slack or email are good tools. It is whether communication about operations should live outside the operational system itself.
What changes when coordination is treated as part of the infrastructure, rather than something that happens around it?
No responses yet