The front page of Tuesday's W$J featured an interesting piece on the hidden challenges of hiring workers in faraway places, especially when the goal is saving money ("Some in Silicon Valley Begin to Sour on India") Emphasis added:
Last year, Mr. Shah paid his engineers in India about half of Silicon Valley levels. By early this year, it was 75%... India's software-and-service association puts wage inflation in its industry at 10% to 15% a year. Some tech executives say it's closer to 50%. In the U.S., wage inflation in the software sector is under 3%, according to Moody's Economy.com.
Rafiq Dossani, a scholar at Stanford University's Asia-Pacific Research Center who recently studied the Indian market, found that while most Indian technology workers' wages remain low -- an average $5,000 a year for a new engineer with little experience -- the experienced engineers Silicon Valley companies covet can now cost $60,000 to $100,000 a year. "For the top-level talent, there's an equalization," he says...
Some Indian outsourcing companies are themselves looking to other countries -- mostly as a response to the globalizing nature of their business, but also to tap new labor pools amid a tight hiring situation at home. TCS recently opened a center in Mexico and is planning to move into Morocco. Wipro has two centers in China and is thinking about adding one in the Philippines...
[Wage] increases... have spurred a lot of job-hopping in India. Pervasive Software Inc. of Austin, Texas, opened a Bangalore unit in 2004 and hired 45 people. But soon its turnover was more than 25% a year, says the company's CEO, John Farr. The company kept having to invest in training workers, only to see them leave. A year ago, it shut its Bangalore unit.
Hidden outsourcing costs surfaced for other tech companies as well. To bridge the geographic and time gaps, some have found they need to hire more U.S. managers to handle their Indian teams. Kana Software in Menlo Park has one engineering manager for every 25 to 50 engineers, but it found it needed one for every five to 10 engineers it employed in the Indian city of Chennai. In December 2005, Kana decided to close its Indian operation.
Mr. Khan, Riya's California-based vice president of engineering, says he often stayed up until 4 a.m. so he could talk with the team in Bangalore. Mr. Shah, the chief executive, flew to India six times a year to make sure things were running smoothly.
Straddling time zones slowed development work. Sometimes a researcher gets stuck on a problem. "It's not really a good thing to keep bugging people at midnight every day, so that introduces some delays," says Mr. Dalal. He also felt cut off. "For us sitting here in India, it's hard to get the business aspect of the problem," he says...
Shutting down in India isn't cheap. Teneros, which closed a 30-person operation in New Delhi in late 2005, says it spent $2 million to do so. It had to get out of contracts, and it brought 12 of its Indian workers over to the U.S. on work visas, incurring immigration fees. Teneros left partly because of wage inflation and a lack of information-technology infrastructure that was slowing its work, says its CEO, Steve Lewis. Mr. Shah says Riya's shutdown costs, such as immigration charges and a broken lease, will be in six figures.
He has cleared eight desks in San Mateo for the eight Indian engineers coming over and is waiting for their paperwork to clear, hoping they'll be in Silicon Valley by the end of the year. "I thought I understood India," Mr. Shah says, "but now I know it's so much more effort to have a remote office as a start-up."
The article is instructive in its particulars. One of the things I find most fascinating are the hidden risks some may be incurring in dealing with a partner in one highly stable country ('A') who is turning around and outsourcing to countries B, C, D, and E, each of which is exposed to far more significant risks. (Pop quiz: what former world power used to be talked about enthusiastically in the 1990's as a major source for technical talent... but isn't much anymore? Hint#1: they have some of the highest rates of alcoholism, TB and premature death on the planet. Hint#2: they're sometimes referred to as a deflationary authoritarian kleptocracy with nukes. Hint#3: they use the Cyrillic alphabet.)
As both customer and service-provider, I've dealt with companies operating in India (as well as some headquartered there). The former experience, e.g. talking to a remote call center, is far less unique than it used to be. Few in the U.S. have not been forced at some point to try and deal politely and expeditiously with the intangible but very real challenges of accent, culture, pacing and shared interpersonal communication conventions easy to take for granted--until they're missing.
Dell's withdrawal from India is the most well-known case illustrating that even if all aspects of it cannot be fully defined in advance, customer experience eventually translates to the bottom line--for good or for ill. There's something jarring and difficult that I've never quite been able to put my finger on about sitting down at the end of a long day and dealing with some poor sleep-deprived third-shift worker in India. It's just as difficult--in a different way--to re-read my 2AM e-mail response to a colleague on the other side of the world over coffee the following morning and wince a la Hunter S. Thompson at how poorly my brain must have been working when I wrote it. It may be true that money never sleeps, but like it not we must.
I find the article even more interesting however as a lesson in the increasing fluidity of a global economy and the fundamental uncertainties and complexities of contingent strategic decision-making on such a stage.
Painting with a deliberately broad brush for a moment, I'll assert that difficult-to-revoke choices entailing 'big-bet' consequences tended--in the past--to match the scale of uncertainties with the resources the decision maker had at his or her disposal.
A small business (or her banker) needing to choose a retail location for (say) a bakery has always been able, without much trouble, to scope out the key dimensions of site risk (e.g., sidewalk traffic, local competition, parking, utilities, rent, wage rates for counter help, etc.). By contrast, large multi-national corporations have always been able to afford (whether they chose to or not) to devote several individuals--if not an entire planning department--to analyzing a vast array of long-term economic scenarios and political risks for operating around the globe.
In today's super-connected world however, it's much easier for smaller companies to find themselves making massively risky geopolitical decisions without fully realizing they are doing so and without the ability to assess or the scale and diversity to hedge such decisions. The anecdotes in the WSJ article prove that out.
The point? It's easy to read about globalization and come to the premature conclusion that one is missing out on riches by not plunging in headfirst and surfing a trend that's pervasive. As a friend and former colleague enthusiastically put it to me recently: the future is all about Dubai, Mumbai and Shanghai! That's fine insofar as it goes. This post is not about ignoring globalization but about assessing its complexities and the myriad strategic options it presents with thorough research, appropriate reverence for what is unknowable and sufficient thought about alternatives and contingencies.
Depending on one's business, Dubai, Mumbai and Shanghai may be fine choices--provided one stays aware of (respectively) increasing political and cultural extremism, the aforementioned inflationary flies in the ointment of international wage arbitrage, and the perniciously arbitrary nature of operating in a Communist country.
All may be risks worth taking if one goes in with one's eyes open. Unfortunately some don't. Sound bytes and rumors about the grass being greener make for lousy strategic planning.
Recent Comments