Reading the System

How Organisations Defend Themselves, and When They're Right To

Every organisation has an immune system.

This isn't a metaphor for dysfunction. Immune systems are necessary. They protect against bad ideas, maintain coherence, and prevent chaos. An organisation without one would lurch from initiative to initiative, destabilised by every new proposal.

The problem is that immune systems can't distinguish between a pathogen and a transplant. They attack novelty because it's foreign, not because it's harmful. The same mechanisms that protect the organisation from bad ideas also kill good ones before they can prove themselves.

If you want to create change, you need to understand how these defences work. Not so you can defeat them—they're not enemies—but so you can read them accurately. Sometimes the immune system is protecting against dysfunction. Sometimes it's giving you feedback. Your job is to distinguish.

The antibodies

Organisational immune responses have recognisable patterns. Learning to name them helps you see what you're facing.

Governance. The proposal needs sign-off from committees, review boards, and steering groups. Each review adds delay and creates opportunities for rejection. Governance exists to ensure accountability and prevent reckless decisions. It also creates friction that kills momentum and advantages easy-to-approve ideas over good ones.

Prioritisation. Your initiative must compete with other priorities for limited resources. It goes on a backlog, gets ranked against other priorities, and waits its turn. Prioritisation focuses effort on what matters most. It also embeds existing assumptions about what matters, making it hard for new categories of value to get traction.

Alignment. The proposal needs to align with the strategy, support the OKRs, and connect to the vision. If it doesn't align, it's out of scope. Alignment exists to maintain coherence and prevent fragmentation. It also privileges incremental ideas over novel ones, since anything genuinely new won't align with a strategy designed before it existed.

Consensus. Everyone needs to agree, or at least not actively object. Stakeholders must be consulted. Concerns must be addressed. Consensus exists to build buy-in and reduce resistance to implementation. It also gives anyone a veto, which means the most cautious voice sets the pace.

"Not now." The timing isn't right. We're in the middle of a reorg. Let's revisit next quarter. There's too much on already. Deferral exists to protect capacity and avoid overload. It also becomes a permanent state for ideas that are never quite urgent enough to prioritise.

Risk management. What could go wrong? What are the dependencies? What's the fallback? Risk management exists to prevent failures and protect the organisation. It also systematically favours doing nothing, since every action carries risks and inaction appears (falsely) to be risk-free.

These antibodies are not illegitimate. Each protects something real. The question is whether they're being triggered appropriately or have become automatic responses that hinder learning.

Follow the incentives

This is the single most useful tool for reading the system: understand what people are rewarded for.

Not what the organisation says it values. What it actually promotes, pays bonuses for, and praises. The gap between stated and enacted values tells you almost everything you need to know.

What is your sponsor actually measured on? If they're measured on delivery predictability, they'll filter out anything that introduces uncertainty. If they're measured on cost control, they'll filter out anything that requires investment. If they're measured on stakeholder satisfaction, they'll filter out anything that might upset important relationships. This isn't cynicism—it's rational behaviour. They're responding to the incentives the organisation has created.

What happened to the last person who took this kind of risk? If people who tried new things and failed were punished, the rational response is to avoid new things. If people who tried and succeeded were rewarded, but people who tried and failed were also punished, the expected value of trying might still be negative. Organisations often claim to want innovation while punishing the failures that innovation requires.

What gets celebrated here? Look at who gets promoted, who gets praised in all-hands meetings, whose names come up as examples. That tells you what this organisation actually values, regardless of what it claims to value.

What gets punished? Look at who got managed out, what projects got cancelled, and what ideas got someone in trouble. That tells you what this organisation actually avoids, regardless of what it says about risk-taking and experimentation.

Who benefits from the current state? Every status quo has beneficiaries. They may not be obvious. The inefficient process might be keeping someone employed. The bottleneck might be giving someone power. The dysfunction might be protecting someone from scrutiny. Change creates both winners and losers. Those people have rational reasons to resist, even if they never say so directly.

Reading incentives isn't about manipulation. It's about understanding. If you can see why someone's filtering makes sense given what they're rewarded for, you can either address that concern directly or recognise that you're asking them to act against their interests—which is a different kind of ask that requires different tactics.

What each antibody is protecting

When you encounter resistance, ask, what is this mechanism designed to protect?

Governance protects against unaccountable action. If someone is blocking you through governance, they may be concerned about who gets blamed if this goes wrong or who loses control if it succeeds.

Prioritisation protects against overcommitment. If your idea keeps losing the prioritisation battle, it may be that the people with the broadest view genuinely see more important uses for limited capacity.

Alignment protects against fragmentation. If you're being told your proposal doesn't fit the strategy, the concern may be that the organisation can't absorb another direction at this time.

Consensus protects against alienation. If someone insists on more consultation, they may be worried about people feeling steamrolled or left out.

Deferral protects against overload. If you keep hearing "not now," the organisation may genuinely be at capacity, even if it doesn't look that way from your position.

Risk management protects against failure. If your proposal is being picked apart for risks, the concern may be that failures are punished harshly in this organisation, and no one wants to be associated with one.

None of this means the filtering is correct. But understanding what it's protecting helps you address the actual concern rather than fighting a proxy battle.

Structural vs. substantive filtering

This is the crucial distinction.

Substantive filtering engages with your idea on its merits. "Here's why that won't work." "Have you considered this trade-off?" "The evidence doesn't support that assumption." Substantive filtering is feedback. It might be wrong, but it's taking your proposal seriously and offering reasons.

Structural resistance doesn't engage with merit. "That's not how we do things." "The timing isn't right." "It needs more alignment." "Let's put it on the backlog." Structural resistance is the immune system activating. It's not evaluating your idea; it's pattern-matching against novelty.

The test: could any idea have passed?

If the answer is yes—if you can see how a different proposal, better framed or better timed, might have succeeded—then you're facing substantive concerns, even if they're frustrating.

If the answer is no—if the process seems designed to filter out any change, regardless of merit—then you're facing structural filtering.

This matters because the responses are different.

Substantive filtering requires stronger arguments, stronger evidence, and revised proposals. You can work with it because it's a conversation about what's true and what's valuable.

Structural filtering doesn't respond to better arguments. You can't reason your way past it. You have to work around it or wait it out.

Most frustrated change agents assume they're facing structural filtering when they're actually facing substantive feedback they don't want to hear. Be honest with yourself about which situation you're in.

When the system is right

Sometimes the filtering is correct.

Not because the organisation is too conservative. Not because they don't understand. But because the idea is genuinely bad for this context, this moment, this organisation.

Some ideas deserve to be filtered out:

Ideas that solve your problem, not theirs. What's painful to you might be functional for the system. The process that frustrates you might be protecting something you don't see. If your idea only makes sense from your position, it may not be as good as you think.

Ideas that have been tried before. Organisations have longer memories than individuals. What looks like a fresh proposal to you might be the third time this has been suggested. The filtering might be "we tried that, and it failed", even if nobody tells you directly.

Ideas that ignore real constraints. You may not see the budget pressures, the political dynamics, the dependencies on other initiatives, or the commitments already made. From where you sit, the path looks clear. From where they sit, it runs through a minefield.

Ideas that require more trust than you've earned. Big ideas require sponsors to spend political capital. If you're asking for a level of commitment that exceeds your track record, the filtering might be appropriate. You're asking them to bet on you, and they're not sure you're a good bet.

Ideas whose time hasn't come. Timing matters. An idea that's right for the organisation in two years might be wrong for the organisation now. Deferral isn't always cowardice; sometimes it's judgment.

None of this means you should give up on ideas that are being filtered. But it means you should take the filtering seriously as information, not dismiss it as obstruction.

The information asymmetry problem

You don't know what they know.

This is obvious, but its implications are easy to forget when you're frustrated.

The senior leader who blocked your proposal may have information about budget cuts coming next quarter. The steering committee that deferred your initiative may be aware of a reorg that will change everything. The manager who keeps saying "not now" may be managing three other crises you can't see.

Information asymmetry doesn't mean they're right and you're wrong. It means you should hold your certainty loosely. The picture looks different from different positions in the organisation. Your view is not the complete view.

Some questions worth asking:

What might they know that I don't? What would have to be true for their response to make sense? If I assume they're acting reasonably given what they know, what would that imply about what they know?

You won't always get answers. But asking the questions helps you avoid the trap of assuming that everyone who disagrees with you is either ignorant or captured.

Mapping the system

Before you try to change anything, try to see it clearly.

Where are the real decisions made? The formal decision-making process may not be where decisions actually happen. Steering committees may ratify decisions made in informal conversations. Approvals may be determined before the meeting starts. If you're not visible where the real decisions happen, the formal process won't save you.

What are the actual values (not the stated ones)? Every organisation has espoused values (what we say we care about) and enacted values (what we actually reward and punish). The gap between these tells you a lot about what you're working with.

Who are the informal influencers? Formal hierarchy is not the only power structure. Some people have influence that exceeds their title. Some have titles that exceed their influence. Understanding who actually shapes opinions and decisions helps you know who you need to reach.

Who loses if you succeed? Change creates losers as well as winners. Whose budget shrinks? Whose authority is diminished? Whose expertise becomes less relevant? Those people have rational reasons to filter out your signal, even if they never say so directly.

This kind of mapping takes time. It's not something you do once; it's an ongoing practice of paying attention. But without it, you're trying to navigate a landscape you can't see.

The respect the system deserves

It's easy, when you're frustrated, to see the system as stupid, broken, or corrupt. Sometimes it is. But often it's doing something more complex: it's balancing concerns you don't see, protecting against risks you haven't considered, maintaining coherence across a scale you don't experience.

The immune system that blocks your idea has probably also blocked many harmful ideas. The bureaucracy that frustrates you has likely also prevented significant chaos. The caution that feels like cowardice has probably also avoided many failures.

Respecting the system doesn't mean accepting everything it does. It means taking it seriously as a thing with its own logic, history, and reasons. It means approaching resistance with curiosity before contempt.

The best change agents are not those who view the immune system as an enemy to be defeated. They're the ones who understand it well enough to work with it—helping the organisation develop better pattern recognition rather than simply trying to evade its defences.

That understanding starts with accurately reading the system. Not as you wish it were. Not as you think it should be. But as it actually is.

Next in the series: where attention flows in organisations, and how the stages we perform on shape what change is possible.