Slashdot Mirror


Ask Slashdot: What's the Best Way to Retrain Old IT Workers?

A medium-sized company just hired a new IT manager who wants advice from the Slashdot community about their two remaining IT "gofers": These people have literally been here their entire "careers" and are now near retirement. Quite honestly, they do not have any experience other than reinstalling Windows, binding something to the domain and the occasional driver installation -- and are more than willing to admit this. Given many people are now using Macs and most servers/workstations are running Linux, they have literally lost complete control over the company, with most of these machines sitting around completely unmanaged.

Firing these people is nearly impossible. (They have a lot of goodwill within other departments, and they have quite literally worked there for more than 60 years combined.) So I've been tasked with attempting to retrain these people in the next six months. Given they still have to do work (imaging computers and fixing basic issues), what are the best ways of retraining them into basic network, Windows, Mac, Linux, and "cloud" first-level help desk support?

Monster_user had some suggestions -- for example, "Don't overtrain. Select and target areas where they will be able to provide a strong impact." Any other good advice?

Leave your best answers in the comments. What's the best way to retrain old IT workers?

17 of 343 comments (clear)

  1. ask them by Anonymous Coward · · Score: 5, Insightful

    People honest enough to admit their shortcomings, are probably quite able to tell where they can still be a good contribution. This late in the game, they must have ownership of their tasks, or they will hold everybody else up.

    1. Re:ask them by Anonymous Coward · · Score: 4, Insightful

      Who was managing IT while company transitioned to Linux / MAC?

      Silly to blame workers for doing what they've been told, as they themselves don't have the resources and funds to fix the gaps.

    2. Re:ask them by upuv · · Score: 4, Insightful

      Exactly ask them.

      30 years of experience means they actually know a lot more about the business than you might think.

      Granted if they are unwilling to just leap on over the the current hipster computing model then maybe you have to figure something out.

      These guys literally hold the companies legacy in their heads. Move them away from ops type tasks and onto data capture tasks. These people have seen every reason and method of storing legacy data over the years. Pick their brains and use it as input to migrate and obsolete legacy data stores and structures.

      They more than likely also understand the business model over time better than most. Yeah they may be a horrible pain in the ass to talk to. But for a product manager they probably hold a mountain of info.

    3. Re:ask them by ranton · · Score: 4, Insightful

      People honest enough to admit their shortcomings, are probably quite able to tell where they can still be a good contribution. This late in the game, they must have ownership of their tasks, or they will hold everybody else up.

      This. Identify the current workload within your IT department and any staffing deficiencies you have in completing that workload (skill gaps and/or not enough people with certain skills). Provide this information to these workers and work with them to develop a training plan. Maybe they just need a few books and a couple weeks of instructor led classes. Maybe they just need to work closely with other IT workers who have this knowledge for a while.

      But please don't start training them on anything until you have a good idea what your company needs. Don't train them on AWS if you already have a resident expert who handles all those tickets. Don't train them on Mac driver updates if the OS handles them well enough there are only a few tickets per month. Find where you currently have trouble handling support tickets and train them on that.

      --
      -- All that is necessary for the triumph of evil is that good men do nothing. -- Edmund Burke
  2. People Skills by Anonymous Coward · · Score: 5, Insightful

    Sounds like they are well liked and have excellent people skills. Use that. 1st level help desk, training new employees, vendor contact, IT intranet, etc.

    1. Re:People Skills by Anonymous Coward · · Score: 5, Insightful

      IT people who don't tightly control what people do and can solve 99% of the problems that ordinary users have with their PCs? No wonder they're well liked.

  3. Values by Bongo · · Score: 4, Interesting

    A thing with people that's often overlooked is that different people have different values. The main ones are

    traditional authoritarian
    individualistic achiever
    egalitarian community
    and systemic integrative [1]

    For example, the traditional mindset is happy so long as there is a hierarchy which is dictating what needs doing, with a sense of loyalty and appreciation. So change for change's sake is not welcome, but change in the context of stability and loyalty, can be welcome. The core point is, safety and loyalty and conforming to the norms.

    Whereas, the individualistic achiever is happier being able to do independently driven, the typical "modern thinker", the self-made man, etc. Here you might be more concerned with, asking people what do they want? Where do they want to go with this job? What are their interested? What do they personally want to develop? And then just letting them get on with developing any opportunity which appeals to them and which is useful for the company.

    The egalitarian community type is motivated somewhat differently to the first two. This is anti-hierarchy and is looking more for meaning and purpose in the job. This person want to work for a charity which is devoted to a good humanitarian cause. They have a need for personal meaning and a sense of being equally valued as everyone else. Their own voice matters. The group is important, and so it is about helping people to voice their own experience and do so in a way which helps them relate to the group more, in a more meaningful way.

    So that's three main "values" and there is one more crucial point: people's values change over decades. So you might find that, people who were happy in the same job doing the same standard thing for 30 years -- which would suit them if they were traditional authoritarian ie. they valued stability and being told what to do -- may by now be in the achiever value or the egalitarian value, simply because as individuals, they grew as people and now have new needs.

    So part of retraining isn't just swapping out one set of work tasks for another -- that may be done perfectly well, yet kinda fail -- because as a person one may now wish for a different kind of expression of values in their work, and in their training.

    Another way to out this is that as people grow they tend to become more complex and have more complex aspirations.

    Actually my reason for writing this is that the article description suggests that the "problem" is how to deal with people who seem stuck in old patterns and unable to change... so I thought it worth mentioning that the people may have indeed changed... they have become more complex individuals, but the work itself hadn't changed... so the opportunity here is to tap into whatever new complexities these individuals may now be capable of. Older may well mean wiser.

  4. Domain knowledge is sometimes more important by MrDozR · · Score: 5, Interesting

    We had a not too similar situation when we decommissioned our old COBOL system. The developers were of more mature years (50+), but instead of just letting them go, they were moved into more of a BA role. They have a lot of domain knowledge built up from years of working on a monolithic system, it transferred quite well to doing business analysis and converting it into specs for devs on the new tech. They also had better people skills than green devs, which is rather important when trying to understand WTF the business wants or means

  5. There isn't by zifn4b · · Score: 4, Insightful

    If you are a Journeyman in the field of IT, people don't train and update your knowledge, you do it for yourself. People who are good at this trade are also good at educating themselves and learning in general. People who aren't good at it might get a little better with training but they were probably not very good to begin with.

    --
    We'll make great pets
  6. Re:old? Old? OLD? by CustomSolvers2 · · Score: 4, Insightful

    IT workers are "old" when they reach 30, not 40.

    For whatever meaning of "IT workers" (see my comment below for more clarifications), this isn't applicable under highly-specialised conditions, where the more experience the better. I am 39 (although started programming a bit too late) myself, I am working under very demanding conditions and planning to continue doing it for many years. The older I become, the clearer are my ideas and the better and easier my work becomes.

    When talking about programming/software/IT, low-specialisation or too-narrowly-delimited experience are starting to become a problem almost in any context. Although there seems to be a tendency towards easier environments, the reality is that everything is getting systematically more complex and being very knowledgeable/resourceful is starting to become a requirement almost anywhere. When problems appear, you want trustworthy people able to quickly and reliably fix them; to not mention that, ideally, you would prefer those errors not having been provoked in the first place, what is much more likely to occur when experienced people are around.

    There are certainly quite a few privileged companies with good enough resources which are mostly interested in people using/applying what someone else did before. Those companies might afford relying on cheaper/younger labour force, but that attitude is likely to provoke long-term problems anyway. Experience will always be a very relevant asset in a field as complex and systematically evolving as IT, regardless of its exact meaning; at least, when talking about medium/high quality products and services.

    --
    Custom Solvers 2.0 = Alvaro Carballo Garcia = varocarbas.
  7. Ageism again by Max_W · · Score: 4, Insightful

    "Old IT Workers". It is one more stereotype. There are weak "Young IT Workers" too.

    For example, one may think that workers in advance age miss work due to illness more often than young workers. It is a stereotype too. The research shows the opposite.

    It is due to such managers we have got cute baby-face puppets at about any office and counter who do not have a clue, who do not have any real life experience. And as a result the production goes away from Europe and the US.

    I would start with the retraining course "Prejudice or discrimination on the grounds of a person's age" for this IT manager.

    1. Re:Ageism again by Baron_Yam · · Score: 4, Insightful

      Older workers are generally more familiar with their rights and more willing to stand up for them. Of course, we should be condemning management for taking advantage of the naÃve youth, but instead we blame the old people for wanting their half of the contract honored.

      Younger workers are generally more likely to miss Fridays and Mondays due to 'illness' - either skipping out to start the weekend early or coming back late because they're hung over. And in fact younger workers are more likely to come in hung over on Thursdays, too.

      Older workers are less likely to be enthusiastic about new tasks, because in addition to just generally not wanting to put in extra effort on something they may not like, they also have spent a lot of time getting good at what they already know.

      Younger workers are often more willing to throw their own time into a project they are enthusiastic about. This is because they haven't discovered life balance yet, and because they have fewer responsibilities (or haven't learned to respect what responsibilities they have). Again, this is a case where we should condemn management for taking advantage of the youth, not condemn older workers for not wanting to be taken advantage of.

  8. Use their strengths by Cesare+Ferrari · · Score: 4, Insightful

    It sounds like they have loads of experience, but not practical skills for your current setup. Realistically if you were to train them to update their skills they would be just the same as any new (and potentially cheap) hire that you make - this isn't getting the best out of them.

    No, what you want to do is take advantage of their experience. I'd be looking to shift their role, and only you can know what slots you have open, or where they may be able to contribute most. If they know everyone, then liasing between departments, IT and the users for example, may be good. They have probably got management skills which are under-utilised, and they will certainly be able to provide mentoring to new and inexperienced team members.

    I'd start by talking your thinking through with them (individually) explaining the potential they have, and sounding out what they think they would like to do. You may find they have ideas which you haven't considered. If they want training up, then that is an option, but this is unlikely to be the best for the business.

    1. Re:Use their strengths by TheRaven64 · · Score: 4, Insightful

      If they're only a few years away from retirement, then they absolutely should be spending that time in training, but not the way that the original question was posed. You should hire people who understand the technologies that you're using and have the old guys train them to understand the business needs. They sound as if they're too valuable to waste for the few years that you still have them.

      --
      I am TheRaven on Soylent News
  9. Re: What's the point? Here's the point by Anonymous Coward · · Score: 5, Insightful

    You were hired to manage two guys who are on their way out. And you can't fire them.

    Take that as a lesson in the organizational reality rather than your stated position.

    You should consider that your position is not as secure as you think it is, and respond by turning these employees into niche superstars. Help them go out on their high note and you will give yourself a leg up.

    They have internal cred. You are the new guy everyone 'above' is evaluating.

    It's important to know that the administrative staff and others who hold goodwill toward these subordinates of yours could be your position's catapult, or it's anchor.

  10. I'm doubting the article is real. by clovis · · Score: 4, Insightful

    I doubt the article is about a real company, but let's pretend it is.

    So you have these two guys that don't know anything but Windows desktop support, and now you want to train them to be admins for Linux servers?
    I call bullshit. What is going on here is that you have Windows server and domain admins that don't want to learn Linux, so they're trying to escape that duty by dumping it on the Desktop guys.

    You claim to be a medium size company. Are these two guys clearing their calls and keeping busy for 40+ hours a week or are they sitting on their butts all day? You did not say, but If they're putting in over 40, then adding Linux server support to their jobs means you're being a jerk. The correct thing to do is hire an another admin to manage the servers, or more likely, you need to make your server admins do their jobs.

    The two desktop guys do indeed need to be able to do OSX desktop support, and probably smartphone email integration. You'll have to buy them each a OSX box and a book to learn, practice and troubleshoot.

    Server admin job is a different job than desktop support (except in small business). It is a different mindset for the most part, and it's not a good idea to mix the roles.

  11. Re: What's the point? Here's the point by sycodon · · Score: 5, Insightful

    I work for a major defense contractor. I mean big.

    We had a guy that was here long before I arrived. He worked with the top level management and was very well regarded.

    He did not re-install windows. He did not program. He did not configure switches, routers, or firewalls. He did not build computers, install servers, or anything else.

    So what good was he?

    He knew everyone who could do these things.
    He knew all the policies and procedures and work flows.
    He knew how all of these disciplines interacted.
    He knew the right way to set up infrastructure for the best supportability and growth.
    He knew how to get priorities changed to get support to your project.

    If you had an outage of any kind and had 100 people on the manufacturing floor idle, he was the one you called. He coordinated all the disciplines and made sure the problem got resolved.

    But he was an old guy who didn't have current skills, so what the fuck use was he, eh?

    Maybe this new IT manager should sit down with management and find out why these two have such goodwill. Then talk to them and find out what they really do.

    --
    When Fascism comes to America, it will call itself Anti-Fascism, and tell you to give up your guns.