You noticed it about six weeks in. Two people had built slightly different versions of the same thing. Someone was blocked for three days and nobody knew. A decision you thought was made came back for a second debate. So you did what most managers do — you added a call. Then another. And now the calendar is full and the team is still out of sync.
The takeaway up front: alignment is not a meetings problem, it's a written-record problem. In an office, alignment happened by accident — overheard conversations, the walk to the kitchen, seeing someone's screen. Remote, none of that happens by accident, so it has to happen on purpose. The teams that manage it well have replaced ambient awareness with a small number of written habits, not with more video calls.
Here is the system, in the order you should build it.
Start by naming what people are actually missing
"Alignment" is too vague to fix. Break it into the four things that quietly went missing when the office did:
- Who is working on what right now — the ambient awareness you used to get for free.
- What has been decided, and why — decisions used to be witnessed; now they evaporate into a chat thread.
- Who is stuck — blockers used to be visible on someone's face.
- What "good" looks like — standards used to be absorbed by watching other people's work.
Each has a different fix, and none of them is a recurring call. Diagnose which one is actually broken on your team before you add anything to the calendar. Usually it is two of the four, not all of them.
Replace the status meeting with a written weekly update
This is the highest-return change available to a remote manager, and it costs each person about ten minutes.
Everyone posts a short update in the same place, at the same time each week — Friday afternoon or Monday morning, whichever suits your working patterns. Same four headings every time, so it can be skimmed:
- Shipped this week — what is actually done, with a link.
- On next week — the two or three things you'll be working on.
- Blocked or at risk — what you need, and from whom, by when.
- Worth knowing — anything the rest of the team would want to have heard.
Three rules make it work. Keep it short — if it runs past a screen, it is a document, not an update. Make it public to the whole team, not a private report to you, because half the value is people discovering each other's work. And respond in writing to at least two updates every week yourself, because a channel nobody reacts in quietly dies.
Then delete the status meeting. Not "shorten" — delete. If you leave it on the calendar, people will save their news for it and the writing becomes duplicate work. What you get back is a searchable, timestamped record of the quarter that no meeting ever produced.
Keep a decision log
The single most common source of remote confusion is a decision that was made in a call or a thread and never written down anywhere findable. Two months later nobody can remember whether it was decided or just discussed, and the argument runs again.
Keep one document. One row per decision, five columns: date, decision, why, who decided, where to raise it if it needs revisiting. Four sentences maximum. Add a row every time something is settled, and link to it when you announce it.
The "why" column earns its keep: new joiners inherit the reasoning instead of the rule, which stops them quietly undoing decisions they don't understand. The "where to raise it" column stops the log becoming a wall — decisions can change; they just have to change on purpose.
Write down how the team works
Most remote friction comes from unstated expectations about availability. Someone thinks a message deserves an answer in ten minutes; someone else answers at the end of the day. Neither is wrong, and both are annoyed.
Agree a short working agreement with the team — half a page, written together in one session, revisited quarterly:
- Core overlap hours. The window when everyone is reachable. Four hours suits most teams; outside it, people work their own way.
- Response expectations by channel. Chat within the working day, not within minutes; email within two working days; one channel reserved for genuinely urgent things. Then honour it yourself — the manager sets the real expectation regardless of what the document says.
- Meeting defaults. Camera optional. Agenda in the invite or the meeting is cancelled. Notes posted afterwards where the team can read them.
- How to signal availability. Calendar blocks and status messages people actually trust.
- What must be written. Decisions, requirements, and anything a person joining in six months would need.
The point is not the specific choices — teams differ. It's that they are choices, made once and out loud, rather than twenty private assumptions.
Protect the meetings that are genuinely about people
Cutting meetings does not mean cutting contact. Two things should survive any purge:
One-on-ones. These matter more remotely, not less, because they are now the only reliable place you'll hear that someone is frustrated, bored, or thinking about leaving. Keep them weekly or fortnightly, keep them, and don't let them decay into status updates — the written cadence exists precisely so they don't have to be. What to actually do in them is in our one-on-ones and feedback guide.
One live session where the team thinks together. Planning, a retrospective, a design discussion — work that involves people building on each other's half-formed ideas in real time. That is genuinely worse in writing, and it is the thing most remote teams accidentally cut while keeping the status call they should have deleted. Our framework for deciding whether something should be a meeting applies with more force when the meeting costs someone their evening in another time zone.
Make work visible without watching people
The fix for "I don't know what anyone is doing" is a shared board where work items live, with an owner and a state, updated by the person doing the work. Not a tracking tool. Not a screenshot monitor.
Keep the states few enough that updating is trivial, and check the board before you check on the person. If you find yourself asking for progress reports between updates, the board is not being maintained — fix the board rather than adding a check-in.
The distinction worth holding on to: you are making work visible, not people visible. Surveillance tooling reliably damages trust and produces the theatre of activity rather than the substance of it. The trust side of this — and why it is the foundation everything else sits on — runs through our guide to leading people.
The tools that support this
Deliberately unglamorous, and the order matters — pick the workflow first, then the tool that fits it:
- A team chat tool with channels, threads and searchable history. Threads are not a nice-to-have remotely; without them a channel becomes unreadable within a week.
- A shared document space for the decision log, the working agreement and meeting notes. Anything that matters should have a URL.
- A work-tracking board with owners and states, visible to the whole team.
- A calendar everyone keeps current, showing working hours and time zones.
One of each, integrated well enough that a link from one opens usefully in another. You do not need four tools that each do all four jobs — the sprawl is itself a source of misalignment, because there is no longer one place to look. If you are choosing or consolidating, our compared shortlist of team collaboration tools sets out what each type is genuinely good at.
FAQ
How often should a remote team meet?
Less often than most do, and with more purpose. Keep your one-on-ones, keep one live session for work that needs real-time thinking, and move status entirely into writing. Many teams land at one recurring team meeting a week plus individual one-on-ones — and find alignment improves, because what used to be said once in a call is now written down where people can find it.
Isn't async communication just slower?
Individual answers are slower; the work is usually faster. Async trades a short wait for uninterrupted focus time and a written record that stops the same question being asked three times. The pattern that fails is async without a response expectation — that isn't async, it's abandonment. Set a clear window, honour it, and keep a narrow escalation path for genuinely urgent things.
How do I build trust with people I never see in person?
Through reliability more than socialising. Reply when you said you would, do what you said in the one-on-one, share context before decisions rather than after, and be visible about your own mistakes. Scheduled social time helps, but it doesn't compensate for an unpredictable manager.
What about a hybrid team where some people are in the office?
The risk is a two-tier team where in-office people get information and remote people get the summary. The fix is to run every meeting as if everyone were remote — everyone on their own screen, notes and decisions written up regardless of who was in the room — and to keep the written cadence even for people sitting next to each other.
Build the habits, then choose the tools
Alignment on a distributed team is a small number of written habits repeated reliably: one weekly update per person, one decision log, one working agreement, one visible board, and the human conversations protected around them. Set those up over a fortnight and the calendar problem tends to solve itself.
When the workflow is settled and you want the software to match it, see our compared shortlist of team collaboration tools and the full how-to-manage-a-remote-team playbook on YouManageIt.
