Camera On or Off: What Four Weeks of Switching Changed
In a four-week trial across 61 calls, cameras were on for 78 percent of participant-minutes in week one and 31 percent in week four, with no measurable change in how decisions were rated afterwards. The trial was meant to test fatigue. It mostly tested habit.
The team was a 16-person customer success group spread across five countries, running daily check-ins and about a dozen client calls a week.
The assumption being tested
The group assumed that cameras improved attention and trust, an assumption stated confidently by three managers and supported by no measurement the team could find. The trial was designed to produce a number rather than an opinion.
Attention was measured by a short self-report after each call, using one question with a five-point scale. Trust was not measured, because the team could not design a question that would survive a four-week window.
Week one, before any rules
Cameras were on for 78 percent of participant-minutes, which is close to universal given that some attendees joined by phone. Calls with clients had cameras on almost always; internal calls were mixed.
The self-reported attention score averaged 3.7 out of 5. Nobody reported fatigue in week one.
The switch
From week two, cameras were optional on internal calls and remained on by default for client calls. No other change was made. Optional meant optional: nobody was asked to justify a dark rectangle.
By week three, cameras were on for 44 percent of participant-minutes internally and 93 percent externally.
What the attention scores did
The average score stayed between 3.5 and 3.8 across all four weeks. The variation between weeks was smaller than the variation between individual calls, which suggests the camera is not the variable people think it is.
Two calls scored below 2.5 in every week, and both were long agenda-free sessions that would have scored badly with cameras on or off.
The effect on participation
Speaking turns per call rose from 6.2 to 8.4 after cameras became optional, driven mostly by three people who had previously spoken once per call. Their reason, given afterwards, was that they had been managing their own appearance rather than listening.
That is a small sample and a self-reported cause. It is also the only measurable change the trial produced.
Where cameras stayed mandatory
Client calls kept cameras on, on the grounds that a client who turns on a camera and sees a blank screen draws an inference the team does not intend. Three internal calls also kept them on by team choice: onboarding, difficult conversations and anything involving a new joiner.
Nobody argued for cameras in status updates, which had been the most common call type.
The fatigue question
Reported fatigue rose in week one and fell afterwards, which is the opposite of what the trial predicted. The team’s best explanation is that optionality removed the low-level monitoring of one’s own image, which is the part people describe as tiring.
A different explanation is that the novelty of the trial made week one unusual. The team cannot separate the two and does not claim to.
Four weeks on
The optional rule survived the trial and was written into the team’s meeting norms, with the client-call exception stated explicitly. Cameras are on in about a third of internal participant-minutes and almost all client ones.
The client who noticed
One client asked, on a call, whether the team was short-staffed because three participants had cameras off. The account lead explained the internal norm and the client accepted it, then turned her own camera off for the rest of the call. That exchange is the reason the client-call exception is written down rather than assumed.
External perception is not a reason to keep cameras on internally, and it is a reason to be explicit about which setting applies where.
Seventy-eight percent of participant-minutes once had a camera on and attention scored 3.7. A third of them do now and attention still scores 3.7, which is the least exciting result of the exercise and the most useful.
