Communication Is Important — But It’s Not the Most Important Thing in Engineering Teams

“Communication is key.”

We hear this all the time.

And yes — communication matters.

But here’s the uncomfortable truth:

Too much communication is often a sign of broken processes.

---

Not everything should depend on talking

In many teams, people say:

• “Let’s align on this”
• “We should discuss this”
• “Can we jump on a quick call?”

But why does everything need alignment?

Why do we need constant clarification?

As product leader Marty Cagan often emphasizes, strong teams are empowered by clear context and autonomy — not constant coordination.

If people need to ask at every step, something deeper is missing.

---

The real problem: lack of clarity

The biggest issue is not communication.

It’s this question:

“Where does my responsibility start and end?”

When that’s not clear:

• People overstep
• Or worse — no one takes ownership
• Decisions get delayed
• Meetings multiply

This connects directly with a classic idea from Melvin Conway:

Systems mirror the communication structure of organizations.

If your system is full of dependencies, your team will rely on constant communication just to function.

---

When communication becomes a crutch

Without strong processes and culture:

• Communication turns into dependency
• Teams rely on conversations instead of structure
• Knowledge stays in people’s heads, not in the system

Engineering leader Camille Fournier highlights this well:

Teams that depend too much on synchronous communication usually lack strong documentation and clear processes.

---

The deeper issue: unclear thinking

There’s another layer here.

As Sam Altman has pointed out:

Unclear communication is often a symptom of unclear thinking.

If the system, the problem, or the goal isn’t well understood, no amount of communication will fix it.

---

What actually makes a team agile

Agility is not:

• More meetings
• Faster replies
• Constant alignment

Even decades ago, management thinker Peter Drucker argued that meetings are often a symptom of poor structure.

Real agility comes from:

• Clear responsibilities
• Well-defined processes
• Autonomy with boundaries
• Shared understanding of how work flows

Communication supports this.

It does not replace it.

---

A more mature way to think

Instead of asking:

“Did we communicate enough?”

Start asking:

“Was this supposed to require communication at all?”

---

Final thought

Great teams don’t communicate more.

They communicate better and less — because the system already does most of the work.

And without structure, no amount of communication will make a team truly agile.

---

References / Further Reading

Product & Empowered Teams

• Inspired — Marty Cagan
• Empowered — Marty Cagan

Engineering Management

• The Manager’s Path — Camille Fournier

Organizational Design

• Conway’s Law — Melvin Conway

Management

• The Effective Executive — Peter Drucker
• Management: Tasks, Responsibilities, Practices — Peter Drucker

Thinking & Clarity

• Talks and interviews — Sam Altman