Your SOPs are killing your marriage

Friday evening. Finally. We'd been waiting for this all week. No fires. No emergencies. Just us, a bottle of wine, some fruit on the small table in the bedroom, and whatever romantic movie we'd picked.

I was pouring the wine when my phone buzzed.

Beep beep.

‍

My wife looked up. "Who's that?"

I grabbed my phone. Slack. A client.

"Just... let me check real quick."

‍

She sat back, staring into her empty wine glass, foot tapping against the floor.

That's when I saw the message. A furious client. Hadn't received a single update on his project in a month. Prepayment spent. Demanding a full refund. I had no idea what he was talking about.

‍

The next three hours were a blur. Trying to calm him down. Promising we'd figure it out. Offering discounts. Swearing I'd fire whoever was responsible come Monday. Digging through JIRA looking for any trace of the project. Messaging managers. No one online. They were all off — doing exactly what I was supposed to be doing. Having their Friday evening.

By the time I closed my laptop, the wine was warm. The movie forgotten. My wife had already showered and gone to bed.

‍

Another romantic evening, buried under operational chaos.

‍

She'd said one word when the message came in: "Again?" Not angry. Just... resigned. Because this wasn't the first time. Or the tenth. Someone got sick. Someone needed a day off. New client wanted a call. Old client needed approval. Candidate to interview. Always something. Always pulling me back in.

‍

We worked until late every night. Weekends too. Life kept happening around the business, but we never seemed to catch up to it. And that evening, sitting there in the dark while she slept, I realized something uncomfortable:

‍

If this kept going, no marriage could survive it. Not because of one ruined evening. But because of the pattern. The constant state of emergency that made it impossible to ever fully be present.

‍

What actually went wrong

‍

Monday morning, I pulled the team together to figure out what happened. Turns out? Total communication breakdown. We had a 10-page SOP about client communication. Checklists. Email templates. JIRA protocols.

But:

‍

1. Nobody read it.

2. It was outdated as hell.

3. Everyone assumed someone else was handling it.

‍

A month. An entire month, and nobody thought to update the client. Here's the kicker: The manager who'd written those SOPs with me had quit a month earlier. He was the only one who actually remembered what was in there — and more importantly, what was bullshit and should be ignored. But he never passed that knowledge on when he left. Because there was no handover process. He just... left. "Here's the project, here's JIRA, here's the team." That was it.

And in the year since we'd written those SOPs:

‍

• JIRA updated its interface twice
• We moved communication from email to Slack
• The email templates got deleted from someone's personal Google Drive (they thought they were copies)
• Half the team didn't even know the SOPs existed
• The other half were doing things completely differently

‍

When I wrote those SOPs originally, I was so proud. So thorough. Every detail covered. But without someone responsible for keeping them current, they'd become worse than useless. They'd become toxic.

‍

The thing nobody tells you about balance

‍

I don't believe in work-life balance. Not as some fixed state you achieve and maintain. Balance is a process. Sometimes you lean into work — new launch, crisis, opportunity. Sometimes you lean into life — family needs you, health demands attention, you just need to breathe. The problem isn't the leaning. It's getting stuck. And I was stuck. Not because I was building something revolutionary. Not because I was chasing some massive strategic breakthrough. But because someone kept screwing up. Because I hadn't thought something through while I was putting out some other fire.

That Friday evening wasn't about one ruined date. It was about a pattern where the business constantly pulled me away from life — not for growth, but for chaos.

‍

What actually works

‍

After that night, I changed how we handled SOPs:

1. Keep them simple.

If someone can't understand it in a day, it's too complicated.

‍

2. Assign an owner.

One person responsible for keeping it current. Not just writing it — maintaining it.

‍

3. Build a handover process.

When someone leaves, there's a formal knowledge transfer. What's in the docs, what's not, what's outdated, what actually happens in practice.

‍

4. Review quarterly.

SOPs don't stay relevant on their own. Schedule time to check: does this still match reality?

‍

The marriage survived. But that evening was a wake-up call: A business that doesn't let you live — even when there's money — is a broken business. What's the point of the money if you can't use it to build a life worth having?

‍

Something you can do this week:

‍

Open your most critical SOP. The one everyone supposedly follows.

Now ask three people on your team:

• When did you last read this?
• Is this how things actually work?
• What's outdated or wrong in here?

I guarantee you'll find gaps. Things that changed and nobody updated the docs. Workarounds everyone knows but aren't written down.

That gap between documentation and reality? That's where your Friday evenings disappear.

‍

So here’s a question I have for you this week:

When's the last time outdated processes cost you something that mattered? Not just money — time, relationships, sanity.

Hit reply and tell me. I'm curious how many of us are running businesses held together by undocumented tribal knowledge.