Skip to main content

Co-opetitive Virtual Teams - An Introduction Part 2 - Project Manager Challenges -

I have described in Co-opetitive Virtual Teams - An Introduction the current trend of many companies, who try to cooperate and compete globally to retain their current clients and win more businesses. At this blog, I will open the discussion of the role of the project manager who has a Co-opetitive Virtual Team. (Let's call her Mrs.PM)

Mrs. PM has different challenges than her colleague who work in a non-copetitive virtual team:
  • She needs to balance client stakeholders and a team of competitors!
  • She has to balance the sales team passion of winning more businesses to be able to keep the overall Co-opetitive strategy healthy, But she does not have enough position or coercive power over account/sales team.
  • She has to be able to manage a pool of resources, but these resources are from competing companies , so she need to balance the usage of resources and try to minimize conflict between competing teams!
  • She has to keep all team members - from all groups - motivated and she must to be able convince them that the competitor is not the enemy - try to work with each other, please!
  • She has to make sure that members of the Co-opetitive Virtual Teams communicate effectively and can get things done.
  • She should be able to handle organizational diversity in such co-opetitive virtual environment.
  • She needs to be able to manage her team, who are from different competing entities, with minimum coercive power effectively.
  • She should facilitate sharing of information between her team members, who are from competing entities. Competitors keep critical information from each other, and they also keep their weaknesses secret!
  • If she is in a premature co-opetitive virtual team, She needs to deal with high staff/team members turnover rate, which this will impact standard project constraints - Cost, Quality and Time.Therefore in one project the cycle of Forming, Storming, Norming and Performing may happen several times or it may restart midway through. Obviously, such fluctuation in team development impacts the overall team performance and it is Mrs PM's job to first prevent such changes, and second creates and environment that team goes through such cycle as fast as possible, when a team member gets replaced. This is not easy or almost impossible ,as Mrs PM is an employee of one of the co-opetitive organizations ,and she does not have power/control over her resources whom they are from another co-opetitive organizations!
  • Due to fluctuation in team development, the level of conflict is much higher in Co-Opetitive Virtual Teams and it is Mrs PM's job to make sure conflicts get resolved soon. She needs to be an influential leader.
Some may argue that such project management challenges are same for a project manager who is managing projects in a multinational company - who works with different vendors in one project. Here is a simple comparison to demonstrate the different:

Co-opetitive Virtual Teams 1:
  • Company A, B, C, D, E are located in five different locations in three different time zones.
  • They all have same competencies and skillset.
  • They are after the same market.
  • They are competitors.
  • They decide to create a Co-opetitive Virtual Team to handle a large client globally.
  • Mrs PM is from company A and her resources are from company A, B, C, D and E.
  • Project Owner is from company B, and Project Sponsor is from Client
Co-opetitive Virtual Team 2:
  • Company A, B, C, D, E are located in five different locations in three different time zones.
  • They all have same competencies and skillset.
  • They are after the same market, therefore They are competitors.
  • They decide to create a Co-opetitive Virtual Team to handle a large client globally.
  • Mrs PM is from company A and her resources are from company A, B, C, D and E.
  • Mrs PM has a project manager colleague who is from company B, and they both use the same resource pool to manage their projects.
  • Project Owner 1 is from company C and Project Owner 2 is from company D.
  • Project Sponsor is from company E who get paid from client.
Multinational company with different vendors:
  • Company XYZ is a multinational company and works with four vendors globally on each project.
  • Vendors are Company F, G, H, I
  • Vendors have technology, skillset and competency overlap and therefore are competitors in "some areas."
  • Mr PM is from company XYZ, Project owner is from company XYZ, most likely Project Sponsor is from company XYZ.
  • Both PM and project owner have power over vendors, and they can decide what to buy from each vendor.
At this post , I tried to demonstrate in brief challenges of a project manager at a Co-petitive Virtual Environment and a short comparison with a multinational company with virtual team across the glob. The challenges mentioned here are only organizational challenges and NOT strategic, infrastructure, technology, Human resource & competency challenges. These challenges also influences the ecosystem and as result impact project performance.

Post a Comment

Popular posts from this blog

Escalate, Escalate, Escalate!

What is escalation at organizations? Is it a way to solve problems? Is it a way to report things? Is it a way to put more pressure? Is it a CYA technique? What is it? How do you use it at your organization? How other colleagues of yours use escalation? Really, think about it and observe.

At IT service companies, leadership measures the performance of IT Help Desk by number of escalated work items over a period of time. The less escalation the better. The reasons are simple:

It is cheaper for companies if an IT Help Desk Specialist resolves an issue than an experienced technical specialist at one or two level higher. This is simple math, one gets $X and the other get $X*2And when client gets result fast, he/she will be happier. So, less escalation equals happier client in IT Services. Client raise an issue, IT Help Desk Specialist resolve it, BOOM, Next!

At organizations, It is amazing (sadly) to see how much lower level managers escalate problems, that they and their fellows can resol…

DAD Inception Phase Workshop Agenda

Disciplined Agile Delivery (DAD) realised the reality of the projects and introduced back phases to Agile community. Whoever works in a project based company, especially a project based company where projects are usually less than one year in length and each are for different clients, understands the reality of Agile in such environment. When you start working on a new project for a new client, it is essential to go through a phase that you get to know each other better, to understand the business purpose of the project, to understand the scope of the project, to know what are the high level architecture and what technologies are going to be used and who is the initial team, and if funding is available and also when things must be delivered and to whom.
In answering these questions you may need to meet with different people, run couple of workshops and brainstorming sessions. And this is called Inception Phase. As DAD is more like a goal oriented decision framework and not a prescrip…

Collocation is not the silver bullet for success and agility

To collocate or not to collocate? Most companies that are new to agile have been "consulted" by a "Scrum" Agile Coach, who suggested that they must break their organisation and have cross-functional teams to sit together in one location. Is that the recipe for success?.. Is it really?

Even though collocation has its benefits, it is not the necessary condition for a successful delivery team. Collocation as a dogmatic view may hurt you more than you think, and will not necessarily help you to deliver more successful products.

I am neither for nor against collocation, but I have experienced and worked with both approaches. And each sometimes worked very well and sometimes failed. All the variations of teams geolocation (collocated, fully-dispersed, partially-dispersed, or distributed) can work. It all depends on how the collaboration model is setup, what is the context and conditions, and how much the team and organisation are aware of each other, and are aligned.

Ha…