Working from the Inside

Post 1 — Tuesday, May 6

[Working from the Inside - Part 1 of 6]

You can read the system. You’ve been able to for a while now.

You know which post-mortems are going to find individual error before the first interview happens. You know which metrics are proxies for the thing that actually matters, and which dashboards your organization runs on because nobody ever asked whether the original question was still the right one. You know where the load is accumulating — the relationship that’s fraying, the process that’s compliant but increasingly brittle, the project that’s on track until it isn’t.

You know this because you’ve done the work. You’ve read the pattern instead of the case. You’ve asked what the system is producing rather than who produced it.

And then you’ve written it up. Sent it to the right people. Waited.

Sometimes nothing happened. Sometimes the finding got absorbed into the next planning cycle and came out the other side as a bullet point. Sometimes the same failure happened six months later and you watched the post-mortem land in exactly the place you said it would.

The analysis was right. The analysis didn’t move anything.

Here’s the thing that’s easy to misread about that gap: it feels like a standing problem. Like you need a title, a mandate, a seat at a different table before the work you’re doing can actually land. So you wait for the promotion, the restructure, the moment when someone in authority finally sees what you’re seeing and hands you the lever.

That waiting is the problem. Not a condition to be patient about. The problem itself.

The system doesn’t need to give you permission to read it. You already have it.

What you haven’t figured out yet is what to do with it from where you actually stand.

Post 2 — Wednesday, May 7

[Working from the Inside - Part 2 of 6]

The first form of influence authority doesn’t require a title. It requires a map.

Not a map someone gave you. The one you built — by paying attention to what the system is actually producing while everyone else was managing what it was supposed to produce.

Here’s what that map looks like in practice. You know which projects are structurally similar to the one that failed last quarter. You know where the accountability process stops asking questions. You know which metrics are drifting in the direction nobody wants to name in a review. You’ve been watching the slope. You know how loaded it is.

Most of your colleagues don’t have that map. Not because they’re less capable — because they’re managing events while you’ve been watching the accumulation. That’s a different kind of attention, and it produces a different kind of picture.

The map is the leverage. Not because you announce it, but because people can feel when someone is oriented. When the room is trying to figure out what’s happening and one person already knows — not what to do, just what is actually true — that person becomes the point others navigate by. Without a mandate. Without a presentation. Just by being the one who has already looked.

The map exists because you built it.

The question is whether you’re using it — or sitting on it, waiting for the right moment, waiting for someone to ask, waiting for the authority to hand it over without risk.

The map doesn’t get more valuable the longer you hold it.

What are you currently watching that the organization is treating as background noise?

Post 3 — Thursday, May 8

[Working from the Inside - Part 3 of 6]

The second form of influence authority is a single question asked at the right moment.

Not a presentation. Not a reframing of the whole problem. One question, precisely placed, that the room wasn’t going to ask.

Here’s what makes it work. Every room has a consensus it’s moving toward. You can feel it — the slight relaxation when the finding lands, when the name goes on the table, when the action items get assigned and the meeting is functionally over even though there are fifteen minutes left. The room has exhaled.

That moment is the moment. Not to challenge the finding — the finding is usually partially right. Not to reframe the whole analysis — you’ll lose the room. Affirm what is true in the finding and extend it. What were the conditions that made this behavior not just possible, but predictable?

Timing matters more than position. A question asked before the room has exhaled lands as a challenge. The same question asked in the exhale lands as a natural extension — it sounds like the next thing, not a competing thing. The room is relaxed enough to follow it somewhere it wasn’t going.

Register matters as much as timing. The question has to be genuinely curious, not rhetorical. If it sounds like you already have the answer and you’re leading the room to it, it closes. If it sounds like you’re actually asking, it opens. The difference is felt immediately.

This is the hardest move to calibrate because it requires reading two things simultaneously: the room’s temperature and your own certainty. The analyst who has a map tends toward certainty. Certainty changes the register. The question stops working.

You have the map. The room is about to exhale.

What question have you been sitting on that you haven’t asked yet?

Post 4 — Tuesday, May 13

[Working from the Inside - Part 4 of 6]

You have the first lever: the map. You have the second: the question. You need the third.

The first two — the map, the question — are acts. You do them, they land or they don’t, the room moves or it doesn’t. The third one works differently. It accumulates over time and earns interest.

It’s naming.

When you give a mechanism a name — a failure mode, a recurring pattern, a thing the organization keeps doing that nobody has called anything — you change how other people see it. Not just in the moment. Going forward. Once something has a name, it becomes possible to refer to it, to track it, to notice when it’s happening again. Before it had a name, it was just a thing that kept happening.

The person who named it owns the frame. Not permanently, not uncontestably — but in practice, in the rooms where the name gets used, the person who coined it is the person whose analysis of it carries weight. That’s influence authority that compounds every time someone uses the name.

This is why the naming move is the hardest to start and the easiest to sustain. Starting requires the confidence to say: this is a pattern, it has a shape, and here is what I’m calling it. That confidence is exposed. The name might not stick. The pattern might not be as general as you thought.

But when it works — when the name travels, when someone uses it in a meeting you’re not in, when it becomes part of how the organization talks about a class of problem — what you’ve built is a piece of shared analytical infrastructure. That infrastructure carries your prior every time it’s used.

What mechanism have you been watching that doesn’t have a name yet?

Post 5 — Wednesday, May 14

[Working from the Inside - Part 5 of 6]

Here’s what doesn’t work, because it’s important to be precise about this.

Performing analysis nobody requested. You’ve seen the failure mode, you’ve traced it to the mechanism, you’ve written it up, and you’ve sent it to three people who didn’t ask. The analysis may be exactly right. It will almost certainly be filed, forwarded once, and not acted on — not because the analysis is wrong but because unsolicited diagnosis lands as criticism. The room wasn’t asking the question your analysis answers. Correct answers to questions nobody asked don’t accumulate into authority. They accumulate into reputation for being difficult.

Trying to redesign the process from inside it. The accountability mechanism is captured. You can see exactly how it’s captured and where it’s aimed. You have a clear structural account of what would fix it. This is the analysis that feels most urgent to act on — and the one most likely to fail if the action is a proposal to the people the mechanism is protecting. The people with standing to redesign the process are the people the process currently serves. Presenting them with a structural critique is not a lever. It’s a target.

Waiting for the right moment to use the map. The analysis matures, the moment doesn’t come, the map gets more detailed. This is the accumulation trap applied to your own leverage — the same error the organization makes with load metrics, now made by the analyst who can see it. The map doesn’t get more useful the longer it’s held in reserve. It gets stale, or it gets overtaken by events you were watching but didn’t move on.

What each of these has in common: they are forms of authority that require the system’s cooperation to land. The map needs a mandate. The critique needs receptive leadership. The moment needs to be offered.

The three moves in this series don’t require the system’s cooperation. They work from where you actually are.

You have the map. You know the room. Which of these moves fits the system you’re actually in?

The system doesn’t give you permission to read it. Which means it can’t take the reading away.

Post 6 — Thursday, May 15

[Working from the Inside - Part 6 of 6]

Here is what the series has been showing you.

The map you built is real. The question you know how to ask is real. The mechanism you’ve been watching without a name — that’s real too.

None of those required a title. You built them through practice: paying attention to what the system was producing while everyone else was managing what it was supposed to produce, asking the question the room wasn’t going to ask, naming the pattern that kept recurring without a name.

That practice is the authority. Not a credential someone conferred. Not a seat at a table someone gave you. Something that accrued through sustained contact with what the system actually does.

The waiting was never the right posture. Waiting for the mandate, the restructure, the moment when someone in authority finally hands you the lever — that’s the same error as waiting for the break instead of watching the breaking. The standing doesn’t arrive before the practice. The standing is the practice, recognized.

The system doesn’t give you permission to read it. You already have it. What you do with that reading — whether you build the map, ask the question, name the mechanism — that’s the work. Not a function of title. Not contingent on the system’s cooperation. Not waiting on anything the system controls.

The analyst who can read the distribution instead of the case, who asks what the system is producing rather than who produced it, who names the mechanism before the next post-mortem finds it again — that analyst isn’t waiting to be made.

They’re already working.

Behavior is output. Debug the system.