The ‘cameras always on’ policy debate — and what to do if your manager won’t budge.

The “cameras on” argument has been going on for so long that even the people who started it are tired of it. In 2021, a group of researchers from BYU and Arizona State, writing in Harvard Business Review, ran the first decent study on the question and found that employees who kept their cameras on during virtual meetings reported significantly higher fatigue than those who didn’t — and that the effect was stronger for women and newer employees. The headline was on the front page of Hacker News for a day, and then we all kept turning our cameras on anyway.

Four years later the policy has not softened. If anything, the return-to-office push and the rise of distributed teams have made the camera question more loaded. Plenty of mid-sized companies now have a formal “cameras on for all meetings > two people” rule, baked into a Notion page nobody re-reads after onboarding. The HBR finding hasn’t propagated up.

The case for cameras on (it’s not nothing)

Most defenses of the policy aren’t bad faith. They are some mixture of:

• Trust signal in distributed teams. For managers who can’t walk the floor, seeing faces is the cheapest available proxy for engagement.
• Onboarding. New hires genuinely benefit from seeing the rest of the team’s faces. Reading nonverbal cues speeds up the period where you’re still learning who is who.
• Client work. If your customer expects to see you on camera, your camera is on. That’s the deal.
• Inclusion concern. If half a meeting is on camera and half is off, the off half drops out of the social fabric of the call. There’s a real coordination argument here.

None of these are wrong. Some of them describe meetings that actually need cameras. The trouble is that the policy gets applied to all meetings — including the four-person product sync, the weekly all-hands listening session, the cross-team status meeting where you contribute eleven words in forty minutes.

The case against (the part HBR documented)

The BYU/ASU paper isolated camera-on time as an independent variable and measured both self-reported fatigue and meeting engagement. Findings, in plain terms:

• Camera-on participants reported significantly more end-of-day fatigue.
• The fatigue effect was stronger for women and for newer employees, which the authors attributed to higher self-presentation pressure.
• Higher fatigue correlated with lower vocal engagement in the same meetings — so the camera-on policy was not just costly, it was counterproductive on the metric it was designed to support.

A follow-up by Stanford’s Jeremy Bailenson coined the term “Zoom fatigue” for the specific exhaustion that comes from prolonged mirror-image self-monitoring during video calls. The mechanism isn’t mysterious. Humans are not evolved to spend nine hours a day looking at a small picture of their own face.

Camera-on policies cost more than they pay. That doesn’t mean they’re going away tomorrow.

What to do if your manager won’t budge

You’ve probably already tried the obvious moves: brought up the HBR piece in a 1:1, asked for permission to be off-camera in specific recurring meetings, pointed out that your output hasn’t suffered on the days you forgot to dress up. If those worked, you wouldn’t be reading this. So: pragmatic options.

Pick your battles

You will not win a blanket exemption. You might win the “turn cameras off for the weekly read-out where nobody talks” exemption. Frame it as a specific meeting, with a specific reason, with a specific time cap. Bring data — your own calendar audit of how many hours a week you’re on camera. Numbers move conversations that vibes can’t.

Use the structural fixes first

Audio-first meetings, recorded async updates, walking calls, and shorter default meeting lengths all reduce the camera-on hours without anyone fighting about cameras. If your org accepts any of these, push on them. They are easier wins than the camera fight itself.

The bio-break safety net

Here is where MeetingDouble fits, and I want to be careful about framing. A virtual camera loop is not a way to lie about whether you are working. It is not a way to skip your job. It is a small, specific tool for a small, specific problem: you are stuck in a back-to-back stretch where cameras-on is mandatory, and you need eight minutes for a bathroom break, a sip of water, or a moment where your face is not being broadcast to twelve coworkers.

The product was designed as a bio-break safety net. The away detection wants you to come back. The microphone stays muted on re-entry, deliberately, so you can’t accidentally come back live mid-bite. The whole posture of the app is: be present when it matters, take human breaks when it doesn’t. I wrote about the underlying tradeoffs in more detail in the 8-minute bathroom problem note.

Where the line is

There’s a question I get a lot, usually phrased apologetically: “Isn’t this a tool for slacking off?” Honest answer: it can be, in the same way that mute-on-by-default is a tool for ignoring your coworkers, or noise-cancelling headphones are a tool for not hearing your spouse. Most people don’t use those tools that way. Most people use them to manage a constant low-grade demand on their attention so they can do their actual work.

The line I’d draw: if you would not be comfortable explaining how you used MeetingDouble to a reasonable peer, you’re past the line. That’s a judgment call, and the app doesn’t make it for you. It just makes the eight-minute version possible without you having to interrupt a meeting to ask.

If your manager really won’t budge

Eventually the conversation isn’t about cameras. It is about a working relationship where you don’t feel trusted and your manager doesn’t feel listened to. Tools won’t fix that. The note on mouse jigglers vs camera loops is partly about the same uncomfortable reality: a lot of these tools are pressure valves on management problems they cannot themselves solve.