>>
Site Map
>>
News
We Received this Story
#7 - 0--webmaster--We Received this Story--2004-05-01 11:30:39
#After reading today's account of your business as posted on AOL, I have to make comments. After 24 years in IT, I have been persistently seeking employment for 2 yrs (completely willing to accept whatever the employeroffers, etc), but so far have gained only one 2-month gig. Mine is probably similar to all the other stories you hear - except maybe that my wife lost her IT job at the same time, so now she works 2,500 miles away from her family to keep us off the streets, etc. - <P></P>
<P>Mr. Jennings...<BR>After reading today's account of your business as posted on AOL, I have tomake comments. After 24 years in IT, I have been persistently seeking employment for 2 yrs (completely willing to accept whatever the employer offers, etc), but so far have gained only one 2-month gig. Mine is probably similar to all the other stories you hear - except maybe that my wife losther IT job at the same time, so now she works 2,500 miles away from her family to keep us off the streets, etc.</P>
<P>That's not why I'm writing, however. I want to point you to a NY Times story yesterday if you haven't seen it already:<A href="http://www.nytimes.com/2004/04/28/technology/28SOUR.html">http://www.nytimes.com/2004/04/28/technology/28SOUR.html</A> You'll need to do the free registration to read that.</P>
<P>My point is: These companies you're talking to are arguing with you, but not really listening - as I know everything you list on your web page aboutthe down-side of outsourcing is totally true. Only those outsourcedprojects which require no thought beyond robotic-like coding will stand achance of saving our companies any money. All the others are going to costthese companies dearly, and they will eventually stop this trend..unfortunately, this might take a very long time, as no one wants to admitthe gross error they've made in outsourcing. I say this as one who wastasked with running three remote projects (Y2K) in 1999: One in India, one in Puerto Rico, and one in a neighboring state of the US. The Indian project was virtually impossible to control or get any satisfaction from.The vast differences in culture (even though most of the Indians had beenbrought to the US for specific company training for 6 months or more),language, time zone, and mostly just basi!c comprehension of US business systems and US thinking. The other twoprojects worked well-enough, but far from perfect.</P>
<P>That Cincinnati company decided to close all of it's India-based operations,because the end results were horrendous and deemed far beyond workable.This, even with a US manager sent to live in Bangalore to oversee thedivision.</P>
<P>I've had US workers tell me privately that the end result coming back from India is seriously problematic, costing the company more than if they had stayed local, and they take care to not openly discuss it. By then, ofcourse, the CEOs and CIOs etc have all been made out to be heros and somemay have even received grand bonus checks for their wise maneuvers.Personally, I think some of them ought to go to jail.</P>
<P>Thank you for reading this... I know you're a busy man. May your business thrive and prosper.</P>
<P>PS: I read there are companies now (Chicago) whose purpose is to quietly take in the many unworkable projects returned from India, and fix them. They work with little fanfare, because part of the service provided is to help keep the company name (or the CEO's name!) out of the news.</P>--comments-->0--1958--6
