The curious case of the unanswered message

May 24, 2026

Banner Image

 

An observation on modern communication, efficiency, and the messages that quietly disappear.

I’ve developed a new professional fear.

And before this turns into a “get off my lawn” moment, I’ll admit I might be slightly more sensitive to this than most, having spent a large part of my career around corporate communications, tight timelines, and people who tend to respond.

It’s not budgets or deadlines, and it’s not even software rollouts with too many stakeholders and not enough good coffee. It’s sending a message that disappears into what I can only assume is a highly efficient digital black hole, not broken or malfunctioning, but functioning exactly as designed – just gone.

Most of our communication now happens in quick bursts. Texts, Teams and Slack messages, and email threads. The kind of exchanges that feel conversational until they’re not.

You send something thoughtful, timely, maybe even helpful. It lands with a soft, optimistic “we should catch up soon,” the kind of message that, in a previous era, would have resulted in at least a nod, maybe even a calendar invite if everyone was feeling ambitious.

But today – nothing.

No response, no acknowledgment, no signal that the message was received by another living, breathing human being, or politely evaluated by an AI agent add-on that concluded, with confidence, “no reply needed.”

Just silence. The type that makes you stare at your screen a few minutes longer than you’d like to admit, wondering if you somehow imagined the entire interaction, and debating whether following up would make you look proactive, needy, or just slightly unhinged.

I’m starting to believe there’s an agreement I never signed, a quiet shift in modern communication that says messages no longer require acknowledgment unless they are urgent, tied to a deadline, or actively on fire. Everything else feels optional, possibly even discouraged.

To be fair, I understand how we got here. We’ve built incredibly fast, efficient communication systems that let us message anyone, anywhere, at any time. We’ve removed friction, increased speed, and multiplied volume to the point where we can send emails during meetings, respond to texts while walking between meetings, and ignore both while sitting in meetings about how to improve communication so we can have fewer meetings.

It’s remarkable, in a slightly ironic way.

And in the process, we may have introduced a small issue: we broke the feedback loop.

Messages go out, and nothing comes back. There’s no confirmation, no acknowledgment, no simple signal that says the message landed and didn’t immediately fall into a digital abyss. It’s not rudeness, and it’s not even intentional. It’s a system design flaw.

I’m reminded of a text exchange with a coworker in a role that absolutely requires strong communication and leadership.

It started simply enough:

Monday

Coworker: Hi 👋

Me: Hey. What’s up?

(30 minutes later)

Coworker: We should grab lunch and catch up. How does your week look?

Me: Pretty tight, but I’m open Thursday or Friday for lunch, or we could grab a drink Wednesday night.

(5 minutes later)

…the sound of crickets.

Thursday, 3 PM

Coworker: Sounds good. How about tomorrow at 11:30?

Me: Bro. I replied Monday morning, and it’s now Thursday. Did you throw your phone into the Pacific Ocean?

Needless to say, we didn’t have lunch that week.

 

This is what broken feedback loops look like in real time.

That’s a small example with low stakes, but the pattern doesn’t stay small.

Recently, I sent a more important note to a couple of colleagues about a personal matter that would require me to be out two to three weeks, an adjusted software rollout schedule, and timing changes on a major initiative. It’s the kind of message that affects everyone in the company and, historically, triggers at least acknowledgment, alignment, or basic human empathy.

I clicked send. And once again, two weeks later, nothing.

No “got it,” no “thanks for the update,” not even a quick “hope everything goes well,” which honestly feels like a fairly low bar in most communication frameworks.

So it leaves you wondering whether they read it, missed it, don’t like me, or simply processed it in a system where acknowledgment is no longer required. And if that’s the case, we should probably document it somewhere.

Because this isn’t really about politeness anymore. It’s about the signal the silence sends.

Acknowledgment is the smallest, simplest form of feedback we have. It tells people the message was seen, understood, and at least temporarily aligned. Without it, everything becomes slightly ambiguous, and in an AEC consulting setting, ambiguity is where small inefficiencies quietly turn into bigger ones.

That’s why high-reliability environments don’t leave acknowledgment to chance. In the military, it’s called closed-loop communication, where instructions are acknowledged and repeated back before action is taken. Not because it’s courteous, but because it prevents errors. That’s where “10-4” comes from.

If you’ve ever seen the movie Airplane! (1980), you’ve seen a satirical version of this taken to the extreme:

Clarence: Roger

Roger: Huh?

Victor: We have clearance, Clarence

Clarence: Roger, Roger

Roger: Huh?

Clarence: What is our vector, Victor?

It’s funny because it’s overdone. In real life, we’ve drifted in the opposite direction.

Follow-ups get sent, assumptions get made, timelines drift, and people hesitate when they shouldn’t or move forward when they shouldn’t. Entire conversations get recreated because no one confirmed the original one actually happened, all because a message went unanswered.

Beyond inefficient operations, there’s something else we’re losing: the human layer.

In real life, we don’t do this. If someone sitting next to you in a meeting says something, you don’t stare at them silently, close your laptop, and walk out of the room as if the interaction never occurred. That would just be weird. No, you nod, you respond politely, you acknowledge that the interaction happened.

Digital communication removed those micro-signals, and somewhere along the way, we decided we didn’t need to replace them.

So now we have incredibly efficient systems that occasionally feel like we’re talking into the void, and we’ve become so effective at filtering noise that we may have started filtering each other.

I like closure, clarity, and knowing that something I sent didn’t just vanish into the digital equivalent of a junk drawer next to an expired login password written on a Post-it note.

But I don’t think I’m wrong.

Because this isn’t about writing long replies or adding more noise. It’s about restoring one small, almost invisible signal: “got it,” “sounds good,” “let’s do it,” “hope it goes well,” or in some cases, even the indifferent thumbs up emoji👍.

Because right now, silence doesn’t mean agreement, disagreement, or even indifference. It doesn’t mean anything at all. And in a world optimized for speed and efficiency, that might be the most inefficient outcome of all.

Kraig Kern, CPSM is the innovation and integration lead at The Wooten Company. Contact him at kkern@thewootencompany.com.

About Zweig Group

Zweig Group, a four-time Inc. 500/5000 honoree, is the premier authority in AEC management consulting, the go-to source for industry research, and the leading provider of customized learning and training. Zweig Group specializes in four core consulting areas: Talent, Performance, Growth, and Transition, including innovative solutions in mergers and acquisitions, strategic planning, financial management, ownership transition, executive search, business development, valuation, and more. With a mission to Elevate the Industry®, Zweig Group exists to help AEC firms succeed in a competitive marketplace.