Communication practices for leading a team spread across locations

You lead a team whose members work from different locations. What strategies and day-to-day practices would you put in place so that communication across the team stays clear and effective? ```hint Tie each practice to a failure Start from what actually breaks when people are far apart, such as decisions some members never hear about or a question that waits a full day for an answer, and match each practice to one of those problems. Then support it with a time you led people across locations. ``` ### Clarifying Questions - How many time zones does the team span, and how many working hours overlap? - Am I the team's direct manager, or a product manager leading engineers, designers and analysts who report to other people? - Is everyone remote, or does most of the team sit in one office with a few members elsewhere? ### What a Strong Answer Covers - Naming the specific communication failures that distance creates rather than listing tools - A deliberate split between written, asynchronous communication and live time, with written decisions as the record - Norms and rituals fitted to the time-zone overlap, including sharing the burden of inconvenient meeting hours - Inclusion and trust for members outside the main office, and a way to check whether communication is actually working - A concrete example in STAR form with a measurable result ### Follow-up Questions - An engineer in a distant time zone keeps learning about decisions after they are made. What would you change? - How would you handle an urgent launch decision when the team shares only one working hour a day? - How would you know your communication practices are working, beyond people saying so?