Actually it was my company's IT outsourcing system. I work for a very big company: it has about 150,000 employees spread across the world. I work in north west England amongst other things I look after a little unit which uses a particular piece of bespoke software, the unit involves seven people in an office a couple of hundred metres from where I sit at work. The tale of our new bespoke software is long and tortuous and I won't go into it here but to relate my adventures in getting the test version of the software copied onto the live system today.
The servers on which this software resides are located in North Wales (15 miles away) and a spot down the road about 8 miles away. The outsourcing of our IT services means that the manager for this process is located in the Netherlands, and the person actually doing the process, Supriya, is in India. I can tell she is in India because she has an Indian phone number. Her e-mail signature says her "office base" is in North Wales, it must be a bit inconvenient having your "office base" in North Wales, a location I suspect Supriya has never visited, and a phone in India. Do my company think I am some sort of dribbling BNP little Englander who would dissolve in rage if I thought I was dealing with someone in India? I regularly work with people from China, France and even the US, trying to obfuscate where someone works is frankly patronising and offensive - particularly if you do it so ineptly.
The process doesn't go entirely smoothly, largely because Supriya is too polite to tell me that the procedure she'd been asked to carry out throws up some errors. I can't help because I'm not given permissions to see the servers where the software resides, Supriya has a difficult time because she has no absolutely idea what the software does. However, with the help of James, who wrote the software, based in Manchester but whose boss is in Sunderland we do manage to get everything sorted out by the end of the day (or about 10pm in Supriya's time zone).
This is not an isolated incident: receipts for my travel claims are sent to Iron Mountain (a company just outside Birmingham) where they are converted to electronic form before being sent to Manila (I can't help thinking this may have been due to a misunderstanding involving envelopes) and paid via India. In a fit of tidiness I once decided to get a stash of 6 computers removed from a desk in my office: they'd been left by a sequence of unnamed, and now forgotten contractors. I received endless fractious e-mails from a centre in Bulgaria, belonging to the leasing company, demanding to know who all these computers belonged to, or why I appeared to be in possession of 6 computers.
The old way of doing things involved a prescriptive system of doing stuff where you filled in a form and it went through a process and something got done. But actually it didn't, actually you learnt who was going to do what you wanted, went over for a little chat whereby you found out what incantation you needed to inject into the system in order to get your job squared with the system whilst they got on and did the job. Outsourcing frequently loses this human contact, in fact it purposefully eliminates it.
8 comments:
Brilliant rant. IT systems and their support networks are surely the cause of more premature ageing in the workplace than anything else. All the IT in my old University workplace was located on campus & yet it was still a nightmare resolving issues.
Also when you mentioned Iron Mountain I thought for a minute some of your IT had been outsourced to Middle Earth.
University IT where I've been has generally been better than I experience now, largely because it tried to serve an audience of people like me. I'm a bit more of an outlier for corporate IT.
When Lehmann Brothers went bust I distinctly remember someone carrying their desk contents out in an Iron Mountain box!
When we've an active project our meetings are between manager in the U.S, developers in the U.K, and testing in India. You'd think this would limit when the meeting could be but from what I can tell our teams in India work 12-hour days every day - they certainly seem to!
In the end though, no matter how much we might like to think the elimination of human contact encourages proper documentation (which to a certain extent it has), really it comes down to cost!
@Phil - yes, Supriya does seem to get awfully long working days.
My company has research labs in Connecticut, Europe, India and China (Shanghai) - they get together for the occasional teleconference - which is a bit of a stretch!
Sounds pretty easy by corporate IT standards - but then I'm sure you gave the requisite 2 months notice that you wanted to deploy the software.
Now I'm working in a University I just do the deployments myself which is nice
It would be so much easier if I was empowered to screw things up myself!
Goodness, Ian - quite a tale. Is this really typical for corporate IT?
Perhaps next time I feel like cursing the University IT Department, I will remember this and give quiet thanks instead.
I suspect my experience would be familiar to people working in very large companies.
University IT have quite a difficult job because they're generally required to pay substantial attention to the desires of academics with a broad range of preferences!
Post a Comment