Skip to main content

Tag: Team

The Three Myths of Virtual Team Leadership

I recently worked with a virtual team that was developing and rolling out a new product across many European countries. One colleague in London refused point blank to cooperate with another colleague who was based in Amsterdam. When I asked why, I was told that my English colleague found his Dutch counterpart rude and offensive-even though they had never actually met or spoken. When I dug deeper, it became clear that the real issue was about culture and style: the Dutch team member, for time management reasons, only checked his e-mails once a day, used a far more direct form of speaking than his English counterpart, and wrote his e-mails all in capital letters. His English colleague felt he was being ignored and, when he did get a response, that his Dutch colleague was SHOUTING AT HIM!

This is typical of the problems that occur when a team is spread across time zones, national borders or cultural boundaries. A virtual team does not have the same advantage as a team whose members meet face-to-face on a regular basis-when all the team members are inside the “30-foot limit.” Unconsciously, people pick up innumerable subtle cues when operating face to face with colleagues. We acquire information about our colleagues, including what is acceptable behaviour and what is not through observation. Inside the30-foot limit, people find ways to work together without even being aware of it. When we have no face-to-face experience with our new team colleagues, our communication lacks a certain richness. And because we don’t consciously attend to these things when we’re in close propinquity, we don’t appreciate their importance. As a result, the importance of these activities is often overlooked when working with remote teams. To ensure success, the virtual team leader must avoid being seduced by the three myths of virtual teams and must proactively attend to providing the social richness that virtual communication lacks.

The Reality of Virtual Teams

What can you do? At the start of the project, bring team members together in a start-up session so that they can meet each other face to face and socialize. This meeting will establish relationships in a way that is only possible when people are in each other’s physical presence. Human beings can relate to, start to trust, and feel responsibility towards someone they have met in ways that aren’t possible with a stranger.

Use this meeting to involve the team in developing team processes. This includes mapping dependencies between members, articulating their expectations of each other, and explicitly discussing and agreeing on the protocols that will operate between team members. The process-setting portion of the meeting may be the “official” reason for holding this meeting. This involvement will also create commitment and buy-in among the team members for these processes. If the start-up meeting isn’t feasible because of cost or time constraints, you should ensure that any complex work that requires close collaboration is handled by team members working inside the 30-foot limit.

Another option is to have key team members visit their remote colleagues to establish relationships and agree how they will work together. If neither of these options is feasible, be sure that your timeline and budget allow for the additional problems, delays and rework likely to be caused by mistaken assumptions, misunderstandings and conflict. During the life of the project, make sure that all team members are kept up to date on its progress, both what is going well and what is still to be achieved. This helps both to reduce the “outpost syndrome” and to show team members where they fit into the big picture. Repeat and reinforce the agreements made during the initial face-to-face meeting.

The Three Myths of Virtual Teams

As a virtual team leader, you must reject these three myths:

Myth #1

“My virtual team will be successful because they all share a common goal.”

Clarity of purpose and a compelling vision of success is a prerequisite for all high-performing teams. However, outside the 30-foot limit, the shared context that vision provides gets lost or forgotten if it isn’t reinforced daily through words and actions. You must ensure that everyone is up to date with the team’s progress and that expectations and dependencies between team members are understood.

Myth #2

“My virtual team will be successful because I have the best people on it.”

Individuals who perform at a high level in a co-located team situation aren’t guaranteed to operate well in a virtual or remote team. Often, individuals who find themselves working alone stop feeling connected to the team-an emotional state known as the “outpost syndrome.”

Myth #3

“My virtual team will be successful if technology is in place to allow them to communicate.”

It is, of course, vital that appropriate technology be evaluated and deployed in a considered and planned manner (and subsequently monitored to ensure it delivers the expected results). But, with due respect to all currently available technology, technology cannot and does not replicate human communication: technology doesn’t provide the same richness as that of people working in close proximity. The successful virtual team leader recognizes this gap and takes action to bridge it by addressing the human factors that technology filters out. As a team leader, you must initiate action to support the transition to remote working as well as develop team processes and enable a feeling of connection to prevent the outpost syndrome.


Judi Williams is the owner of Great Beginnings Limited and an author and instructor with Learning Tree International. Great Beginnings offers tailor-made training solutions. They design and develop a wide variety of training and professional support material such as fully immersive classroom training, interactive e-learning tools, video-based training, downloadable products etc. Judi has authored a number of courses for Learning Tree International such as The Art of Coaching, Effective Time Management and Personal Skills for Professional Excellence.

The Virtues of Virtualization

Virtualization technologies have graduated to the big time, but it didn’t happen overnight. While early virtualization application experiments can be traced back to the 1960s, it is only in the past decade that there has been growing acceptance of this cost-saving technology.

Foreshadowing new virtualization breakthroughs, a 2006 IDC analysis projected that companies would spend more money to power and cool servers by 2009 than they would spend on the servers in the first place. And a recent Goldman Sachs survey of corporate technology users found that 45% of respondents expect to virtualize more than 30% of their servers (up from only 7% today).

The heart and lifeblood of virtualization consists in using a hypervisor (software that provides a virtual machine environment), situated between the hardware and the virtual machine. The virtual machine is, in essence, data, while its applications files are stored on a physical server or on a remote storage device. The result is that the virtual machine has portability, which translates into a strategic advantage in adverse situations.

Virtualization technologies have come a long way, says James Geis, director of integrated solutions development at Boston IT consulting firm Forsythe Solutions, because evaluating capacity was once difficult. Thanks to improved capacity management tools, that task has been simplified and has become a mainstream means for resource planning.

Geis also notes that, while massive adoption of virtualization solutions has become commonplace, not all servers and applications are meant to be virtualized. The choice, he says, of when, where, and how an application can be virtualized should be based on performance metrics. “There are cases where processing, memory, storage, and network requirements dictate a solely dedicated server.”

However, the value of virtualization as an enduring strategy for continued growth is enormous. Geis outlines the following benefits:

Capacity optimization. Virtualization places capacity planning and optimization at the forefront of data center management. Properly implemented, it produces the maximum return on investment per server dollar.

Rapid server provisioning. Speed and accuracy are essential in a frenetic virtual business environment. Using a server template, virtual servers can be created effortlessly. Geis says new server provisioning takes minutes or seconds, rather than the days or weeks required to procure a new box and install an operating system and software.

Server portability. Virtual servers and the applications they support can be easily moved or copied to other hardware, independent of physical location or processor type. This feature alone provides unlimited flexibility for hosting servers and applications on any combination of physical hardware.

Reduced hardware, facilities, and HR expenses. Fewer server boxes cost less, take up less floor space, require less electricity and air conditioning, and require less maintenance, thus reducing costs related to hardware procurement, real estate, utilities, and human resources.

Larry Honarvar, vice president, consulting services, at CGI, a Montreal-based IT and systems integration consulting company, employs virtualization technologies in the following areas: managed services, software development and maintenance, and hosting solutions.

For software development, virtualization better leverages hardware and software investments, Honarvar says. This works well, given the fact that customers are often scattered around the globe, working in different time zones. “Virtualization makes better use of our infrastructure investments because it allows us to test different development and testing environments. It lets us control costs and redirect funding into product maintenance and enhancement,” he explains.

In hosting solutions, CGI employs virtualization solutions to maximize services and, at the same time, contain costs. Honarvar stresses that a compelling selling point for clients is that virtualization offers transparency. “They see the benefit of being able to have more environments pre-configured and quickly available to map their needs.”

The virtualization solutions marketplace gets bigger every year. Many companies are turning out half a dozen virtualization solutions a year. Here are two examples:

Toronto-based company Asigra has developed a line of backup and recovery services. Its Multi-Tiered Storage Billing System is designed to save the time and expense of developing or modifying an existing billing system, which the company says could run up to thousands of dollars. Its features include “agentless simplicity” (software is installed on only one node, whether the customer has one PC or hundreds); advanced security features (authentication, encryption and non-escrowed keys); and autonomic healing (provides managed backup/restore services for customers).

Ottawa-headquartered Mitel has introduced a number of communication tools for small and medium-size businesses, offering reporting and a signaling protocol called SIP (Session Initiation Protocol) capabilities. Mitel is aggressively promoting its Business Dashboard, which allows companies to track call activity on an internal IP network with both historical and real-time reporting. It collects trend data on call volumes and times, and trunk usage. Its neatest feature is tracking the path of a single call through internal systems and departments, which makes for accurate management of calls.

And that’s just a brief sampling of the virtualization technologies on the market. Look for aggressive new startup companies from all over the globe to jump into this application-rich, expanding niche.


Bob Weinstein is a science and technology writer with Troy Media Corporation.

The Teamwork Model

People fall into the following three levels of teamwork:

Level 1: Individuals. Individual performers on solo projects.  Within a limited scope individuals can deliver exceptional results.

Level 2: Groups. A group includes the participants and a leader.  The team’s final product is a joint contribution and reflects the strength of the group as a whole.  Teams at this level take time and require a stable environment to build working relationships amongst the participants.

Level 3: A Collection of Individuals. This level of teamwork exemplifies the positive attributes of individuals and groups.  A Collection of Individuals is able to tackle the most ambitious and difficult projects.  Each member is a master craftsman.  At this level of teamwork the product reflects the strengths of individual participants and the group as a whole.  Level 3 teams typically do not require a stable environment and may, in fact, thrive under changing circumstances.

The business world demands that Collections of Individuals be formed on an ad hoc basis.  In many cases it is neither cost effective nor an efficient use of resources to commit a group of people to the same set of tasks for any length of time. While it may be unrealistic to expect a level of true mastery from everyone it should be the goal we all strive to achieve.

Re-Focusing and Re-Energizing Teams

How would you measure your efforts to involve the entire workforce in resolving problems that inhibit productivity and their ability to succeed? Although there are exceptions to every rule, it is a relatively safe hypothesis that most people want some control over how they perform their jobs each day. A key factor in the success of teams assembled to analyze problems, define requirements and offer solutions is how management responds to those suggestions. If those suggestions are accepted and acted upon, this is often the catalyst for motivating the team to reach for, and achieve, higher levels of quality.

In my experience, teams that are most successful and have the longest life span are those with the fewest layers of “leaders.” Each leader added into the mix represents opportunity to compromise the effectiveness of communication within the organization. On high performing teams, leadership is a shared role. All members are developed to take a leadership role as required. This structure increases the feeling of responsibility for all members.

Reviving excitement in a team is a considerable challenge that can be accomplished if the team can be convinced their efforts are important and will be rewarded. The first step is to understand the causes of the team’s loss of focus. Successful teams often “cool-off” or lose interest more frequently than those who are struggling. The reason for the loss of focus is often boredom. Teams need a reason to remain excited and motivated. Each team is different and will be excited and motivated by different things. Your challenge is to understand what will excite your teams and motivate them to see the value and pay-off for the projects you’re advocating.

Many organizations complain about not having enough time to get their products out, and their inability to meet delivery schedules. In this case, the paramount question becomes: How can the performance of the teams be improved? First, it becomes critical to understand why there is a persistent problem in order to move forward with attempts to refocus the teams. Is the pressure to meet schedules due to insufficient staff to handle the work, a need for better processes, or people not adhering to the processes?

If the perception is that team meetings will only take away time required to complete the work, it is going to be very difficult, if not impossible, to refocus the teams. This is a prime opportunity for management to evaluate the current situation, and solicit the help of the teams to reach viable solutions. If there are not enough people to complete the work, it is going to be difficult to address the problem through the efforts of the teams. However, if the problems can be addressed through process improvements, this is an excellent opportunity to return excitement and motivation to your teams by asking them to improve the processes. I have always found it necessary to know the members of a team as individuals in order to achieve optimum results. Coaching the managers closest to the teams to attempt to understand what motivates each person, and rewarding the person accordingly, will help keep the teams focused. It is also important to demonstrate that their outputs are important. This means that meetings must be treated as work. They must be scheduled the same as other tasks, with attendance manadatory.


Dr. W. Pearl Maxwell is a Principal Consultant at Advanced Management Services, Inc. (AMS), a full service management consultancy servicing an international client base. Since 1989, Pearl has developed a successful career as an organizational development practitioner, professional trainer and keynote speaker. Pearl has extensive experience working with process improvement and reengineering initiatives helping clients, such as SCC, Sprint, Rehab Care, Symphony Health Services, to create functional business models for enhanced organizational productivity.

Tools of the Trade Part II; Implementing a Requirements Management Tool

Part one in this series described how to prepare, plan, and select a requirements management tool. Selecting the tool is usually the easy part. Implementing the tool without causing mass chaos brings a greater challenge. Now that a tool has been selected, what is the best way to gain acceptance and adoption of the tool within your organization? Change rarely comes without some resistance. This article will address how to maneuver through the resistance in order to successfully implement a requirements management tool by recruiting early adopters, marketing the tool, and communicating the change early and often. Finally, I will address some lessons learned while implementing a tool at several organizations.

Implement a Tool

Production is not the application of tools to materials, but logic to work.
~ Peter F. Drucker

Form a Team

Once the tool is purchased, implementation will take some planning, training, and mentoring in order to effectively rollout the tool. If you haven’t already, start with forming an implementation team. This team will represent the tool and its benefits to the greater IT department. The team will also help plan, create guidelines and best practices, and mentor analysts in their given departments.

Treat this implementation just like you would any other IT project. Start with a project plan, determine implementation tasks, and assign resources. Then execute on the plan.

Once the project plan is in place, get the team members completely trained and comfortable with the tool. At one organization we brought in the tool vendor to train the team members and a few key QA folks. We gave the vendor some samples of use cases from our own projects and utilized these as examples during the training. Team members then began using the tool on their own projects. As we met together we learned from our own experiences and utilized these experiences to draft best practice guidelines for the organization. Best practices included how to structure requirements within the tool, creating templates for different types of projects, naming conventions, and tips and tricks for some of the tool’s quirks.

Recruit Early Adopters

Once the team has established some guidelines and tested the tool out on their own projects, it is time to branch out. Find a few experienced analysts who are willing to be early adopters of the tool. Have team members train and mentor the early adopters on how to use the tool. Early adopters should then go through a complete project lifecycle while using the tool. Periodically touch base with early adopters to apply what they learned from their experience to the best practice guidelines. Also, gather feedback from the developers and QA team members on their perceptions of the tool. Since these groups typically consume the output of requirements gathering, they will need to accept the tool and perhaps adapt their work habits to accommodate a new method for managing requirements. Don’t underestimate this change!

Communicate Early and Often

As with any change, there will always be nay-sayers and skeptics. Implementing a requirements management tool will be no different. In fact, writing requirements in a tool rather than a Microsoft Word document requires a change in mindset. This change is easy for some to make and difficult for others. The implementation team can smooth this transition through communication. Hold forums where the tool is demonstrated, the benefits and limitations are discussed, and early adopters’ experiences are shared. Hold these forums on a regular basis so that teams are kept informed as to the progress, and reminded of the tools benefits.

Word-of-mouth advertising will go a long way to help encourage other analysts to adopt the tool. Have the early adopters talk about their experiences and spread the good news throughout their teams. After trying the tool on a few development projects, one early adopter expressed his enthusiasm for the tool stating “I want to write all of my requirements in this tool.” By trying the tool out on a few simpler projects, he became comfortable with the tool, its limitations, and saw the benefits gained from utilizing the tool. We harnessed his enthusiasm to help sell the tool during an analyst open forum. He also spread the word to his immediate team members and more people signed up to use the tool on their next project.

An Excuse to Celebrate

Finally, use the tool as an excuse for a party! At one organization, to gather excitement for the event, we hosted online trivia questions on our SharePoint site. We posted daily questions and the top five winners received gift certificates to the event establishment. At the event we re-iterated the benefits of the tool, provided links to training simulations, demonstrated examples of successful projects, and distributed the best practice guidelines. Once the formalities were complete, we broke out the entertainment and used the opportunity to socialize with our peers.

When it was all said and done, the tool implementation was really a non-event. There was no loud outcry, no grumbling amongst peers, no mass chaos, and no wasted money. We methodically went about our task of implementing the selected tool, sought help from our peers, and repeatedly delivered the same message throughout the organization which resulted in an easy transition to tool adoption. The complete process took about a year. We steadily increased user adoption during that year and by the time we held our event, most people had already begun using the tool. Compared with the previous implementation of a tool mentioned in part one, where little thought went into the needs of the user community, this tool implementation went off without a hitch.

Final Thoughts

Wisdom too often never comes, and so one ought not to reject it merely because it comes late.
~Felix Frankfurter

Despite the claims of many vendors, no tool is perfect. It is better to discover early on in the process the limitations of the requirements management tool. Once you know the limitations, devise a plan on how to work around the limitations and minimize the impact to your organization.

Test the performance of the application prior to purchasing. One of the biggest frustrations of a tool I have personally used is its inability to perform when multiple users are accessing the repository. Loading some projects will take 10 minutes or longer, while working in other projects completely freezes the tool. If at all possible, learn this before you buy! It will save you great frustration and keep analysts productive.

Never underestimate an employee’s need to resist change. It’s only natural. We all do it. Plan for it, accept it, and continue to communicate the benefits of the tool even when met with organizational resistance. Eventually people come around and the use of the tool will become a part of daily life within the organization.

Finally, learn from your experiences. Have an open mind and listen to the experiences of early adopters and implementation team members. Tout your successes and learn from your failures. Success will, undoubtedly, follow.


Renee Saint-Louis is a Senior Systems Analyst with a subsidiary of The Schwan Food Company where she established and led an Analyst Center of Excellence. Prior to joining Schwan, Renee served as the Requirements Elicitation Practice Lead at a large insurance company. Renee has been a practicing analyst for more than 10 years.