29 August 2026
You can't guilt people into turning their cameras on, and the managers who try end up with dead-eyed faces staring at a wall behind them instead of real engagement. The fix isn't a policy, it's making the meeting worth being seen in, and being honest that some meetings are genuinely better with cameras off.
When someone says "let's have cameras on today," the room complies for four minutes and then, one by one, tiles go dark again. Nobody says why. The reason is usually not laziness — it's that the meeting doesn't need their face, only their attention, and their face costs them something the meeting doesn't repay.
A camera is not neutral. It's a live feed of a person's apartment, their tiredness, their eight back-to-back calls that day, sent to people who are mostly multitasking anyway. Asking for it as a compliance measure treats the symptom and skips the actual trade a person is making.
Ask people privately and you get the same three answers every time, and none of them are fixed by a rule.
Cameras go on for themselves in meetings that reward attention — a design review where someone's reaction changes the direction, a retro where the room needs to read the tension in the account, a 1:1 where the whole point is the human moment. Nobody has to ask in those rooms.
They stay off in status updates, standups, and anything that's really information transfer dressed as a meeting. If the content would survive as a doc, the camera requirement is asking people to perform presence for something that doesn't need it — see our piece on when a meeting should have been an email. Fix that first and the camera problem often disappears with it, because half the dark tiles belonged to a meeting that shouldn't have happened at all.
The workable policy isn't "cameras on" or "cameras off" — it's default-off, on-for-purpose. Open the meeting with cameras optional. When you hit the segment that actually benefits from faces — a decision that needs to read the room, a hard conversation, a first meeting with someone new — say so explicitly: "can we go cameras-on for this next ten minutes, I want to see how this lands." People say yes to a scoped ask far more than a standing rule, because the cost is bounded and the reason is visible.
This also removes the awkward math of "am I the only one off." If the default is off, turning yours on is a signal you chose to send, not a penalty you're paying for opting out.
In AVAY, the meeting is transcribed and the notes get built regardless of who has a camera on — the AI participant isn't reading faces, it's reading what people say, so a camera-off meeting loses nothing on the record it produces. That's worth knowing before you make cameras a proxy for engagement: the actual signal of engagement — who spoke, what got decided, who committed to what — is captured either way.
Where AVAY does show its limits is that it can't tell you someone's checked out if they're silent and off-camera; it only knows what was said out loud. If presence really matters for a specific meeting, that's still a human call to make explicit, not something to infer from a grid of thumbnails.
| Cameras always on | Camera-optional, on for purpose | |
|---|---|---|
| Compliance | High for a few minutes, then quietly ignored | Consistent, because nobody's fighting the rule |
| What it actually measures | Willingness to perform, not attention | Genuine moments where being seen matters |
| Fatigue cost | Paid every meeting, regardless of content | Paid only when the meeting earns it |
| Effect on quiet meetings | Adds pressure to meetings that didn't need faces | Leaves status updates and standups alone |
Only when the meeting already needs to be watched — a negotiation, a design review, a hard conversation. In a status update or standup, a camera adds performance cost without adding information, so "engagement" from a camera mandate is usually just compliance dressed up as attention.
1:1s are one of the few meeting types where video reliably earns its cost, because reading someone's face is often the actual point of the conversation. Even there, ask rather than mandate — someone having a rough day may need the option to keep the camera off and still get the meeting.
Those are purpose-driven by nature, which is exactly the case for cameras on — say so explicitly rather than relying on an unwritten norm, since a candidate or client won't know the expectation unless you state it up front.
No. AVAY's AI participant works from the audio and the words spoken, not the video feed, so a fully camera-off meeting still produces an accurate transcript, notes, and decisions. Video only matters for the humans in the room, not for what gets recorded.
Yes — recurring status meetings, large all-hands, and anything where the content is really a broadcast are usually better off-camera by default, because the camera adds fatigue without adding a signal anyone uses. Save the ask for the meetings where being seen changes the outcome.
Don't mandate cameras — make the meeting worth being seen in, default to camera-off, and ask explicitly for the specific parts that actually need a face.
AVAY is a video meeting platform that transcribes the call itself — no bot joins, because there is nothing to join. Start one at avay.ai, read how each part works in the documentation, or see what it costs.