The Diagnostic

How to Know If You're the Problem

You're frustrated.

Something you can see clearly isn't changing despite your best efforts. The organisation says one thing and does another. Good ideas die in committee. The same dysfunctions persist year after year while leadership talks about transformation.

I hear you. But I'm also going to challenge you, because frustration is not evidence.

Frustration tells you something is blocked. It doesn't tell you whether the blockage is appropriate. It doesn't tell you whether your idea is good. It doesn't tell you whether you've actually tried to make change happen, or just tried once, badly, and given up.

Before we talk about amplifying your signal, we need to figure out what the signal actually is.

The uncomfortable possibility

You might be wrong.

Not wrong about the dysfunction. Organisations are genuinely dysfunctional. But wrong about your solution, or your approach, or your reading of the situation. Wrong in ways that the organisation's filtering is trying to tell you, if you were willing to listen.

The feedback loops that filter out your ideas also filter out bad ideas. They can't tell the difference, which is part of the problem. But that means some of what gets filtered deserves to be filtered.

So the first diagnostic question isn't "why won't they listen?" It's "what if they're right?"

Signs your idea might not be as good as you think

None of these are proof. But if several apply, slow down.

You can't articulate the trade-offs. Every change has costs. If you can only see benefits, you haven't thought hard enough. When someone raises concerns, do you engage with them or dismiss them as resistance? If your response to every objection is that they just don't understand, consider that you might be the one not understanding.

No one with more context agrees. The people who've been here longer, who see more of the system, who have tried similar things before: what do they say? If the answer is "they're all captured by the status quo," you might be right. You might also be discounting expertise because it's inconvenient.

You've never revised your idea based on feedback. If your proposal looks the same after six months of pushback as it did on day one, you're not learning. Either the feedback contains nothing useful (which is possible but unlikely), or you're not listening to it.

You're more attached to the solution than the problem. Would you be satisfied if someone else solved the problem differently? If the answer is no, your ego is involved in ways that might be distorting your judgment.

The problem you're solving is your problem, not theirs. What's painful to you might be functional for others. The process that frustrates you might be protecting something you don't see. Have you genuinely tried to understand why things are the way they are?

Signs the filtering is structural

If the previous section didn't land—if you've genuinely wrestled with the possibility that you're wrong and still believe the filtering is the problem—here's what to look for.

No substantive objections are offered. When you propose something, the response isn't "here's why that won't work" but rather "that's not how we do things", "the timing isn't right", or "we need to focus on priorities." These are structural deflections, not substantive engagement. They tell you the idea isn't being evaluated on its merits.

Approval requires evidence that requires approval. You can't run the pilot without sign-off. You can't get a sign-off without data. You can't get data without the pilot. This catch-22 is a signature of structural filtering: the system has made it impossible to test ideas it hasn't already endorsed.

The same ideas die repeatedly, from different sources. If multiple people have tried similar changes and all failed in similar ways, the pattern isn't individual failure. Something about the system reliably filters out this kind of idea. That might mean the idea is genuinely bad for this context. It might also mean the feedback loops are broken.

Success in one area doesn't spread. Someone ran the experiment, it worked, and nothing changed. The pilot was successful and wasn't scaled. The proof of concept proved the concept and was quietly shelved. When evidence doesn't update behaviour, you're looking at structural filtering.

The stated values contradict the enacted incentives. The organisation says it values innovation, but nobody gets promoted for taking risks. It says it wants collaboration, but rewards individual performance. When the gap between rhetoric and reality is this wide, the formal channels are performing legitimacy rather than enabling change.

What kind of organisation are you in?

This question matters more than most people realise. The sociologist Ron Westrum identified three types of organisational culture, and they handle information—including signals from sensors like you—very differently.

Pathological (power-oriented). Information is hoarded as a source of power. Messengers are shot. Failure is punished, so it gets hidden. New ideas are seen as threats to existing power structures. If you're in a pathological culture, sensing is dangerous. Speaking up can end your career. The feedback loops aren't just broken—they're weaponised.

Bureaucratic (rule-oriented). Information moves through proper channels. Messengers are tolerated if they follow the process. Failure triggers reviews and new procedures. New ideas are evaluated against existing rules and precedents. If you're in a bureaucratic culture, sensing is slow. Your signal might eventually get through, but it will be filtered, translated, delayed, and possibly neutered by the time it arrives.

Generative (performance-oriented). Information is actively sought. Messengers are trained and valued. Failure is treated as an opportunity to learn. New ideas are welcomed and evaluated on merit. If you're in a generative culture, you probably don't need this series—or you're in a generative pocket within a larger bureaucratic or pathological organisation.

Most organisations are mixed. You might have a generative team inside a bureaucratic department inside a pathological company. The culture that matters is the one at the boundary where your signal needs to cross.

Why this matters for your diagnostic:

In a generative culture, if your ideas aren't landing, the most likely explanation is that they need work. The feedback loops are functioning. Listen to them.

In a bureaucratic culture, if your ideas aren't landing, it might be the ideas or it might be the process. The feedback loops exist, but they're slow and lossy. You may need to be more patient, more persistent, and more skilled at navigating channels.

In a pathological culture, if your ideas aren't landing, it might not matter whether they're good. The feedback loops are serving power, not performance. Your signal isn't being evaluated—it's being assessed for threat. In this case, wait for the last post in this series. The question isn't how to be a better sensor. It's whether to stay.

The ego trap

There's a failure mode between "I'm wrong" and "the system is broken" that's worth naming: you might be right, but not yet persuasive.

This is uncomfortable because it puts the responsibility back on you. It's easier to believe you're being silenced than to accept you haven't yet learned to make your case effectively. But for many frustrated ICs and middle managers, this is the actual situation.

Signs you might be in the ego trap:

You've tried once or twice, not ten times. Institutional change usually requires multiple attempts, refined each time. If you proposed something that didn't fly and concluded the system is broken, you may have given up too early.

You've tried the same approach repeatedly. Doing the same thing and expecting different results isn't persistence, it's stubbornness. Have you actually varied your approach based on what you learned?

You're frustrated with the pace, not the direction. If things are moving your way but not fast enough, that's not broken feedback loops. That's institutional time, which moves more slowly than individual time. Impatience isn't the same as being blocked.

You're focused on being right rather than being effective. Winning the argument and making the change are different things. Some people would rather be vindicated than successful. If that's you, notice it.

The conditions for safe-to-fail experiments

The previous post introduced safe-to-fail experiments: small tests within your authority that generate evidence. Before you go down that path, some conditions should be met.

You've genuinely tried formal channels. Experiments aren't a shortcut around doing the work of legitimate influence. If you haven't made your case through normal means—skilfully, more than once, learning and adapting each time—you haven't earned the right to route around them.

The experiment is actually within your authority. You probably have more latitude than you think, but you don't have unlimited latitude. Running experiments that clearly exceed your authority isn't evolutionary change. It's insubordination, and the consequences are different.

You're prepared to share what you learn. An experiment that stays hidden isn't building toward anything. The point is to generate evidence that can eventually inform a formal proposal. If you're not planning to surface the results, ask yourself why.

You can explain it honestly. If someone asks what you're doing, can you tell them without spinning? "I'm trying a different approach to X to see if it works better" is honest. "I'm just doing my job", when you know you're testing something that is not.

Failure is actually safe. "Safe-to-fail" isn't just a phrase. If the experiment going wrong would cause real damage—to customers, to colleagues, to the organisation—it's not safe to fail. Scale down until failure is genuinely low-cost.

The honest assessment

Here are the questions to sit with before you act. Not to answer quickly, but to genuinely wrestle with.

What kind of organisation am I in? Pathological, bureaucratic, or generative? Where are the boundaries between cultures? What does that imply for my approach?

Have I genuinely tried to understand why things are the way they are? Not to agree with it, but to understand the function it serves, the history that created it, and the incentives that maintain it.

Have I engaged seriously with the objections to my idea? Not dismissed them as resistance, but treated them as potentially valid concerns that might require me to revise my approach.

Have I tried formal channels more than once, varying my approach each time? Not the same proposal to the same people, but genuinely different framings, different sponsors, different moments.

Am I frustrated because the feedback loops are broken, or because I haven't yet developed the skills to use them? This one stings. Sit with it anyway.

If someone I respected told me I was wrong about this, would I be able to hear it? If the answer is no, you're not in a position to assess your own situation accurately.

Where this leaves you

If you've worked through this diagnostic honestly, you're in one of four places.

You realise you have more legitimate work to do. You haven't actually exhausted formal channels. Your idea might need revision. Your influence skills might need development. The next post is for you.

You're confident the filtering is structural, and you're in a bureaucratic culture. You've tried, you've learned, you've revised, and the feedback loops still aren't carrying your signal. But the organisation isn't hostile—just slow and process-bound. The rest of the series is for you.

You're in a pathological culture. The feedback loops aren't just slow—they're dangerous. Speaking up has real costs. The question isn't how to be more effective. It's whether to stay. The final post is for you.

You're not sure. That's fine. Uncertainty is appropriate here. If you're genuinely uncertain, err on the side of more legitimate work before you try evolutionary approaches. The cost of trying formal channels one more time is low. The cost of running experiments when you haven't done the groundwork is higher.

The goal of this diagnostic isn't to stop you from acting. It's to make sure that when you act, you're acting on accurate information about your situation rather than on frustration alone.

Frustration feels like clarity. It usually isn't.

Next in the series: what legitimate influence done well actually looks like, and how to know when you've genuinely exhausted it.