In a particular work group this morning, a detailed email was sent out instructing team members on how to handle complicated work inquiries. There were bullet points and seven different email points to use. This was done, allegedly to improve efficiency. That afternoon, with no notice at all, the name of the Teams Channel used for the entire group to communicate was changed without notice. Staff searched emails to find the notice. There was none. Finally, a team member posted the obvious question. Why? What happened? Had a notice been missed? A senior leader posted back, "No, there was no notice." Nowadays, it's easy to incite a mild panic. WTF? About an hour later, the senior leader posted again, the name change was to bring it into alliance with other name changes. And yet, no one showed the team the respect that a brief email would have provided. Employees remain an afterthought.
2 replies (most recent on top)
Posts must be vague for obvious reasons. Consider what you don't know and cannot be revealed. Some groups, perhaps not yours, have experienced significant, multiple changes in very short order. In hindsight, some have learned that signals of these changes were there when strung together. This group's status is fragile for many reasons, so more vulnerable to what might seem like nothing to you. If you are outside of FIS, it might seem really odd. But, it ain't. If you have stability of any kind, value it. It can change without warning regardless of where you are.
You really hit the nail on the head with the mild panic part, but not for the reason you think. You really need a notice for a Teams channel name change? And it's really that scary and confusing that it makes you worry about your job stability and stops you from simply asking someone about why it happened? Unless I'm not understanding something here? (The vagueness of the post definitely doesn't help)