Project Management

Please login or join to subscribe to this thread

How to Move from Competion to Cooperation?

linkedin twitter facebook   Communications Management   Complexity   Organizational Culture  
avatar
Gwenola Michaud
Community Champion
Project Manager & Advisor| Geosciences & Monitoring Consulting Milano, Italy

Competition is natural—especially among ambitious individuals striving to grow, innovate, and lead. In many cases, it drives performance and progress.

However, it can also create silos or unintentionally undermine collaboration.

As project managers, how do you help shift the dynamic from individual competition to effective cooperation?

  1. Do you focus on reinforcing common objectives?
  2. Align incentives and success metrics?
  3. Create shared accountability?

Curious to hear your experiences and practical approaches.

Sort By:
avatar
Piotr Lis Plano, Tx, United States
Moving from competition to cooperation means shifting the focus from “winning against others” to “winning together.” It doesn’t happen by accident, you have to design it into how you work.
avatar
Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal

This discussion takes the question to a different level.

The challenge is no longer just moving from competition to cooperation between people, but ensuring coherence across humans, agents, and systems.

In AI-enabled environments, competition does not disappear. It shifts level.

If not intentionally designed, we get:

  • Humans optimizing local outcomes
  • AI agents optimizing their own metrics
  • Teams appearing aligned, while decisions fragment underneath

This creates a new risk:

Not conflict, but misaligned collaboration at scale.

So the question becomes architectural:

Who decides what?

How are trade-offs integrated?

What defines success at system level?

And this is where a critical distinction emerges:

It is not about keeping humans in the loop to validate every decision.

That creates bottlenecks and limits scale.

It is about placing humans in command.

Not as approvers of micro-decisions, but as designers of:

  • Decision boundaries
  • Operational constraints
  • Ethical guardrails

We do not need humans checking every action.

We need humans defining the decision architecture the system cannot violate.

Because agents will do exactly what they are designed and measured to do.

If KPIs are local, they will compete.

If value is systemic, they can cooperate.

But there is another layer often overlooked:

In an agent-driven environment, governance is no longer a document.

It becomes part of the runtime.

If cost is optimized at the expense of risk or ethics, that is not an efficiency issue.

It is a governance failure by design.

Which means:

Ethical and organizational principles must be embedded into how the system operates, not added afterwards.

Finally, this also challenges how we think about projects themselves.

AI systems are not static deliverables.

They are evolving, learning ecosystems.

So success is no longer just delivering an output.

It is maintaining the integrity, coherence, and resilience of the system over time.

In practice, this elevates the role of project management:

  • From coordinating work to designing decision systems
  • From managing stakeholders to orchestrating human–agent contribution
  • From delivering outputs to sustaining adaptive systems

So the shift is clear:

Collaboration is not a soft skill.

It is a design responsibility.

And if governance is not embedded into execution, we do not have a collaboration problem.

We have a systemic governance failure, amplified by the speed of AI.

Cooperation, in this context, is not encouraged.

It is engineered.

avatar
Lissette Indhira Pimentel Sosa
Community Champion
Program Manager| HARPER SRL Santo Domingo / Distrito Nacional, Dominican Republic
If cooperation is not designed into how people work, competition just fills the gap.

The shift usually happens when success is shared. If people are measured individually, they will compete. If outcomes are shared, they start working differently.

Making dependencies visible also helps. When teams see how their work affects others, collaboration turns out to be more natural.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"If you work on a lobster boat, sneaking up behind people and pinching them is probably a joke that gets old real fast."

- Jack Handey

ADVERTISEMENT

Sponsors