liveBook · Manning

Distributed team

As explained in Think Like a Software Engineering Manager

A team whose members work from geographically separate locations and coordinate primarily through remote communication and collaboration tools.

A distributed team works across separate locations, coordinating through remote communication and collaboration practices. Fully remote teams may span countries, while hybrid teams combine remote and in-office work. Both require explicit norms, shared purpose, and attention to time zones, well-being, productivity, and connection. section 3.2.5

Manage a distributed team through practical routines:

  • Set clear team norms, vision, and purpose so distance does not leave collaboration to subjective interpretation. section 3.2.5
  • Provide functional home-working equipment, reliable internet connectivity, and security-compliant infrastructure. section 3.2.5
  • Use regular one-on-one meetings and team check-ins to understand motivation, support performance, and maintain social connection without micromanaging. section 3.2.5
  • Use video and focused participation to strengthen human connection, engagement, transparency, and attention during virtual meetings. section 3.2.5
  • Create occasional in-person opportunities, such as shared seating or lunch meetings, to foster togetherness and collaboration. section 3.2.5

A practical management pattern

A manager supporting employees across time zones schedules recurring one-on-ones, checks whether declining productivity signals an underlying problem, and combines virtual meetings with occasional shared office time or team events. section 3.2.5

The arrangement trades physical proximity for broader access to global talent and potentially lower office expenses. Effective leadership balances virtual interaction, occasional in-person contact, accountability, trust, morale, and individual well-being. section 3.2.5 section 3.5

How Think Like a Software Engineering Manager covers it

How deep it goes
Provides practical management strategies and trade-offs, but does not detail specific collaboration technologies or operating procedures.
Examples
Uses one-on-ones, team check-ins, video meetings, home-working infrastructure, shared office time, lunch meetings, and team events.
What it assumes
Assumes basic team-management responsibility and teaches how physical distance changes communication, support, monitoring, and connection.
What you can do after
Operate remote or hybrid teams through clear norms, infrastructure support, check-ins, focused meetings, and deliberate social connection.
How it connects
Connects remote teams with hybrid teams, team norms, time zones, productivity, well-being, trust, morale, and burnout.

Also explained in

Compare how 2 books explain distributed team →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.