Remember to acknowledge you’ve heard someone when they send you communications. Communications is a two way street, remember. One side sends and another receives. Simple, right? Everyday I have a front row seat to some kinda communication conflict. One person sent a message. Another received it. The conflict came in the silence, in the assumption. Let me attempt to illustrate this by going way back to my CompuServe roots. This could be kinda funny too.
CompuServe built a communications network, back in the day, that was designed to only carry data. In other words, this network wasn’t built to handle any voice communication – only the communication from computer to computer. The network was comprised of computers (called Micronodes) distributed around the world. The magic of this data network was it was shared – public if you will. So, lots of companies were able to share in the cost which made it economical before the freedom we know as the Internet.
The basic protocol that kept everybody’s data from getting lost or sent to the wrong place was the key. Every node was smart. Not as smart as you and me, but intelligent none the less. So every time one node “talked” to another it followed a very specific protocol. The receiving node sent “ACK” to the sending node and computer to computer they compared bits to make sure what was intended actually showed up. Smart, huh. If the sender got no “ACK,” they simply sent it again. No ack; no go. ACK; we go. The network worked amazingly well because this protocol assumed nothing. The network worked because every node was smart. FM, baby.
We humans aren’t micronodes (we’re smarter) but we could learn a little from these ancient machines and the protocol that kept the system together.
Got it can be amazing. Got it? Got it, and, I’m working on it can be even better. Got it, and, thanks for sending and here’s when you can expect to have your request fulfilled is better yet. Got it, and, I’m not sure what you mean can be really good. Got it, and, lets TALK can be the convo that cuts conflict from creeping to the surface. Nothing, however, leaves the sender kinda hanging like a node with no ACK. Today, I heard another story about someone assuming too much. Seems like ACK is really problematic for our young, tech savvy leaders. Way too many young minds assume/trust technology. Stop assuming, friend. Remember, just because you’ve heard someone or read their text/email doesn’t mean they know this. Assume less. ACK more. You are smart enough to know this, right?
ACK. Got it. Good…