# Google Project Oxygen: Be a strong decision maker without steamrolling the team

**Be a strong decision maker** means closing calls with clarity, ownership, and a path to revisit with evidence.
          Project Oxygen highlights this because teams stall in permanent "alignment."
          Decide, communicate, and move. Invite input without outsourcing the call forever.
        

        
## Scenario: the endless align meeting

        

          Two approaches sit on the table for three weeks. Everyone is "almost ready." Nobody owns the decision.
          The team burns energy re-explaining context. You fear picking wrong, so you schedule another sync.
        

        

          Strong decision making names the decision in one sentence, names the owner (often you), sets a decide-by date, and states the default if nobody chooses.
        

        
## Decision operating system

        

          - Write the decision question.

          - List options and tradeoffs (ask the team to draft).

          - Collect input on a deadline.

          - Decide and say why in writing.

          - Set a revisit trigger (metric, date, or risk signal).

        

        

          Steamrolling skips steps 2 and 3. Weak management skips steps 4 and 5.
          Strength is timely closure with respect for input.
        

        
## How iSilta helps

        

          **Team Brief** can capture how your team prefers to decide and commit, so norms are explicit.
          Team-scoped AI can help prioritize from brief, pulse, and open action points, but it does not replace your judgment.
          Treat AI as advisory context, not the decider.
        

        
## Manager map

        
| Pattern | Cost | Strong move |
| --- | --- | --- |
| Endless align | Delay + fatigue | Owner + decide-by + default |
| Silent decide | Surprise resentment | Write why + revisit rule |
| Consensus forever | Lowest common denominator | Input then clear call |

        
## Bottom line

        

          Decision strength is Oxygen's antidote to performative collaboration.
          Seek input, then close. Tell people what you decided and how they can challenge with evidence later.
          Hub:
          [10 manager behaviors](https://isilta.com/blog/google-project-oxygen-10-manager-behaviors/).

## Frequently asked questions

### What if I decide wrong?

Reversible decisions should be fast. For costly ones, gather more input, then still close. Write a revisit trigger so wrong is correctable.

### How do I avoid steamrolling experts?

Require their options and tradeoffs first. If you override, explain why and what would change your mind.

### Who should own the decision?

The person accountable for the outcome. Often the manager for cross-team tradeoffs; often the tech lead for deep design inside agreed constraints.

### How public should decisions be?

Public enough that the affected people can act. A short written note beats hallway lore.

Related: [Google Project Oxygen: 10 manager behaviors](https://isilta.com/blog/google-project-oxygen-10-manager-behaviors/), [collaborate across the company](https://isilta.com/blog/google-project-oxygen-collaborate-across-company/), [empower without micromanaging](https://isilta.com/blog/google-project-oxygen-empower-without-micromanaging/).