The Drummer Isn’t Stalling

Four clicks of the sticks over the drummer’s head, and not one person in the room thinks she’s stalling.

She knows the song. The bass player knows the song. They’ve played it more times than anyone at the bar has heard it. The clicks aren’t there to help anybody remember. They’re there so four people land on the first note at the same speed, instead of four slightly different speeds that all technically count as the song.

Three seconds after someone asks you a question is a count-in. You probably already have the answer. That’s the danger, actually… an answer that shows up that fast was built for the question you expected, and you’re about to play it at your tempo instead of theirs.

I’m writing this to myself first. I’m fast. I can have a rough draft back before the meeting that assigned it has ended, and I say yes to helping no matter what the problem turns out to be (a trait that looks great on a performance review and less great once you’ve sprinted somewhere nobody asked you to go).

In a room, the pause works because they can see it. They watch the question land on you. They watch you turn it over once before you hand anything back. Silence across a table is the most legible proof of listening a person can give, and it costs nothing but nerve.

Then the conversation moves into a text box, and nobody can watch you think.

Three seconds of silence on a call reads as care. Three hours of silence on a Slack thread reads as a closed door. So the pause can’t live on the clock anymore. It has to live inside the reply.

Somebody drops a draft in a channel and asks what you think. “Looks great!” forty seconds later tells them you didn’t open it. The same two words four hours later tells them the same thing, slower. The paused version can come back in ten minutes and point at their second paragraph, the one quietly carrying the whole piece, and say why it works. Same speed as a thumbs-up, give or take. Completely different message.

The bar gets emails asking to reserve the place. The fast answer is true and useful: we keep the doors open to the public, so private events work best around thirty people, and here’s how to book. It answers exactly what was asked.

Somewhere in that email there’s a person. A dad turning seventy. A coworker’s last day. A sister home for the first time in years. The question on the screen is about square footage. The question underneath is whether this night is going to go okay for them. Both replies can carry the same facts, the same thirty, the same corner, the same date. Only one of them is about the dad.

That email is a sales lead, and lead-response advice is mostly a stopwatch. Reply in five minutes, beat the other venue, win the night. All true. Sitting on an inquiry for a day to look thoughtful just hands the party to whoever answered first. A stopwatch can’t tell whether you read it, though… it only knows you were quick. Plenty of fast replies lose anyway, because they were so clearly written to the question everybody asks.

If you lead anybody, the drafts people send you are the ones they’re nervous about. Answer them instantly and generically for long enough and they learn their work is being processed. They don’t complain. They just stop sending you the real version and start sending you the safe one, and you’ll never notice the switch because the safe one also “looks great.”

The count-in was never dead air. It’s the only part of the song that belongs to everybody on stage at once. Skip it and you still play the song. You just play it a beat ahead of everyone you were supposed to be playing with.

Stay Positive & One… Two…

Garth Beyer
Latest posts by Garth Beyer (see all)

Share A Response