I suspect that if you talk to anyone who's trying to get out information about events or changes you'll get the same sort of message - no matter what they do, some people just don't take it in.
I don't think that means we should stop trying - there will be some people who will read notices etc and act on them and we should make sure we put out info when we can for the benefit of those who can be helped :-)
Yup I'm in the "document the lot" camp as well. I sent an email round immediately after the upgrade called "email uggrade... how will affect you?" with some of the benefits of Exchange 2007.
So far I've already had people asking about the remote file share access and pleased with the OWA 2007 enhancements. We'll make more guides for how to use the features then it all goes on our IT Services intranet site. Some people might think no-one reads the guides but if they're well written and easy to use I've seen people printing and using them
Also made a CD for our staff conference with the new SmartBoard v10 software on plus documents about changes to the PC setup so that way if anyone says they didn't know about the changes we're well and truly covered
I agree with the principal of informing users but have the same problem of people not reading stuff or not listening.
I once explained an issue in a staff briefing one morning which I think was to do with laptops and offline folders being moved.
Later in the day someone asked me about this problem and I asked if there were in the briefing becuase I had explained it all then, she said that she was but I hadn't started to say something technical so she switched off.
I offered all staff a 5 minute lunchtime training session on how to log jobs on My Little Helpdesk.
I did this 3 times over 3 days and had in total about 6 members of staff I think it was.
I did the same last week albeit only 1 session for new members of staff starting this year which there must be a dozen or so, 2 new staff turned up and 1 existing member of staff.
So I give up.
Start with the people you think are reasonable (there will always be those that no-one gets through to!) It might be that they'd tried the software, found it easy and didn't want to spend time at lunchtime. It could be that they were busy that week but could have come before school/after school/at some other time. It might be that they would prefer to just read some instructions (I much prefer to be given a set of instructions I can read in my own time for anything new; I can then try things out and, only if I get stuck, ask for help)
I know it can be very disheartening when you think you've made a lot of effort to get things across and it's not taken up but as a couple of people have said in this thread it does benefit in the long run - people don't feel left out and can see you've put in the effort to make things work and explain what's going on.
I also gave up my lunch break to run these sessions to help them out.
If they can't be bothered to turn up I am not going to run around asking why they didn't come.
What is needed is for all staff to be comfortable using the helpdesk which we expect them to use from day 1 therefore providing training on it from day 1 I see as very relevant.
If they don't want to put in the effort to learn why should I run around after them?
The problem does not only come down to timing. It also covers things such as people are only interested when it affects them. People would come in for a 5 min session if they were interested in learning how to do things themselves. Unfortunately there are still poeple who find it easier to ring IT support and get them to setup a projector instead of learning to press a FN key.
I can appreciate that people are busy, but so are IT techs. If people are not interested in helping themselves then there is not a lot you can do. Maybe write an online intrsuction sheet so you cover yourself, but you cant waste more time trying to get people do things they dont want to do. Not without the support from SMT anyway.
Last edited by pallen; 9th September 2008 at 10:27 AM.
It's just basic project management -
working out the customers requirements (not exchange 2007 in this case), testing on small groups of users, handing over the project with some training and documentation.
Training on new systems shouldn't be voluntary, its something SMT should be insisting training happens on new equipment, as it does in almost every other industry. Training budgets and times should have been organised as part of the initial project management.
There are also online tutorials that walk them through the task of creating and tracking their requests.
There are currently 1 users browsing this thread. (0 members and 1 guests)