Newsletters

[tmcd35]

Having had one argument too many with prima donna teachers I've decided to create a monthly newsletter that explains in laymans terms what it is we actually do for them. I think I've got the first issue fleshed out - nearly 3 pages and half a days work. Just wondering if anyone else does this, and if you do what kind of content you put in there?

[Danp]

In a word, no, you are mad for even starting it!

[Edu-IT]

No. Got too much to do without explaining to everyone else what it is we're doing.

[tmcd35]

@Danp, care to expand on that?

[X-13]

We don't... But I doubt a newsletter will help.

 

You need SMT to tell certain teachers to STFU.

[Danp]

@Danp, care to expand on that?

 

Yes, basically, I would not have the time or know how to explain to teachers exactly what we do during the day. Also, I don't need to justify my time to teachers, that sounds harsher than it's meant to but I would only explain my day to my line manager or another member of SLT

[tmcd35]

@X-13, but is half the battle them not understanding what we are paid to do? If we told them what important changes are coming up and how it might effect them. If we gave them some (highly simplified) insight into the complexities of our work maybe the SMT needn't get involved in these petty squabbles?

[CamelMan]

When I first started here I setup a monthly email IT newsletter - basically outlining what we had coming up, new innovations, notification of work, what we do, how to book stuff, a "Dont forget" section for common issues etc. Trying to push the whole communication thing, break down barriers and have the whole open and transparent vibe.

 

I ditched it after 6 editions as it was clear hardly anyone was reading it - the final straw was a teacher saying "oh we're getting that - you should really tell people about stuff like that before doing it" in a patronising way. It. Had. been. in. 3. newsletters.

 

Its a shame as there was one teacher who always thanked me for it - its just a shame the other 115 ignored it.

[X-13]

@X-13, but is half the battle them not understanding what we are paid to do?

 

Nope. It's people thinking they're better than everyone else. [Oh, but I'm a TEACHER!]

 

They don't need to know what I do, they just need to know that I'm here when things go wrong or they need help. [Help != "do it for me"]

 

 

I ditched it after 6 editions as it was clear hardly anyone was reading it - the final straw was a teacher saying "oh we're getting that - you should really tell people about stuff like that before doing it" in a patronising way.

 

^ My point.

[korifugi]

Actually I already kinda do this. As I manage several sites (and getting them to use the helpdesk properly is a losing battle), I sum up a quick review of the days tasks and drop in any advice and comments.

 

This is then emailed to the office, the head and the it co-ordinator. In some sites this is even explained to the staff during briefing, in others - put up for staff to read.

 

You may want to reduce the size of the newsletter from 3 pages though. If it's over a page then staff aren't going to read it.

[naysweb]

We do one a term..

[tmcd35]

You may want to reduce the size of the newsletter from 3 pages though. If it's over a page then staff aren't going to read it.

 

I was aiming for 1 page, but turns out there's a lot going on in the world of IT!

 

[ATTACH]17037[/ATTACH]

I like! Maybe I'm trying to give too much info?

[CamelMan]

I was aiming for 1 page, but turns out there's a lot going on in the world of IT!

 

 

I like! Maybe I'm trying to give too much info?

 

If your going to do it - concise and clear is probably best - if its aimed at teaching staff any technical term is "techno babble" so simple would be the way to go.

 

If you were to be sent a 5 page, text heavy document about the goings on of the history department (no offence to history)- would you read it?

[naysweb]

We always keep to one page and reflect on what has changed or impacted on the staff and students and make it as easy to read as possible. We use as a change management, telling staff what we have done or going to do..

[reggiep]

We do one a term..[ATTACH]17037[/ATTACH]

 

What software do you use to create that? It looks really smart.

[naysweb]

We use a product call Serif Page Plus X3, similar to Publisher.

[tmcd35]

We use as a change management, telling staff what we have done or going to do..

 

I think this is one of the key points for me. Even if only a small % actually read it the information is being given out there. It then becomes easier to say "well i did tell you in the newsletter" - you didn't read it? not my problem!

[korifugi]

Sounds like you may be trying to give too much info - you only need a short summary. Most staff only care about "is my computer fixed?", and a short message of what happened and that its resolved is enough for them.

 

If staff want more information then they can come and find me, but usually the summary is enough.

 

I'm not saying never put detail though - if you need to use it then don't be worried, certainly when staff are used to being able to skim read the update, then a paragraph of info will have the required impact.

Edited February 5, 2013 by korifugi

[naysweb]

I think this is one of the key points for me. Even if only a small % actually read it the information is being given out there. It then becomes easier to say "well i did tell you in the newsletter" - you didn't read it? not my problem!

 

We find we use that **"well i did tell you in the newsletter" - you didn't read it?** loads and we found lost of staff do read it, and staff starting to ask when's the next one..

[tmcd35]

Here's what I typed in to word (no formatting)...

 

Page 1: Introduction, Details about changes to ICT Support Staff, Importance of reporting jobs correctly

Page 2: Highly simplified introduction to "servers" (topic of the month)

Page 3: Bullet point list of projects we're working on, Details of any planned works in the next month, details of next months "topic of the month"

 

I'd hope all staff read page 1, most glimpse page 3 and one or two get something out of page 2. I recon I can get future editions down to 1.5 - 2 pages - single sheet duplexed.

Edited February 5, 2013 by tmcd35

[Danp]

Do you have an intranet? How about putting some of your notices on there?

[tmcd35]

Not at the moment, but I could see this morphing into an Intranet later in the year once we've revisited things like room bookings and helpdesk software. At the moment a paper based handout would work best with out staff and a PDF on the unused knowledge base for future reference.

[Gibbo]

Its a good idea, we do a termly email bulletin indicating what we've been doing during the holidays and what our future plans are.

 

If the staff don't read it that's their problem, it shows good practice that you're bothering.

[Danp]

Not at the moment, but I could see this morphing into an Intranet later in the year once we've revisited things like room bookings and helpdesk software. At the moment a paper based handout would work best with out staff and a PDF on the unused knowledge base for future reference.

 

Get HAP+ installed then, help desk and room booking sorted, then Joomla for intranet.

[tmcd35]

Funny you should say that, I've been looking at HAP+ as a replacement to our current off site web access system. Not sure we'd use it for help desk though, we have other idea's there and want to be more integrated with asset management and site management.