Loom Pro

---
name: loom-pro
description: Master Loom for async video: recording, editing, organizing, and replacing meetings with video messages. Use when adopting async communication or making video updates that people actually watch.
category: productivity
---

# Loom Pro

## Overview

Loom = quick async video messages: screen + camera + voice, shareable by link. The antidote to unnecessary synchronous meetings.

Best for: walkthroughs, feedback, updates, onboarding, bug reports — anything where showing beats telling and timing doesn't need to be live.

Pro Loom: tight recordings (scripts, editing), organized library, and knowing what deserves video vs. text vs. a meeting.

## When to use

- Replacing status meetings with async video updates
- Giving feedback on designs, docs, or code visually
- Creating onboarding and how-to content quickly
- Communicating across time zones without late-night calls
- Reporting bugs or demonstrating issues clearly

## Core concepts

- **Async-first mindset.**
  Default question: 'could this be a Loom?' Status updates, walkthroughs, feedback rounds — usually yes. Reserve live time for debate and decisions.
- **Length discipline.**
  Under 5 minutes is the sweet spot; never over 10 without chapters. Async video respects attention by being tight.
- **Script the beats.**
  Bullet outline before recording: hook, 3 points, call to action. Rambling is the #1 async-video killer.
- **Show, don't just tell.**
  Screen share the actual thing: the doc, the design, the bug. Camera bubble for human connection; screen for substance.
- **Edit ruthlessly.**
  Trim the start ('hey guys so...'), cut dead air, remove tangents. Loom's trim/transcript-based editing makes this fast.
- **Chapters and CTAs.**
  Chapter markers for navigation; end with a clear ask ('comment by Friday', 'approve in the doc'). Async needs explicit next steps.
- **Library organization.**
  Folders by team/project, clear titles (`2026-09: Q3 metrics walkthrough`), descriptions with timestamps. Searchable later.
- **Notifications and sharing.**
  Share in the right channel with context ('3-min walkthrough, feedback by Thu'). Don't drop links without framing.

## Practical workflow

1. **Install and configure.**
   Desktop app + browser extension, camera/mic defaults, recording quality, keyboard shortcut for instant record.
2. **Learn the 3-minute format.**
   Hook (15s) -> context (30s) -> walkthrough (2min) -> ask (15s). Practice until it feels natural.
3. **Script before recording.**
   Bullet beats for every Loom. One minute of outlining saves five minutes of rambling.
4. **Record and trim.**
   Record in one take; trim start/end and dead air after. Transcript-based editing for cutting filler fast.
5. **Organize the library.**
   Folders, naming convention, descriptions. Archive outdated Looms so the library stays trustworthy.
6. **Replace one meeting.**
   Pick a recurring status meeting; propose a weekly Loom + async comments instead. Measure: did decisions still happen?
7. **Build team norms.**
   When to Loom vs. write vs. meet; expected watch turnaround; comment etiquette. Write it down.
8. **Create evergreen content.**
   Onboarding walkthroughs, tool how-tos, process explainers — recorded once, reused forever. Highest-ROI Looms.

## Common pitfalls

- **10-minute rambles.**
  Unscripted, unedited async video nobody finishes. Tight or it doesn't get watched.
- **Loom for everything.**
  Simple text updates don't need video. Match medium to message: text for simple, Loom for show-and-tell, live for debate.
- **No call to action.**
  Video ends, nobody knows what's needed. Every async video ends with an explicit ask + deadline.
- **Dropping links without context.**
  'Here's a Loom' with no framing. Context line: what it is, how long, what's needed, by when.
- **Never editing.**
  Publishing raw with 2 minutes of 'can you see my screen?' Trimming takes 60 seconds and doubles watch rates.
- **Library chaos.**
  'Untitled video (47)' forever. Titles, folders, descriptions — or the library becomes unsearchable within months.
- **Ignoring analytics.**
  No idea if anyone watches. Check view counts; low completion = too long or poorly framed. Iterate.
- **Sensitive content carelessly.**
  Recording screens with visible passwords, PII, or confidential data. Check what's on screen before sharing the link.