The Synchronous Tax

Most software teams run synchronous by default and don’t notice they’re doing it. Someone has a question, they ping you. Someone wants a decision, they put thirty minutes on your calendar. Each one is cheap. Add them up over a quarter and they’re most of what your team could have shipped.

Call it the synchronous tax. It’s a real cost, paid in real attention, and it shows up as the work that didn’t happen — the rewrite still living in someone’s head, the bug nobody had two uninterrupted hours to chase, the doc that’s been “almost done” since March.

The trick is that the tax is invisible to whoever’s collecting it. I ping you, get an answer in three minutes, problem solved. I feel productive. The hour of focus you traded to give me that answer doesn’t show up anywhere on my side. It shows up on yours, but only as absence — the thing you meant to do today and didn’t.

Most async arguments lean on time zones and remote teams. Fine, but that buries the real point. Async puts the cost of interruption back on the interrupter. If I have to write the question down well enough for you to answer it on your own schedule, half the time I figure out the answer mid-sentence and never send it. And when I do send it, what comes back a few hours later is better than the three-minute version would have been, because you got to think.

That’s the pitch. Not fewer meetings. Not “deep work.” Just: make the person asking pay for the ask, instead of charging it to whoever picks up the ping.