Why Silent Meetings With Cameras On Are a Bad Idea

by Eric Hanson, Backend Developer at Clean Systems Consulting

Staring at a screen full of colleagues who aren’t saying a word is surprisingly stressful.
Even with cameras off, the pressure to be “noticed” lingers.

The Awkward Pressure of Silence

Silent meetings feel safe in theory, but they create tension:

  • Every second of quiet feels like a countdown
  • People brace for questions that might never come
  • Anxiety replaces focus

Being watched, even silently, is mentally draining.

Cameras On Doesn’t Fix It

Turning cameras on doesn’t solve the problem:

  • You’re still “on display” for everyone
  • Micro-expressions and body language are misread
  • People overthink small movements or distractions

Productivity suffers because attention shifts from work to self-monitoring.

Cameras Off Isn’t a Magic Solution

Even when cameras are off, stress lingers:

  • Team members fear being called out unexpectedly
  • Silence can feel like judgment or suspicion
  • Multitasking anxiety rises as people try to appear “present”

The underlying issue isn’t visibility—it’s unclear purpose.

Making Meetings Actually Useful

Shift focus from presence to outcomes:

  • Set clear goals for every meeting
  • Encourage brief check-ins instead of long silent watches
  • Use async updates when discussion isn’t necessary

When people know why they’re there, silence stops feeling threatening.

Trust and Respect Over Surveillance

Silent meetings are a symptom of micromanagement:

  • Trust your team to contribute when needed
  • Respect their attention spans and energy
  • Build culture around communication, not visibility

Meetings should enable work, not make people dread every second on screen.

Scale Your Backend - Need an Experienced Backend Developer?

We provide backend engineers who join your team as contractors to help build, improve, and scale your backend systems.

We focus on clean backend design, clear documentation, and systems that remain reliable as products grow. Our goal is to strengthen your team and deliver backend systems that are easy to operate and maintain.

We work from our own development environments and support teams across US, EU, and APAC timezones. Our workflow emphasizes documentation and asynchronous collaboration to keep development efficient and focused.

  • Production Backend Experience. Experience building and maintaining backend systems, APIs, and databases used in production.
  • Scalable Architecture. Design backend systems that stay reliable as your product and traffic grow.
  • Contractor Friendly. Flexible engagement for short projects, long-term support, or extra help during releases.
  • Focus on Backend Reliability. Improve API performance, database stability, and overall backend reliability.
  • Documentation-Driven Development. Development guided by clear documentation so teams stay aligned and work efficiently.
  • Domain-Driven Design. Design backend systems around real business processes and product needs.

Tell us about your project

Our offices

  • Copenhagen
    1 Carlsberg Gate
    1260, København, Denmark
  • Magelang
    12 Jalan Bligo
    56485, Magelang, Indonesia

More articles

How to Handle a Client Who Blames You for Everything

Some clients have a special talent: no matter what goes wrong, it somehow becomes your fault. It’s frustrating—but manageable if you handle it right.

Read more

How to Deprecate an API Endpoint Without Abandoning Your Users

Deprecating an API endpoint isn’t just a technical step—it’s a contract change. Done right, it gives clients time to adapt without disruption; done poorly, it breaks trust.

Read more

New Zealand's Tech Talent Pool Is Small. Async Remote Contractors Are How Startups Close the Gap

You've been looking for a senior backend engineer for three months. You've seen every relevant CV in Auckland twice. The pool isn't refreshing — it's the same twelve people.

Read more

Australia's Backend Talent Pool Is Tiny Compared to Demand — Remote Contractors Close the Gap

You've been looking for a backend engineer for two months. The recruiter keeps sending frontend developers who "also do Node." That's not the same thing.

Read more