# Google Project Oxygen: Collaborate across the company as a manager

**Collaborate across the company** means getting results through peers and partners, not only your reporting line.
          Project Oxygen added this because modern delivery is cross-team by default.
          Map stakeholders, share outcomes, and make cooperation easier than escalation theater.
        

        
## Scenario: the slipping dependency

        

          Another team owns an API your launch needs. Dates slip. Slack gets sharp. Both managers feel blamed.
          Your team wants you to "escalate harder." Their team wants you to "stop changing requirements."
        

        

          Collaboration starts with a shared definition of done, a single joint owner for the interface, and a meeting that ends with tradeoffs, not venting.
        

        
## Cross-company habits

        

          - Stakeholder map: who decides, who advises, who is informed.

          - Shared outcome written in one sentence both teams accept.

          - Interface owner and decision date.

          - Escalate with options, not only frustration.

        

        
## Conversation script with a peer manager

        

          - "Here is the customer outcome we both serve."

          - "Here is what my team can flex; here is what we cannot."

          - "What constraints are you under that I am missing?"

          - "What joint plan makes both of us successful this month?"

        

        
## How iSilta helps

        

          Honest gap: iSilta is team- and 1:1-centric, not a cross-org workflow tool.
          **Handbook** and company listening can reinforce collaboration norms, but stakeholder maps, joint OKRs, and peer negotiation are practices you run in the work system you already use.
        

        
## Manager map

        
| Failure | Why | Collaborate move |
| --- | --- | --- |
| Blame Slack | No shared outcome | Write one joint goal |
| Surprise escalation | Peer feels ambushed | Preview options first |
| Hidden requirements | Moving target | Freeze interface + change log |

        
## Bottom line

        

          Collaboration is how Oxygen-scale managers deliver in matrixed orgs.
          Make partners successful on purpose. Escalation is a tool, not a personality.
          Hub:
          [10 manager behaviors](https://isilta.com/blog/google-project-oxygen-10-manager-behaviors/).

## Frequently asked questions

### When should I escalate?

After a good-faith peer attempt, with a clear decision needed, options, and business impact. Escalate to resolve, not to punish.

### How do I collaborate with a difficult peer?

Document shared outcomes, bring witnesses to agreements, and keep proposals practical. Minimize one-on-one fog if trust is low.

### Does collaboration mean never competing for resources?

You will still compete. Do it with transparent tradeoffs and respect. Scorched earth wins quarters and loses years.

### What if my team wants me to be more aggressive?

Show them the plan: shared outcome, timeline, and escalation path. Aggression without a path is venting.

Related: [Google Project Oxygen: 10 manager behaviors](https://isilta.com/blog/google-project-oxygen-10-manager-behaviors/), [be a strong decision maker](https://isilta.com/blog/google-project-oxygen-strong-decision-maker/), [how corporate politics works](https://isilta.com/blog/how-corporate-politics-works/).