More people are more likely to more regularly use their email.
Teams is too messy for generalised comms. Itās better for focused collaboration or specific areas of interest.
Viva Engage (nee Yammer) is better than Teams for comms. But while I think it could be of use to the org for bilateral comms, I donāt think implementation at this stage would be a positive move, because we already have email, SharePoint, and Teams, plus our own Bader Suite.
If Teams ever becomes more limited again, that would be the time for VE, but I donāt know if the license tiers would work that way.
You can have multiple accounts logged into outlook. Teams doesnāt offer that luxury and there are 3 other accounts that I use for work which would take precedence over cadets for Teams.
Plus, generally Teams is a steaming pile of nappy filler
I mean this is a personal thing that Iāve done but you can set up alerts on the RAFAC Announcements so it will send an email when anything new comes up on there.
Genuinely impressed. Didnāt know anything about it though until reading the post on here, so a send to all would be good as not sure how its been pushed out but Iāve not seen or heard anything about it in this Wing / Region.
Were you not on it when they accidentally turned Viva Engage on a number of years back?
For a few glorious moments, the organisation from top to bottom, and across the whole org, could talk to each other. And then there was panic. What if ACC was now INSIDE the walls!?!
And thus, it was switched back off.
Once weāve got the other platforms sorted, it could make a comeback. Its value lies in the crossovers with SharePoint, building communities of interest, whereas Teams should be communities of work.
SharePoint is on the Influence agenda to tidy up, we just need to ensure we have the support and resources of other departments, and especially need Digital team to be available and ready (but theyāre one of the indemand teams).
I remember it, yes. Issue was the uncontrolled nature of āreleaseā; people took advantage.
Undoubtedly itās a valuable tool if implemented correctly. Whether thereās appetite at the top to use it for its āOmniā properties I donāt know.
They seem very keen on the rigid and malfunctioning CoC communication method.
Fixing everything else and having everyone settled and majority utilising correctly first is definitely a must. Those left behindā¦ Now isnāt the time to be leaving people behind though.
@Wizzle moving the conversation about distribution back over here. (correct thread this time)
You are 100% being lied too if youāre being told it canāt be sent to all personal accounts. Just today Iāve received two emails regarding teams going down. I assume that went to all personal accounts, not just mine!
Yeah, slightly concerned about the number off different ways we are now potentially looking at to gain new information. Weve got:
Sharepoint announcements
IBNs
RAFAC Logs Updates
News letter
Email Announcements
Astra Newsletters
And probably more.
I think having all of those is fine, so long as there is a set system in place for how it works. For example, make it so that any time a(n) IBN/Logs Update/Astra Newsletter/Weekly Newsletter is added or updated, it automatically generates a Sharepoint announcements. Then, make sure that any Sharepoint announcement, including ones generated in the previous step, is then automatically emailed out to everyone.
My day job is working as a project manager in an organisational transformation & change capacity. I have to cut across the various silos within the organisation and ensure that everyone has the same understanding of the operational and project progresses. My experience in this area tells me that there must be just a single source of information for project members (CFAVs) in this case, else people act in good faith but entirely contrary to whatās needed of them. They do this because they went to another source of information that was either out of date or unauthorised.
The risk with having multiple info sources is that their info is collected from different areas by different people and usually with different results. A uniformed data set enables singular reporting and is best served by there being one point of info for CFAVs. The risk of this is demonstrated, in very mild terms, on this forum - as a small (and in this case, inconsequential for us) example, do the Tutors need to complete 140 or 150 hours of flying?
The quote of mine you have is only true with the caveat of there being a set system in place to centralise all of these different mediums. I suggested the announcements section, but it could be something else.
The other option of course is we look to move over to a similar system that DINs currently use. Standardise the letter/notification, but then categorise them. All you have to do is add another number to the IBNs.
DINs are currently formatted yyyyDINxx-zzz So 2023DIN08-006 is the 6th DIN of 2023 that sits in category 08. In the case of DINs, this is finance.
Do we just need to bring all these forms of communication into a single IBN/DIN format, but categorise it better? Then produce a weekly IBN/DIN digest, which is basically the newsletter?
Email is a very dated form of communication. Some companies have banned it for internal communications altogether. Mine merely discourages it and makes sending bulk emails difficult.
(Meanwhile the MOD is measuring productivity by number of emails sent, and taking full Office licenses away from people for using Teams and SharePoint properly and thereby reducing their email output: but thatās another battle.)
Maybe dated for organisations where you log onto their internal sites every day, but for a voluntary organisation email is easiest way to reach the masses, as long as it isnt done every 5 minutes and sometimes a simple prompt to the appropriate site where info is suffice. Not everyone has alerts set on sharepoint