How to Record Meetings for Remote Teams

There's a Tuesday meeting on a team I worked with. Four people in the US, one in Manila who's asleep for it. They talked through an API redesign, landed on a new approach, and everyone in the room walked away aligned. The teammate in Manila woke up eight hours later to a Slack thread that read, in full: "great call today, going with the gateway approach."

That was it. No reasoning, no context, no map of what got ruled out and why. He'd spent the previous day building against the old design, and now he was building the wrong thing, and he wouldn't find that out until his afternoon. By the time he'd pieced together what had actually been decided, he'd lost the better part of two days to a meeting he was never in a position to attend.

Nobody left him out on purpose. The meeting just happened while he slept, the way a big share of your team's meetings happen while somebody sleeps. That's the problem hiding inside every synchronous meeting on a distributed team: whatever happens in the room stays in the room, and the room is only ever a slice of the team.

Some meetings have to be live, and that's fine

I've argued before that a lot of what teams put on a calendar shouldn't be there at all. The weekly status meeting is usually better as a written update, and most decisions are better made async in a doc than hashed out in the one hour everyone's awake. If you haven't done that pruning, do it first. It's the highest-leverage change you can make.

But some meetings survive the cut, and they should. A genuinely contentious design argument moves faster face to face. A tense conversation reads better with tone and expressions attached. Brainstorming that needs six people riffing off each other doesn't work as a thread. When the thinking happens in the back-and-forth itself, live is the right call, and pretending otherwise just makes people write novels at each other for a week.

So this isn't about eliminating the last meeting. It's about what you owe the people who couldn't be in it.

The recording is nearly free, so turn it on

Here's the part that still surprises me: teams hold a meeting the far side of the world can't attend, make real decisions in it, and then record nothing. The knowledge evaporates the second the call ends. If you asked two attendees a week later what was decided, you'd get two different answers.

Every tool you're already using can fix this. Zoom, Meet, and Slack huddles all record with one click. Make it a default, not a decision someone has to remember to make. The rule on the teams that do this well is simple: if the meeting produced anything a person needs to know, it gets recorded, no exceptions. The cost is one click and some storage. The alternative is that the person who was asleep depends on someone else's memory, filtered through a one-line summary, to understand a call that shaped their work.

Recording also quietly improves the meeting itself. When there's a record, people stop relitigating what was said. "Go check the recording at minute twelve" ends an argument that would otherwise burn an afternoon of he-said-she-said across a timezone gap where the two people can't even talk in real time to sort it out.

Nobody watches a 45-minute recording, so write on top of it

Now the honest part. Almost nobody is going to watch your forty-five-minute recording. Your teammate in Manila is not going to spend forty-five minutes of his morning watching four people find their way to a conclusion, and he shouldn't have to. The recording is an archive you can reach for when you need the exact words. It is not, on its own, a way to include the person who missed the meeting.

The thing that actually includes them is a short written summary posted right after, with the recording linked underneath for anyone who wants the full detail. Not minutes. Not a transcript. A few sentences that answer what a person who wasn't there actually needs: what did we decide, why, what got ruled out, and what happens next. Same discipline as a decision doc, just written after the talking instead of before it.

Someone has to own writing that summary, and it should be one named person, not "whoever gets to it." The meeting isn't finished when people leave the call. It's finished when the summary is posted where the asleep half of the team will see it when they wake up. If that summary never gets written, the recording is a tree falling in an empty forest, and you've recorded a meeting nobody outside the room will ever benefit from.

One more thing on the summary: when it names a date or a next checkpoint, anchor it to a real timezone. "We'll revisit Thursday" is exactly the kind of ambiguous time reference that means three different things to three people reading it in three places. "We'll revisit Thursday 4pm ET" travels.

The bigger move: replace the meeting with a recording

Recording a live meeting includes the absent person after the fact. Async video can include everyone from the start, and for a whole class of meetings it's the better tool.

Think about the meetings that are really one person explaining something to a group. A demo of what shipped this week. A walkthrough of a new part of the codebase. Someone narrating how a bad bug happened and how they fixed it. None of that needs the group assembled at the same moment. It needs one person, a screen recording, and six minutes. The person records it once, at whatever hour suits them, and everyone else watches it on their own clock, at 1.5x, pausing to take notes. The Manila teammate gets the exact same walkthrough as the person sitting next to the presenter, just at a civilized hour for him instead of 2am.

I've watched teams replace a standing weekly demo meeting with a channel of short recorded walkthroughs, and the demos got better. When you're recording instead of presenting live, you redo the take that rambled. You cut the dead air. You show the thing working instead of talking around it. And the far-timezone people stopped being second-class citizens who read a summary of a demo they never got to see.

This is the same instinct behind async-first communication generally: default to the format that doesn't require everyone present at once, and reserve synchronous time for the work that genuinely needs it. Video just extends that instinct to the things a text thread handles badly, like anything visual or anything where tone carries the meaning.

What you shouldn't record

A recording culture has a hard edge, and it's worth naming, because the wrong version of this makes a team worse.

Don't record the meetings whose entire value is that they're unguarded. A one-on-one where someone tells you they're struggling is not an artifact for the archive, and the moment people suspect it might be, they stop saying the true thing. The casual hang, the watercooler channel call, the moments a team uses to fight the isolation that quietly pushes remote people out, those work precisely because nobody's on the record. Point a camera at connection and you kill it.

The line is whether the meeting's product is information or intimacy. Record the information. Leave the intimacy alone. A design review, a demo, a decision, a postmortem, record all of it and post the summary, because the value is knowledge that some sleeping teammate has an equal right to. A 1:1 or a Friday hang, never, because the value is trust, and trust doesn't survive an audience it didn't agree to.

Get that split right and recording stops being surveillance and becomes what it should be: the mechanism that lets a person twelve timezones away work from the same understanding as everyone who happened to be awake at the right hour.

Make Your Meeting Notes Read Right Everywhere

A recording is only useful if the summary on top of it says when the next thing happens, and a bare "let's sync Thursday" breaks the moment it crosses a timezone. Timely converts every time mention in Slack to each reader's own clock automatically, so the "revisit at 4pm Thursday" in your post-meeting note lands correctly whether your teammate reads it in Austin or Manila, and nobody has to do the arithmetic to know when they're expected.

Add Timely to Slack — Free · See how it works