Broken Feedback Loops
Strategy travels downward with remarkable efficiency. Reality, however, takes the stairs, gets stuck in middle management, and often never arrives at all.
I once watched a product launch fail in slow motion over eleven weeks. The executive team thought everything was on track. The weekly status updates said so. Green across the board. “On schedule.” “No blockers.” “Proceeding as planned.”
Meanwhile, the actual team knew by week three that the timeline was fiction. A critical API dependency was delayed. The design system couldn’t support the new component patterns. Two engineers had quietly started interviewing elsewhere.
None of this reached the people making resource decisions until week nine, when the launch date became physically impossible to hit. By then, the options had narrowed to bad and worse.
The postmortem blamed “communication issues.” Which is technically true in the same way that a car crash involves “momentum issues.”
The One-Way Valve
Every organisation I’ve worked in has some version of this problem. Information flows beautifully downward. Strategy decks cascade from the executive floor to directors to managers to individual contributors. Priorities get communicated. OKRs get assigned. Everyone knows what leadership wants.
But the return path? That’s where things get interesting.
Reality struggles to travel upward. Not because people refuse to share it. But because the system itself filters uncomfortable information at every level. By the time ground truth reaches the executive floor, it’s been smoothed, softened, contextualised, and occasionally transformed into its opposite.
This isn’t a conspiracy. It’s just how hierarchies work when nobody explicitly designs for reverse information flow.
The distance between “the team knows this won’t work” and “leadership understands this won’t work” is often measured in months. Sometimes the information never completes the journey at all.
For PMs, this creates a specific kind of pain. We sit at the intersection of strategy and execution. We hear the executive vision. We also hear the engineer explaining why that vision ignores three technical constraints. We watch the gap between intention and reality widen, often without clear authority to close it.
Why Reality Gets Stuck
The breakdown happens at multiple points, and understanding each one matters if you want to fix anything.
The translation tax. Every time information passes through a layer, it gets translated. An engineer says “this architecture won’t scale past 10,000 concurrent users.” Their manager hears “there are some scalability concerns.” The director hears “we’re monitoring performance.” The VP hears “the team is handling technical considerations.” The original signal degrades with each handoff.
The optimism gradient. People at every level have incentives to present things positively. Not because they’re dishonest, but because raising problems feels risky while reporting progress feels safe. Each layer adds a small positive spin. By the time it aggregates upward, significant issues have become minor footnotes.
The fear of being the messenger. Telling executives that their strategy has execution problems is career-adjacent behaviour. It can go well. It can also mark you as “negative” or “not a team player.” Most people, quite rationally, choose to let someone else deliver bad news. When everyone makes that choice, the news simply doesn’t travel.
The meeting format problem. Executive updates are typically short, structured, and focused on status rather than exploration. There’s no space for “let me explain why I’m increasingly worried about this.” The format itself selects for green lights and confident assertions.
I worked at a fintech company where the weekly product review had a standing agenda: wins, metrics, roadmap status, blockers. Sounds reasonable. But “blockers” meant things that had already stopped work. There was no category for “things that will probably become blockers” or “risks we’re tracking” or “assumptions that are looking shaky.” So those concerns stayed in team Slack channels and one-on-ones, invisible to leadership until they became urgent enough to qualify as blockers. By which point, urgency meant limited options.
What Executives Actually See
Here’s the part that might generate some empathy for the people at the top.
Executives are drowning in information. They have fifteen direct reports, each running their own domain. They’re in board meetings, customer calls, investor conversations, strategic planning sessions. They’re making decisions about things they can’t possibly understand in detail.
They need filters. They need summarisation. They need people to handle problems without escalating everything.
So when a director says “we’ve got some challenges but the team is handling it,” that’s actually what the executive wants to hear. It means they don’t have to context-switch into your domain. It means they can trust that someone competent is managing the situation.
The system is designed for efficiency, not accuracy. And most of the time, that trade-off works. Most challenges do get handled. Most risks don’t materialise. The filter catches noise and lets signal through.
Until it doesn’t. Until the filter catches signal and lets noise through. Until the thing that looks like a routine challenge is actually a fundamental problem, and by the time anyone realises the difference, the timeline has collapsed.
Executives don’t ignore reality because they’re arrogant. They ignore it because the information systems they rely on are optimised for reassurance, not truth.
The PM’s Peculiar Position
Product managers occupy an odd spot in this dynamic. We’re usually not senior enough to have direct executive access. But we’re close enough to execution to see ground truth clearly. We hear what’s actually happening in standups, in design reviews, in customer calls, in the Slack channels where engineers vent.
This means we often know things that leadership doesn’t. And we face a choice about what to do with that knowledge.
Option one: Stay quiet. Let the information flow through normal channels. Trust that your manager or their manager will escalate appropriately. This is safe. It’s also how problems stay invisible.
Option two: Escalate directly. Go around layers to get critical information to decision-makers. This can work. It can also damage relationships with your direct leadership, who may feel bypassed or undermined. It can mark you as someone who doesn’t respect the chain of command.
Option three: Find indirect paths. Plant questions in meetings. Share data that implies concerns without stating them directly. Hope someone more senior connects the dots. This is politically safer but unreliable.
None of these options are great. The right choice depends on your organisation’s culture, your relationships with specific people, and the severity of the information you’re holding.
I’ve made all three choices at different times. Sometimes the quiet approach was right because the issue resolved itself. Sometimes direct escalation saved a launch. Sometimes the indirect path worked. And sometimes I got it wrong, chose the safe option, and watched something fail that I might have prevented.
There’s no formula. But there are some principles that help.
Building Better Upward Flow
If you’re a PM trying to improve feedback loops, you have limited leverage. You can’t redesign the organisation. But you can change how information moves through your immediate sphere.
Separate status from risk. Most updates conflate these. “Here’s what happened this week” blends with “here’s what might go wrong.” Create explicit space for risk in your communications. A section called “assumptions we’re testing” or “things I’m watching” or “early warning signals.” This normalises surfacing concerns before they become blockers.
Quantify uncertainty. Instead of “the timeline might slip,” try “I’d put our odds of hitting the date at 60%, down from 80% last week, mainly due to the API dependency.” Numbers feel more legitimate than vibes. They also make it easier for someone to ask “what would get us back to 80%?”
Build a reputation for accurate prediction. This takes time, but it matters. If you consistently flag risks that materialise and don’t cry wolf about things that don’t, people start listening. Your warnings carry more weight. One PM I worked with kept a simple log of risks she’d raised and their outcomes. After a year, her pattern recognition was so trusted that executives would specifically ask for her risk assessment on new initiatives.
Find the executive who wants ground truth. They exist. Not all leaders prefer filtered information. Some actively seek unvarnished reality and protect the people who provide it. Find that person. Build a relationship. Give them direct access to your perspective, with appropriate discretion about how they use it.
Create skip-level moments. Not formal skip-level meetings, which can feel threatening to your manager. But natural opportunities for executives to hear from people closer to execution. Invite a VP to a customer research session. Include an executive in a technical review. Let them experience ground truth directly rather than through layers of translation.
The Politics You Can’t Ignore
I want to be realistic about something. Surfacing uncomfortable information has risks. Organisations often punish messengers, even while claiming they want transparency.
If you work in an environment where raising problems consistently damages careers, you need to factor that in. I’m not suggesting you sacrifice yourself on the altar of information flow. Being right about a problem but unemployed doesn’t help anyone.
Read your specific context:
How does your direct manager respond when you raise concerns?
What happened to the last person who flagged a major risk to leadership?
Does your company celebrate people who prevented disasters or just people who delivered successes?
Is there executive sponsorship for honest communication, or just lip service?
If the environment is genuinely hostile to upward feedback, your options are limited. You can work within the constraints, protecting yourself while doing what good you can. You can try to change the culture, which is possible but slow and uncertain. Or you can decide this isn’t the right organisation for you.
I’ve done all three at different points. None of them are wrong. They’re just different calculations about where to spend your energy.
What Executives Can Do (If Any Are Reading)
Most of this article assumes you’re a PM trying to navigate a broken system. But if you’re a leader who suspects your feedback loops are compromised, here are some things that actually help.
Ask questions that invite bad news. Not “are we on track?” but “what would have to go wrong for us to miss the date?” Not “any blockers?” but “what’s the thing you’re most worried about that isn’t on my radar?”
Reward early warnings. Publicly. Explicitly. When someone flags a risk that lets you course-correct, make sure everyone knows that behaviour is valued. The opposite of shooting messengers.
Create safe channels. Anonymous feedback mechanisms. Office hours with skip-level access. Explicit permission to escalate concerns without going through the chain. Not everyone will use them, but their existence signals that upward communication matters.
Go to the ground. Periodically, skip the filtered updates and see reality directly. Attend a sprint review. Join a customer call. Read the support tickets. Not to micromanage, but to calibrate whether the summaries you’re receiving match what’s actually happening.
Audit your own reactions. When someone brings you a problem, what’s your immediate response? If it’s frustration, defensiveness, or “why didn’t you handle this,” people will stop bringing you problems. If it’s curiosity and gratitude, they’ll bring you more.
Try This Tomorrow
If you’re a PM holding information that leadership doesn’t have, here’s a small step.
Write down the thing you know that your executives probably don’t. The risk. The constraint. The customer signal. The team dynamic. Whatever it is.
Now ask yourself: who is one person closer to leadership who should know this? Not necessarily the CEO. Just one step up from your current information boundary.
Figure out how to tell them. Not as an escalation, but as context. “I thought you’d want to know...” or “I’ve been noticing something that might be relevant...” or “Can I share a concern I’ve been sitting with?”
See what happens. Often, the barrier to upward information flow is simply that nobody took the first step. The system defaults to silence, and silence perpetuates itself.
Breaking the pattern starts with one piece of information making one successful journey upward.
The Unfinished Part
I don’t have a clean solution here. Feedback loops break for reasons that are structural, political, and deeply human. The optimism bias, the messenger fear, the efficiency pressure. These aren’t bugs you can patch with a better meeting format.
What I’ve come to believe is that perfect information flow is probably impossible. Some signal will always be lost. Some risks will always stay invisible until they materialise. The goal isn’t a frictionless pipeline from ground truth to executive decision. The goal is good enough information arriving fast enough to enable course correction.
Good enough. Fast enough. Those are fuzzy standards. They require judgment about what matters and what can be safely filtered. They require trust between layers. They require people willing to take small risks to surface inconvenient truths.
Most organisations get this wrong more often than they get it right. The successful ones fail faster. They find out sooner that reality diverged from the plan. They have shorter delays between “the team knows” and “leadership knows.”
That gap will never close completely. But every week you shorten it, you buy yourself options. And options are what let you course-correct before it’s too late.