Your calendar has three 30-minute meetings this week that should have been a Loom. You know because you'll spend the first five minutes on logistics, the middle twenty on context, and the last five on the actual decision — which one person could have delivered and absorbed in a fraction of the time, at the hours they chose.
But the Looms you've tried to send don't land. They're too long, they ramble, and people confess they only watched at 2x speed. The problem isn't the medium. It's that nobody taught you what an effective async video actually looks like.
It has exactly three parts, and the whole thing runs 90 seconds or less.
Part 1: The hook (first 10 seconds)
This is where most Looms die. The speaker opens with "Hey team, just wanted to walk through the analysis I ran last week on..." and the viewer has already decided to skim.
The hook has to tell the viewer two things in the first 10 seconds: what this is about, and why they specifically should care.
Not: "I wanted to share some thoughts on Q3 planning."
Instead: "I think our Q3 targets are about 20% too high, and if I'm right it changes how we hire in July. This is the case for why."
The second version tells the viewer: here's the claim, here's the stakes, here's the relevance. They'll stay for the rest. The first version asks them to trust that something interesting is coming, and they won't.
Part 2: The insight (roughly 60 seconds)
One insight. Not three. Not "a few thoughts." The discipline of async is that you have to pick the single most important thing and say it with precision.
Structure the middle as a brief argument:
- The observation — what you noticed or measured.
- The inference — what it means.
- The implication — what changes if you're right.
Example: "Looking at weekly signups for the last eight weeks, the growth rate has flattened since the April pricing change. I think that's not noise — I think it's the new pricing creating a ceiling we didn't model for. If that's true, our Q3 target, which assumes the old trajectory, is 20% too high."
That's one insight, three sentences, about 25 seconds of speech. You can expand each part a little, add a screenshot on screen, and you're still well inside 60 seconds.
What you don't do: give every piece of context. Give zero history of the project. Don't explain your methodology. Anyone who needs more can ask.
Part 3: The ask (last 15 seconds)
The fatal Loom ends with "...so, yeah, let me know what you think!" That's the async equivalent of trailing off. The viewer doesn't know what you want them to do, so they'll do nothing.
Every Loom needs a specific, time-bounded ask. Examples:
- "Can you react with a thumbs up or thumbs down in the thread by Friday noon? If it's mixed, we'll put 20 minutes on the calendar for the dissenters."
- "I'd like one of you to pressure-test this by Monday. Maria — can you take it, or tag whoever should?"
- "If I don't hear back by Tuesday, I'm going to assume we're moving ahead with the revised target."
The last pattern — "silence means yes" — is underused and enormously powerful. It respects people's time and forces a decision even in absence of response. Only use it when it's genuinely okay to proceed without explicit approval.
The three rules of thumb
One insight, not a meeting
If you catch yourself saying "and another thing..." — stop recording and split into two videos. One video per idea. Viewers will actually watch two 60-second videos. They won't watch one six-minute video.
Show, don't just tell
A Loom without a screenshare is usually a Slack message in disguise. If you're not showing something — a chart, a document, a mockup — write it as a message instead. The medium's whole advantage is visual.
Make the thumbnail work
The first frame of your Loom is its thumbnail. If it's a blurry view of your ceiling, nobody clicks. Put a title slide or a clean screenshot on screen before you hit record, so the preview signals "this is worth 90 seconds."
What to do before recording
Write your hook, insight, and ask on a sticky note. Three lines. Then record. Not because you're reading from it — because having the shape in front of you means the first take is usable. Most people try to wing it, record three minutes, decide it's bad, and never send. The sticky note is the whole difference.
What this replaces
Run these explicitly instead of meetings:
- Weekly team updates — a two-minute video from each lead, posted async on Monday morning. Fifteen minutes of video total replaces a 45-minute meeting for seven people — a 5x time saving for the team.
- Decision requests that need context — "here's the problem, here's my proposed answer, here's the deadline for a thumbs-up/down."
- Onboarding explanations — record once, send to every new hire forever. Update the Loom quarterly.
- Design / code review walkthroughs — let the reviewer respond on their schedule rather than burning an hour of synchronous time.
The one kind of conversation that shouldn't be a Loom
Anything emotional. Hard feedback, conflict, tense decisions. The moment empathy matters, you need bidirectional video in real time. Loom is for decisions and transfer of information. The relationship-shaping stuff still belongs on a synchronous call.
Get the split right and you'll reclaim a morning a week. The async videos will land because they're tight. The synchronous meetings will improve because they're actually used for what humans are best at: reading each other in real time.