...that the company will buy IT as a service from the most cost-effective supplier, most current IT personnel will be laid off (a few will be repurposed), and then users will discover shortly after cutover that calling the (now overseas) helpdesk has suddenly become an exercise in frustration, because of the language barrier and because the helpdesk person often knows less about computers and about the environment than the customer, because the business model dictates that you can pull people off the street, hand them a stack of procedures, and they become IT personnel. (This works as well as you imagine.)
Management and team leaders will beg the remaining IT management not to make their users call the helpdesk, in vain.
Due to lack of effective IT services and the necessity to actually get work done, little pools of IT start to pop up around the company. It starts as a file share on someone's PC, and then an off-the-books PC becoming a dedicated resource (there's a rogue EXSi server not three feet from me) and developers start to remember old admin and dba skills. After awhile, the company IT infrastructure is still used for no-brainer stuff like mail and large storage appliances and relatively static work like billing is still done on big, enterprise-class machines, but more and more anything that needs to be flexible, or resources that need to respond rapidly to user needs, are done surreptitiously, under the table, with the funds being disguised as other thing.
Then, when development itself is outsourced, it's left to the "development managers" and "offshore interface personnel" to maintain the still-used local resources, plus, usually, additional personnel to try to find some use for the code produced by those offshore resources, who have no real context of what the code is being used for.
(Parenthetically, the problem is not confined to IT. A company of which I have experience who has outsourced their accounting, still doesn't realize that after three years the offshore accountants still don't know the difference between California and Canada, and think the transaction must be correct if they don't get an error when they hit "return". The remaining 10% of retained accountants are kept busy correcting mistakes and doing the work over again.)
Anyway, the point being, some IT people don't choose to fade away, they go underground. They find that users can be very thankful of a helpful person who can communicate well and has knowledge of the company and what the user is trying to accomplish. Who isn't following a script but genuinely trying to help, with the expertise to do so. I have a title that sounds like a different job, but I'm still doing admin and customer support. When I'm not at my regular job, I have a side business providing home support for people who are tired of "I am being here for helping you turn it off and back on again".
So yeah, I guess IT has changed.