It started with a Slack ping.
“quick sync? 5 min.”
I was three levels deep in a refactor, holding a mental model together with sheer willpower. The notification popped up like a jump scare. I typed “sure” because saying no feels like being difficult.
Forty-three minutes later, I was back at my desk, staring at the same line of code, trying to remember what I was doing before the interruption.
Then I did it again after lunch. And again before standup.
The calendar said I had three meetings that day. The calendar was lying.
Here’s what nobody tracks: the quick sync.
It doesn’t show up in velocity charts. It doesn’t appear in cycle time. It’s not a Jira ticket. It’s just a Slack message, a tap on the shoulder, a “you got a sec?” that feels harmless because it’s short.
But the cost isn’t the five minutes. The cost is the twenty minutes after — the context rebuild, the mental stack collapse, the quiet “where was I?” that happens when you finally return to your code.
Six quick syncs a day. That’s two hours of deep work gone. And your focus metric still says you’re fine because focus time only measures calendar blocks, not actual attention.
The dashboard is green. The work is bleeding.
The uncomfortable truth is that most quick syncs aren’t urgent. They’re a workaround for broken systems.
The answer wasn’t written down, so someone asked.
The decision wasn’t logged, so someone called.
The ownership wasn’t clear, so someone pinged.
The sync becomes the API for tribal knowledge. And every time you answer one, you’re not fixing the underlying problem — you’re just making the undocumented system feel a little more official.
I once watched a “5-minute alignment” with a PM turn into a scope change that never made it into the ticket. The developer implemented the new thing from memory. The old ticket said something else. The QA engineer flagged it as a bug. Three days of confusion, all because someone didn’t want to type out a decision in a comment thread.
So I started treating interrupts like incidents.
For one week, I logged every unplanned sync. The average was six per day. The total lost deep work was two hours. I showed the list to my team. Nobody had any idea.
The fix wasn’t more discipline. It was better defaults:
If it can be written, don’t say it.
If the answer lives in someone’s head, it’s not an answer — it’s a liability.
Protect deep-work blocks like you protect production uptime.
Before you type “quick sync?”, ask yourself: Is this actually urgent, or am I just avoiding writing it down?
If you absolutely must talk, batch it. Office hours for questions. A daily sync window after lunch. Not a dozen one-off interruptions disguised as collaboration.
The quick sync is a small tax that compounds quietly. It feels productive in the moment — you answered something, you helped someone, you were responsive. But it steals the one thing that actually ships software: uninterrupted thought.
If your team’s default answer to ambiguity is “let’s hop on a quick call,” you don’t have a communication culture. You have a documentation failure with a calendar invite.
Now if you’ll excuse me, I’m putting Slack on DND and writing this down.
