RAFAC Communications - An improvement? 🤞

“The Astra Hub also contains its own newsletter”

Because what we need are even more decentralised comms, rather than a single version of the truth…

4 Likes

Yeah, slightly concerned about the number off different ways we are now potentially looking at to gain new information. Weve got:

  1. Sharepoint announcements
  2. IBNs
  3. RAFAC Logs Updates
  4. News letter
  5. Email Announcements
  6. 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.

I respectfully disagree.

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?

2 Likes

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?

Personally, that would be perfect for me. But I’m a nerd when it comes to data management & structures.

2 Likes

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

5 Likes

Precisely

Give me a digest email to my inbox once per week. Brief headlines and a few bullet points with a link to further information for each headline. Sack the rest of the emails off unless they’re critically urgent.

We could even have a Wing, Region and Corps digest and that would be entirely manageable. Although Region & Corps digests would probably not need to be any more frequent than monthly.

But at least this way the updates wouldn’t be so passive.

2 Likes

you’re describing Routine Orders which were a thing once upon a time…

edit: also there is a thread for comms RAFAC Communications - An improvement? 🤞

which was split from this thread - lets not have the topic return to it

1 Like

This is actually the approach my employer takes. All one-off comms must be through other means (SharePoint, employee portal, employee news app, etc.) and corporate comms, as the only people able to send emails to all, send a digest email with links.

Shooting Briefing Notes, Safety Updates…

I cant see the Astra Hub on sharepoint as a discreate site altho the link works!

Continuing the discussion from What Makes a GREAT NCO?:

This seemed the best place to post for @YO8102s benefit, details on how to join the MS Team are available here - Valuing our People (VoP)

1 Like

That seems to have worked. Thanks very much.

@Phantom details about VoP (Valuing our People) are 2 posts above from me, it’s a Teams setting led by RC(N)

Thank you very much, the fact it’s on Teams may be why I haven’t come across it. Haven’t seen Teams used on the Wing since lockdown ended.

It used to be in SharePoint…

SharePoint is, in very crude terms, the backend of Teams. So it might still be somewhere.

1 Like

Sooo, no weekly brief this week? They’ve managed every week since June, but looks like this weeks is missing, given they have so far been launched on a Friday?

I was wondering how long it would take