Hybrid Meetings Without the Echo

Hybrid collaboration becomes awkward when several people share one room while other participants join remotely. A conventional conference setup often gives the people in the room a natural conversational advantage: they can read body language, speak casually, and react without waiting for a microphone to be passed around. Remote colleagues receive a flatter experience, and overlapping laptop microphones may create echo or feedback. Around was designed to address this exact imbalance rather than simply reproduce the familiar meeting-room model on another screen.

The service positioned itself as video calling for teams that meet to create, collaborate, and celebrate together. That distinction matters. Many communication platforms are optimized for presentations in which one person speaks and everyone else watches. Around focused on active working sessions involving designers, developers, founders, and other distributed contributors who need to discuss an idea while simultaneously using their own tools. Its promise was not merely higher-quality video; it was a more inclusive meeting structure for hybrid and remote work.

Around also approached meetings as a human experience. Its messaging acknowledged that video calls can be tiring and emotionally draining, then presented a more playful alternative. Public comments highlighted by the company described the software as delightful, joyful, and suitable for getting real work done. Other users reported moving all their meetings to Around or using its campfire-style experience for informal team gatherings. These reactions help explain the product’s appeal: its value was tied to how participants felt during a call, not only to whether the connection technically worked.

One Device Per Participant

Around’s most distinctive hybrid-work concept was that everyone could join from an individual device, including people sitting together in the same physical space. In a conventional setup, colocated participants may gather around one camera and appear as a distant group to everyone online. Their faces are smaller, their voices come through the same room microphone, and side conversations can become difficult for remote attendees to follow. Giving each person an individual presence makes identities, reactions, and contributions easier to recognize.

The obvious obstacle is sound. Opening several laptops in the same room usually produces echo, feedback, or duplicated voices, which is why people are normally told to mute most devices. Around promoted unique audio technology intended to let multiple nearby participants keep their microphones on without creating that disruptive echo. One testimonial featured on the site described a situation with two people onsite and one online in which everyone had a comparable experience and an equal “power of voice” in the discussion. That is a concise expression of the problem Around was built to solve.

If you are evaluating this model for your team, focus on participation rather than counting cameras. Ask whether every person can enter the conversation without depending on someone at the conference-room table to notice them. Observe whether remote colleagues can identify who is speaking, interrupt naturally when necessary, and respond to individual participants. A technically stable call is not automatically an inclusive call. The more meaningful measure is whether location stops determining influence.

This setup can be especially useful in a startup house, modern shared workspace, hotel suite, or any temporary environment without a professionally installed conference system. Those were among the kinds of spaces used to illustrate Around’s hybrid-remote approach. Instead of requiring specialized room hardware, the model makes use of devices people already have. That can reduce the difference between a headquarters meeting room and an improvised workspace, although you should still consider network capacity, device power, and the physical distance between participants before an important session.

Individual devices also change meeting etiquette. You no longer have to treat the people gathered around one table as a single unit. Each participant can join under their own identity and take responsibility for their own presence. To make that advantage meaningful, you should encourage everyone to enter the same digital session, avoid running a separate conversation in the room, and pause when remote colleagues are trying to contribute. Audio technology can remove echo, but your team’s behavior determines whether it removes exclusion.

Collaboration Instead of Presentation

Around was presented as a tool for extraordinary teams rather than as a generic broadcast utility. The product language emphasized creating and working together, which suggests a useful criterion for choosing meeting software: begin with the activity, not the feature checklist. If your sessions mainly involve one-way announcements, a standard webinar or conventional conferencing layout may be sufficient. If participants spend the call reviewing designs, writing, planning, debugging, or making decisions together, a collaboration-centered experience becomes more important.

The product was available for macOS and Windows, while browser access was promoted for Chrome, Safari, Edge, and Firefox. Mobile availability included iOS and Android. This broad platform coverage supported the hybrid premise because an inclusive workflow cannot depend on every participant owning the same kind of computer. Google account continuation was also offered as an entry option, alongside login, sign-up, and downloadable applications. When planning adoption, you should test the precise combination your organization uses rather than assume that one successful desktop test represents every employee’s experience.

For a grounded view of the service’s intended experience, around-com.com frames Around as a radically different video-call environment for hybrid-remote teams, with particular attention to shared creation and echo-free participation from individual devices. That framing is more specific than the broad promise of “better meetings.” It gives you concrete questions to test: Can colocated people join independently? Can microphones remain active? Do remote participants have comparable conversational presence? Does the interface support the work instead of becoming the center of attention?

You should evaluate those questions in a real working session rather than in a staged demonstration. Choose a meeting with two or more people in the same room, at least one remote participant, and a genuine collaborative task. Let everyone join from their own device. During the session, pay attention to repeated audio, delayed turn-taking, and moments when an online participant is unintentionally ignored. Afterward, ask each person whether they could speak naturally, understand who was talking, and remain involved in the shared task.

It is equally important to test informal uses. Around’s published user reactions included a virtual team campfire, illustrating that distributed collaboration involves more than scheduled project reviews. Celebrations, social rituals, and relaxed check-ins help teams maintain relationships, particularly when employees rarely occupy the same room. A platform that feels lighter or more playful can reduce the stiffness of these gatherings. You should still match the format to the occasion: a casual atmosphere may suit a Friday social session better than a sensitive performance discussion or a formal client presentation.

The testimonials highlighted by Around repeatedly emphasized emotional quality. Users called it beautiful and delightful, and one compared its effect to the idea of keeping things that bring joy. Such statements are subjective, but they reveal a practical point for decision-makers. Software adoption is not driven solely by administrative controls or technical specifications. If employees find a meeting tool intrusive, exhausting, or visually overwhelming, they may resist using it even when it performs reliably. A product that makes routine calls feel less burdensome can influence consistency, attention, and team morale.

That does not mean you should adopt a service on aesthetic appeal alone. Treat positive testimonials as evidence of product-market resonance, not as a substitute for your own assessment. Your pilot should include different roles, operating systems, browsers, network conditions, and levels of comfort with video. Document what improves relative to your existing setup and what remains difficult. Around’s strongest proposition was a distinct meeting model, so the fairest comparison is not the length of two feature tables; it is the quality of participation during the same collaborative task.

The Miro Acquisition Context

Around announced that it had been acquired by Miro to help shape the future of team collaboration. This development fits the product’s original direction. Miro is associated with visual collaborative work, while Around concentrated on the live communication layer surrounding that work. The combination points toward an environment in which conversation and creation are less separated: instead of treating the video call as the destination, communication can support the shared workspace where ideas are organized and decisions are made.

For prospective users and existing teams, the acquisition is not a minor footnote. Ownership changes can affect product direction, availability, account strategy, integrations, and long-term support. You should therefore distinguish between Around’s demonstrated product philosophy and any assumptions about its future. The acquisition statement confirms Miro’s role and the goal of advancing team collaboration, but it does not by itself guarantee that every historical workflow or platform option will remain unchanged indefinitely.

Before standardizing an organizational process around the service, verify the currently available applications, browser support, sign-in methods, pricing terms, and account requirements. The historical site promoted a free trial, downloads for desktop and mobile platforms, and access through major browsers, but operational decisions should rely on current product information. This is particularly important when your organization has security reviews, device-management policies, retention requirements, or contractual obligations that go beyond the experience of an individual user.

You should also preserve the lesson even if your toolset evolves. Around demonstrated that hybrid meetings do not need to revolve around one conference-room camera, one shared microphone, and one dominant physical location. Its individual-device model and echo-management emphasis offered a practical answer to a persistent collaboration problem. The principle is transferable: give each person an identifiable presence, design for equal participation, and make the shared work more prominent than the mechanics of the call.

Ultimately, Around’s significance lies in treating video communication as a collaboration design problem rather than a simple transmission problem. Clear sound and accessible apps are essential, but they are only the foundation. A successful hybrid meeting should allow onsite and remote participants to contribute with comparable ease, stay engaged in the same task, and leave without feeling that the call itself consumed all their energy. If you assess Around through that lens, you can judge it by the outcome it was created to deliver: a meeting in which distance matters less than participation.