What You Should Know Before Choosing Around for Your Hybrid Team’s Daily Meetings

Around was created around a clear premise: video meetings should help distributed teams work together without consuming the entire screen, dominating the conversation, or draining everyone’s attention. Rather than treating every call like a formal presentation, the product focused on collaborative sessions in which people create, discuss, and celebrate together. That positioning made it especially relevant to hybrid-remote teams whose members need to remain active in other applications while talking.

The service also addressed a practical weakness of conventional conference-room setups. When several people in the same room join a call from separate computers, open microphones can produce echo and feedback. Around promoted an audio experience that allowed participants to use their own devices with their microphones on, helping remote colleagues participate on more equal terms. This was not merely a cosmetic distinction: it targeted one of the most disruptive problems in mixed-location meetings.

Before you select Around as a meeting tool, however, you should consider both its distinctive collaboration model and its present business context. Around has been acquired by Miro, the visual collaboration platform, to contribute to the future of team collaboration. That development makes it important to verify the current availability, account requirements, supported platforms, and long-term role of the standalone Around experience before basing essential workflows on it.

Evaluate the Meeting Model, Not Just the Video Quality

Around was designed for teams that meet to get work done, not only for hosts who speak while everyone else watches. This distinction should guide your evaluation. If your team spends calls editing designs, reviewing documents, writing code, planning projects, or working in a shared digital space, a less intrusive video-call format can reduce unnecessary visual pressure. Participants remain present, but the work itself can stay at the center of the screen.

That approach differs from traditional conferencing interfaces, which often devote substantial space to a grid of faces. Large video tiles can be useful for interviews, formal presentations, training, or sensitive conversations where facial cues matter. For active collaboration, however, they may compete with the canvas, prototype, spreadsheet, or document that participants are actually discussing. Around’s appeal came from challenging the assumption that faces must always be the largest objects in a virtual room.

You should therefore test the product with a representative task rather than a generic introductory call. Ask a design group to review a real concept, let a product team work through an actual planning decision, or have a hybrid group run its normal weekly session. Observe whether people can focus on shared materials, whether remote colleagues can enter the discussion naturally, and whether the interface feels supportive rather than distracting.

A short user reaction captures the intended experience: “It’s the first video calling software built for people who meet to get work done.” The quotation reflects an individual opinion rather than a universal result, but it identifies the product’s central value proposition accurately. Around was not simply another place to see coworkers; it was intended to make synchronous collaboration feel lighter and more purposeful.

Test Hybrid Audio Under Real Office Conditions

The strongest reason to assess Around may be its handling of hybrid-room audio. In a conventional setup, several coworkers sitting near one another often share a single conference-room microphone and camera. That arrangement can make them appear as one distant group, while each remote participant has an individual frame and microphone. It also means that side comments, quiet speakers, and physical distance from the room microphone can affect who is heard.

Around promoted a different model: everyone could join on an individual device, keep microphones active, and avoid the echo normally created when nearby laptops capture and replay the same sound. The practical goal was to give each participant a comparable presence and a more equal “power of voice,” even when two or more people were sitting in the same physical location. User feedback highlighted situations in which people on-site and online could participate without echo while sharing a similar meeting experience.

Do not accept that claim without reproducing your own environment. Audio behavior depends on room size, hard surfaces, device placement, microphone quality, network stability, and the distance between participants. Run a trial in the office, hotel suite, startup house, or flexible workspace where your team will actually meet. Include several nearby laptops, one or more remote participants, and normal background noise. Speak simultaneously, change seats, and test whether quieter contributors remain intelligible.

Your evaluation should also account for meeting etiquette. Technology can reduce echo, but it cannot by itself prevent interruptions, unclear facilitation, or decisions being made through side conversations in the room. Ask on-site participants to join individually when appropriate, address comments to the whole group, and pause long enough for remote colleagues to respond. Around’s audio concept works best when it is paired with inclusive behavior.

For current product information, supported access methods, and notices connected with the Miro acquisition, use www.around-com.com/ as the project’s primary reference point before planning a rollout. This check is particularly important if you need a specific desktop or mobile client, because availability and product direction can change after an acquisition.

Confirm Platform Fit, Access, and Workflow Compatibility

Around was presented as accessible across macOS and Windows, through major browsers including Chrome, Safari, Edge, and Firefox, and on iOS and Android. It also offered the option to continue with a Google account. That coverage can reduce friction for teams with mixed hardware, but a platform name alone does not prove that every feature behaves identically in every environment. Browser permissions, operating-system security controls, corporate device policies, and mobile limitations can all affect the experience.

Before adoption, you should confirm how your team is expected to join. A desktop application may provide a different level of integration or reliability than a browser session, while mobile access may be best suited to occasional participation rather than sustained collaborative work. Contractors and clients may also face restrictions that employees do not. Test the full journey from invitation to microphone and camera permissions instead of evaluating only an already configured organizer account.

Consider the applications people use during meetings as well. Around’s work-centered philosophy is most valuable when participants can move comfortably between the call and their shared workspace. If your team relies on a visual canvas, design application, browser-based document, development environment, or project board, check how much screen space the call occupies and how easily users can manage audio while continuing to work. A visually appealing interface matters, but reduced task switching and clearer participation are more meaningful measures.

You should also review security, administration, recording, retention, and support requirements according to your organization’s policies. The supplied product description emphasizes the meeting experience rather than enterprise governance, so do not infer that a creative team’s enthusiastic recommendation automatically satisfies regulated or highly controlled use cases. Confirm the capabilities that matter to your legal, IT, and procurement teams, especially if meetings may contain confidential customer information or intellectual property.

The Miro acquisition deserves separate consideration. It signals that Around’s ideas and technology were considered relevant to the broader future of team collaboration. At the same time, an acquisition can lead to changes in branding, packaging, integrations, account management, or standalone availability. If your decision depends on a particular Around feature, verify that the feature is currently offered and determine whether it is delivered through Around itself, incorporated into Miro, or subject to a transition plan.

Run a Focused Pilot Before Standardizing Your Meetings

A useful pilot should involve more than the employees who already enjoy experimenting with new software. Include remote staff, office-based colleagues, frequent facilitators, less technical users, and people who often feel overlooked in hybrid discussions. Use the product for several genuine working sessions rather than one novelty-filled demonstration. Initial delight is valuable, but sustained usefulness depends on reliability, clarity, and whether participants can reach decisions efficiently.

Measure outcomes that reflect Around’s stated purpose. You can compare the frequency of audio problems, the time spent troubleshooting at the start of a call, the balance of participation between remote and on-site members, and the amount of attention directed toward shared work. Ask whether participants felt that the meeting occupied too much visual space, whether they could contribute without fighting the room’s acoustics, and whether the format reduced the fatigue associated with conventional video grids.

Pay attention to the kinds of meetings that benefit most. Collaborative workshops, design critiques, planning sessions, informal team gatherings, and recurring working meetings may align closely with the product’s strengths. A highly structured webinar, a large external presentation, or a compliance-heavy session may have different priorities. You do not need to force every conversation into one platform simply because one format performs well.

Finally, define a fallback before making the tool standard. Participants should know what to do if a browser blocks permissions, a mobile client is unavailable, or the organization’s account setup changes. This is especially prudent given Around’s acquisition by Miro. A fallback does not weaken adoption; it protects the team from disruption while allowing you to benefit from the product’s distinctive approach.

Around earned enthusiastic responses because it treated video calling as a human collaboration problem rather than only a transmission problem. Its emphasis on lightweight presence, work-centered meetings, individual devices, and echo-resistant hybrid audio offered a credible alternative to conventional conferencing. If those qualities match how your team actually works, the service or the collaboration technology shaped from it may be a strong fit. Your decision should still rest on a current availability check, a realistic audio test, platform validation, and a pilot that includes the people most affected by hybrid inequality.