How to run a team spread across several cities

How to keep a multi-city team working as one group: written defaults, one overlapping core block, and no headquarters to be left out of.

Six people in four cities and no office to gather in

A team assembled during the remote hiring years tends to look like this. Two people in Columbus, one in Boise, one in Tampa and the founders in Austin. Hiring went well because talent outside the big coastal markets costs less and stays longer. Running the team is the part nobody planned for.

The symptoms are consistent. Decisions get made in whichever city holds two people in a room and arrive elsewhere as a summary. New joiners in single person cities take longer to become useful and leave sooner. Nothing is written down because the founders never needed to write anything down when they sat together.

What distribution costs and what it does not save

It no longer saves much on salary. Pay expectations outside the major metros have risen and a competent candidate in Boise knows what the San Francisco rate is. Treat geographic arbitrage as a modest discount rather than a strategy. Distribution also does not remove your office cost if you keep a headquarters anyway.

The new costs are travel, tooling and compliance. Travel is the one most businesses underfund. Bringing everyone together even twice a year means flights, accommodation and lost working days. Collaboration tools are charged per person per month and those rates are stated before tax since sales tax on software varies by state. Employing people in several states also creates registration and local tax obligations that a single state business does not have.

Who should do this and who should not

A business whose work is physical should not spread out. Fabrication, assembly, laboratory work, inventory handling and anything with a dispatch bay need people beside the material. Hiring a remote coordinator for that work usually adds a layer of relaying rather than capacity.

A business with no written process should also not go multi-city yet. If training currently happens by sitting a new person next to an experienced one then distribution removes your only training method. Write the process down first and distribute second. The same caution applies to a first time manager inheriting a scattered team. Managing by observation is impossible here and managing by written commitment is a skill that takes a while to build.

Distribution works well for software, design, writing, finance operations, support and sales covering regional markets. It also works when your customers are in several states and local presence wins business.

How to make it work in practice

Set one overlapping core block rather than fixed office hours. Four or five hours when everybody is reachable covers most coordination and leaves people free around local commute and family patterns. Keeping the team inside two or three adjacent time zones is what makes that block possible so treat it as a hiring constraint.

Make writing the default. Every decision of consequence lands in one place with the date, the reasoning and the person accountable. A searchable decision log is what replaces overhearing. Keep meeting notes in the same place and treat anything decided verbally as provisional until written.

Give every city of two or more people a local anchor who handles practical matters and reports on mood. Then protect the gatherings. One or two full team meetings a year with real time for unstructured conversation does more for retention than any tool. Schedule them around the school and public holiday calendars where your people live rather than the head office calendar.

How to judge whether it is working

Hours online flatters. So does attendance on calls and the green dot beside somebody's name. All three measure presence and none measures contribution.

What matters is how long a decision takes from question raised to answer recorded, and whether that time differs by city. Compare attrition and time to productivity for new joiners city by city. If people in single person locations leave faster or take longer to become useful then the structure is failing those people quietly.

The common mistake

Running a headquarters with satellites. The founders and half the team sit in one city and that city becomes where things are really decided. Everybody else receives conclusions. This is expensive in a specific way: the strongest remote hires leave first because they can see they are not in the room, and you lose exactly the people you distributed in order to recruit.

The fix is uncomfortable. If a decision meeting includes anyone remote then everybody attends remotely from their own screen, even the three people sitting in the same office. One shared format beats a good camera in a conference room.

A note on employing across states

Employing people in several states usually brings obligations in each of those states rather than only where the company is registered. Registration for state income tax withholding, unemployment insurance contributions, workers compensation cover and any city level payroll tax follow the place of employment, and the rules and rates differ state by state. Payroll software will not work this out for you if nobody has told it where people sit. A qualified professional should confirm which registrations your specific footprint requires before you add the next city.

This guide explains how something works. It is not legal, tax or financial advice, and rules change. Confirm anything regulatory with a qualified professional before you act on it.