Field note

The Hidden Cost of Remote Tech: Burnout in Disguise

What running a tech startup on Teams taught me about over-connection, context switching and recovery.

An empty bench on a ship's deck looking across calm water

What running a tech startup on Teams taught me about over-connection and under-recovery.

Introduction

It started with one Teams call. Then another. Then a “quick chat” turned into 90 minutes, followed by four follow-ups and a document review.

Before I knew it, I’d spent six hours communicating, two hours context-switching, and maybe 40 minutes doing deep work. Sound familiar?

In the world of remote technology leadership, especially when you’re building ambitious innovative technology, the tools that keep you connected can quietly wear you down.


The illusion of remote freedom

We sold ourselves a dream:

“Work from anywhere. Empower your team. Just send a link.”

And don’t get me wrong—I love the tools. Teams, OneNote, SharePoint, synced calendars and integrated wikis have helped Marine Zero scale remotely with clarity.

But here’s the catch: remote technology can hide burnout better than any office ever did.


The symptoms I didn’t spot at first

Symptom Looked like Actually was
Replying instantly to every ping “Engaged leader” Boundary-less overdrive
Constant availability “Supportive culture” Chronic context-switching
Back-to-back Teams calls “Agile collaboration” No time to think, breathe or build

What I’ve learned—the hard way

  1. Being online ≠ being productive
    Most high-value thinking doesn’t happen in a call. It happens in the quiet moments in between.

  2. Presence isn’t performance
    Logging long hours on Teams doesn’t mean things are moving forward. Sometimes, it’s just motion sickness.

  3. Operations and systems reduce brain load
    Every decision delegated, every SOP written and every asynchronous update is one less thing my brain carries.


My survival tactics

  • Create hard stops: If I don’t block downtime, I burn time.
  • Use asynchronous over live: If it can be written, it doesn’t need a call.
  • Keep calls sacred: Limit “catch-ups” unless they truly matter.
  • Track stress like you track metrics: If your KPI dashboard is glowing green but you’re not sleeping, something’s off.

What I’d tell another remote founder

You can’t scale a business from burnout. And you definitely can’t scale clarity when your brain is split between five calls and twenty pings.

Tools like Teams are incredible—but without guardrails, they become your digital cage.


Final thought

The goal isn’t to be “always on”. The goal is to build systems, teams and habits that work even when you’re not.

Because sometimes, logging off is the most productive thing you’ll do all day.

Have you hit this kind of remote wall before? Send me a message or connect on LinkedIn.