Remote Workforce Review

Home / Guides / When to Bring Everyone Together

When to Bring Everyone Together

For a distributed team the periodic gathering is not a perk. It is the mechanism that builds the personal trust that video does not, and organisations that skip it fragment within about two years.

It is also expensive, which is why it should be designed rather than filled.

Frequency

Two to four times a year for a team; once or twice for a whole organisation, depending on size and budget.

Below annual is not enough to sustain relationships. Above quarterly, for most organisations, costs more than it returns.

The first weeks matter disproportionately. A new joiner who meets the team in person within their first two months integrates faster than one who waits nine. If you can time gatherings to catch new people early, do.

What to use the time for

The scarce resource is being in a room together. Spend it on things that need a room.

Worth doing in person: unstructured conversation, difficult or ambiguous discussions, work that benefits from rapid interruption, meeting people you only know as a name, and anything with an emotional dimension.

Not worth doing in person: presentations that could be a document, status updates, individual work, and anything you would have done over video anyway.

The commonest mistake is filling the gathering with a conference agenda — sessions, slides, an audience. That is the least valuable use of the most expensive time you buy, and everyone leaves tired without having spoken to anyone.

Structure that works

Under half the time scheduled. The value is in the gaps. People who have never met need unstructured hours to become colleagues, and a full agenda removes exactly that.

Meals together, unhurried. Consistently reported as the most valuable part, and the cheapest thing on the budget.

Mixed seating and mixed groups. Left alone, people sit with the colleagues they already talk to daily.

Some real work. Purely social gatherings feel indulgent to participants and to whoever approved the budget. A genuine problem worked on together justifies the trip and produces the shared experience.

Nothing that requires everyone in a room for eight hours. Attention does not survive it, and neither does goodwill.

Practical points people miss

Accessibility and dietary needs collected in advance, and actually accommodated.

Time zones on arrival day. People flying long distances are not useful on the first morning. Plan accordingly rather than scheduling the important session at 9am.

Caring responsibilities. Multi-day travel excludes some people entirely unless you are flexible about attendance, support costs, or occasionally location.

Cost policy stated up front. Who books, what is covered, what is not. Ambiguity here produces people quietly out of pocket.

Do not schedule the evening every night. Enforced socialising three nights running is exhausting, particularly for the people who most need the daytime contact.

Afterwards

Write down what was decided. Gatherings generate decisions that exist only in the memory of the people present, which recreates the problem you gathered to solve.

Follow through visibly. A gathering that produces commitments nobody acts on makes the next one harder to justify.

Ask what was worth it. Not a satisfaction survey — a specific question about which parts earned their place. The answers reliably favour fewer sessions and more unstructured time, and organisations reliably ignore them.