DEV Community: Sannan Malik

Meeting Fatigue Is Real. Here's What's Actually Causing It (and How AI Helps)

Sannan Malik — Thu, 02 Jul 2026 08:15:02 +0000

Meeting fatigue isn't about video. Researchers who initially attributed the exhaustion of remote work to video calls — "Zoom fatigue," as it was widely labeled — have since found a more complicated picture. The camera isn't the main culprit. The structure of the meetings, or the lack of it, is.

What actually causes meeting fatigue

Context switching. Most knowledge workers move between meetings with no buffer. The cognitive cost of shifting from a technical review to a client call to a strategy discussion, back-to-back, accumulates in a way that a single long meeting doesn't.

Low signal, high noise. Meetings where attendees don't know why they're there, decisions never get made, or topics drift without resolution aren't just a waste of time — they're actively draining. The brain works hard tracking a conversation that goes nowhere.

The burden of being "on." Video adds a specific layer: the awareness of being seen, managing your own image (the self-view problem), and the social obligation to appear engaged even when the content doesn't require it.

Post-meeting overhead. The meeting ends, but the work doesn't. Someone needs to write the notes, send the follow-up, debrief stakeholders who weren't there, and track the action items that came out of it. That invisible overhead falls unevenly across teams.

What makes it worse on distributed and global teams

Remote and hybrid teams have amplified every one of these factors. More meetings happen because fewer decisions are made in passing. Async coordination gaps get patched with synchronous calls. And for global teams with language differences, the cognitive load of following a meeting in a second language sits on top of everything else.

Non-native speakers in a meeting aren't just listening — they're translating, processing and responding simultaneously. The fatigue that creates is different in kind from what native speakers experience, and it rarely shows up in satisfaction surveys because it's rarely named.

Where AI actually helps — and where it doesn't

AI isn't a cultural fix. If your meetings are poorly structured, have unclear ownership, or exist because your organization hasn't learned to communicate asynchronously, adding an AI summary tool will give you a more organized record of a bad meeting.

That said, there are specific fatigue vectors where AI genuinely reduces load:

Note-taking anxiety. Many people attend meetings half-listening, half-documenting, fully not doing either well. When notes are generated automatically, attention can go fully on the conversation. That's not a small thing.

The "what was decided" loop. The cycle of following up, re-checking, and re-litigating decisions because there's no reliable written record is exhausting. AI-generated recaps with structured decisions and action items break that loop.

Translation overhead. For non-native speakers, per-participant live translation — the kind where each person reads in their own language, not a shared second language for the room — reduces cognitive load in a way that a monolingual transcript doesn't. Tools like MeetOye build this into every call, so it's consistent rather than something the host has to configure per meeting.

Post-meeting documentation. Automatically emailed recaps replace the half-hour one person spends reconstructing the meeting from memory afterward. That half-hour, multiplied by meeting frequency and team size, is real recovered time.

What HR teams should actually measure

Meeting fatigue doesn't show up cleanly in engagement scores. If you want to actually understand it:

Meeting load per person: total hours in meetings per week, not just count
Meeting-to-outcome ratio: how many meetings produce a clear decision or action vs. status updates and discussions with no output
Post-meeting time cost: who is doing the recap, debrief and follow-up work, and how long it takes
Participant role distribution: are most attendees active or passive? High passive-attendee rates signal a list problem (too many people invited) or a structure problem (no clear reason to be there)

The goal isn't to eliminate meetings. It's to make the time in them worth the cognitive cost — and to reduce the invisible overhead that happens after them.

Author bio:
The MeetOye Team writes about people operations and the future of work. MeetOye (meetoye.com) is an AI-native video meeting platform that automatically transcribes, translates per participant, and emails a recap with decisions and action items when every call ends.

How AI Is Actually Changing the Meeting Room in 2026

Sannan Malik — Thu, 02 Jul 2026 08:14:52 +0000

Every productivity category eventually gets an AI layer. Meetings are no different — but the way AI is integrating into meeting rooms is less uniform than the marketing suggests. There are two genuinely different approaches, and they produce very different outcomes for the teams using them.

The first wave: AI as a visitor

The earliest AI meeting tools were add-ons: a bot you invited to your call. It joined as a visible participant, announced itself, recorded the audio, and sent you a transcript and summary afterward.

The appeal was obvious — it worked across any video platform you already used. The friction was also obvious: you had to remember to invite it. Someone occasionally forgot. Sensitive calls made attendees uncomfortable with an unrecognized participant recording everything. And the summary arrived via a third-party service that now held your meeting data.

This model is still dominant — Otter.ai, Fireflies.ai, and dozens of similar tools operate this way. They're useful. But they solve the transcript problem while introducing new ones around reliability, data custody and participant trust.

The second wave: AI as infrastructure

The more interesting shift is AI that doesn't arrive as a visitor — it's already in the room, built into the meeting platform itself.

This changes the dynamic in ways that matter. There's nothing to invite, so coverage is consistent. There's no separate participant making people pause before saying something sensitive. The transcript and recap aren't held by a third-party service — they're part of the meeting record, subject to whatever data policy applies to the meeting itself.

Platforms built on this model — MeetOye is one example — treat the AI layer as the default infrastructure of every call rather than an optional add-on. Oya, MeetOye's built-in assistant, transcribes and translates in real time, then emails a recap with decisions and action items to every attendee automatically when the call ends.

The translation gap

One specific area where AI is making a measurable difference: live translation.

The previous approach to multilingual meetings was simultaneous interpretation — an expensive human service reserved for conferences and executive calls. The tier below that was nothing: participants in a meeting they only half-understood, relying on the dominant-language speaker to summarize.

AI translation has moved this from a conference luxury to a per-meeting default. The more sophisticated implementations don't just show one shared translated caption for the room — they give each participant their own caption stream in the language they chose, regardless of what language the speaker is using. That distinction matters more than it looks: one shared caption language still requires participants to read in a second language; per-participant translation lets each person choose their own.

What AI still doesn't do well in meetings

Honest assessment:

Follow-up enforcement. AI can write an action item. It cannot make anyone do it. The accountability layer is still social and organizational.

Judgment about what to escalate. A transcript of a tense conversation and a structured summary of a productive one look similar to a language model. The nuance of what matters is still human.

Real-time facilitation. AI can suggest an agenda and flag when time is running short. It cannot redirect a derailed conversation or manage the room dynamics of a difficult discussion.

The practical takeaway

AI in meetings is most valuable when it handles the mechanical cognitive work — capturing, labelling, summarizing, translating — so that human attention can stay on the judgment-intensive parts: listening, deciding, responding.

The teams getting the most out of it are treating the AI layer as infrastructure: always on, consistently applied, not something that requires anyone to remember to set up. That shift from optional add-on to default behavior is where the actual productivity gain lives.

Author bio:
The MeetOye Team covers AI and the future of work. MeetOye (meetoye.com) is an AI-native video meeting platform with Oya, a built-in assistant that transcribes, translates per participant, and recaps every call automatically.

The IT Buyer's Checklist for Video Conferencing Platforms in 2026

Sannan Malik — Thu, 02 Jul 2026 07:57:25 +0000

Buying a video conferencing platform has always been more complex than it appears. The sales demo looks clean. The pricing page looks simple. And then procurement, security, legal and IT operations each have a list of questions that didn't come up in the demo.

This checklist is for the people who have to live with the decision after the contract is signed.

Section 1: Identity and Access

SSO and directory integration

Does it support SAML 2.0 or OIDC for SSO?
Does it integrate with your identity provider (Okta, Azure AD, Google Workspace, etc.) for automated provisioning and de-provisioning?
What happens to an account when a user is terminated? Is de-provisioning instant, or is there a lag?

Guest access

Can external guests join without creating an account?
Is guest access controlled per-meeting by the host, or globally?
Are guest identities verified, or anonymous by default?

Section 2: Data Residency and Compliance

Where does data live?

In which country or region are recordings, transcripts, and meeting metadata stored?
Is data residency configurable by region (EU, US, APAC)?
Can you get a Data Processing Agreement (DPA) on request, or is it standard?

Regulatory alignment

Is the platform documented as GDPR-compliant?
For healthcare customers: is a Business Associate Agreement (BAA) available for HIPAA?
What certifications does the platform hold (SOC 2 Type II, ISO 27001)?

AI data handling

If the platform uses AI for transcription or summarization, is meeting content used to train models?
Is there an opt-out mechanism, and does it apply to all AI processing or only some?
Which third-party AI providers does the platform send meeting content to?

Section 3: Media Architecture and Security

Media path

Does audio/video flow through a vendor-operated media relay, or is there a self-hosted option?
Is end-to-end encryption available, and is it on by default or opt-in per meeting?
What happens to a meeting if the vendor's media infrastructure has an outage?

Self-hosting and on-prem

Is self-hosted or on-prem deployment offered?
What components can be self-hosted (just the media server, or also the application and database)?
What is the operational overhead of the self-hosted deployment — is it containerized and documented, or requires specialist knowledge?

Platforms like MeetOye are designed with this separation from the start: media runs through a dedicated SFU (Selective Forwarding Unit) that can be self-hosted, separate from the application API, so a compromise of one layer doesn't automatically expose the other.

Section 4: Administration and Operations

Admin console capabilities

Can administrators see meeting attendance, duration and recording status across the organization?
Are there role-based access controls (RBAC) for host permissions?
Can admins configure defaults at the organization level (e.g., recording off by default, AI on by default)?

Audit logging

Are admin actions and meeting events logged in an audit trail?
Is the audit log exportable, and in what formats?
How long are logs retained, and is that configurable?

Retention policy

What is the default retention period for recordings and transcripts?
Can retention be configured per organization or per meeting type?
Is deletion verifiable — can you confirm that data has been removed from backup systems?

Section 5: Reliability and Scalability

SLA and uptime

What uptime SLA does the vendor offer, and what is their documented historical uptime?
What compensation is offered for SLA breaches?
Is status and incident reporting publicly available?

Behavior at scale

What is the documented maximum participants per meeting?
Is video quality adaptive to network conditions, or does quality drop uniformly?
Are there documented limits on concurrent meetings across an organization?

Section 6: AI Features — Questions Enterprise IT Often Misses

AI meeting features (transcription, translation, summarization) are now part of most platform evaluations, but the questions IT usually asks are about the surface features. The deeper questions:

Is AI processing done on the vendor's infrastructure, or outsourced to a third-party API?
If outsourced, to which providers, and what are their data terms?
Are AI features on by default for all users, or must an admin explicitly enable them?
Can AI be disabled per meeting for sensitive discussions?
Is the generated transcript available only to attendees, or to any org admin?

Quick reference scoring matrix

Category	Questions to settle before contract
Identity	SSO, provisioning, guest control
Data residency	Storage location, DPA, GDPR/HIPAA
Media security	E2E encryption, self-hosting, SFU architecture
Admin control	Org-level defaults, RBAC, audit logging
AI data handling	Model training opt-out, third-party AI sub-processors
Retention	Default period, configurable, verifiable deletion

Author bio:
The MeetOye Team covers enterprise technology procurement and IT operations. MeetOye (meetoye.com) is an AI-native video meeting platform with SOC 2 Type II, GDPR and HIPAA-aligned controls, self-hosting support, and a media architecture that keeps audio/video separate from the application backend.

Who Owns Your Meeting Transcripts? A Question More Teams Should Be Asking

Sannan Malik — Thu, 02 Jul 2026 07:57:16 +0000

When someone asks you to sign a meeting NDA, the implicit assumption is that what's said in the call stays between the people on it. In most video conferencing setups, that assumption is wrong — not because of a data breach, but because of the default architecture.

Your meeting transcript, in most configurations, is stored by a vendor you pay for a service. Their privacy policy governs what they can do with it, their security practices govern how well it's protected, and their infrastructure (and the infrastructure of their sub-processors) determines where it actually lives.

For most consumer and SMB use cases, this isn't alarming. For teams handling regulated data, sensitive client information, or IP that represents genuine competitive advantage, it's worth understanding before it becomes a problem.

The three-layer data question for meetings

When evaluating where your meeting data goes, there are three distinct questions:

1. Where does the media go?
Audio and video during a call travel through a media relay server — a Selective Forwarding Unit (SFU) in modern WebRTC implementations. In most hosted platforms, this is the vendor's infrastructure. In self-hosted deployments, it stays on infrastructure you control. The distinction matters: your team's audio and faces traverse this infrastructure in real time.

2. Where does the transcript go?
Speech-to-text requires compute — the audio has to be sent somewhere for processing. In most platforms, this means a cloud AI provider (often one of a few major US or EU services). The privacy policy governs data retention and usage for training. Not all policies are equivalent.

3. Where does the summary/recap go?
Summary generation is an additional AI processing step on top of the transcript. If the platform uses a third-party LLM API for this, the text of your meeting — decisions, action items, discussion content — is sent to that API under that provider's terms.

What makes this concrete

Most organizations couldn't immediately answer these questions about the meeting platform they use today:

Which country are meeting recordings stored in?
Does the vendor use your meeting content to improve their AI models, and can you opt out?
If the vendor has a data breach, what was exposed — video files only, or transcripts and summaries?
Are transcripts automatically deleted after a retention period, or stored indefinitely?

Under GDPR, HIPAA, and similar frameworks, these aren't abstract questions — they're due-diligence requirements for organizations handling data subject to those regulations. Many companies discover the gap when a compliance review asks for a data processing agreement with their video platform and the vendor can't produce one quickly.

Architecture choices that reduce exposure

Separate media from application logic. Meeting platforms where audio/video flows through a dedicated media engine — rather than through the same infrastructure that handles authentication and data storage — have a smaller attack surface. A compromise of the application layer doesn't necessarily expose media content.

Self-hosting. Keeping media and transcripts on infrastructure you own and control is the highest-assurance option. It's operationally heavier, but for regulated industries it's often the only viable path.

Explicit data retention controls. Transcripts and recordings should have configurable retention — automatically deleted after 30, 90 or 180 days, or on request, rather than stored indefinitely as a default.

Audit trails. For regulated environments, knowing who accessed a meeting transcript, when, and from where is as important as knowing where it's stored.

Platforms like MeetOye are designed with these considerations as defaults rather than enterprise add-ons: media runs through a dedicated, separable engine; transcripts are visible only to meeting attendees; self-hosting is available for teams that need full data sovereignty; and deletion is attendee-controlled rather than vendor-determined.

The practical steps for any team

If you're not ready to switch platforms, there are things you can do with your current tooling:

Read the DPA (Data Processing Agreement). Most major platforms have one. It tells you exactly what they can do with your data. If you can't find it, ask — the response time tells you something.

Audit your recording defaults. Many platforms enable cloud recording by default. Verify whether your meetings are being stored when you don't intend them to be.

Turn off AI features for sensitive calls if needed. If you don't need a transcript for a particular call — legal discussion, HR conversation, M&A discussion — check whether your platform lets you disable it per meeting.

Include meeting data in your data classification policy. If your organization classifies data by sensitivity, meeting transcripts should be in that taxonomy. Right now, most organizations treat them as unclassified by default.

The meeting room is where decisions get made, sensitive topics get discussed, and confidential information gets shared. Treating its data residency and retention as an afterthought is increasingly hard to justify — and increasingly hard to explain to regulators when it comes up.

Author bio:
The MeetOye Team covers data privacy and enterprise security. MeetOye (meetoye.com) is an AI-native video meeting platform with privacy-by-architecture: media flows through a dedicated engine separate from the application layer, transcripts are visible only to attendees, and self-hosting is available for regulated environments.

The Case for Transcript-First Meetings

Sannan Malik — Thu, 02 Jul 2026 07:51:46 +0000

There's a quiet assumption embedded in most meeting tools: the recording is the record.

This is how it works: the call gets recorded, the video file sits in cloud storage, and anyone who needs to know what happened can "go watch the recording." In practice, nobody watches the recording. It's a 47-minute MP4 file with no searchable content, no timestamps tied to decisions, and a viewing experience that requires scrubbing through other people's camera feeds to find a two-minute moment that mattered.

The recording-first model optimizes for completeness (everything is captured) while failing at usability (almost nothing captured is ever retrieved). The alternative — transcript-first — flips that trade-off.

What transcript-first actually means

A transcript is a time-stamped, speaker-labelled text record of what was said. In isolation, it's long and unwieldy. But it's the foundation for everything else:

Searchability. You can find a decision made three months ago in ten seconds. You can't do that with a video.
Summarization. A language model can produce a useful summary from a transcript. It cannot reliably do so from an audio stream alone.
Translation. Text translates well. Video of someone speaking in a second language, with background noise and varying audio quality, translates poorly.
Async access. Reading a transcript at 3x speed takes a fraction of the time watching a recording does. The information density per minute is higher.

Why most teams still default to recording

Inertia and familiarity. Video platforms built video recording first, and transcript as a secondary feature — often added later, often gated behind higher plan tiers. The transcript feels like an add-on to the recording, rather than the reverse.

There's also a false equivalence between completeness and usefulness. A video "captures everything," which feels thorough. But capturing everything is only valuable if someone retrieves it, and the retrieval mechanism for video (scrubbing) is slow enough that most captures are effectively permanent archives that nobody accesses.

The async implications

For distributed and remote teams working across time zones, this distinction matters most. The transcript — not the recording — is what enables async participation. Someone who couldn't attend the meeting can read the transcript and the AI-generated summary in five minutes and understand what happened and what's needed from them. They cannot reasonably do this from a recording.

This changes what "recording the meeting for people who missed it" actually means. A transcript + structured recap is a more useful artifact than a video for almost every async purpose. The video is useful for presentations, demonstrations or context where tone is crucial — not for the decisions and action items that make up the majority of meeting content.

What a transcript-first architecture produces

When the transcript is primary:

Storage is cheap and content is searchable. Text is orders of magnitude smaller than video. A year of meeting transcripts for a team of twenty is trivial to store and search.

The recap writes itself. With a full transcript, generating a structured summary — decisions made, action items assigned, topics covered — is a well-solved problem for current AI tools.

Privacy exposure shrinks. Video of your team's faces and office environments sitting in cloud storage is a different kind of sensitive than a text record of what was said. Many teams that have concerns about recording are comfortable with transcription-only.

The record belongs to the meeting, not the video file. Transcripts can be attached to calendar events, project tickets, CRM records, or anywhere the meeting's context is needed. A video file sits in a separate storage system that almost nothing else integrates with natively.

MeetOye is built on this model: transcript and recap are the default output of every meeting, and full video recording is optional and off by default. The trade-off is explicit rather than accidental — completeness of audio/video when you need it, structured text record when you don't.

The practical starting point

You don't need to switch tools to test whether transcript-first works for your team. For the next month:

Turn recording off by default
Turn automatic transcription on
Share the transcript summary to wherever your team tracks decisions (Notion, Linear, Slack — wherever)
See how often anyone asks to watch the recording

The teams that run this experiment almost universally find they don't miss the recordings for day-to-day meetings. What they were actually looking for was a reliable text record — and transcription delivers it more usably than a video does.

Author bio:
The MeetOye Team writes about remote work and async collaboration. MeetOye (meetoye.com) is an AI-native video meeting platform that's transcript-first by design — every call produces a speaker-labelled transcript and AI summary; full recording is optional.

Small Teams Don't Need Enterprise Meeting Tools. They Need Better Ones.

Sannan Malik — Thu, 02 Jul 2026 07:51:37 +0000

The conventional wisdom in business software has always been: enterprise tools get built first, then simplified versions trickle down to small businesses. The small team gets a lite version of the thing the Fortune 500 uses, with fewer features, cheaper pricing, and the same underlying architecture.

In meeting software, this produced a generation of tools with admin consoles designed for IT departments, AI features gated behind enterprise contracts, and pricing built around seat counts that assume a company of thousands.

Small teams — startups, agencies, consultancies, remote-first companies under fifty people — mostly ignored the enterprise-tier AI features because they either couldn't access them or couldn't justify the cost. The irony is that small teams often have more to gain from good meeting tools than large ones do.

Why small teams lose more to bad meetings

In a large organization, a poorly run meeting has redundant coverage. Someone takes notes. Someone else chases action items. A third person follows up. The overhead gets absorbed into the general noise of a large team.

In a small team, that redundancy doesn't exist. When the meeting ends without a clear record, the founder has to write the recap. When the action item doesn't get tracked, the head of product has to chase it. When the decision gets half-remembered differently by two people, someone has to schedule another meeting to relitigate it.

The waste per bad meeting is proportionally much higher when everyone is already stretched.

What small teams actually need from a meeting tool

Not a stripped-down enterprise console. The requirements are different in kind, not just in scale:

Frictionless for guests. Small teams have client calls, vendor discussions, candidate interviews — calls with people who have no relationship to your meeting platform. A tool that requires a download or an account to join is a tool that creates friction before the conversation even starts.

AI that's included, not tiered. The value of automatic transcription and recap is clearest at the small team level, where nobody has time to write structured notes after every call. But "AI summary" as a premium add-on means small teams — who need it most and can afford it least per-seat — get it last.

No IT setup required. A small team typically doesn't have a dedicated IT function. A meeting tool that requires SSO configuration, admin console setup or API integrations before it works is a tool that doesn't get deployed for three months.

A reliable written record by default. When the team is five people, institutional memory lives in people's heads. When someone leaves or goes on holiday, it leaves with them. A meeting that automatically produces a structured record — decisions, action items, attendees — is building organizational memory in the background.

What this looks like in practice

Platforms like MeetOye start from different assumptions than traditional enterprise tools: Oya, the built-in AI assistant, runs in every meeting by default with no per-user setup required, guests join with one browser click and no account needed, and the recap — summary, decisions, action items — emails to every attendee automatically when the call ends.

For a small team, this closes a specific gap: the gap between "we talked about it in the meeting" and "we have a written record of what we decided." That gap is the single most common source of miscommunication, repeated discussions and missed follow-up in small companies. It's fixable, and the fix is now accessible without enterprise pricing.

The practical test

Before committing to a meeting tool, run this test: schedule a call with someone outside your company (a client, a candidate, a vendor) and have them join from a link on a device that doesn't have your platform installed. Time how long it takes from clicking the link to being in the call. If it's more than 30 seconds or requires any account setup, that's the friction your clients will experience on every call.

Then check: after the call ends, what exists? If the answer is "whatever notes someone took," the tool is still expecting a human to do the work that software can now handle.

Author bio:
The MeetOye Team covers tools and operations for small and growing businesses. MeetOye (meetoye.com) is an AI-native video meeting platform designed to work well for teams of any size — with Oya's automatic transcription, recap and live translation included by default, no enterprise plan required.

Why AI Should Be Infrastructure, Not an Add-On

Sannan Malik — Thu, 02 Jul 2026 07:46:06 +0000

Every major software category eventually faces the same architectural question: is the new capability a feature, or is it the foundation?

Email clients added spam filtering as a feature. Then spam filtering became so essential that a client without it wasn't really a product. Navigation apps added live traffic as a feature. Then it became the baseline expectation, and a map without it felt broken.

AI is going through this transition in meeting software right now — and the difference between "AI as feature" and "AI as infrastructure" turns out to matter a lot in practice.

What "AI as feature" looks like in meetings

The feature model is familiar: you open your meeting platform, and somewhere in the settings or the toolbar there's an AI option. You enable recording, or you invite a bot, or you activate the summary feature. You might need a specific plan tier. You might need admin permissions. The AI is there when you remember to use it.

This model produces inconsistent coverage. People forget. The bot doesn't get invited. Someone disables the recording because a sensitive topic came up. The useful output — transcript, summary, action items — shows up for some meetings and not others, which means you can't build workflows that depend on it.

What "AI as infrastructure" looks like

Infrastructure doesn't get switched on per use. It's just there, like the network connection or the authentication layer. You don't "enable" HTTPS for individual requests. You build on the assumption that it's always on.

The same logic applies to AI in meetings. When the transcript, summary and action item extraction are defaults — not options — the team can build workflows that count on them. "Add your action items from the meeting recap to the project tracker" is a real daily habit when a recap reliably exists. It's a sporadic maybe when it only happens for some meetings.

MeetOye is built around this principle. Oya, the AI assistant, is active in every call by default. It doesn't require the host to remember to turn it on, a guest to consent to a bot joining, or anyone to be on a specific plan tier. The transcript and recap exist after every meeting because that's what the platform produces — not because someone set it up correctly.

The product architecture implications

Building AI as infrastructure rather than a feature changes what you optimize for:

Latency matters more. If AI output is optional, it can arrive in five minutes and still be useful. If it's the primary record of the meeting, it needs to be there before people close the tab.

Reliability requirements go up. A feature that fails occasionally is annoying. Infrastructure that fails occasionally breaks workflows.

Privacy architecture has to change. When AI is opt-in per meeting, you can route it to a third-party service without too much concern. When it's on for everything, where the transcript goes and who controls it becomes a material decision. Infrastructure-first AI meeting tools typically process on your behalf rather than sharing data with an external service, and make the data custody model explicit.

The product separates from the AI layer. A meeting tool that depends on a single AI provider can be held hostage by that provider's changes. Infrastructure-grade meeting AI is provider-agnostic at the architecture level — the AI serves the product, not the other way around.

Why this matters for how you evaluate tools

When you're evaluating a meeting platform and the AI summary is listed as a feature — something you turn on, something that requires a higher plan, something that joins as a separate participant — that's a signal about how the product thinks about AI.

The question to ask is: what happens to this meeting if the AI feature doesn't fire? Does the meeting still produce useful output, or did we just lose the whole record?

If the answer is "we lost the record," the AI isn't a feature. It's load-bearing infrastructure that you've accidentally made optional.

Author bio:
The MeetOye Team writes about product architecture and AI strategy. MeetOye (meetoye.com) is an AI-native video meeting platform where Oya, the built-in AI assistant, is on by default for every call — transcript, translation, and recap, without any setup required.

Breaking Language Barriers in Remote Teams: What Actually Works

Sannan Malik — Thu, 02 Jul 2026 07:45:58 +0000

The standard model for a global remote team looks like this: hire great people from anywhere, standardize on English, and accept that some of your team will always be operating at a disadvantage.

It works, in the way that a workaround works. People adapt. They get better at English. The friction becomes invisible because everyone stops mentioning it. But the friction doesn't go away — it just becomes background noise in your team's ability to communicate clearly.

The actual shape of the language problem

Language barriers in remote teams show up in several places that are easy to misread:

Quieter meetings. Non-native speakers contribute less in real-time discussion. This gets attributed to personality ("they're introverted") or culture ("they come from a culture where junior people don't push back") when the reality is simpler: it's harder to interrupt, disagree or make a quick point when you're doing it in a second language under time pressure.

Miscommunications that surface slowly. When someone didn't fully understand what was decided but didn't want to ask for clarification again, the misalignment shows up weeks later when work doesn't match expectations. By then, the connection to the original meeting is lost.

Uneven quality of written work. Writing in a second language is slower and more effortful than writing in your first. Team members who are native speakers produce more written communication, which gets read as more engaged or more competent — not as an artifact of the language environment.

What teams try and why it only partially works

"Speak slowly and clearly" helps at the margins but requires consistent discipline that degrades over time, especially in fast-moving discussions.

Async first reduces the real-time language pressure, but decisions still need synchronous discussion at some point, and async writing in a second language has its own barriers.

Hiring for English fluency filters for a specific kind of competence — English — that may or may not correlate with the skills you actually need, and it systematically deprioritizes candidates from countries where English isn't the dominant language.

Machine translation for written comms has become genuinely good and is widely used. The gap that remains is live meetings, where there's no pause to run something through a translator.

Where technology is closing the gap

Live meeting translation has reached a point of practical usefulness. The key distinction to understand is between room-level and per-participant translation:

Room-level: one shared caption language for the whole meeting, often selectable by the host
Per-participant: each person chooses their own caption language independently

Room-level helps. Per-participant solves the problem. In a meeting with an English speaker, an Urdu speaker and an Arabic speaker, room-level translation still requires someone to read in a second language. Per-participant translation means each person reads in their own.

Platforms like MeetOye implement per-participant translation as a default part of every meeting — each person selects their caption language before joining, and the translation runs continuously through the call without anyone needing to configure it mid-meeting. The original transcript is preserved alongside translations, so there's an accurate record in the source language as well.

The organizational changes that matter

Technology handles the mechanics. The organizational changes that actually shift team culture around language take longer:

Normalize "I didn't catch that." Model it yourself, as a native or dominant-language speaker. When asking for repetition becomes socially comfortable, non-native speakers stop letting unclear moments accumulate.

Rotate meeting ownership. When the same English-fluent person runs every meeting and writes every recap, the meeting is implicitly theirs. Rotating these roles — with appropriate support — distributes ownership more honestly.

Evaluate contribution asynchronously. Performance assessments that lean heavily on how someone shows up in live meetings systematically disadvantage non-native speakers. Async writing, documented decisions, and output quality give a more complete picture.

Take the recap seriously. An AI-generated recap in the dominant language, shared immediately after the call, gives non-native speakers who missed details a chance to catch up on what was said and decided before the next meeting picks up from there.

Author bio:
The MeetOye Team works on global team communication. MeetOye (meetoye.com) is a video meeting platform built for multilingual teams, with per-participant live translation and AI-generated recaps included by default in every call.

The Hidden Cost of Bad Meeting Notes (And What Actually Fixes It)

Sannan Malik — Thu, 02 Jul 2026 07:37:59 +0000

Every company tracks the cost of too many meetings. Almost no one tracks the cost of meetings that produce nothing usable afterward.

That cost is significant — and almost entirely invisible on a budget.

What a bad meeting note actually costs

Here's a simple calculation. Your team has eight people in a one-hour call. Average loaded cost per person: $80/hour (conservative for a knowledge-worker team). That's $640 of salary-equivalent time spent in the room.

Now add the follow-up. Someone spends 25 minutes writing a recap from memory. Someone else sends a Slack message asking what was decided because they missed the first five minutes. A third person schedules a 20-minute call two days later to re-litigate a decision that was made but not clearly written down.

That single meeting just cost closer to $1,100 — and its output was an email nobody reads and a Notion page nobody updates.

Multiply that by how many meetings your company runs per week.

Why meeting notes are almost always bad

The problem isn't that people don't try. It's that writing accurate notes during a live conversation requires splitting attention between two cognitively demanding tasks: following the discussion and capturing it simultaneously. Nobody does both well.

What you get is a reconstruction, not a record. Notes taken after the fact are worse — memory degrades fast, and the person writing them unconsciously frames decisions in ways that favor their own understanding of what happened.

The result is a document that's more interpretation than transcript, written by whoever had time (or remembered to do it), available only to people who thought to look for it.

Three things that are worse than no notes at all

1. Notes that capture activity but not decisions
"We discussed the Q3 roadmap" tells nobody anything. The question is: what was decided, who owns it, and by when.

2. Notes that live in the wrong place
A Word doc in someone's Downloads folder, a Slack message that gets buried, a Confluence page with the wrong date in the title. The information exists; nobody can find it.

3. Notes written by the loudest person in the room
The most talkative participant's interpretation of what happened is rarely the most accurate one. It's just the most confident.

What actually fixes this

The honest answer is that you either need a professional dedicated to the task — an executive assistant whose job is accurate note-taking — or you need the meeting itself to produce the record automatically.

The second option has become genuinely good in the last two years. Modern AI meeting tools don't just transcribe — they produce speaker-labelled transcripts, extract decisions and action items, and deliver a structured recap before the tab is even closed. Platforms like MeetOye are built around this as the default behavior, not an optional feature: every meeting produces a summary, a list of decisions and attributed action items, automatically emailed to every attendee.

The shift this creates is subtle but significant. Accountability becomes structural rather than social — action items are written down and attributed by default, not remembered selectively.

What you can do right now, without new tooling

If you're not ready to change platforms:

End every meeting with a 60-second verbal recap of decisions only (not topics discussed — decisions made)
Write action items in the format: [Person] will [do thing] by [date] — not "we should look into X"
Send the recap within the hour, not the next morning
Put it where people already look, not where they should look

But the honest productivity advice is: if your team runs more than three meetings per day, the math of automating this is overwhelmingly in your favor. The savings from one recovered "re-litigation" call per week pays for almost any meeting tool on the market.

Author bio:
The MeetOye Team writes about operations and productivity for fast-moving teams. MeetOye (meetoye.com) is an AI-native video meeting platform that automatically transcribes, recaps and emails a structured summary of every call — decisions, action items and all.

How to Run Inclusive Multilingual Team Meetings (Without Making It Weird)

Sannan Malik — Thu, 02 Jul 2026 07:37:51 +0000

If your team spans more than one country, you've probably been in this meeting: everyone nods along, the call ends, and then three different people walk away with three different versions of what was decided.

It's not an attention problem. It's a language problem — and most meeting tools weren't designed to fix it.

Why "just speak English" isn't a real solution

The default advice for multilingual teams is to standardize on English, or whatever the dominant language is. In practice, this creates a two-tier meeting: native speakers run the conversation, and everyone else spends cognitive energy translating rather than thinking.

Research on multilingual workplace communication consistently finds that people think more creatively, ask better questions, and challenge assumptions more readily in their first language. Making half the room do real-time mental translation isn't a neutral choice — it systematically disadvantages some team members over others.

What inclusive multilingual meetings actually require

1. Acknowledge that the language gap exists

Don't pretend everyone is equally comfortable. A quick "feel free to ask me to slow down or repeat anything" costs nothing and signals that non-native speakers aren't expected to keep pace at any cost.

2. Slow down for clarity, not for condescension

Pace and clarity help everyone: shorter sentences, fewer idioms, pausing before moving on. This isn't dumbing down — it's communication discipline that native speakers almost universally lack.

3. Use visual anchors

Agendas, shared screens and live notes give people something to follow that isn't just the audio stream. When someone misses a word, they can orient from context on screen rather than falling further behind.

4. Let technology carry the translation load

The more mature approach — and increasingly the default one — is to use meeting tools that handle translation as infrastructure rather than asking your team members to handle it mentally. Platforms like MeetOye give each participant their own caption language during the call, so a speaker talking in Urdu is understood by an English reader and an Arabic reader simultaneously, without anyone switching tools or slowing the meeting down.

5. Rotate who runs the recap

If the same English-fluent person always writes the post-meeting summary, you've outsourced meaning-making to one perspective. Rotating recap responsibilities — or using a tool that generates the summary automatically — removes that bottleneck.

The recap is where the real inclusion happens

What gets written down after a meeting defines what actually happened. If the notes are written by and for native speakers, the framing reflects that. Automatic transcription with speaker labels gives a more faithful record and lets participants verify what was captured in their own words — not in someone else's paraphrase.

A practical checklist for your next multilingual meeting

Send the agenda in writing before the call, so non-native speakers can prepare
Use screen share to show key points in text, not just say them aloud
Enable live captions or translation if your platform supports it
Assign a dedicated note-taker (or use AI-generated notes) rather than relying on memory
Close the meeting with a verbal recap of decisions before anyone drops off
Send a written follow-up the same day, not three days later

The bigger point

Inclusive multilingual meetings aren't a diversity checkbox — they're a competitive advantage. Teams that communicate clearly across languages make decisions faster, retain international talent better, and build stronger cross-cultural relationships with clients and partners.

The tools to do this well exist. The question is whether you treat language support as a last-minute accessibility add-on or as something you design for from the start.

Author bio:
The MeetOye Team is part of the team at MeetOye (meetoye.com), an AI-native video meeting platform built for multilingual and global teams. Oya, MeetOye's built-in AI assistant, transcribes, translates and recaps every meeting automatically.