Communication as Infrastructure: The System Behind Autonomous Teams

When I first became an Engineering Manager, I thought my role was mainly about delivery, deadlines, and processes. I quickly learned that what truly makes a team successful goes far beyond shipping features. Code matters, but even more important are the people writing it, and the systems that enable them to collaborate effectively.

Photograph by the author, Speicherstadt, Hamburg, Germany

Reflecting on this, I realised that many of the challenges I faced weren't really about technical delivery. They were about making sure the team had access to the right information at the right time — and in a way everyone could act on. The way we communicate and share context determines whether a team can make aligned decisions independently or becomes dependent on constant guidance.

This is why I consider communication not a soft skill, but infrastructure — a foundation that supports every other aspect of team performance and a core principle of my Systemic Lead philosophy, which aligns context, communication, confidence, and growth to build stronger, more autonomous teams.

Why Communication Matters

In high-performing teams, effective communication works like networking in a distributed system: reliable channels and clear patterns allow engineers to make confident, aligned decisions without constant supervision.

Information bottlenecks slow down entire teams. Misalignment compounds over time, leading to costly rework. Remote and hybrid work amplifies communication failures. And new team members often struggle when knowledge lives only in people's heads.

For instance, a developer once assumed that a database schema change had been communicated across services. It wasn't — leading to a subtle production issue that could have been avoided with systemic communication.

These challenges rarely happen because engineers don't want to communicate. More often, they arise because engineers were never systemically prepared to do so: what questions to ask, how to extract information, which details are important, and whom to consult at different stages. When engineers focus narrowly on technical tasks, they start expecting all necessary information to be pre-packaged. That often leads to misunderstandings, missed context, and frustration.

Identifying these bottlenecks is one thing; addressing them systematically is another. By creating a systemic approach to communication, we ensure that knowledge flows intentionally rather than accidentally.

Learning to Ask Questions

One of the most powerful shifts comes from teaching engineers how to ask the right questions. This is something I deliberately practice in teams. Before diving into a task, engineers are guided on:

• what to ask
• who to ask
• when to ask
• why each piece of information matters

Books like System Design Interview: An Insider's Guide by Alex Xu inspired this approach in interviews: candidates clarify constraints, user needs, and trade-offs before designing a system.

In a different setting, with my team, I ran an exercise where engineers mapped exactly who they would consult before making a critical change — and why. The exercise helped engineers identify additional stakeholders and context they hadn't initially considered, leading to clearer decisions and stronger alignment.

Both examples show that communication is an active, learnable skill rather than a passive expectation. The focus is not just on delivering the "right answer," but on surfacing context through disciplined inquiry. Teams that master this skill reduce misalignment and increase shared understanding, making communication an active, learnable capability rather than a passive expectation.

Practicing Communication in Interviews and Teams

These principles are not just theoretical — they can be actively practiced, both within the team and even during interviews to cultivate clarity and context-awareness. A small exercise I often use during interviews illustrates this clearly. I ask candidates:

How would you explain your main technology stack to someone without a technical background?

I encourage them to imagine they are speaking to a child, a grandparent, or someone in a completely different profession. What I'm looking for is clarity, patience, and the ability to simplify complex topics. Engineers who can describe systems without jargon usually demonstrate true understanding, which is the foundation for effective communication across teams.

We encourage engineers to keep practicing this daily — whether explaining a pull request to a teammate, presenting a design in a cross-team call, or writing a technical spec — so clarity becomes second nature.

This principle carries over directly to daily work. Engineers who can explain their work clearly to non-technical colleagues or stakeholders can share context more effectively, prevent assumptions, and align faster.

Making Communication Systemic

While practicing communication individually is valuable, the real leverage comes when communication is systemically embedded into the team's operations. Strong communication doesn't happen by chance; it must be systemically embedded into the team's operations. Treating communication as infrastructure ensures that it is reliable, measurable, and repeatable — not dependent on personality or chance.

Here's how we interlace communication into the fabric of our teams:

• Treat documentation as a first-class citizen, not an afterthought.
• Establish clear channels for different types of communication.
• Default to transparency — make information accessible, not hidden.
• Include engineers early in discussions, not only during implementation.
• Create explicit space for questions, and reward curiosity over compliance.

When communication is systemically embedded, teams operate more autonomously, knowledge flows naturally, and context is always accessible. In essence, communication becomes the infrastructure that supports alignment, decision-making, and impact.

This skill will only grow in importance as AI takes on more of the repetitive coding and optimisation tasks. Engineers who can ask the right questions, extract critical information, and communicate context effectively will drive better decisions, higher-quality systems, and more impactful work.

The Long-Term Impact

Teams that internalise this principle gain autonomy, make better trade-offs, identify edge cases earlier, and challenge assumptions respectfully. They start seeing themselves as part of a larger system: the team, the company, and the customer journey.

Leadership is not about issuing ever more precise instructions. It is about creating an environment where good decisions happen even when you are not in the room. Looking ahead, the ability to extract, structure, and share context will be the differentiator for high-performing engineers and teams (especially in an era where AI takes on more routine coding tasks).

Teams that communicate well consistently deliver impact — not just code, but aligned, thoughtful, and sustainable results.