Why the People Who Could Fix It Are the First to Leave
SubscribeSign in
Why the People Who Could Fix It Are the First to Leave<br>Someone tried. The reform was real, it worked, and the system absorbed it like nothing happened. Then she updated her resume. Part IV of Organizational Physics Applied.<br>Jul 14, 2026
Share
By month 12, Northstar has a VP of Engineering named in this installment only by her role, because what happens to her happens to a role more than a person. She came up through the company, she is good, and she has watched the last three stages from close enough to name them without the vocabulary. She sees the escalation latency that became a designed path. She sees the enterprise pod producing customizations as a default. She sees that her best people have started routing around problems instead of surfacing them, and she sees, correctly, that none of this is a people problem. It is a system problem, and she decides to fix the part of it she can reach.<br>This is the installment where someone fights back. Remember that, because the reason it matters is not that she fails. It is how she fails, and who pays for it.<br>The Reform Was Real
She does not run a culture initiative or hire a coach, though either would have been forgiven. She does the harder, better thing. Inside her own org, the part she actually controls, she changes what gets rewarded.<br>She makes surfacing a problem early a thing that earns visible credit rather than quiet suspicion. She protects the engineer who flags the ugly dependency instead of the one who ships around it. She holds a standard on commitments and enforces it in the moment, the way Part I described and the company stopped doing two stages ago. She is, without using the word, correcting the structural variable inside her span of control.<br>And it works.<br>This has to be true for the rest to land, so it is worth being precise about how real it is. Within a quarter her org is measurably different. Escalation latency inside her teams drops back toward where it was before any of this started. Her people start telling her things earlier, because she has made early bad news safe. The interacting-dependency problem from Part II, the real one that never climbed, finally gets surfaced and handled inside her org because she built the conditions where surfacing it was rational. Morale in her group lifts in a way that is visible to anyone walking the floor or observing their interactions.<br>She has proven the additive thesis with her own hands: she took the same kind of good intention the coaching world sells, attached it to an actual change in what the system rewards, and got the result the coaching alone never delivers.<br>If the story ended at month 13, it would be a case study in a leadership book. It does not end at month 13.<br>The System Absorbs It Like Nothing Happened
Her org does not exist in a vacuum. It sits inside Northstar, and Northstar’s incentive geometry is unchanged. The enterprise pod still needs its customizations. The curated reporting still flows upward to a CEO whose picture still feels clean. The coordination layer from Part III still routes escalations through its designed six-day path.<br>She fixed the reinforcement inside her walls. Everything outside her walls is still running the pattern she fixed.<br>So the reabsorption begins, and it does not look like sabotage. It looks like gravity. Her teams have to interface with the pod, and the pod operates on the old logic, so her people relearn the old logic at the boundary. Her standard on commitments collides with a cross-functional dependency owned by someone who never adopted it, and the dependency wins, because it always wins, because the rest of the company is structured to make it win.<br>Her early-surfacing culture produces signal that flows up into a system designed to round it toward fine, and the signal she worked so hard to generate gets compressed the moment it leaves her org, exactly as Part II described, which means the company above her never even learns that her experiment worked.<br>The improvement does not get reversed by a decision. Instead it gets eroded at every edge where her corrected org touches the rest of the uncorrected company, a little more each week, until what remains is a VP working twice as hard as her peers to hold a standard the surrounding system is steadily dissolving. She is the leader from the public synthesis post, the one fighting the structural current on sheer will and character, and you are now watching what that costs in real time.<br>What Survived, and Why It’s Not Clean
Something does survive, and this is where the honest version of this story refuses to be tidy.<br>One piece of what she built does not get reabsorbed. The practice she instituted of protecting the early bad-news messenger outlasts her reform, and it spreads, slightly, into one adjacent org, and it holds there past month 15. By the framework’s own logic it should have dissolved like everything else, because the incentive...