I used to think my team was slow because decisions piled up. This month I noticed the real pattern: most of those decisions were waiting on me, and I was processing them “when I had a moment.”
That phrase is the problem.
“When I have a moment” feels generous. It sounds like flexibility. In practice, it’s a black box where urgency goes to wait.
The pattern I missed
A draft lands. A PR needs a look. A spec needs a sign-off. None of them are emergencies. All of them are mine.
I tell myself I’ll get to it after the current thing. The current thing runs long. The draft sits. The PR sits. The spec sits.
Two days pass before anyone nudges. By then, the person waiting has context-switched, moved to other work, or quietly lost momentum. The work didn’t stall because it was hard. It stalled because my review had no clock.
Why casual review breaks delivery
Most teams measure the work that moves. Almost none measure the work that waits.
But latency is where the real cost hides. A two-day review delay on a one-day task doesn’t show up as 3 days of effort. It shows up as a one-day task that took three. The math is invisible because nobody tracks review latency as a metric. We track velocity, throughput, cycle time — all of which assume the queue is flowing. When the queue is stuck on one person, those metrics look fine. The bottleneck is silent.
I’ve watched this happen to me from both sides. When I’m the one waiting, I feel it instantly. When I’m the one blocking, I don’t feel it at all. That asymmetry is the whole problem.
What I changed
Three small rules, all forced.
Every review gets a time box. Not “this week.” A clock. A PR gets 4 hours. A draft gets a day. A spec gets 48. If I can’t hit it, I hand it to someone who can, or I say so explicitly and renegotiate.
No review sits unread. If I’m not going to look at something today, I say that out loud — to the person waiting, in writing. Ambiguity is what creates the delay. Naming it kills it.
I batch, but I don’t defer. I still do reviews in dedicated windows. But the window has a hard stop, and anything not handled by the end of the window gets reassigned or dropped, not carried forward.
None of this is clever. None of it is a framework. It’s just refusing to let “when I have a moment” be a real commitment.
The thing I had to admit
The hardest part wasn’t building the rules. It was admitting that I was the bottleneck.
That’s a strange thing to resist. Being the bottleneck should be obvious. But it’s not, because the work still moves — slowly, unevenly, but it moves. The slowness gets absorbed into “how things are.” The team learns to route around you. The cost shows up in morale and momentum, not in any chart.
I had to stop reading my own busyness as a reason. Being busy doesn’t make the wait acceptable. It just makes it harder to notice.
What I’d tell a younger version of myself
If you’re the person things wait on, your review isn’t a courtesy. It’s a dependency. Treat it like one.
Give it a time. Hit the time. If you can’t, say so before the deadline, not after.
The teams that ship reliably aren’t the ones with the fastest reviewers. They’re the ones where nothing waits in silence.
That’s the whole shift. Not faster. Just visible.