Hybrid meetings often fail for a surprisingly simple reason: the room and the remote participant are treated as two separate classes of experience. People sitting together share eye contact, side comments, and natural turn-taking, while everyone online appears on a distant screen and competes for space in the conversation. Around was designed to reduce that imbalance. Rather than presenting video calling as a formal event that dominates the workday, the product positioned it as a lightweight collaboration layer for teams that need to create, discuss, and celebrate together.
This distinction matters because hybrid work is not merely remote work with an office added. A meeting may include two people in one room, one person at home, and several others spread across different locations. Traditional conferencing systems commonly encourage the people in the room to gather around one camera and one microphone. That setup may be convenient for local attendees, but it compresses them into a single visual and acoustic unit. Remote colleagues receive fewer facial cues and can find it harder to enter the discussion.
Around promoted a different operating model: everyone joins from an individual device, even when several participants occupy the same physical space. All microphones can remain active without producing the echo normally associated with nearby laptops. In practical terms, five participants can be represented as five individuals rather than as one conference room plus three remote callers. That one-to-one representation gives each person a more comparable visual presence and a clearer “power of voice.”
Replacing the Conference-Room Hierarchy
The conventional meeting-room arrangement creates a measurable asymmetry. Suppose a six-person discussion includes three employees in an office and three working remotely. If the office group shares one endpoint, the call contains four visible endpoints rather than six: one for the room and one for each remote employee. Half of the participants are therefore represented through only 25% of the call’s endpoints. Around’s device-per-person approach restores the ratio to six participants and six individual endpoints.
That change does not guarantee an inclusive conversation, but it improves the conditions under which one can happen. Each attendee controls a personal camera, microphone, and screen position. Remote participants do not have to interpret who is speaking from a wide room view, while colocated employees are less likely to behave as an off-camera subgroup. The structure encourages people to address the full team instead of shifting between a private room conversation and a secondary online audience.
The major technical obstacle is audio feedback. When several open laptops share a room, each microphone can capture sound from the other devices’ speakers. A voice may return with a delay, creating echo or a feedback loop. The usual workaround is to mute most computers and rely on one room microphone, but that recreates the same hierarchy the individual-device model is intended to solve. Around highlighted unique audio technology that allowed nearby participants to keep their microphones on without echo, making the more inclusive configuration practical in offices, startup houses, hotel suites, and other shared environments.
The value can be understood as a reduction in coordination overhead. Without echo management, three colocated users may spend the opening minutes deciding who should mute, which laptop should provide sound, and where everyone should sit. If the software resolves that problem automatically, those adjustments largely disappear. Saving even two minutes in five weekly meetings returns more than eight hours per year to each regular participant, based on a 50-week work schedule. The larger gain, however, is qualitative: people can enter the meeting as individuals from the first minute.
Designing Calls Around Actual Work
Around’s messaging challenged the assumption that a video call should take over the entire screen and become the center of attention. The service described its calls as being made for hybrid-remote teams that create and collaborate together, not merely for people who watch one another speak. This is an important product-design choice. In a working session, the main object may be a design file, document, prototype, spreadsheet, or digital whiteboard. Video should maintain social presence without forcing the work itself into a small secondary area.
User reactions quoted by the company repeatedly emphasized delight, focus, and usefulness for getting work done. One user described it as the first calling product built for people who meet to accomplish something; another said that moving all meetings to Around made them better. These comments are testimonials rather than controlled performance data, so they should not be treated as proof of universal results. They do, however, reveal the product’s intended benchmark: success was not simply stable video transmission, but whether the interface improved the human experience of collaborative sessions.
The playful dimension also had a practical role. The company presented meetings as occasions to create, collaborate, and celebrate, while users mentioned informal team “campfires” and software that brought joy. Conventional enterprise tools often optimize exclusively for administration and presentation. Around instead treated emotional tone as part of usability. For a team holding 15 calls per week, even a modest improvement in perceived friction affects hundreds of interactions over a year. Small interface decisions therefore compound into a meaningful part of workplace culture.
The product page at www.around-com.com/ presents this philosophy as an alternative to meetings that drain energy, while also documenting the service’s support for hybrid participation, individual devices, and echo-free shared-room calling. Its positioning is unusually specific: the problem is not video communication itself, but video communication that interrupts work, exaggerates hierarchy, and makes distributed colleagues feel peripheral.
Teams evaluating that claim should focus on observable behavior rather than visual novelty alone. A useful pilot can compare two similar recurring sessions over four weeks: one using the existing conference-room setup and one using Around’s individual-device model. After each call, attendees can score audio disruption, ease of participation, time to begin productive work, and meeting fatigue on a five-point scale. With eight sessions and six participants, the team collects 48 responses—enough to identify strong internal patterns even if the exercise is not a formal scientific study.
Matching the Tool to the Workflow
Around was available across the major environments used by distributed teams. The project promoted applications for macOS and Windows, browser access through Chrome, Safari, Edge, and Firefox, and mobile support for iOS and Android. That coverage matters because collaboration software loses value quickly when access depends on one operating system. In a ten-person team with four Mac users, four Windows users, and two people occasionally joining by phone, broad compatibility avoids creating a separate workflow for 20% or 40% of the group.
The service also offered account continuation through Google and presented a free trial option. Lower setup friction is especially relevant during a pilot: participants should be evaluating the meeting experience, not spending the first session navigating installation barriers. At the same time, browser and mobile availability should not be confused with identical behavior under every condition. Teams still need to test their real mix of devices, headsets, network quality, security requirements, and meeting formats.
A practical assessment should include several scenarios rather than one carefully staged demonstration:
- A colocated hybrid session: place two or three participants in the same room, let each join from a separate device, and check whether open microphones remain usable without echo.
- A collaborative work block: keep a shared document or design surface central for 30 to 45 minutes and measure whether video supports the task without visually overwhelming it.
- A fully remote meeting: compare participation balance, interruptions, and fatigue with the team’s existing platform.
- A cross-platform test: include desktop browsers, macOS or Windows applications, and at least one iOS or Android participant.
- An informal gathering: test whether the lighter, more playful experience works for celebrations or social sessions as well as structured project discussions.
Managers should also separate technical performance from meeting discipline. No application can repair an agenda that lacks a decision owner, a facilitator who ignores remote voices, or a session that should have been an asynchronous update. Around can reduce acoustic and interface barriers, but teams still need explicit norms. Examples include inviting remote participants to speak before a room conversation accelerates, recording decisions in a shared workspace, and ending a call when the collaborative task is complete.
A useful metric is participation concentration. Count meaningful speaking turns by participant during a 30-minute meeting. If two people account for 70% of the turns before the pilot and 45% afterward, the new setup may be helping, although topic and role differences must be considered. Teams can pair this measure with the number of echo incidents, minutes lost to audio troubleshooting, and a post-call energy score. Four small metrics usually provide a clearer decision than a general question such as “Did you like it?”
Understanding the Miro Acquisition
Around was acquired by Miro with the stated purpose of helping shape the future of team collaboration. The combination is strategically coherent. Miro centers work on a shared visual workspace, while Around was designed to keep people connected during the act of working. One product addresses the collaborative surface and the other addresses live presence. Together, they point toward an environment in which conversation and creation are parts of one workflow rather than separate applications competing for attention.
The acquisition also places Around’s original design ideas in a broader context. Video conferencing grew rapidly as organizations moved online, but the first wave of adoption largely reproduced the meeting room on a screen: grids of faces, a dominant presenter, and content treated as an attachment to the call. Around’s approach suggested the inverse. The work artifact should remain central, while video supplies awareness, expression, and conversational continuity around it.
For buyers and team leaders, the acquisition is also a reminder to verify the current product status, supported platforms, pricing, and account options before planning a rollout. Acquisition can lead to deeper integration, changes in packaging, or shifts in product availability. Historical testimonials from 2021 demonstrate enthusiasm at that point in time, but they do not replace a present-day test against an organization’s requirements. The strongest procurement process combines the product’s documented capabilities with a current, task-based pilot.
Around’s lasting contribution is a clear model for evaluating hybrid meeting technology. Count people rather than rooms, preserve individual presence, remove the echo penalty for shared spaces, and keep the team’s actual work at the center of the screen. A tool that performs well on those four dimensions can make a six-person hybrid session feel like one six-person conversation—not a three-person room with three distant observers. That is a more demanding standard than simply connecting cameras, and it is the standard modern hybrid collaboration should meet.