When's the last time your in-person meeting actually needed to be in-person?

A 60-minute in-person meeting rarely costs 60 minutes. Five of them a week costs you a full working day of hidden overhead. Every week. Nobody audits that number, so nobody fixes it.

Default to video for execution work. Use in-person strategically.

Most organizations still treat in-person meetings as the standard and video as a fallback. Flip the default for execution-layer work and speed goes up the same week.

The operator case for video as baseline:

1. Meetings cost more than the meeting

A 60-minute in-person meeting is rarely 60 minutes. Add 30 to 90 minutes of travel, buffer time on either side, and the cognitive hit of leaving your workspace.

Run the math across a week. Five meetings, two hours of hidden overhead each, ten hours back. A full working day reclaimed every week.

2. Scheduling becomes elastic (with discipline)

Video calls collapse to fit the work. Ten-minute syncs become viable. Reschedules stop cascading into lost half-days.

The trap: video defaults can expand meeting volume instead of shrinking duration. Pair the elasticity with a protocol. Default length 15 minutes, agenda required, no agenda no meeting.

3. The cost structure runs deeper than fuel

Surface costs: gas, parking, vehicle wear. Real costs: opportunity cost of lost working hours, meeting room infrastructure, coordination overhead, travel reimbursements. Most of it is invisible on the books. Video removes nearly all of it with no drop in output on execution-layer work.

4. Decision velocity compounds

Pulling stakeholders together takes a calendar invite instead of a commute. Decisions happen in hours instead of days. Fewer blockers. Tighter feedback loops. Competitors still scheduling in-person reviews fall behind on iteration speed alone.

5. Meetings become assets, not ephemera

This is where the operator edge lives.

A typical pipeline: Fathom or Fireflies records the call. Transcript drops into n8n. Claude or GPT extracts action items, owners, and deadlines. Output writes to Airtable, Notion, or the CRM. A Slack DM fires to each owner with their tasks.

The meeting moved from an ephemeral conversation to structured data in your stack, automatically.

In-person meetings rely on manual notes and memory.

6. Energy stays in the work (mostly)

Honest caveat: video fatigue is real. Bailenson's Stanford research documented the cognitive load of mirror anxiety, reduced mobility, and hyper-gaze. Back-to-back video days drain people.

The fix: meeting-free blocks on the calendar, camera-optional defaults for internal calls, and walking audio-only calls where the content allows. With those in place, removing commute fatigue and context switching is still a net gain.

When in-person still wins

High-ticket sales closes (Gong data consistently shows in-person outperforms video by 20 to 40 percent on net-new enterprise deals). Complex negotiations where body language carries signal. Mentorship and onboarding for junior team members. Relationship building where physical presence is itself the message. Site visits where the physical space is the subject.

Default to video for execution. Protect in-person for the handful of situations where presence is doing actual work.

The operator caveat

If you work inside an org that mandated return-to-office, you can't flip the location policy. What you can flip is meeting format inside the office. Half the in-room meetings in RTO buildings would run tighter as video calls with participants at their desks.

The honest take

Remote matches in-person value for execution-layer work once the tooling and discipline are in place. Meetings that can be video should be.

What's the strongest counter-argument you've had to answer on this?

2 comments