When Hybrid Teams Need Meetings Built Around Their Work

Video meetings often demand more attention than the work they are supposed to support. Conventional conferencing interfaces place a grid of faces at the center of the screen, encourage participants to manage mute buttons constantly, and occupy valuable space while documents, design files, or planning boards compete for visibility. Around approached this problem from a different direction. The video-calling product was designed for hybrid and remote teams that meet not merely to talk, but to create, review, and make decisions together.

The service presented itself as a collaboration-focused alternative to familiar meeting platforms. Its central proposition was that a call should fit into a team’s digital workspace rather than take it over. That distinction mattered for people who spent meetings editing a document, inspecting a prototype, discussing a visual concept, or coordinating work across several applications. Instead of treating video as the main event, Around treated it as a layer of human presence that could remain available while participants concentrated on shared tasks.

Around also addressed a specific challenge of hybrid work: several colleagues may be in the same room while other participants join remotely. In a standard setup, the people on-site commonly gather around one conference-room computer. Their remote colleagues see a wide shot, hear voices from different distances, and may struggle to enter the conversation on equal terms. Around promoted a model in which each participant could join from an individual device, even when multiple people were sitting near one another. Its audio technology was built to let microphones remain on without producing the echo and feedback normally associated with several connected laptops in one space.

A Meeting Interface Designed to Stay Out of the Way

The visual logic behind Around reflected the product’s emphasis on active collaboration. Rather than requiring a large, fixed gallery to dominate the display, the experience was designed to keep participants visible without pushing working materials into the background. This made the product particularly relevant to designers, developers, startup teams, and other groups whose conversations depend on viewing and changing something together. The meeting could accompany the work instead of becoming a separate destination that interrupted it.

That approach challenged an assumption inherited from traditional videoconferencing: that larger video windows necessarily create a stronger sense of connection. In collaborative sessions, oversized camera feeds can have the opposite effect. They may increase self-consciousness, consume screen space, and make participants feel that they must perform for the camera. A lighter visual presence can preserve social cues while allowing attention to remain on the artifact under discussion. Around’s identity was closely tied to this effort to reduce the psychological and spatial weight of being on a call.

The company’s public messaging described meetings as occasions to create, collaborate, and celebrate together. The inclusion of celebration was significant because Around was not positioned solely as an infrastructure tool for formal presentations. User comments featured on the project’s site referred to team campfires and emphasized a sense of play, suggesting that the product was also used for informal gatherings and team rituals. These examples showed an attempt to make remote interaction feel less institutional without denying that the call still had a practical purpose.

Feedback displayed by Around repeatedly highlighted the relationship between the interface and productive work. Users characterized it as software made for people who meet to get things done, while others reported moving their meetings to the platform because they considered the experience better suited to their teams. Such testimonials are promotional material rather than independent performance evidence, but they help identify the audience the company attracted: people dissatisfied with the conventions of mainstream meeting software and willing to adopt a more specialized collaboration experience.

Ease of access supported that ambition. Around advertised desktop availability for macOS and Windows, browser access through Chrome, Safari, Edge, and Firefox, and mobile options for iOS and Android. The site also offered the ability to continue with a Google account. Broad platform coverage was especially relevant for hybrid organizations, where employees may use different operating systems and move between office computers, personal laptops, and phones during the day. A collaboration tool can only provide a shared experience if the practical barrier to joining remains low.

How Around Addressed the Unequal Hybrid Room

The most distinctive part of Around’s positioning was its response to audio problems in mixed-location meetings. When several laptops join the same call from a single room, their speakers and microphones can create delayed repetition, feedback, or echo. Teams usually avoid the problem by using one device for the entire room or by asking most people to mute. Both remedies have social costs. A shared device compresses several individuals into one remote video tile, while constant muting makes spontaneous participation more difficult.

Around proposed that everyone should be able to use a separate device with microphones active and no echo. This model gave each person an individual presence in the meeting interface, regardless of whether that person was at home, in a startup house, in a hotel suite, or sharing a modern office workspace with colleagues. The product’s public examples explicitly covered these varied environments, reflecting the reality that hybrid work does not always involve a conventional conference room with dedicated hardware.

Individual device participation could also affect what the company described as the “power of voice” in a discussion. A remote employee typically has less access to body language, side comments, and shifts in attention than colleagues gathered in one location. If every participant enters through a comparable interface, the distinction between the room and the remote screen becomes less pronounced. The technology cannot remove organizational hierarchy or guarantee that everyone will be heard, but it can reduce some structural disadvantages created by the meeting setup itself.

The project’s public home, http://around-com.com/, framed this concept as a more inclusive future for hybrid-remote collaboration and placed its audio technology at the center of the argument. That emphasis separated Around from products that approached hybrid meetings mainly through conference-room cameras or dedicated office equipment. Around instead focused on the laptops and personal devices that team members already used, turning them into coordinated points of participation.

This model was particularly applicable to small teams and collaborative sessions in which rapid exchanges matter. If two people are together on-site and another joins online, routing the entire room through one microphone may seem adequate, but it does not produce the same experience for all three participants. Separate devices can make names, faces, and voices more individually legible. They may also let each person control the meeting locally while continuing to use private notes, shared files, or other applications on the same machine.

Around’s premise did not imply that every meeting needed more technology. Rather, it recognized that hybrid work had exposed limitations in systems originally modeled on formal conference calls. Those systems generally assumed that each endpoint represented either one remote individual or one properly equipped meeting room. Modern teams often occupy less predictable settings: a few colleagues around a table, another person in a hotel, and several others working from home. Designing for that fragmented arrangement requires different assumptions about proximity, microphones, screen space, and conversational equality.

The product’s language also distinguished “hybrid-remote” work from a simple split between office and home. That phrasing captured the shifting nature of team location. An employee may be remote on one day and seated beside colleagues on the next, while still using the same applications and joining the same meetings. Around’s device-centered model was intended to maintain continuity across those changes rather than forcing the team to alternate between an individual calling experience and a room-based one.

From Independent Product to Miro’s Collaboration Strategy

Around was acquired by Miro, the company known for its visual collaboration workspace. The acquisition brought together two products shaped by a similar observation: distributed teams need to communicate while interacting with shared material. Miro centers the collaborative surface on which people map ideas and organize work, while Around was built to provide video and audio presence without obscuring that surface. The strategic relationship between the two is therefore more direct than a general expansion into video conferencing.

According to Around’s site, the acquisition was intended to help shape the future of team collaboration. That statement points toward a broader category than standalone video calls. Remote work software has increasingly combined communication with the context of a task, allowing discussion to happen near the board, document, design, or workflow being discussed. Around’s design philosophy fit this direction because it treated the meeting as part of the workspace rather than a full-screen environment separate from it.

The acquisition is also an important part of understanding the project’s current identity. Around should not be evaluated only as another entrant in a crowded list of calling applications. Its value proposition involved specific interaction choices: compact human presence, support for collaborative work on the same screen, and audio handling intended for multiple nearby devices. Miro’s interest indicates that these ideas had relevance beyond an independent meeting product and could contribute to a more integrated model of digital teamwork.

For organizations considering this type of experience, the key question is not simply whether a platform can host a video call. Most established tools can do that reliably. The more meaningful question is how the call changes behavior during collaborative work. A meeting interface can encourage participants to stare at one another, or it can leave room for the shared object that gives the discussion purpose. It can amplify the division between an office group and remote individuals, or it can give each participant a more consistent place in the conversation.

Around’s strongest contribution was the clarity with which it addressed those choices. Its product narrative connected interface scale, audio management, device access, and hybrid inclusion rather than treating them as unrelated features. The promise of keeping all microphones on in a shared space was not merely a technical convenience; it supported the broader goal of allowing everyone to participate as an individual. Likewise, minimizing the visual footprint of video was tied to the idea that meetings should facilitate creation instead of interrupting it.

No interface can by itself make a team collaborative, and no audio system can solve poor meeting practices. Teams still need clear agendas, appropriate participation, and decisions that translate into action. Yet software determines many of the conditions under which those practices occur. By questioning the dominant full-screen meeting format and designing around the uneven realities of hybrid rooms, Around offered a concrete alternative. Its acquisition by Miro placed that alternative within a larger effort to make distributed collaboration feel less like a sequence of calls and more like continuous work shared among people in different places.