We've become obsessed with real time communication. It is immensely easier to get a hold of someone than it was before, but with great power comes great responsibility. Clearly, team chat is here to stay, and rightfully so (we ♥ Slack). If something requires a quick chat, it's overkill to fire off an issue, task, or Action.
However, the inverse is also true. Chats are super powerful, but they can also create glaring problems for your product team. When you misuse a team chat, you essentially create a ticking time bomb in your organization that could either prevent you from getting to the next level, or explodes when you do.
Here are 10 reasons why real-time may not be the right time for your Product Team:
- If something is important, you need TIME to think it through
- Things inevitably slip through the cracks
- Miscommunications quickly transform into totally avoidable disagreements
- It's actually MORE work to keep up
- It's impossible to avoid FOMO
- Inability to perform retrospectives
- 10 emails have been replaced by 30+ chats
- It becomes an excuse to avoid meeting face-to-face
- You falsely feel productive if you send many chats
- Your colleague is busy getting the job they said they'd get done.
A blend of real and quasi real time generally produces the best results IMO. Anything relating to formalized communication surrounding concrete measurable topics should be put in a quasi-real time state (your issue trackers, task trackers, or even better: Profecta). Remember, these subjects matter, so simply getting feedback isn’t enough. You want fast feedback, but more importantly you want THOUGHTFUL feedback.