Offshoring for the project manager. Globalization is here. Are you ready to take advantage of it?


Offshoring to India, China, and other countries is a trend that has steadily gained momentum over the past 15 years. Though offshoring is sometimes seen as a threat to employment, it may also be an opportunity. This paper will outline a practical approach to managing offshored projects. The first section examines some of the most recent trends in the offshoring industry, focusing on information technology (IT) project offshoring. The second section outlines pitfalls in managing offshored engagements. The final section outlines methods a project manager can use to maximize opportunities for successfully managing an offshored project.


IT offshoring is a major business around the world. India is the largest player in this market followed by China. This is already big business and few of us are unaware of a company that is not trying offshoring.

With a trend this large, project managers should be ready to participate in it. After all, you could find yourself with the opportunity to run an offshored project.

This paper will first outline the offshoring industry. Then the challenges and pitfalls of running offshored projects will be discussed. Finally, techniques that can be used to manage successfully offshored projects will be covered.

The Background of Offshoring

The Offshoring Industry

The following is an example of offshoring in the IT industry:

  • Example IT industry:
    • Indian IT exports expected to be near $20 billion this year,
    • Chinese IT exports are estimated to be near $2 billion, and
    • The total global IT Offshoring market (including between developed economies) is estimated to be $50 billion.
  • Offshoring is also occurring in other industries:
    • Business process outsourcing (PBO), and
    • Call centers, accounting, and insurance.

Of course, though IT was one of the first industries to try offshoring, it is now being applied to a wide range on non-IT industries. This list is growing every day.


India is one of the major players in international offshoring. Here are some relevant facts:

  • Population: 1.29 billion people,
  • More than 200,000 technical graduates are produced by Indian universities each year,
  • That number is similar to the number of technical graduates produced in the entire United States,
  • Many Indian universities teach all courses in English, and
  • Starting salary is under $10,000 per year.


China is also a major player in offshoring. Here is a similar list of facts about China:

  • Population: 1.32 billion people,
  • More than 600,000 technical graduates are produced by Chinese universities each year,
  • Three times the number of technical graduates produced in the entire United States,
  • Graduates usually have taken English courses, and
  • Starting salary is under $6,000 per year.

According to the numbers, China produces many more technical graduates than India. However, these figures may include two year and technical degrees, such as mechanics and technicians. The number of technical graduates in China is of course still large.

Other Countries

The following regions also have an active offshoring industry:

  • Eastern Europe (Romania, Russia),
  • Southeast Asia (Philippines), and
  • South America (Brazil).

There are numerous other countries that have or want to have an offshoring industry. Programmers in Romania are available for less than what Indian programmers are currently earning. Russia at one time appeared to be ready to dominate this market with its large pool of highly trained technical people. This may have been slowed by the relative strength of the Russian economy and the value of the ruble. Other countries, such as Brazil, have large populations with their share of technically savvy people available for work.

A key challenge is that though many countries offer outsourcing services, not all of the companies offering those services are experienced in the industry. The big players have likely done engagements similar to a customer’s needs before but it may all be new territory for smaller companies.

With the best and the brightest of these educational systems available, do outsourcing projects always go smoothly? Often times, they do not go smoothly. This sounds like a way for companies to get large teams for a fraction of what it would cost onshore. However, managing large projects with team members on the other side of the world is not easy, and there are many things that can go wrong. There are numerous examples of companies which have tried offshoring only to abandon it when faced with the difficulties.

Potential Problems in Offshored Projects

Of course, running a project with much of the team half way around the world and who may not speak the same language can have potential problems.

The following are some typical problems a project manager on the ground may run into:

  • Language,
  • Time zones,
  • Communication,
  • Team experience,
  • Culture, and
  • Infrastructure.

Time Zones

Here are some of the typical time-related issues:

  • Little is gained from 24-hour work cycle.
  • Can they work during your business hours? They will most likely work their regular hours.
  • Teams need to be ready for early and late meetings.

Most offshored projects are completed with the offshore team in a time zone that is close to 12 hours different than the timezones in the west. Therefore, the team’s working hours will probably not overlap. For example if an offshored team is in Bangalore, India, and the home office is located in New York, the times will be about 10.5 hours apart. Therefore, a 9:00 a.m. meeting New York time would be 7:30 p.m. Bangalore time. When one project I worked on came to a critical point, management meetings had to be scheduled 8:00 a.m. and 10:00 p.m. Eastern time each day in order to ensure issues were communicated promptly.

It is sometimes stated that offshoring will allow the offshore team to work while you sleep and therefore result in the team working more efficiently. This 24-hour team concept is sometimes used as part of the sales process. In fact, the time difference often results in the offshore team waiting for answers while the local team sleeps.

Staff offshore may also be resistant to working late hours, even more so than in North America. You need to remember that the infrastructure offshore is not like that in western countries. There may not be transit available late at night or restaurants open late. Though their management can mandate it, in the hot offshore job market, you may be faced with team members leaving for other jobs if they do not like working off hours.

What usually happens is that the offshore team works their regular hours while the local team works its regular hours. This will inevitably result in important questions coming up while those who can answer them are asleep. Some delays are inevitably caused by this. Of course, this will often have the most impact in key project phases.


  • What will be the common language for most offshored project? Broken English.
  • Their English is usually less fluent than the local teams’ English.
  • The team needs to make sure communications are understood.

Regardless of the amount of language courses the offshore team has taken, there will be some misunderstanding and language difficulties. English will not be their native language. They may not be familiar with all the technical and business terms you are used to. In addition, though English is spoken in India in particular, they will use terms that are not familiar to western ears.

Do not assume they fully understand your question or request. It is easy for information to be lost over phone lines and with time zone differences; communications will have a limited time window. Language will even impact e-mail communication. As English is not their first language, it will take longer for them to write long e-mails and therefore they may tend to send short e-mails when what is really needed is a lot of detailed information to understand the issues. They may also not fully understand everything in the e-mails that are sent to them. It never hurts to confirm their understanding.


Some suggestions to improve intra-team communication:

  • Get good phones,
  • Use instant messaging,
  • Recap what was discussed, and
  • Issue meeting minutes.

It is import to get good conference phones with multiple microphones. Communication will be difficult enough as it is. Teams should make good use of instant messaging. It can allow back and forth communication between team members without the delays of e-mail. It is also an easy way to find out if the offshore team members are still in the office before calls are made. Some people like to use it to send asides to others during phone conferences.

Recapping what was agreed to in meetings and issuing meeting minutes is good general project management practice. It is critical to offshored projects. Sometimes, they did not hear correctly or did not understand the request. Culturally, they may be hesitant to disagree with the customer, client, or project manager publicly in a meeting. Ensure they agree with requests and then provide minutes from the discussions.

Team Experience

Here are some of the typical challenges with team experience:

  • Lower level of general experience,
  • Younger, less experienced management,
  • High turnover! Key skill sets are in high demand, and
  • Shortage of senior staff in many areas.

In general, offshored teams have a lower level of experience than internal teams. Offshoring vendors have a much shorter track record than North American or European companies. The first of these companies emerged in the 1990s. This should color expectations when engaging and planning for offshored engagements. Some organizations expect offshoring companies to be able to succeed in technical areas where local staff have failed or assign them the most challenging projects. Often this has not worked out as well as intended.

Expect less experienced management offshore. Older managers are not used to the western management style and techniques. Younger managers may have modern management training but have less experience then their onshore equivalents. This is likely to impact your project. Some offshore vendors are accredited up to CMM 5 or adhere to other quality methodologies. However, this may not compensate for a less experienced team.

Offshoring is booming, there is high demand for experienced staff and wages are rising. Taken together, these conditions together are a recipe for high turnover. It is necessary to ensure the offshore team, especially the senior positions have back ups in place. It is not unusual to loose several senior team members during the course of a single project.


Managers need to be aware of cultural issues. Here are some of the key areas:

  • Differences in cultures,
  • Deferring to authority vs. questioning decisions,
  • Saving face may be important, and
  • Level of customer focus.

Cultural issues may also have an impact on a project. An example is that the team may be hesitant to highlight problems on the project and may not want to bring forward bad news. They may also defer to authority whether it is the customer’s project manager or their own project manager when perhaps they should be questioning assumptions.

The offshore team may be hesitant to say no. Instead, they may say perhaps, maybe, or not say anything when the answer is really no.

There may also be a strong respect for authority. However, that may not extend through the organization. The project director or vice president may get their requests addressed immediately, while the project manager may be getting frustrated by the lack of responses to requests. I worked on a project where the offshore project manager responded to an offhanded request for a presentation from a client’s vice president and spent more than a week putting it together. Meanwhile, the project action items languished untouched and a team of 20 was lacking direction.


Infrastructure can also be a risk area and can cause delays particularly at the start of the project. Here are some of the areas that can cause issues:

  • Infrastructure vendors overseas may take time to deliver,
  • Latency issues,
  • Overnight access,
  • 24-hour system support, and
  • Infrastructure should be running before the project is to start.

Project teams cannot underestimate the difficulty in getting the infrastructure set up between the main office and offshore. The team will have to set up a remote office, and be able to access all of the main office systems from the offshore office. The technology for this has come a long way in the last few years, however, it is still not necessarily easy, and teams should expect some problems.

For example, latency can cause unexpected problems. The few seconds a signal takes to get to India or China can cause certain systems to fail or not function as they would at the home office. This can apply to internal systems or even to some off the shelf applications the team may be using. Until systems are up and running, the project manager cannot be certain that everything will work seamlessly. There are very likely to be problems and delays.

Making an Offshored Project Successful

There are some steps that can be taken to help ensure an offshored project is successful.

Define Project and Goals

The following questions should be asked right at the beginning of planning for an offshored project:

  • Is in-depth business knowledge required?
  • Is experience with your existing systems or technology required?
  • What are the complex requirements?
  • Are these good candidates?

What a company chooses to offshore is as important or more important then how the team manages the outsourcing engagement. For a successful offshored project, it may be best to select a project that is:

  • self contained,
  • not overly complex, and
  • not requiring too much communication with the onshore organization.

Often the project manager will not have the final say in what project is offshored but the suitability of the project should an input into the risk analysis.

The Onshore Team

Offshored projects require local support to be successful. Some or all of the following people will be required onshore to support the project: program manager, project managers, solution architects, business specialists, leads, and subject matter experts (SMEs). With all of those senior roles required, offshoring does not necessarily mean a large loss of jobs. Sometime the more desirable senior jobs stay onshore while the more junior roles go offshore.


Exchanges are also important tools to improve the likelihood of project success. It is critical to have an offshore representative on site. Furthermore, local team members should be sent overseas during critical periods. With all of the potential problems of communications, it is important to have team exchanges. This can facilitate communication and issue resolution. Nothing can substitute for face-to-face communication after all.

Members of the offshore team will often want to spend time in the west and sometimes it is considered a perk of their positions. During critical periods, such as the project initiation, start of testing, and other key milestones, having an experience person working offshore can resolve issues immediately and speed progress substantially. For example, the offshore team is setting up a complex system and there are 10 critical points where they run into problems and need questions answered. Worst case, these could take 10 full days to work through if you consider a one-day wait for response from onshore. If the right person was on site, perhaps you could get through all the problems in one or two days.


Planning for an offshored project involves taking into account issues that may not impact a on-shore project:

  • Assuming lower level of experience,
  • Lowering productivity,
  • Learning curve,
  • Scheduling very frequent deliverables,
  • Scheduling demos of their progress,
  • Involving your experienced internal staff, and
  • Using peer reviews.

A mistake that some organizations make is to assume the offshore team will be as productive as or more productive than the onshore team. The offshore vendor may be CMM level 5 after all. In fact, though there will be some very proficient team members offshore, and there will also be some junior team members. Assuming a steep learning curve and lower productivity than on-shore staff is the safest.

Because of the distance issues, communications issues, and newness of the offshore team to the client environment, the project manager needs to see what progress the offshore team is making to ensure the final deliverable is what is being paid for. Companies do not want to come to the end of the project and find out that what was built is completely unsuited to the requirements. To avoid this, the project manager should build demos, iterations, or phases into the project plan from the onset. The team should insure that internal staff is involved. Their knowledge and experience will be invaluable to making the project a success.

There are many good reasons to use peer reviews in projects. For an offshored project, these become even more important. Unless onshore team’s review deliverables in detail, they will never be certain that the deliverables meet an organization’s quality needs.


Governance processes need to keep the following issues in mind:

  • Some companies offshore are CMM 5,
  • Processes may not translate,
  • Use your own successful processes, and
  • Have escalation paths in place.

The project manager will need to ensure there are good project governance processes in place. Many companies offshore are certified up to CMM 5. However, their processes may not translate into documents that fit into the client’s internal company standards.

So, whose processes will be used: the clients or the vendors? It is recommended the client try to use its own successful processes and use the vendor’s processes where there is a gap. In addition, it is important that a project have escalation paths in place. If things are not going well with the vendor, the project manager needs to know who to escalate to.

The onshore client will probably want documentation at the end of the day that can be transitioned to the company to become part of the base of documentation. The project manager should therefore plan the type of documentation needed to come out of the project and ensure that the quality of these documents meet the internal standards.


Tracking an offshore project is important to ensure it is progressing as planned. Here are some key points:

  • Difficult to monitor progress due to distances,
  • Schedule early deliverables,
  • Schedule demos, and
  • Iterative approaches.

Distance means it is more difficult to monitor progress offshore. For offshored projects, the project manager cannot walk around to see how things are going. The project manager needs to put in place a formal tracking and monitoring system.

The team should use deliverables that are scheduled early. They should schedule concrete deliverables throughout the project. Demos can also be invaluable to confirm progress and see exactly what work is being done offshore.

Project managers should consider using iterative or phased approaches. This breaks up the project into small pieces so the team can see the results earlier and make any necessary adjustments for future phases. The biggest risk is that at the end of the day, the deliverable from the project has serious flaws. The project manager will want to know about these problems while there is still an opportunity to fix them.

Good Points

There are good points to offshore projects these can include:

  • work ethic,
  • motivation,
  • fill roles that you cannot, and
  • cost.

Offshored jobs are often some of the best available in the host countries and pay the best wages. The offshore team will, therefore, usually be highly motivated. They may work long hours and weekends to meet deadlines. I had an offshore project manager who would send me e-mails at 2:00 a.m. his time, on a regular basis. One of the key reasons that companies use offshoring is that it is easier to fill roles and build a large team quickly through an offshoring vendor.

Can it work?

  • The offshore industry did not grow to where it is without successes,
  • Failures do happen, and
  • If your project succeeds under your leadership where others fail, then it will be a success for the project manager.

Of course, the offshore industry did not grow to where it is without successes. Offshore projects may involve budgets of many millions of dollars. If a large project fails, no one involved will look good. However, an offshore project that is successfully managed with all the challenges involved is a feather in the cap of any project manager.

Agrawal, V., Farrell, D., & Remes, J.K. (2003). Offshoring and Beyond. The McKinsey Quarterly, 2003 Special Edition Issue 4, p24-35

Aspray W., Mayadas F. & Vardi, M.Y. (2006). Globalization and Offshoring of Software, Association of Computing Machinery (ACM).

Balasubramaniyan, M. & Guyer, L. (2004, July 5). Face Off: Do offshoring’s benefits outweigh its drawbacks? Network World 21 (7) 42.

Bardhan, A.D. & Kroll, C. (2003). The New Wave of Outsourcing. Research Report 1103, University of California, Berkeley: Fisher Center for Real Estate & Urban Economics

Bardhan, A.D., Jaffee, D., & Kroll, C. (2004). Globalization and a High-Tech Economy: California, the United States and Beyond. New York, NY: Springer.

Fannin, R. (2004,May). India’s Outsourcing Boom. Chief Executive 28-32.

Friedman, T. (2005. The World is Flat. New York, NY: Picador.

Gereffi, Gary. & Wadhwa, V. (December, 2005). Framing the Engineering Outsourcing Debate: Placing the United States on a Level Playing Field with China and India; Durham, NC: Master of Engineering Management Program – Duke University

Hagel, J. III (2004). Offshoring Goes on the Offensive. The McKensey Quarterly 2, 82-91.

Hira, R. (2003). Utilizing Immigration Regulations as a Competitive Advantage: An Additional Explanation for India’s Success in Exporting Information Technology Services. New York, NY: Center for Science, Policy, and Outcomes, Columbia University (March).

Huws, U., Dahlmann, S., & Flecker, J. (2004). Outsourcing of ICT and Related Services in the EU. European Foundation for the Improvement of Living and Working Conditions. Dublin, Ireland.

Kletzer, L. (2004, December). Trade-Related Job Loss and Wage Insurance: A Synthetic Review. Review of International Economics 12 (5) 724-748.

Mann, C. (2004, July/Aug). What Global Sourcing Means for U.S. IT Workers and for the U.S. Economy. Virtual Machines 2, (5)

Moore, S (2004) For Newcomers to Offshore: Leveraging What’s Out There; Forrester Research, Inc. ,

Wessel, D. (2004 April 2). The Barbell Effect. Wall Street Journal (April 2) A1.

This material has been reproduced with the permission of the copyright owner. Unauthorized reproduction of this material is strictly prohibited. For permission to reproduce this material, please contact PMI or any listed author.

© 2008, Pedro Serrador
Originally published as a part of 2008 PMI Global Congress Proceedings – Denver, USA



Related Content