I left every team chat for a month. I came back to some, not all
In February I was answering team chats from 7:30 to 23:00. In March I went silent for four weeks. What happened to the team — and to me.
Late February 2026, I was sitting in my kitchen at ten on a Thursday evening, talking to my wife about something important (I don't remember what), and I checked my phone seventeen times in an hour and a half. Each time — Slack. Each time — a team chat. Half of them about things I had no particular opinion on. I answered everything. I was a good founder.
On Friday morning I counted. From 7:30 to 23:00 — about two hundred messages a day across three channels: general "team", "engineering", and "sales". Forty or so were mine. Of those forty, maybe five actually needed my reply. The other thirty-five were polite participation. 👍 reactions. Clarifying questions. "Got it, thanks." "Agree with Anya." "Can we sync tomorrow?" Good thing I was a good founder. Bad thing I was not very good at anything else.
On Friday evening I declared an experiment. For one month I'm out of every group chat. One channel stays — DMs from two people: CTO Lyosha and ops lead Anya. Everything else — without me.
The first three days I was as irritable as a patient skipping his morning coffee. I kept reaching for Slack. Opened it. Remembered. Closed it. Felt I was missing — what? — missing something. Couldn't say what.
Monday at lunch Anya called. "Hey, weird thing — you didn't see in chat — Grisha wants to start his vacation a week early, you good with that?" Sure, I say. Anya: "Thought so, I wrote him back and tagged you just in case. Sorry to bother." I hung up and got the first lesson.
Anya already knew how to make that decision. The thing was, I used to answer faster than she could finish reading her own draft. I never let her finish a thought out loud. I outran her. And she, like any normal employee, stopped forming conclusions — I started forming them for her.
By the end of week one Anya was sending those messages without my approval. By the end of week two — she stopped sending them at all. Decisions were made. I heard about them once a week at our 1-1.
Week two brought something I hadn't expected. The team started talking to each other differently.
I never noticed it before, because in my presence the dynamic was one thing. When the CEO is in the chat, everyone's reading sideways at the CEO. Every message — including yours — gets written less for the colleague and more for what the CEO will see. Fear isn't the issue. Attention is the limited resource. You spend it first on "how Mike will read this", and only the leftovers go to "what I want to say to Lyosha".
Once I left, the chat got shorter and clearer. Lyosha told me this in week four: "You know, we've been writing less. And we're agreeing on things faster. I thought it was June and everyone in vacation mode. Then I realised — it's because we're not waiting for you. Before, we had to wait for your reaction to know if we move on or you're about to chime in. Not anymore."
I sat with that for a while. It was an unpleasant thought. I had been slowing the process. Not with my decisions. With my mere presence.
Week three gave the only real test. We had an integration break with one external service — the one that handles client payments. The old script: it would have hit the general chat — "Mike, we have beep-beep, what do we do?". I would have come running, started untangling, hurried someone, fixed in an hour.
The new script played out like this. Lyosha spotted the failure at 11 a.m. Wrote in engineering (without me): "Integration is down, who's free?". One of the guys — Dima — took it. Fixed by 1 p.m. At 14:15 Lyosha DMed me: "We had a payment outage from 11 to 13. Done. Damage — three support tickets, replied. More on Wednesday's 1-1." I read it. Replied "thanks, got it." Closed the phone. Went to lunch.
That was the moment it became clear — for better or worse — that most of my operational work was getting done not because it couldn't happen without me, but because I got there first. Take away "I get there first", and someone else fills the slot. And on average that someone does it just as well.
(Sometimes better. That part was even less comfortable.)
Week four was strange. The team was working. I was free. I was — sometimes — bored. That, as it turns out, is its own important signal: founder boredom by week four of the moratorium means your operational load was less than it felt and more than it needed to be.
That week I did three things I'd been putting off for eighteen months. Reread our strategy (found two places where I was contradicting myself, fixed them). Called two clients I'd been meaning to ring back — both had new work for me. Wrote a big chunk of this blog, including one piece you may have already seen.
This is different work. The kind that needs uninterrupted hours. The kind that's impossible to do when your Slack pings every seven minutes.
On April 1st I came back to the chats — but not to all of them.
General "team" — yes, that's where announcements, birthdays, news live. I show up there once a day at lunch, read, react, leave.
"Engineering" and "sales" — no. I didn't go back. Decisions in those zones the team makes itself. Once a week — 1-1 with Lyosha and Anya, forty minutes each. That's enough.
The rule I introduced: if something is urgent, DM me. The word "urgent" in a team chat with my handle on it is not urgent — it's a request that I take responsibility on. Urgent comes as a phone call or a DM marked "please look within the hour". In four months that has happened twice. Once a real emergency. Once Anya was just worried.
I know this doesn't work for every kind of team. In a two-person company the founder has no choice — they are the process. In a hundred-person company the founder isn't in the group chats by default. This problem is for teams of seven to thirty-five, where the founder still feels like "part of the team" but shouldn't be part of every decision.
And I know it's hard. Not technically. Emotionally. When you leave the chats, you cut yourself off from a steady supply of the pleasure of being needed. Every "thanks, Mike" is a small dopamine your brain expects. By the second day of withdrawal you'll realise how much of it you were getting per day. That, I think, is the real reason founders don't leave the chats voluntarily. Not because the team can't manage without them, but because without the chats they have nowhere to put themselves.
Two months after coming back I looked at the numbers. The team shipped exactly as many releases in March as in February (my last "fully present" month). Support response time improved by 18% (Lyosha credits this to support no longer escalating every sneeze into the general chat). Zero attrition, same as before.
My hours on ops: minus eight per week. What I do with those eight hours is a separate conversation. Short version — I don't fill them with work. I freed them for myself. Mornings for sport, Wednesday for a long lunch with my wife, Friday — nothing. That's the resource founders are short on, not because there's no time, but because they're — in the chats.