Google Project Oxygen: Have a clear vision and strategy for your team

Engineering leadership

Have a clear vision and strategy for the team means people can answer what winning looks like and what to ignore. Project Oxygen expects managers to provide direction, not only facilitation. If priorities change weekly with no narrative, you have a vision gap.

Scenario: post-reorg pull in three directions

After a reorg, your team inherits platform debt, a new product bet, and a reliability fire. Everyone is busy. Nobody shares a story of what "good" means in 90 days.

Your job is to name the few outcomes, the sequence, and the explicit non-goals. Strategy here is a one-page operating story, not a slide novel.

Write a 90-day team strategy

  1. Mandate: who we serve and why we exist now.
  2. Three outcomes that define success.
  3. Non-goals you will refuse or defer.
  4. Capabilities to build (skills, systems, rituals).
  5. Risks and how you will watch them.

How iSilta helps

Team Brief captures mandate, operating norms, and 90-day focus so the story is shared, not trapped in your head. Team OKRs turn that story into co-edited objectives the team can track between meetings.

Manager map

Symptom Likely gap Fix
Everything is P0 No non-goals Publish what you will not do
Re-litigate weekly No written strategy One-pager + OKRs
Hero projects Vision is personal Co-create with tech leads

Bottom line

Vision is Oxygen behavior seven because autonomy without direction becomes chaos. Say what good looks like, what you will ignore, and how you will measure progress. Hub: 10 manager behaviors.

Frequently asked questions

How detailed should a team vision be?

Short enough to remember. A page for 90 days beats a 40-slide deck nobody opens.

What if company strategy is unclear?

State assumptions, local outcomes, and what would change your plan. Waiting forever for perfect clarity stalls the team.

Should vision come only from the manager?

You own the final call, but build it with tech leads and product partners so it sticks.

How often should I refresh it?

Review monthly; rewrite when reality shifts. Do not thrash weekly without a reason.

Related: Google Project Oxygen: 10 manager behaviors, be productive and results-oriented, be a good communicator.

Prefer prepared conversations over memory alone? Explore iSilta features or try the product demo.