Skip to main content

Co-opetitive Virtual Teams - An Introduction

Global economy demanded experts to solve the dilemma of distributed teams productivity over the past several years and there are still many researches going on regarding workflow and productivity of such teams. Technology evolved and resolved many problems of distributed teams. Virtual teams enhanced productivity by applying new technologies and companies invested fortunes on infrastructure. However, the global economy demands more solutions for an even more complex problem, I would like to call it Co-opetitive Virtual Teams. 

In today's open society and competitive business environment, competitors realized that creating coalition serves them the best in winning businesses. Such coalition happens between companies in different geographical locations and mostly in service industries. They are at different offices in one city or country, sometimes they are in different countries, sometimes they are in different continent and often it is a hybrid of all above!

While these companies serve a client and try to stay as cooperative as possible, they also compete in getting new businesses (new client) and try to win over each other by all means. It sometimes get more complicated when they compete in getting more business from the same client that they agreed to create the coalition at the first place, and all is legitimate!

The concept of co-opeition is fairly new to business world. Some may argue that the basic concept started from Theory of Games of Economic Behavior in 40s or 50s. But it did not get into main stream business vocabulary until 1997, when Adam Brandenburger and Barry Nalebuff published their best selling book. In their book, they describe co-opetition as follow:
CO-OPETITION is a new way of thinking about business. Some people see business entirely as competition. They think doing business is waging war and assume they can't win unless somebody else loses. Other people see business entirely as co-operation-teams and partnerships. But business is both co-operation and competition. It's CO-OPETITION. That's why we've chosen CO-OPETITION as our title, a word coined by Ray Noorda, founder of the networking software company Novell: "You have to compete and cooperate at the same time."
That is true, you need to compete and cooperate at the same time, But when it comes to a global economy with virtual teams distributed all around, then competition and cooperation gets little bit more tricky! Imagine seven competing companies distributed in 5 different countries in three different time zones serve the same client(s) and share their resources with each other in one pool. The main question here is , how several companies who are direct competitors and have almost the same skill-set can cooperate effectively and with high productivity globally?

The answer is more moral related than a technology or processes solution. They simply need to take risk and trust and try to not make problems for each other, And they all MAY need to practice disciplined Buddhism or Zen to control their fear and greed!

At the end, I think this is a new trend that researchers need to work on these days. there are many examples out there and businesses are eager to have some solutions for such mess!

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…

Moving from Basic DAD Scrum Based LifeCycle to Continues Delivery (Kanban Based) Lifecycle

I was thinking what the title of this blog post could be, I had couple of options to select from and decided to use a title that uses Disciplined Agile (DA 2.0) Lifecycle. Other options for titles were: Moving From Scrum to KanbanFrom High Performing Scrum Teams to Hyper Performing Kanban  The bottom line is that at some point you may want to move away from Time boxes to a flow of work and service oriented teams and improve performance and throughput without massive and sudden organisational change.  As always, I only share my experience and this may not apply to all situations, context is important. 
Another reason that I selected “Moving from Basic DAD Scrum Based LifeCycle to Continues Delivery (Kanban Based) Lifecycle” as the title, was that for many it is a question mark how to navigate through DAD life cycles. and I think this blog post could be one of the ways to navigate. 
Context: A Delivery Team started with Type A Scrum with 2 weeks Sprints. After a while, they deploy their …

New Organisational Model For Project Based Companies

Elliot Goldratt suggested a Strategy Tree for project based companies. While that may work for some companies, it will not work for knowledge based workers or Software Development Companies, or Digital Agencies. On the other hand traditional resource planning and resource allocation is also not effective despite all the effort one put into it to make it less of a command and control model - Here I assume we know who are knowledge workers and how their productivity works, Peter Drucker has a fantastic article about Knowledge Workers that I highly recommend you to read, if you have not read it yet:
Also, it has been proven that stable teams work better together on long term projects in software development. However, almost majority of software development companies or digital agencies break teams and reassemble them based on new projects or clients. This creates unnecessary complication and waste w…