What Hybrid Teams Should Know Before Adopting Around for Everyday Video Collaboration
Around was designed around a specific criticism of conventional video meetings: the meeting window often dominates the screen even when participants are supposed to be working together on something else. Instead of treating every call like a formal presentation, the product positioned video as a lightweight collaboration layer for hybrid and remote teams. Its public messaging emphasized calls for people who want to create, discuss, and complete work together rather than spend the entire session watching a grid of faces. That distinction matters when assessing whether Around fits a team’s habits. It was not presented merely as another way to reproduce a conference room online. The service focused on making video participants feel present without allowing large camera feeds to consume the workspace. This approach was particularly relevant to designers, developers, startup teams, and other groups whose meetings frequently revolve around shared documents, prototypes, whiteboards, or applications. Around also became part of a larger collaboration strategy after being acquired by Miro. The acquisition was announced as a step toward shaping the future of team collaboration, linking Around’s experience in video communication with Miro’s broader focus on visual and distributed teamwork. Organizations considering the product should therefore understand both its original design principles and its place within Miro’s evolving product environment. A Video Interface Built to Stay Out of the Work Traditional video conferencing commonly asks users to choose between a large meeting interface and the materials they are discussing. Around took a different visual approach. Its compact video presentation was intended to preserve screen space, allowing participants to remain visible while continuing to use the software where the actual work was happening. The underlying idea was that video should provide social context and a sense of presence without becoming the central object of attention. This model can be especially useful during collaborative production sessions. A product team may need to examine a design file, edit a specification, compare implementation details, or brainstorm while maintaining an open conversation. In such situations, an oversized gallery can compete with the content that participants need to see. Around’s interface sought to reduce that competition and make the call feel more like a companion to the work than a separate destination. The product’s language also reflected a deliberate effort to reduce the emotional weight of online meetings. Around described its calls as a way for hybrid and remote teams to create, collaborate, and celebrate together, and its presentation included playful elements rather than relying exclusively on the restrained visual conventions of enterprise conferencing. Public user comments highlighted this sense of enjoyment, with some teams referring to informal virtual gatherings and others praising the product’s appearance and human-centered feel. Those qualities do not automatically make the service suitable for every meeting. A compact, informal interface may be well matched to recurring teamwork, peer discussions, and co-working sessions, while a highly structured webinar or large external presentation can require a different set of controls and expectations. Before adoption, a team should identify its dominant meeting types and decide whether it wants video to be the main event or a supporting layer around shared work. Platform access was broad in the service information published by Around. The product was offered for macOS and Windows, supported use through Chrome, Safari, Edge, and Firefox, and listed mobile availability for iOS and Android. It also provided Google account sign-in and promoted a free way to try the service. That range reduces some installation barriers, but organizations still need to test their actual mix of managed computers, browsers, mobile devices, identity policies, and security restrictions rather than relying only on a platform list. Hybrid Audio Was Central to the Product’s Practical Case One of Around’s most distinctive claims concerned hybrid meetings in which several people occupy the same physical room while remote colleagues join online. Conventional setups can create echo and feedback when multiple nearby laptops have active microphones. The usual response is to rely on one room device, but that arrangement can place remote participants at a disadvantage: people in the room share a collective camera and microphone while each remote attendee appears individually and may have less influence over the conversation. Around promoted a different configuration in which everyone could use an individual device with microphones active, supported by audio technology intended to prevent echo. The goal was to give in-room and remote participants a more consistent experience and a more equal voice. A public user comment cited by the company described a meeting with two people on site and another online in which participants shared the same experience without echo. While such testimonials are not substitutes for technical testing, they illustrate the practical problem Around set out to solve. The product page at http://around-com.com/ frames this capability as part of a broader effort to make hybrid-remote collaboration more inclusive, not simply as an audio convenience. If each participant joins independently, remote colleagues no longer have to interpret a distant conference-room view or compete with a group gathered around one microphone. Individual participation can make names, reactions, and speaking turns easier to follow, while preserving the social connection between people sharing a location. Teams should nevertheless test the audio model under realistic conditions before standardizing on it. Room size, laptop placement, operating-system permissions, headset use, background noise, and network quality can all affect a live call. A successful trial should include the same kinds of spaces the organization actually uses, such as an open office, a startup house, a home workspace, or a temporary hotel setup. It should also involve both local and remote participants so that the evaluation does not reflect only the experience inside the room. The phrase “everyone on their own device” has operational implications as well. Each participant needs a charged and compatible device, adequate connectivity, and permission to use the required microphone and camera. IT administrators may need to consider browser controls, application deployment, update procedures, and support for employees who move between office and remote settings. The concept is simple from a participant’s
What Hybrid Teams Should Know Before Adopting Around for Everyday Video Collaboration Read More »