I had the unrealistic expectation that we would just offshore our product development and "poof," we would realize great savings in time and money. Contrary to my rosy expectations, the only "poof" was the sound of our investment going up in smoke. I have since found there are many strategies to mitigate the stress caused by a lack of preparation and understanding.
We all know why companies are offshoring software development. I mean, how can you not save money when offshore developers can make an annual salary equal to the cost of a widescreen plasma HDTV? But just like everything else in life, it is very easy not to save money if you do not plan and prepare. Sure there are other benefits, like gaining productivity with a potential round-the-clock work day, but when it comes down to it companies are choosing to offshore because of the lure of cutting costs.
I'm not here to argue with the Lou Dobbses of the world who believe offshoring is detrimental to the U.S. economy. The fact is we live in a global economy and companies will continue to offshore as a competitive response. Therefore plenty of U.S. managers will have to cope with these offshore projects.
Don't Downplay Cultural Differences
To gain additional perspective, I spoke with Tiffany Mura, president of bizprox, LLC, a management consultancy based in Boston. Mura has managed multiple offshore projects, and I found she had similar initial experiences.
"We ventured into offshoring for the same cost-saving reasons that are fueling this trend. However, we had a more difficult time than anticipated in realizing the benefits," says Mura. "We ran into cultural differences and communication issues, along with the unexpected difficulties in dealing with the time difference in India."
In Mura's case, they did not discover the severity of these issues until the first code delivery. "When we were evaluating the offshore firm, they did a good job of convincing us of their stable, repeatable processes. However, when we looked at the initial project, there was no consistency in the standards and documentation," says Mura. "The worst part was that when we went to install in our customer's environment, the software didn't work, because the target environment configuration was not documented. So the offshore firm did not build or test for the right environment."
Another unexpected issue was in dealing with the time difference. Although there can be a time-to-market advantage if you have resources working around the clock, these benefits may not inspire your state-side personnel to enjoy attending status meetings at 6 a.m. or 11 p.m.
According to Mura, many of her project managers, who had never dealt with offshore projects before, balked at this unorthodox schedule.
"Our team did not care for the extended work day, because it was something that they believed was forced upon them. Additionally, they didn't like the pressure of having to get our state-side work completed before the end of the day. This was because if we didn't provide our offshore team with what they needed before we went to sleep, then we could lose an entire day of work on their end."
Mura says the worst part was during crunch time, when key state-side resources had to be on call throughout the night to answer critical, time-sensitive questions.
Ease Into Any Outsourcing Relationship
What to do about these pitfalls? There are several proactive steps you can take.
Start small with a project that isn't mission critical. This will lower your risk as your team learns the ropes. It also will make it easier for you to feel out the offshore firm's standard processes. Even if they are ISO- or CMM-certified, daily execution is what really matters.
Provide your team with an "introduction to offshoring" training where you can directly address their concerns and how to eliminate common problems. Companies like Intel have had success providing managers with "cultural sensitivity" training that addressed issues upfront.