You found something wrong. Not vague, not theoretical, a specific thing that doesn’t look right.
You reported it to the person above you, the way you’re supposed to.
And now you’re waiting.
Except you’re not really just waiting. You’re replaying the conversation. You’re wondering if you explained it clearly enough. You’re checking your email every hour for a response that hasn’t come, and wondering if that means they took it seriously or dismissed it quietly.
Maybe they told you it’s already been considered…
Maybe they said it’s being handled…
Maybe they used the word “material” and you realized you don’t actually know if your concern qualifies…
And now you have a thought that won’t leave you alone:
Is anyone actually going to fix this? Or am I just going to watch it disappear into the organization’s internal processes?
That thought is the thing that changes everything.
The problem with “move it up the chain”
Most organizations tell you the same thing: if you see something wrong, report it to your manager. If nothing happens, escalate. If that doesn’t work, escalate again.
This sounds like safety built in. It feels like a system designed to catch problems.
But what actually happens when you move a concern upward?
It enters a structure where people are already connected to each other.
Your manager made a decision. The person above your manager knows that this decision was made. They know who made it. They may even know why.
So when your concern lands on their desk, they are not starting fresh. They are looking at information that is already integrated into the organization’s understanding of what happened.
And they face a natural institutional question:
Why should we overturn a decision made by someone closer to the matter than I am?
Usually, that question makes sense. The person closer to the ground often does have better information. But it becomes a trap when the original decision was itself the problem you’re reporting.
Here is the distinction that matters:
A person higher up has more authority. They don’t necessarily have more independence.
Those are completely different things.
Barings shows how this breaks
Nick Leeson worked for Barings Bank in a position that combined trading with responsibility for reporting and settlement. That arrangement allowed the same individual to create positions, obscure losses and provide information to people who were supposed to be overseeing the operation.
The bank had layers of hierarchy. It had oversight. It had reporting systems.
What it lacked was a structure that effectively separated the person making the decisions from the person independently verifying what those decisions were producing.
When people in London asked questions, they were relying heavily on information coming through the same structure that had produced the problem.
They had authority.
They did NOT have the independent visibility needed to verify what they were being told.
The lesson is broader than a single bank collapse:
You can have multiple levels of oversight without having any real mechanism for independent verification.
The difference is crucial when you are trying to figure out where to report something.
One layer higher is not the same thing as independent.
What actually happens
Let’s say you report a concern to your manager.
Your manager says it’s already been considered. Maybe she’s right. Maybe someone else raised the same thing months ago.
You push back. You escalate.
The next person asks your manager what happened.
Your manager explains the original decision.
The person above your manager thinks: that sounds reasonable.
Nothing improper has necessarily occurred. Your manager may have had good reasons for the decision. The higher-level person may be right to trust them.
And yet something crucial has not happened:
The original question has not been reconsidered. It has just moved up.
Your manager has provided the answer. The person above your manager has reviewed the fact that an answer was provided.
These are not the same thing.
A reporting system can be excellent at moving information upward while being terrible at creating genuine reconsideration.
This is where your isolation arrives. Because now YOU are the only person in the chain who still thinks this matters.
Your manager considers it closed. The person above your manager considers it handled. And you are left wondering if you’re missing something, or if you’re just the only one still alarmed.
The organization is not necessarily acting badly. Your managers may be thoughtful people doing their jobs well.
Yet you are still trapped.
This is where courts of appeal matter
Here’s what makes a court of appeals actually valuable: it’s not just that it’s higher. It’s that it occupies a different structural position.
An appeals court can reconsider a trial court’s decision without simply being another node in the same chain that produced the original decision. It has institutional distance.
Most organizations have escalation pathways. They do not always have something with that kind of structural independence.
That distinction is critical:
Escalation moves information up.
Independence changes the structure where it’s being considered.
They can happen together.
They don’t have to.
Wirecard makes it visible
Wirecard is an extreme case, which is exactly why it’s useful.
By 2019, the Financial Times was publishing investigations into allegations surrounding Wirecard’s business. German authorities responded in part by investigating the journalists for suspected market manipulation. Those proceedings were eventually dropped.
That is NOT ordinary.
Most people reading this will never encounter that dramatic a warning sign. But Wirecard makes something visible that is much harder to see in ordinary cases:
The structure responsible for scrutiny can itself become committed to a particular interpretation of what is happening.
The problem was not simply that nobody had information. Critical reporting existed. Regulators had received information. The later parliamentary inquiry found serious problems in the way responsibility, decision-making and oversight had operated.
By the time the alarm became undeniable, however, the institution had already accumulated years of explanations, assurances and decisions that pointed in another direction.
Wirecard is an extreme case.
But the mechanism it reveals is not.
How ordinary institutional traps work
Someone makes a decision. Someone else reviews it and finds it reasonable. Another person does the same. Each step is defensible. Each person makes a sound judgment from their position.
And somehow, an error becomes institutional knowledge.
Once it has, asking someone higher up to overturn it is no longer just asking them to assess evidence.
It’s asking them to invalidate part of the organization’s existing understanding of what happened.
That carries a weight you cannot see from the outside.
The difficult cases don’t come with red flags
Most of the time, you won’t see dramatic warning signs.
You’ll just see:
- A manager who seems competent
- A compliance function that’s been consulted
- A legal opinion that says it’s fine
- Silence when you push back
Nothing looks wrong. It just looks closed.
This is why “report internally first” is both good advice and deeply incomplete advice.
Internal reporting can be entirely appropriate.
But before you trust internal escalation as a safeguard, it is worth asking some hard questions:
Who made the original decision?
Who supplied the information on which it was based?
Who benefits from leaving the decision undisturbed?
Who bears the consequences if the decision is wrong?
Does the person who can reopen it have a reason and a structural capacity to disagree with the people who made it?
These questions don’t prove wrongdoing.
They establish something more basic:
whether independent reconsideration is actually possible.
The answer is often structural, not personal
This matters because it’s tempting to blame individuals.
A manager who won’t listen. A compliance officer who’s in someone’s pocket. A culture that punishes dissent.
Sometimes those explanations are correct.
But they’re not required.
A regional office might reasonably trust its national office. A department head might reasonably trust a manager. A compliance officer might reasonably rely on information provided by the business itself. A board might reasonably assume that management has dealt with an operational matter.
Each person makes a reasonable decision from their position.
The organization nevertheless becomes increasingly committed to the first decision.
That is how an error can transform into institutional knowledge.
And once it has, the structure itself can become the problem.
Not the people in it.
The structure.
So what should you actually do?
There is no universal rule that every concern should immediately go outside the organization.
That would be as simplistic as insisting that every concern must travel first through internal hierarchy.
The useful question is different:
Where does genuine independent reconsideration actually exist?
Sometimes that’s an internal audit function with real independence.
Sometimes it’s an audit committee.
Sometimes an ombudsman.
Sometimes a regulator.
Sometimes the relevant question is jurisdiction… whether there is a reporting authority whose legal framework gives meaningful protection to the person making the disclosure.
The important thing is not to find the next rung on the ladder.
It is to identify the point at which the matter can be genuinely reconsidered without simply reproducing the same institutional logic that produced the original decision.
That might be higher up in your organization.
It might be outside it entirely.
But the structure has to actually be different.
The question that matters most
When a concern has already been considered internally and you’re wondering whether to escalate further, don’t ask only:
“Who is higher?”
Ask:
“Who is structurally capable of reconsidering this without being dependent on the people who already decided?”
That is a fundamentally different question.
It considers authority without assuming independence.
It considers the position of the person reporting (i.e. you) without pretending that a reporting channel, by itself, solves the structural problem.
Because here is the thing:
A reporting channel can be open.
A process can be followed.
A concern can be escalated.
And the original decision can still remain effectively unchallenged.
The existence of a path does not prove that the path goes anywhere.
When you need to see outside the frame
There is a deeper problem here.
When you are inside an organizational structure, that structure determines not only what you can do, but much of what you can see.
The information available to you is filtered through the roles around you. The explanations available to you are shaped by the decisions that have already been made. The people you can ask may themselves depend on those decisions.
That does not mean people inside organizations are incapable of seeing problems.
It means there are questions about the structure that are difficult to answer using only the structure’s own interpretation of itself.
You may be right about what is happening.
You may be wrong.
You may simply be missing something that someone in another position can see.
The point of an outside perspective is not to tell you that you are right.
It is to help determine what your position makes visible, what it makes difficult to see, and whether the structure actually gives you a viable route to reconsideration.
That is a different kind of help.
And sometimes it is the first time the situation becomes legible.
The question before the next step
If you’re reading this because you’re in the middle of exactly this situation, you don’t need to have all the answers right now.
You need to know what you’re looking for.
You’re looking for a place where someone can say no to the people who came before them.
Where the original decision isn’t treated as institutional truth simply because it has already been made.
Where the person reconsidering the matter has enough independence to reach a different conclusion.
And if you cannot identify such a place inside the organization, THAT is itself important information.
You don’t necessarily need to act on it immediately. But you should know it. Because the first problem may not be that your organization lacks a reporting channel.
It may be that you have mistaken a path for an exit.
That is the distinction worth seeing before you take the next step.
Structural Snapshot
See what your position makes possible… and what it doesn’t.
A Structural Snapshot maps the situation you’re actually in: who holds authority, where information sits, what has already been decided, where your exposure lies, and whether there is a genuinely independent route to reconsideration.
Centreline Clarity 