Outsourcing Growing Beyond India
PreacherTom writes "One of the most controversial aspects of the global economy has been the newfound enthusiasm of companies, freed from the constraints of physical location, to outsource jobs. No country had embraced tech outsourcing with more passion than India. Of late, problems are beginning to arise in Indian outsourcing: engineers will start a project, get a few months' experience, and then bolt for greener pastures. The level of attrition can cause the turnover of a project's entire staff within the course of a year. Combine this with salaries in Bangalore that are rising at 12% to 14% per year and it is no surprise that companies are looking beyond India to a slew of emerging hotspots for IT, such as Brazil, China, and Vietnam. Will Ho Chi Minh City be the new Bangalore?" From the article: "India remains an IT outsourcing powerhouse, with $17.7 billion in software and IT services exports in 2005, compared with $3.6 billion for China and $1 billion for Russia... India's outsourcing industry is still growing at a faster pace than that of... other wannabe Bangalores... By the third year of an outsourcing deal, after all the costs have been squeezed out, companies get antsy to find a new locale with an even lower overhead."
When people find out what they are worth, they start demanding it. Pretty soon, the entire world's IT population will be high-salaried, no matter where you go.
My twitter
But turnover is the real project killer. But what did they expect? Worker Loyalty after they proved that they had no loyalty? The strange part though is how this infects EVERYTHING- I moved to government for stability, but my sub-sub-department of application developers has a 26% annual turnover rate; for the simple reason that in America we've destroyed the loyalty of the workforce! Now we're doing the same in India. If you treat people like widgets, expect them to act like widgets- and move to the most ecconomically efficient place for them to be.
SJW: a person who perceives an injustice, and while correcting it, commits a greater injustice.
So you see high staff turn-over in India. The "solution"? Move the project to a different country.
But why would that country's people be any different?
The fact is, once the outsourcing staff has the knowledge and experience that was previously YOUR expertise, there is no reason for them to keep working for you. Eventually, they start their own companies in your market and replace you.
Don't focus on short term profits at the expense of long term survivability.
Logic says the same thing is going to happen in every place that is outsourced to. Maybe that is the point to make to the CIOs. Just keep projects where you can control it in the first place, and it will save money in the long run. Lack of control on a project and high personnel turn over can be more expensive and deleterious to a project than keeping things close to home and paying a reasonable salary to begin with.
-- I ignore anonymous replies to my comments and postings.
How can you structure a CEO's (or other CxO's) salary/bonus plan so that their incentive is to keep the company productive and viable instead of "shedding" all the "unprofitable" sections (such as IT) and outsourcing them to raise short term revenues, cash in the bonus and leave for another company?
It is far more profitable for a CEO to wreck and sell the company than it is for him/her to actually spend time running the company.
...for which I offer no apology.
Outsourcing is neither good nor evil, but the motivation behind outsourcing tends to be overwhelmingly merciless and short-term. Taking a knowledge activity and attempting to turn it into a commodity or near-assembly line function is, I suppose, a managerial Holy Grail worth undertaking in different guises each decade.
Consider H1B visas. Is there a shortage of IT workers in the US, or a shortage of *cheap* IT workers in the US? Most major media publications are overwhelmingly guilty of dropping the telling adjective, and the quotes they gather all support a lack of IT talent, no qualifiers added.
We who work in this space, live in the space, can confirm some of this. It *is* hard to find a superior talent for an IT position above entry level. However, it's not impossible if you have a salary and excellent position to offer.
So, when I read about outsourcing arbitrage and the chase for ever-cheaper talent, I just wait it out. Eventually, all of the talent, cheap or not, will come to fore and then the real shoot-out over quality and reliability can begin. Does anyone truly believe there's a hidden cachet of Polish supercoders who haven't been discovered because they lack the Internet connectivity? Does anyone see the inherent flaw in that premise, and by extension, any argument like it?
I'm not overly impressed with a single outsourced individual or group in my eleven pro years of IT, and that includes old Anderson Consulting of 1995 up to Patel Consulting of 2006. The prestige of the firm should only get them an interview: talent and not cost is what you'll need to survive.
As a final note, what, if anything, will the US do if it successfully outsources all of its IT functions? Does anyone expect anyone to major in CS in this country, knowing that electricians make far more and took less formal schooling? I think not. You can't outsource a physical service.
-BA
Loyalty is and always has been a fairy story told to you by people in power to get you to do things for them cheaply.
Oh yeah, that includes patriotism as well btw. Typically they want you to die for their benefit.
Deleted
I disagree that outsourcing is bad. Generically that is like saying hiring a babysitter or a neighbor or anyone other than yourself is bad. So what are the indicators that outsourcing is bad? Just saying there are indicators is not the same as showing that the indicators are bad.
1) If you hire your son to mow your lawn, there is nothing stopping him from hiring his friend in turn... ala Tom Sawyer. If the job is unacceptable, make the terms part of the contract.
2) Customer service is not a function of outsourcing, it is a function of cost. You can have equally horrible customer service inside the US itself.
3) High turnover is also not a function of outsourcing, it is a function of management. If an employee has no training and advancement path then it is up to the employee to figure out their own. This is true of any company in any country.
All these problems would exist if the companies in question practiced homesourcing, where a company like IBM hired a temp agency in Alabama to support their developers in San Jose.
Again, why give work to a neighbor or a friend when you can do it yourself?
Answer: Because division of labor and speciality encourages increased productivity when both parties can do separate things more effectively than both parties replicating work.
In this case the flaw with outsourcing is that there was not a good reason or a good implementation for the division of labor.
GPL Deconstructed
This is the biggest problem I have with globalization: we have removed all constraints from capital and freed it from all other considerations. It is truly a race to the bottom - who has the lowest labour costs, who has the fewest environmental restrictions "wins" some starvation wage jobs until we can find someone else who can be exploited even more.
The fear used to be that jobs were being sent south to Mexico. But when Mexicans workers start demanding fair wages, we sent the work to Viet Nam, where people earn $2 per day. But even that looks pretty expensive when there are people in China willing to work for $.50 a day.
It's exploitation plain and simple, and we don't care because we are insulated from the uglier aspects of it. Of course, we are getting screwed too - those over-priced sneakers are now manufactured for a fraction of what they used to cost, but we still pay roughly the same price at retail. At least the shareholders are happy, but if they could find someone who would work for $.25 a day, they would be even happier.
Whenever someone argues in favour of a living wage, we are told it is too expensive. What a shame that poverty has become an official requirement of our economic system.
If we found ourselves working in the sweatshops for less than a buck a day, I wonder if we would be grateful...
*** Where are we going? And what's with this handbasket?
There's will come a time when the supply of IT workers will match or exceed the demand.
Take an econ class. You don't even know how to use the terminology right.
And as technology improves, the run of the mill business programming will become so easy (adding, updating, deleting data from RDMSs, biz logic, etc...) that the only need for real programmers will be for systems and development software (reason why MS Office is soooo popular! You wouldn't believe how many VBA apps I've seen on Excel!!! And all you need is the office developers to support ALL of those biz "programmers".). And that will be a much smaller labor market (hence plenty of supply) for programmers.
In my experience, the number of professionals who want to learn anything about IT besides "type it in here and press this button." is exceedingly small.
Even now, the number of people who are capable of doing IT work, let's say 70th percentile of the population, means there are over a billion people on this planet with the brains to do the run of the mill programming.
There's about 3 Million people in the US and about 800,000 people working as software developers. That means, in the US. about 0.267% of the population is a software developer. I doubt that we'll see drastically higher worldwide programmer/population rates any time soon.
However, I do thing that the vast majority of human activities can be made more efficient through software. So as the world's population becomes more computer-using I'd expect the market for software to expand greatly.
I say there's plenty of supply and salaries will always get lower - overall - regional differences may apply.
There were certain countries that had a waiting, highly-trained work force but they couldn't get the work because of high transaction costs. The internet drastically lowered the transaction costs but did not eliminate them. During the time when those costs were plummeting, we saw a massive influx of new developers into the market. So, the countries that had highly trained workforces sitting on the sidelines are all now pretty much in the game, So, I wouldn't expect to see another influx like that unless there's another radical change in the transaction costs.
The problem is that the remaining transaction costs are pretty hard -- mostly organization and physical.
In other words, the "damage" is pretty much done. Frankly, I think the world as a whole is better off due to outsourcing.
You are not a beautiful or unique snowflake -- but you could be if you got off your ass.
They said that about COBOL as well.
You may be right, but the "higher levels of abstraction" will,
in my opinion, call for more knowledge, not less, requiring
more skilled persons, not less.
Until the point that we have true AI, that is. ( And it will
still be true, but handled by the AI. )
emt 377 emt 4
Employee loyalty is a measure of how much the company values the employee also. Most of my friends who quit their workplace complained that the company recruited people far less experienced than him at a greater salary, a cardinal sin in the Indian Workplace.
The HR policies of some companies are frightening, they want employees to be loyal, but they dont honor loyalty. And they are the once who recruit employees who have jump companies at whim, I heard cases where a people have stayed in their jobs at an average of 6 months, I wonder how they get picked up at all.
So if there is a lesson that the outsourcing firms should take, it is this:
1. Award Employee loyalty
2. Stop recruiting people who jump companies, even if they are from your competitors.
3. Question bosses who have low employee retention rates, most of the time 'they' are the problem.
4. Tune your HR policies, its evident that they dont have an eye for talent, less for an unbiased compensatory practice.
Absolutely.
20 years ago you could produce what was considered commercial quality code for those days and make a living off it with knowledge that was equivalent to 1-1.5 years of university education, sometimes less. Nowdays 4 years of college are not always enough to get you through your first day in the job.
Baker's Law: Misery no longer loves company. Nowadays it insists on it
http://www.sigsegv.cx/
How long before the circle completes and companies start outsourcing to the USA? Any bets?
There are so many flaws in this thinking I don't know where to start.
First of all, CEOs don't reap what they sow. They'll only be CEO for a few years, they'll make a shitload of money, and when they leave they'll get an even bigger shitload of money as a golden parachute. You can't blame someone for taking that kind of work, and the long term implications of what they do won't affect them. Somebody will reap what they sow, but it won't be the CEOs.
Secondly, when did they "kill the industry" in the US? I'm working in "the industry", and this job gives me the most dollars-per-effort ratio of anywhere I've ever worked. Unemployment in IT in the US is what, 2%? That's hardly a dead industry.
Third, I don't know if you remember the bubble years, but turnover was pretty damn high in the US at that time. I recall the conventional wisdom was you'd make the most money if you moved on after two years, and lots of people did. I stayed at one company for four years and the only original coworkers who were there when I left were people who couldn't leave until their green card came through. When it did they left that day. Turnover is a sign of a good job market. People will stay in crappy jobs if there isn't anything else available.
If outsourcing moves on to other countries, so what? We went through the same thing with Japan. As countries emerge from the third world their economies create more demand for these kinds of skills than supply. In another generation American companies will be competing with Indian companies for high-tech workers in Africa, but due to cultural and time zone issues there will still be jobs in the US for people with skills.
News flash: India is not a bottomless well of instantly tappable programming talent.
... India. However it won't look like the round we've been through. It will look something more like toe-to-toe competition.
What folks are complaining about is simply signs that there's a sellers market for programming skill in India these days. This will raise Indian salaries to the point where Indian salaries plus transaction costs are the same as US salaries. Another thing I've seen is that the average skill level level of Indian programmers isn't as high as it once was. Which isn't the same as saying the Indians are losing skill -- it's the opposite. The time was when nearly every Indian programmer you met was probably brilliant. There are more great Indian programmers than ever, but there are also lots more mediocre ones than there ever were.
I expect India's programming talent pool to continue increasaing, but you can't grow such a skill based industry overnight without compromising a little on quality and losing some price advantage.
There will never be another outsourcing phenomenon like the India. India has had three great advantages: (1) a huge and highly educated middle class population; (2) widespread English fluency; (3) stable government and laws. There isn't any other place remotely like it.
The next great outsourcing horizon will be
Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
They don't require more skilled programmers, though. They require more skilled specialists in whatever field the program is being used.
It's not so much shareholder demands as it is customer demands. Companies wouldn't be under so much pressure to charge less if customers weren't so stingy with their dollars.
Don't piss off The Angry Economist
At least for America's workers, whose wages will never recover from the downward pressure of globalism.
America's booming IT industry is a thing of the past, as the entry level jobs needed to train people for higher end jobs no longer exist in America. Our IT industry will continue to shrink until it's completely gone, and all that is left in America are people jobs. The low paying cashier and medical clinic crap, with a smattering of middle class nursing jobs and doctors being crushed by malpractice premiums in malpractice award-capped states.
For globalism to succeed, successful nations must be impoverished.
Now where, you ask, is all the growth coming from? Simple. America is drowning in utterly unmaintainable consumer and national debt. Eventually that all has to be repaid.
Pray ye diligently that ARMs stop rising and that home prices stop falling in the superhot markets of today, or you may find yourself eating the words you're thinking of responding to me with - because that's all you'll have to eat when the shakedown comes.
--- Grow a pair, liberals... stop letting the Republicans bully you!
I know it seems a little pedantic to quibble over terminology but when you start thinking like this you can end up with all sorts of nonsensical conclusions. This is a case in point. Since we are talking about curves that intersect curves, talking about one as being higher than the other makes no sense.
This terminology and the difference between demand and quantity demanded is one of the points that's driven home in any decent intro microeconomics course. Hence, we have someone trying to hold forth on Economics, a subject in which he obviously has no training. Being a proto-Economist myself, it drives me nuts when people who have no training try to do Economics because everyone seems to think they are qualified but few people have had even a single course.
For a better explanation than I'm managing at this point check out this and take a look at the section "A Shift versus a Movement Along a Demand Curve". You can have an available supply of IT workers exceeding the demand for IT workers. And, of course, when this happens, the price -- the wage rate -- of IT workers falls; too many workers chase too few jobs. Think of shifts in the curves. You also have to consider short-run Vs. medium run elasticities. You are correct, in a sense, in the short run, labor supply is relatively inelastic. Meaning that shift in demand causes fairly large changes in salary. But, in the long run people head off to other industries and the elasticity is greater and the change in salary moderates. At this point the wage rate is probably somewhere between the original wage rate and the "shock" wage rate. Now, in practice the wage rate of employed workers doesn't fall (usually, though the end of the dotcom boom was an exception) - their pay is generally regular. But unemployment for that worker group rises, so the *mean* wage rate of *all* workers - the unemployed plus the employed - decreases. What you are talking about here is known as "wage stickiness". There's recent work on wage stickiness in labor markets but frankly, I'm not up on it. If I weren't in the middle of prepping for finals (and procrastinating on slashdot) I'd read this
And to quote you out of order: I did a minor in Economics at university (major in CS. I'm a developer too), with pretty good marks, particularly in the introductory courses, where econo-jargon is defined. I don't see anything wrong with his statement. Since you did a minor in Economics, I'd recommend a PBS series called "The Commanding Heights". It's not particularly germane to this discussion just really interesting. I'd wager that you're Canadian or British (because everybody in the US calls university "college"). So I suspect it will make your blood boil a little bit because it's flattering of Reagan and Thatcher.
As an aside, I'm an older developer (about 18 years of experience) who went back to do a math/econ degree.
You are not a beautiful or unique snowflake -- but you could be if you got off your ass.
I've taken and aced a handful of university econ courses, and one of the problems I noticed was a massive over-reliance on graphs.
The graphs sometimes contained too much information, somtimes not enough. Nobody understood that when you draw a supply vs demand curve, you're implicitly claiming to know the elasticity (via the slope). On the other hand it only shows you what's going on in one time frame but I rarely see people draw more than one curve per discussion.
A12A.713 is the root of ASC('evil')
Therefore, if you're the type of engineer that is GOOD AT WHAT HE DOES, and gets the job done right the first time, YOU WILL NOT BE OUTSOURCED.
You're looking at it only from an engineering perspective, and you may be right in that perspective. However "IT Outsourcing" does not just refer to engineering or software development. It also covers services and support. A much wider range than what you're pointing to.
I didn't make my original statement without consideration. Several years ago I spent some time as part of a consulting team doing outsourcing evaluations in one services field. Yes, I'm being generic. At the time India was attempting to get into that field, but realistically, they were a joke. The quality of work they were producing was so bad, it was ridiculous. The only thing recommending them at all was that they were doing it for 25% of the cost. There were a number of other outsourcing companies providing this service, with quality ranging from "good" to "oh god no!" The big selling point was always price. There were a lot of organizations looking to cut costs, and this was one of the prime targets.
What we quickly learned was that what these organizations were looking for from us was not an honest evaluation of whether outsourcing this was good for the organization, but a rubber stamp approval of their decision to outsource. One of the worst cases was an organization we did, where the department we evaluated was in the top 1% of the field. Our recommendation was "under no circumstances should you outsource. You have one of the best departments in the country, you'll never find anyone who will give you the quality and performance that you already have." Two weeks after our presentation, they announced their new outsourcing contract, and fired the entire department. The only solace I take from that was that the contract turned into an expensive nightmare for them.
That's why I took exception to the statement that if you're good, you won't be outsourced. Yes, sometimes outsourcing is a good idea. But I've also seen too many cases where it was a bad idea to begin with, but because "it saves money" (even when it doesn't), it still gets done. Competence is no security, sad to say.