- Undivided
- Posts
- 6 Words That Kill Your Team's Productivity
6 Words That Kill Your Team's Productivity
Why 'quick questions' cost more than you think—and the communication fix that changes everything
"Hey, do you have a quick second?"
These six words represent one of the biggest productivity killers in modern business—and most people don't even realize it.
The problem isn't the question itself. It's the fundamental difference between two types of communication:
Synchronous Communication: Both people need to be available at the same time Asynchronous Communication: Messages can be sent and received at different times
Here's what most people miss: These two modes operate by completely different rules.
Synchronous communication slows down based on availability.
When you need an immediate response, you're at the mercy of the other person's schedule. If they're busy, you wait. If you're both busy, nothing happens.
Asynchronous communication gets lost when bandwidth is exceeded.
When someone's inbox is flooded or their task list is maxed out, your message simply disappears into the noise—even if it's important.
This creates a fascinating business paradox:
The more urgent something feels, the more likely we are to use synchronous communication ("Can we hop on a quick call?")
But urgent items are often exactly what should be handled asynchronously to avoid disrupting focused work.
Here's how this plays out in real organizations:
» "Quick questions" interrupt deep work sessions » Impromptu meetings derail planned priorities
» Waiting for immediate responses creates artificial urgency » Important but non-urgent items get buried in reactive communication
The solution isn't choosing one over the other—it's being intentional about which mode serves each situation.
Use synchronous communication for:
Complex problem-solving that benefits from real-time interaction
Situations requiring immediate decision and action
Relationship building and nuanced conversations
Use asynchronous communication for:
Information sharing and updates
Non-urgent questions and requests
Anything that can be handled in the recipient's optimal timeframe
The most productive teams I've worked with have clear protocols for this distinction.
They ask: "Does this need to be resolved right now, or does it need to be resolved well?"
Because here's the truth: Most "urgent" communication isn't actually urgent—it just feels that way because we haven't developed better systems for managing the flow of information.
What's one "quick question" pattern that disrupts your team's productivity? How might you convert it to asynchronous communication without losing effectiveness?
Reply