Skip to content
GanttPal
Log in Get started

Managing Distributed Teams: A Practical Guide from Johanna Rothman

Johanna Rothman, author of From Chaos to Successful Distributed Agile Teams, discusses with Brett Harned how to tell co-located, satellite, cluster and nebula arrangements apart, why an all-remote setup can be fairer, and the everyday practices that help distributed teams collaborate, learn and deliver.

First, classify how the team is arranged

Start by naming the arrangement honestly. The discussion distinguishes co-located, satellite, cluster and nebula teams. Only the co-located boundary is defined in the captured material: people working within about 30 metres of each other. If that test fails, plan as a distributed team rather than assuming hallway contact will fill the gaps. That single decision changes facilitation, onboarding and tool access.

Why all-remote can be the fairer default

An all-remote arrangement removes the headquarters advantage: nobody is automatically an insider and nobody is automatically an outsider. Rothman also notes a management benefit — distance makes micromanagement harder, freeing managers to do the work only they can do. For a product owner, the practical prompt is to ask for the one thing they need most, then use cycle time as a signal of flow rather than watching activity.

A distributed-team operating checklist

Use this checklist before the next sprint or project cycle:

  • Pair every new person with an onboarding buddy and schedule regular one-on-ones.
  • Run short, regular team learning sessions alongside retrospectives, so improvement is continuous rather than episodic.
  • Set up a dedicated text back-channel for quick questions and context that would otherwise be lost.
  • Confirm every member has full access to the same tools; unequal access recreates a headquarters hierarchy.
  • Collaborate in one shared document so decisions and edits are visible to everyone.
  • Keep remote meetings under 50 minutes and end with a clear next step.
  • Facilitate deliberately: distributed teams need structure for turn-taking, decisions and follow-up, not just a video link.

Applying the ideas without adding meetings

The episode moves between theory and tactics: how to categorise the work environment, why distributed teams can work well in Agile settings, how to earn buy-in across distance, and how to communicate and collaborate from afar. A useful way to apply it is to pick one friction point — for example, slow answers in a shared channel — and fix it with the back-channel and shared-document practices above before adding more meetings.

Team arrangement labels
ArrangementWhat the captured material establishesPlanning implication
Co-locatedWithin about 30 metresIn-person contact can be assumed more readily
SatelliteNamed as a distinct arrangement; no further definition capturedConfirm location and communication norms explicitly
ClusterNamed as a distinct arrangement; no further definition capturedConfirm grouping and shared-work practices explicitly
NebulaNamed as a distinct arrangement; no further definition capturedConfirm grouping and shared-work practices explicitly

Only the co-located distance boundary is defined in the captured material; the other labels are named without full definitions, so do not infer detailed structures for them.

Frequently asked questions

When is a team actually distributed?

Use proximity as the starting point. A group working within roughly 30 metres is treated as co-located; beyond that, treat the team as distributed and design communication, tool access and facilitation accordingly, even if members share a building or city.

What practical setup supports a distributed team?

Give everyone the same tools, keep one shared document for collaboration, use a dedicated text back-channel, pair newcomers with a buddy, hold one-on-ones, and keep remote meetings under 50 minutes.

Why prefer everyone being remote over a mixed setup?

When everyone is remote, no location becomes the default headquarters, reducing insider and outsider dynamics. Distance also makes close surveillance impractical, which can free managers to focus on enabling the team.