A Healthy Communication Chain or You Keep Reliving the Past

The Problem Isn't That You Didn't Learn

Six months after a painful project failure, a VP I know sat in a retrospective and said, "We need to make sure we never let this happen again." Good instinct. The right energy. Except I had been in a room with her direct reports eight months earlier, and one of them had flagged the exact same risk, in almost the exact same words.

The org had already learned the lesson. Nobody transmitted it.

This is the pattern I've watched repeat itself across almost every organization I've been part of or consulted for. Leadership isn't ignoring the problems on purpose. They genuinely don't know what's happening two or three layers below them, because the chain between line-level reality and the people making decisions is broken, clogged, or performing health it doesn't actually have.

The single biggest predictor of whether an organization keeps reliving its past is the health of that communication chain. Not the quality of the postmortems. Not the sophistication of the OKRs. The chain.

This Is Not an Information Problem

Before we talk about what to do, let's be clear about the diagnosis.

Most leaders frame this as "we need better information." So they invest in dashboards, reporting tools, weekly status updates, and project tracking software. All of which is fine. None of which actually fixes the underlying problem.

The problem is transmission, not data. The organization has the information. It exists somewhere, usually in the heads of your frontline people or mid-level managers who deal with the real work every day. The issue is that it isn't traveling anywhere useful. Leadership keeps making decisions with stale or filtered inputs, not because the data doesn't exist, but because nobody built a reliable channel for it to move through.

And that is almost always a leadership problem. If the manager isn't asking specific questions, if the manager's manager isn't asking specific questions, if skip-levels are sporadic or purely theatrical, the signal never reaches the people who could act on it. So someone two layers up rediscovers the same issue next quarter and thinks they're the first to see it. They're not. They're just the first person in the chain who finally got exposed to it.

What a Broken Chain Actually Looks Like

Status meetings are probably the most common symptom, and also the most normalized. You know the format. Everyone goes around the table, everyone says some version of "we're on track," the meeting ends, nothing changes. Two months later something blows up that was not on track at all.

The issue isn't that people are lying, though occasionally they are. The issue is that open-ended status check-ins create social pressure to perform wellness upward. Nobody wants to be the person who says "actually we have a serious problem" in front of their peers and their boss. So they hedge. They soften. They report the best-case interpretation of a messy reality.

The manager's job in that room is to create a different condition. That means asking specific questions rather than accepting the open mic. Not "how are things going?" but "what's the one thing that would go wrong with this project that we haven't talked about yet?" or "where are you most likely to miss the deadline and why?" Those questions change the dynamic because they normalize the existence of problems. They give people permission to surface real information instead of performing optimism.

Most managers do not do this because they were never taught to do it, and because it's uncomfortable. It requires tolerating tension, sitting with bad news, and sometimes hearing things you'd rather not hear. But that discomfort is the job.

The Skip-Level Is the Most Underused Tool You Have

If you're a director, VP, or above, you probably have skip-level meetings on your calendar. The question is whether they're doing anything, or whether they've become another forum where people perform "things are great" because they're sitting across from someone even further up the chain.

The difference is almost entirely in how you run them.

Skip-levels that work are not listening tours. They're not open-mic sessions. They're not "tell me what's on your mind" conversations, because what's on someone's mind when they're sitting across from the VP is how to make a good impression. You will get curated information, and you'll mistake it for unfiltered signal.

The ones that actually work are structured around specific, targeted questions about specific parts of the operation. What are you seeing on the ground that you think I'm not seeing? Where do you feel like decisions are being made without the right information? If you were in my seat, what would you change first? Those questions are uncomfortable to ask because they imply you might be missing something. You are. That's the point.

I've had skip-level conversations that completely changed my view of what was happening on a team, because one person felt safe enough to tell me something that had been filtered out of every official update for three months. That's not a failure of the person who filtered it. That's a failure of the chain.

The Translator Problem

Here's the part that doesn't get talked about enough. Most managers do one direction of communication reasonably well and the other direction poorly.

They're decent at pushing context down. Here's the strategy. Here's why the company made this decision. Here's what the leadership team is thinking. Most managers can do that, even if they do it imperfectly.

What they're terrible at is pulling signal up. Capturing what their team is actually experiencing, synthesizing it into something coherent, and getting it to the people who need to act on it. This is the harder skill, and it's the more important one for keeping the chain healthy.

If you're a manager and your boss doesn't have a clear, accurate picture of what your team is dealing with, that's on you. Not because you should be constantly complaining upward, but because your job is to translate the line-level reality into something the organization can actually use. That includes surfacing problems before they become crises, flagging risks before they materialize, and making sure that when something goes wrong, the lesson doesn't just live in your head.

Postmortems That Go Nowhere

One more pattern worth naming: the postmortem that produces action items nobody owns.

The format is familiar. Something bad happens. The team assembles. Someone facilitates a conversation about what went wrong and what to do differently. Action items get written down. The meeting ends. Six months later, none of the action items shipped, and the same conditions that caused the original failure are still in place. Sometimes the same failure happens again.

The postmortem didn't fail because people weren't paying attention. It failed because "improve cross-team communication" was listed as an action item with no owner, no deadline, and no follow-up mechanism. That's not an action item. It's a wish.

Lessons travel through organizations when someone is specifically responsible for carrying them, with a clear mechanism for doing so. A postmortem without an owner for each action item is just documentation of a problem you're going to have again.

Build the Chain Deliberately

Healthy communication chains don't happen by accident. They are built intentionally, maintained actively, and defended against the constant gravitational pull toward theater.

That means managers asking specific, uncomfortable questions rather than accepting performed optimism. It means skip-levels designed to surface real signal rather than reinforce the official narrative. It means postmortems with owners. It means leaders at every level treating the upward flow of information as a core part of their job, not a nice-to-have on top of it.

The org is smarter than the leadership team, most of the time. The line-level people know what's actually happening. The question is whether you've built a chain that lets that knowledge reach you before it's too late to act on it.

If you haven't, you're not going to keep reliving the past by accident. You're going to keep reliving it by design.