The Agenda of a Three-Day All-Hands for a Remote Company

Three days is a practical length for a remote company. One day is rarely enough to reset relationships and make decisions, while five days become expensive in time, travel and energy, particularly for parents and people who joined recently. Three days allow a full arrival, two working days and a short close, with one evening that everyone can attend.

The agenda should be fixed before anyone travels. A written programme with start and end times, the owner of each session and the decisions expected at the end of it signals that the event is a working meeting, not a holiday. It also protects the bonding parts, because people are less tempted to skip them when they know what they are for.

Write the agenda in the company's own language, and keep a short version for the team: three columns for the day, the purpose and the output. Participants who only read the summary should still know what to expect.

Day one should be short on content and long on orientation. A typical structure starts with arrival and check-in in the early afternoon, followed by a welcome session of about 90 minutes. In this session the leadership explains the purpose of the three days, reviews the company's numbers and priorities, and names the decisions the group will take. Questions are taken openly, and a shared document collects them for later answers.

The late afternoon belongs to small groups. Mix people who rarely work together, such as support and product, or engineering and finance, and give them a simple task that they must present the next morning. The aim is to create a first working relationship before the serious sessions begin.

End with a dinner that is relaxed and seated, with time for conversation. Avoid a sequence of speeches. Thirty minutes of remarks is enough, and the rest of the evening should be left to people to talk to each other.

The second day carries most of the working content. A workable pattern is four blocks of about 75 minutes in the morning and early afternoon, each with a facilitator, a note-taker and one question to answer. Typical questions include the priorities for the next two quarters, the way two teams hand over work, or the process for making product decisions.

Use a simple format for each session: context in ten minutes, options in twenty, a decision or a next step in the last part. Record decisions in one shared place with an owner and a date. Sessions that end without a decision should either be re-scheduled or explicitly marked as exploration.

Break the day with movement and short walks, especially for people who have been on screens for months. Lunch can be a working meal, but make it optional, so that people who need quiet can take it. The late afternoon is a good moment for a short review of what has been decided so far.

The final day turns decisions into plans. Start with a short review of the decisions from day two, then give teams a block to draft their next-quarter plan, with a maximum of three objectives each. Ask each team to name the dependency it needs from another team, and make sure those dependencies are reviewed in plenary.

The closing session should be brief and concrete. Each team presents its three commitments in two minutes, and each commitment has a named owner. Agree a date for a follow-up review within four to six weeks, and publish the notes within 48 hours of the event.

Leave the last hour for an open reflection, in which participants say what worked and what they would change. Collect the feedback and use it for the next gathering. A remote company that does this visibly, and acts on the input, builds the trust that the event was designed to create.

Bonding is not an add-on in a remote company, because many relationships exist only through a screen. The most effective activities are those that require people to work together in small, mixed groups. A cooking workshop, a team puzzle or an urban game in which every group needs every member can do more than a general networking drinks session.

Keep groups small enough for everyone to speak, usually six to eight people, and rotate them across the three days. Avoid activities that single out individuals, such as public performances, unless everyone has agreed in advance. Offer an alternative for anyone who prefers a quiet walk or a rest.

In Paris and in the regions, several venues and providers can design these sessions. Ask for a plan that links each activity to a point on the agenda, so that the bonding time supports the decisions rather than competing with them.