Atlassian's Teamwork Lab tested a lightweight manager routine: a Monday update on priorities and a Friday message recognizing contributions. Forty-four Atlassian managers sent either written Slack messages or Loom videos, and 309 direct reports answered surveys. Compared with the prior week's baseline, respondents reported greater connection, recognition, and goal clarity; the article says video produced stronger gains than writing. The intervention is practical and refreshingly modest.
The conclusions are less modest than the design permits. A one-week internal experiment can show that employees noticed a new communication routine. It cannot establish that asynchronous video itself builds durable managerial connection.
Novelty is an immediate alternative explanation. People received two deliberately structured messages, including explicit recognition, while being asked to complete a survey about the experience. Managers knew they were participating in an experiment and likely paid unusual attention to wording and delivery. Any of those changes could improve a short-term response. The effect may fade once updates become routine, delegated, skipped during busy weeks, or consumed alongside dozens of other recordings.
The comparison between Loom and Slack is also bundled. A video contains voice, face, timing, and presentation effort; the article notes that recording made at least one manager think more carefully about the audience. If video respondents felt more connected, the cause could be medium, manager preparation, message length, perceived effort, or different starting relationships. Saying video is significantly better requires the underlying effect sizes, uncertainty, assignment method, baseline balance, response rates, and analysis—not only the phrase "twice as likely."
Self-reported connection is worth measuring, but it is not the same as receiving useful management. A polished weekly broadcast may clarify priorities while leaving workloads unreasonable, decisions unchallengeable, and individual concerns unheard. Recognition delivered to a group can feel meaningful or selective. Employees may understand what matters this week without understanding why priorities changed or having any power to negotiate them.
The promise of no additional meeting time hides another tradeoff. Managers spend up to an hour preparing two updates, and every direct report spends time watching or reading them. Asynchronous communication shifts and distributes time; it does not remove it. For a large team, broadcast video may be efficient. For employees who need captions, searchable details, low-bandwidth access, or a private conversation, writing or a meeting may be more accessible and accountable.
A stronger trial would run across several cycles, randomly assign comparable teams where practical, report attrition and uncertainty, and measure whether the effect persists after novelty. It would separate message structure from medium: priorities plus recognition in writing, audio, and video with comparable preparation. Outcomes should include not only feelings of connection but recall, conflicting-priority resolution, response burden, equitable recognition, and whether employees can raise concerns and receive action.
Managers need no perfect study before trying a humane practice. A concise Monday explanation and sincere Friday acknowledgment may be worth piloting precisely because the cost is low. The evidence should determine how confidently the result travels, not whether anyone is allowed to experiment.
The addendum is that the article has found a promising prompt, not a proven video solution. Connection is reciprocal and accumulates through fair decisions, reliable support, listening, and follow-through. A manager's face on screen can add social presence, but it can also turn management into a broadcast. Use the routine, compare formats, and ask what changes over months. Do not let a one-week survey convert a product-compatible result into a general law of distributed work.