Google Project Oxygen: Be a good communicator - listen and share context

Engineering leadership

Be a good communicator means listening carefully and sharing the context people need to act. Project Oxygen treats communication as a core manager skill, not a soft extra. If your team learns strategy from rumor, you have a communication problem, not a gossip problem.

Scenario: roadmap by hallway

Product changes priority. You heard it in a leadership meeting. You plan to "tell the team Friday." By Wednesday, half the team has a distorted version from Slack screenshots. Trust drops before you speak.

Good communication is timely, plain, and two-way. Share what you know, what is undecided, and when the next update lands. Then listen for what people heard.

Listen and share, both

Practical weekly rhythm

  1. One written team update: decisions, risks, asks.
  2. In 1:1s, ask "What are you hearing that I am not saying?"
  3. Close loops: if you promised an answer, deliver or say when.
  4. Adapt channel to the person: some need async notes, some need talk.

How iSilta helps

Shared AI profiles make communication preferences explicit so you do not broadcast in one style. 1:1 notes preserve continuity so context does not live only in your head. Pulse helps you hear team sentiment between meetings and act on it.

Manager map

Gap Symptom Fix
Late context Rumor mill Same-day written update
One-way talk Silent meetings Ask what they heard
Overshare chaos Anxiety spiral Decide / undecided / next date

Bottom line

Communication is Oxygen's glue: coaching, vision, and decisions fail without it. Listen harder than you broadcast. Write what matters. Check what landed. Hub: 10 manager behaviors.

Frequently asked questions

How much should I share from leadership meetings?

Share impact on the team's work, timing, and constraints. Skip gossip. If confidential, say what you can and when more is public.

What if I am a poor verbal presenter?

Lean on short written updates and prepared 1:1s. Clarity beats polish.

How do I listen when I am overloaded?

Protect 1:1 time, use a pulse for between-meeting signal, and stop multitasking in conversations.

Is over-communication better?

Better than silence, but structure it. Unfiltered dumps create noise. Decide, undecided, next update is enough.

Related: Google Project Oxygen: 10 manager behaviors, care about success and well-being, clear vision and strategy for your team.

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