My only objection to your points on my use of social networking was your repeated use of the word 'resist'. I've taken the cotton out of my ears several times, but the siren song doesn't seem to have any pull on me. It's probably because I'm tone deaf to many forms of social interaction. I didn't engage in these behaviors before they were automated; moving them online hasn't made them any more attractive to or easy for me.
We discourage the use of social networking at work and block most sites. Those aren't my policies, but I agree with them. Even if we let much of the Metro live tile candy through the firewall (and I suspect we won't), 90% of my users run all their apps maximized. They'd never see the content anyway.
I admit I'm still trying to 'get' IM. We're upgrading Office Communicator to Lync in the spring. Other than saving costs on international calls, I can't find a reason to use it. I don't think I'm 'resisting' it; I'll respond when others initiate a conversation instead of ignoring it or closing the client. But I rarely initiate a connection myself; I don't get what it does that can't be done with at phone call or (in the case of your example) an e-mail. I realize that I'm an exception here too, but I have no problems with rolling it out if that's what the PTBs want.
Yes, I'm letting the Start Menu issue override my acknowledging some of the benefits. But I'm still missing why including them mandated the Metro interface. The registry hack for the Classic desktop was already there; they had to work to remove it. We skipped W98 and Vista without performance or user efficiency issues; I've no reason to think skipping W8 will be any different, but it isn't my call. Fortunately, training isn't my problem.
Yeah, I'll figure out how to use the damn thing and capably deploy it when told to do so, but acceptance isn't affection. If I beat my head on it long enough, I'll eventually go numb and stop feeling it; that doesn't mean I'm enjoying the pain.
Keep Up with TechRepublic