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.
You can put your ideas to the test by putting them on trial. A very successful team building and idea vetting exercise is to literally organize a mock trail, with prosecuting and defending teams and even a jury. Not only is it fun, but it can be eye-opening: “It was one of the better things we’ve done in a long time,” says Richard D. Fain, chairman and C.E.O. of Royal Caribbean Cruises.
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.
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.
Risk management has become mainstream. It’s no longer the domain of rocket scientists and actuaries. In fact, it’s become so mainstream that formal risk management practices are showing up everywhere we look. But is all this sudden attention to risk management going in the right direction? Or are recently defined risk management methods just introducing unproven, sometimes crackpot solutions into a well-understood space? Find out why Harvard Business Review found that “Most of the management tools and techniques we studied had no direct causal relationship to superior business performance.”
Get your team to write an obituary for your project — before you start the project. Make it part of your risk planning exercise. This exercise is related to the Merlin backward planning exercise and is also used in the Toyota Production System. Toyota used the obituary approach when creating their “Toyota University” program and engaged [...]
Organizations that are “training challenged” must learn to do things differently. This includes delegating authority along with responsibility, being inspirational to employees, building trust and improving communication — all of which are direct benefits of a comprehensive process that incorporates training. Take a look at part two of Should Training be an Integral Part of [...]
Training budgets are one of the first to go in a down economy. I first pointed this out in Finding Strategic Learning Funds, but there’s ample evidence to be gathered. When the money isn’t there, organizations start casting about for any program they deem expendable. But the unfortunate truth is that training is the best [...]
Testing, testing, testing. In a recent article by John Parkinson (Strong Signals, CIO Insight magazine) the value of testing is raised on par with the activity of design and coding itself: Testing is becoming as necessary a profession as design and coding. Skills and experience matter. Process matters. Tools matter. Let the tests begin. Our [...]
The price of software problems is very high: As much as 50% of development and 100% of all maintenance costs can be attributed to software defects. Often, this price becomes apparent late in the software life cycle—quite often after the software has reached its operational phase (after the software ships)—as previously undetected defects are discovered [...]