Loom''s Position in the Remote Work Revolution
Loom pioneered the async video category - the idea that a quick screen recording with voiceover can replace dozens of meetings. By 2026, Loom has been acquired by Atlassian, integrated into the Jira/Confluence ecosystem, and has recorded over 1 billion videos by users globally. The product has become a fundamental layer of async-first remote work culture. More interesting is how Loom itself operates: a company whose product is about reducing meetings that has built one of the most meeting-light remote cultures in tech.
Loom internally tracked that their own teams averaged 8 meetings per week per person before systematically replacing meeting types with Loom videos. After two years of deliberate async-first practice, they reduced that to 3 meetings per week per person with no decrease in output quality.
Loom''s Async-First Communication Practices
How Loom uses its own product internally:
- Code reviews: Developers record Loom walkthroughs explaining their PR before requesting review
- Design reviews: Designers present work via Loom to allow async viewing and commenting before any live session
- Weekly updates: Team leads record 3-5 minute Loom updates instead of attending status meetings
- Onboarding: All training content exists as Loom recordings, allowing new hires to self-serve at their own pace
- Customer support training: Support team uses Loom to share product knowledge updates asynchronously
Loom''s Meeting Reduction Framework
Loom has developed a clear framework for deciding when to meet vs when to Loom:
- Use Loom: Status updates, design previews, code walkthroughs, feedback on work, announcements
- Use a meeting: Final decisions requiring real-time consensus, relationship building, conflict resolution, complex brainstorming
- The test: "Could this be a Loom?" If the answer is yes, it should be a Loom
Life Inside Atlassian
After the Atlassian acquisition, Loom''s remote practices have been exported to parts of the broader Atlassian organization:
- Loom is now deeply integrated with Confluence for video documentation
- Jira issues can link directly to Loom recordings for context
- Atlassian has adopted Loom''s "async by default" meeting philosophy in its own team guidance
What Remote Teams Learn From Loom
Practical lessons from Loom''s async-first culture:
- Start with one specific meeting type (weekly status calls are the easiest) and replace it with Loom updates
- Measure the change - before and after meeting hours, employee satisfaction scores
- Train your team on Loom basics - recording, trimming, sharing - so the tool is not a barrier
- Build a library of Loom templates for common communication types (project kickoffs, design reviews, sprint recaps)
The single most valuable async communication shift for any remote team is the "show, don''t tell" update. A 3-minute Loom screen recording of what you shipped this week communicates 10x more information than a bullet point list - and it is watched asynchronously by everyone at their own time.