What Managers Don’t See: The Cost of Missed Conversations

27 January 2026

What Managers Don’t See: The Cost of Missed Conversations

A support engineer at a SaaS company spent twenty minutes crafting a detailed question for her manager about a recurring customer issue. She hovered over “send” for thirty seconds, saw her manager was in back-to-back meetings, and deleted it. The issue caused three escalations the following month. Her manager never knew she’d nearly prevented them.

This is a missed conversation. Not a failure of communication skills or individual judgement. A failure of systems to capture information that matters. This guest post from Sam King examines why this is important and what you can do about it.

Managers make decisions based on the information available to them: meetings, reports, dashboards, one-to-ones, performance metrics. But there is another layer of activity that never appears in management discussions: conversations that don’t surface at all. Requests that go unspoken. Questions that arrive at the wrong moment. Issues quietly absorbed by individuals rather than fed back into the system.

Research suggests the scale of this problem is significant. A study in the Journal of Management Studies found that 85% of employees had been in situations where they felt unable to raise an issue to a supervisor, even when they believed the issue was important.”

Defining Missed Conversations

A missed conversation is a potential exchange of information where organisational friction prevents capture, completion, or learning—leaving managers operating on incomplete intelligence.

This definition has three parts, each essential:

Friction prevents capture: The conversation doesn’t happen because barriers—time, access, perceived receptiveness—get in the way.

Friction prevents completion: The conversation starts but fails to reach resolution. It fragments, stalls, or disappears.

Friction prevents learning: The conversation happens but never feeds into improvement. The insight exists but doesn’t accumulate.

Apply this test tomorrow: identify one interaction where friction—not intent—stopped information from reaching you. That’s a missed conversation.

The Five Types of Missed Conversations

1. Conversations that never start

A customer needing to change their subscription tries calling at 2pm. Wait time is fifteen minutes. They close the tab and forget. Three months later they cancel, citing “poor service” in the exit survey. No manager sees the connection.

A mid-level manager notices her team checking Slack at 9pm to catch up on requests that arrived after 5pm. She mentions it once in passing. Her director nods. It becomes normal. No one escalates. The pattern continues.

From a management perspective, silence can easily be misread as stability. Harvard Business Review research on “organisational silence” found that 85% of managers surveyed could identify at least one issue they felt unable to raise with their superiors. Silence rarely signals contentment.

2. Conversations that start but don’t complete

A team member sends a detailed proposal on Tuesday. Their manager is preparing for a board meeting. They acknowledge receipt with “Thanks, will review.” Friday passes. The following week brings new priorities. The proposal is never discussed.

These incomplete interactions don’t disappear. They resurface as rework, escalation, or dissatisfaction—at higher cost than if addressed earlier. One study of project failures found that 57% could be traced to breakdowns in communication, with incomplete handoffs among the leading causes.

3. Conversations that happen but go nowhere

Customer service logs show the same question appearing forty times per month: “How do I change my billing date?” Each time, an agent answers. Each time, the conversation ends. No one aggregates the data. No one changes the interface. The question keeps arriving.

When conversations don’t inform learning or change, organisations stagnate. The insight exists—scattered across support tickets, casual comments, and hallway chats—but it never accumulates into action.

4. Conversations absorbed by individuals

A senior developer notices a colleague struggling with a new codebase. Rather than flag it as a training gap, she spends her evenings answering questions directly. The work gets done. Her manager sees on-time delivery and assumes the system is functioning. The developer burns out within six months.

Gallup’s research on burnout found that unclear communication from managers was among the top five factors contributing to employee exhaustion. Much of this stems from work that is handled but never made visible—absorbed rather than escalated.

5. Conversations that arrive at the wrong time

A major client sends an urgent request at 4:55pm on Friday. The account manager is offline. The request sits in an inbox until Monday morning. By then, the client has called a competitor.

In appointment-based businesses—clinics, salons, professional services—this plays out dozens of times per week. The phone rings while the team is with clients. By the time anyone checks voicemail, the caller has booked elsewhere. Most will never call back.

These are not people failures. They are system mismatches between when demand arrives and when capacity exists to meet it. Research on response time expectations shows that 90% of customers expect an immediate response to support queries. Yet most organisations structure availability around internal schedules, not external demand.

Why Managers Rarely See Missed Conversations

Most management systems measure activity, not absence.

They report how many tasks were completed, how many requests were handled, how many issues were resolved. They rarely show how many requests never made it through, how much demand arrived at the wrong time, or how often staff quietly compensated for gaps.

Because missed conversations generate no immediate incidents, they are easy to overlook. Teams adapt. Managers cope. The system appears to function—until cumulative pressure shows up elsewhere: in turnover data, in customer churn, in the slow erosion of trust.

The Psychology of Silence

Organisational friction explains some missed conversations. Psychology explains the rest.

Amy Edmondson’s research on psychological safety—the belief that one can speak up without punishment—reveals why many conversations go unspoken. In teams with low psychological safety, people don’t raise concerns because they fear looking incompetent, being seen as negative, or burdening others.

This creates a paradox. The managers most likely to believe their teams communicate openly are often those whose teams feel least able to do so. A leader’s perception of accessibility rarely matches their team’s experience of it.

Three psychological barriers drive silence:

Power dynamics: Junior staff calculate the risk of raising issues with senior leaders. Often, the safest choice appears to be saying nothing.

Impression management: People avoid questions that might make them seem unprepared, confused, or critical.

Assumed futility: When past concerns have gone unaddressed, people stop raising them. They learn that speaking up costs effort and yields nothing.

Managers who want to surface missed conversations must address these dynamics directly—not by announcing an “open door policy,” but by demonstrating through repeated action that speaking up is safe and valued.

The Hidden Cost for Managers

Missed conversations quietly increase the cognitive and emotional load on managers.

Instead of dealing with clear, structured information, managers are pulled into reactive problem-solving, fragmented decision-making, and constant interruption. Leadership time is consumed by firefighting. Strategic thinking is squeezed out by urgency.

Well-being suffers not because managers are ineffective, but because the system they operate within is noisy and opaque.

The Impact on Teams

For teams, missed conversations create uneven pressure.

Some people become informal intake points—the colleague everyone asks because they always seem to know. Others shield managers by absorbing issues themselves, building invisible workloads that never appear in capacity planning.

Over time, this leads to frustration, fatigue, and disengagement. Because much of this work is invisible, it is rarely recognised or rewarded. The most conscientious team members often carry the heaviest hidden loads.

The Impact on Customers

From the customer’s perspective, missed conversations shape trust and confidence.

A single point of friction may be forgiven. Repeated difficulty accessing help is not. Research on customer behaviour shows that 96% of unhappy customers don’t complain—they simply leave. By the time dissatisfaction appears in feedback or performance data, the original missed conversations are long gone.

Why Adding More People Is Not Always the Answer

When pressure increases, organisations often respond by adding capacity.

Sometimes this helps. Often, it doesn’t. Without changes to how communication is captured and routed, additional people can increase complexity: more handovers, more interruption points, more diffusion of responsibility.

Basecamp found this when they shifted from reactive communication to structured “office hours”—async by default, synchronous by appointment. Rather than adding staff, they changed how requests flowed. The result was fewer interruptions, clearer accountability, and reduced pressure across the team.

If demand remains unmanaged, adding people simply spreads it across a wider surface area.

What Better-Managed Organisations Do Differently

Organisations that reduce missed conversations don’t rely on individuals to cope. They design systems that make communication visible and manageable.

Atlassian uses a “question queue” system where non-urgent requests go to a shared board, reviewed at set times. This eliminated a reported 60% of manager interruptions while ensuring no query disappeared.

Buffer operates with radical transparency on workload through rotating support responsibilities. By rotating who handles incoming requests weekly, they make absorbed work visible and reveal true demand patterns that would otherwise stay hidden.

Stripe documents decisions and context obsessively, creating written records that allow asynchronous participation. Conversations that might have been missed because someone was unavailable can be rejoined later.

Common characteristics across these organisations include:

• Clear rules for how requests enter the system
• Separation between urgent and non-urgent demand
• Protected time for focus and decision-making
• Mechanisms that capture enquiries even when people are unavailable
• Regular review of what arrives versus what gets addressed

Technology can support these efforts. Tools like Calendly and SavvyCal help structure meeting requests rather than letting them scatter across email. Intercom and Help Scout capture customer queries asynchronously so nothing disappears during busy periods.

For appointment-based businesses: clinics, salons, professional services, the problem is acute. Phones ring while teams are with clients. Enquiries arrive after hours. By the time anyone checks voicemail, the caller has often booked elsewhere.

As noted earlier, these are not people failures, they are system mismatches. Technology can close that gap.

For example, Intavia is an AI receptionist built for this specific gap. It answers every call instantly, captures enquiries outside working hours, handles routine scheduling, and routes urgent queries to the right person, so conversations that arrive at the wrong time still get captured rather than lost. For managers, it provides clearer visibility of true demand: not just what was handled, but what arrived.

(For more on how these gaps compound across inbound calls, reminders, and follow-up, see this guide on fixing appointment leakage, or compare AI Receptionists.)

The key with any technology is intent: it should make communication visible and manageable, not replace human judgement or add complexity.

How to Audit Your Missed Conversations

Most managers have never systematically looked for what they’re not seeing. These prompts can help:

Ask frontline staff directly: “What questions do you answer repeatedly that never reach me? What issues have you handled this month that you considered escalating but didn’t?”

Review timing patterns: How many requests arrive outside your availability? What happens to them? Who handles the overflow, and at what cost?

Measure lag time: How long between when someone identifies a problem and when you hear about it? The gap often reveals where friction lives.

Examine your own behaviour: When did you last delete a message you were about to send? What stopped you? Your team is doing the same calculation.

Check for informal workarounds: Where has “just how we do things” replaced formal process? Those workarounds often mark sites of repeated missed conversations.

Spend thirty minutes this week with these questions. The patterns that emerge will show you where your systems hide information.

Seeing What’s Missing

Good management depends not only on responding to what is visible, but on understanding what is absent.

Missed conversations don’t trigger alerts. They don’t show up in dashboards. They accumulate quietly—in workload that shifts onto certain shoulders, in customers who drift away, in ideas that stay unspoken because the moment never felt right.

The shift from coping to managing well begins with a different set of questions. Not just “What happened?” but “What nearly happened and didn’t? Who absorbed pressure this week that I never saw? Where did information disappear?”

This week, ask your team one question: “What did you handle recently that you thought about escalating but didn’t?” Listen without defensiveness. The answers will tell you what your systems hide.

Header Image by Malachi Witt from Pixabay

Building well-being through better teams

Effective employee recognition is a fundamental of team building. If you want to build better teams, look at our teams  resources. Here you’ll find more information and a wealth of practical resources, in our colossal Team Building Bundle.

Containing 240 pages and 50 tools, these are the 8 key guides we recommend to help you do more than define teamwork, build it!

Why is Teamwork Important
Build a Better Team
The Problems with Teams
Team Health Check
Team Building Exercises
Leading with Style and Focus
What’s the Problem?
Making Better Decisions