Launching a global project presents many problems that are completely foreign to most project leaders and managers. Last month I pointed out that we have to deal with a lot more than language barriers with global projects. For example, in some cultures, speaking openly is not to be expected, in any setting. For this second installment, I thought I’d share a few concrete ideas for tackling some of these issues, things that can make a real difference and that are easy to put into play. To keep on a theme, I’ll focus on strategies to tackle the common, core issue raised in last month’s article: communication and execution problems. One of the first things I generally want to take a close look at are the techniques and processes used to manage a project. Most of the time, they are not adequate for one reason: They weren’t designed to support a global, multi-cultural organization.
Launching a global project presents many problems that are completely foreign to most project leaders and managers. Understanding the cultural differences, communication differences, and interpersonal relations of a global team is only the beginning. Business environment, local regulatory and compliance issues, and international laws scratch a bit deeper, but managing a global project is more complicated than most project managers anticipate.
Capturing lessons learned at the end of a project sounds like a great idea. Who wouldn’t want to reflect on what was done right, what could be done better, and then apply those lessons to the next project? Unfortunately, few organizations take the time to build the right kind of lessons learned system, and that means critical information is being lost.
Is the key to a successful project in the planning, as the axiom goes… or have we already been lost in the trees? My problem with this is that it’s a very narrow, incomplete answer to a much larger scope problem. Creating the project plan is important, but it’s not “the” key to project success [...]
One of the most significant risks we identify is a globally disparate (geographically separated) team. Teams working in separate regions face tremendous challenges that a co-located team doesn’t have to think about, a situation made worse when outsourcing, where conflicts in language, time, culture, and business environment all affect the organization.
How do you ensure that one person doesn’t derail your entire project? Most of us have been there before. Maybe it’s a co-worker who doesn’t work well with the team. Maybe it’s your boss, who has to oversee every single decision even though he’s an overtasked bottleneck. Either problem poses a critical risk to your project: Delays, mistakes and rework because one person isn’t part of a streamlined effort. Learn how the situation can be improved, realizing positive gains in this habitually entrenched process.