Coordinating Across Teams

Context – Where this shows up

Work begins to span multiple teams, functions, and domains.

What once moved within a single team now depends on coordination across many—each with their own priorities, timelines, and constraints. Planning expands to account for these connections. Alignment becomes more frequent. Visibility increases.

From the outside, the system appears more aligned.

Inside, the cost of keeping work moving begins to rise.

What becomes visible

As coordination increases, certain patterns start to surface.

Work progresses unevenly—not because of effort, but because it waits. Dependencies shape timelines more than the work itself. Teams complete their portion, but overall progress remains unclear.

Planning cycles grow longer. More stakeholders are involved. More alignment is created. Yet confidence in delivery does not increase at the same rate.

Local decisions make sense within each team, but create unintended consequences across the system. What optimizes one area introduces delay in another.

Escalations become a mechanism for movement. Not as exceptions, but as part of how work gets done.

Attention starts to move —separate from delivery, but inseparable from it.

At some point, the question is no longer how to coordinate better—but why coordination has become so central to getting anything done.

What begins to shift

Attention starts to move.

From how teams collaborate → to how work is connected

From individual delivery → to system-level flow

From managing dependencies → to examining why they dominate

Coordination is no longer seen as something to improve through better communication alone. It begins to be understood as a property of how the system is structured—how work is divided, how decisions are made, and how constraints are distributed.

In this shift, certain questions begin to surface:

  • Why does work slow down as more teams are involved?
  • What determines where coordination becomes necessary?
  • Which constraints are inherent, and which are created by design?

The system becomes something that can be observed—not just operated within.

This shift does not happen in isolation. It connects to how work flows, how decisions are made, and how the system is structured.

How this work happens

This work unfolds across multiple levels of the organization.

Leadership conversations begin to examine how coordination is shaped by structure, decision boundaries, and competing priorities. Teams continue their work, while also making visible how dependencies affect flow.

A shared way of describing what is happening begins to emerge—not as terminology, but as recognition across teams.

In some cases, structured learning environments are used to support this shift. These may include Scrum Master progression pathways or scaling-oriented programs, where they help establish a common understanding of coordination, flow, and system constraints.

These elements do not operate independently. They begin to connect—allowing patterns to be seen across teams, rather than within them.

Related system perspectives

These patterns are often connected to other system-level dynamics.

Supporting learning paths

Where shared understanding is needed across teams, organizations sometimes draw on structured learning pathways:

 

In some cases, these patterns are explored in practice through:

These are used to support shared understanding—not as isolated interventions, but as part of a broader effort to work at the system level.

Coordination challenges rarely appear all at once.

They emerge gradually—as more teams become involved, as dependencies increase, and as the system grows in complexity.

From within, they can look like issues of communication, alignment, or execution.

But over time, a different pattern becomes visible:

The system is not struggling to collaborate.

It is operating within conditions where coordination has become the dominant form of work.

And once that becomes visible, the nature of the work begins to change.

Start a conversation

If you’re exploring how these patterns are showing up in your organization, we can start there.