The Burst Pipe: Why Everyone's Problem Is Nobody's Problem

A pipe bursts in a crowded municipal square.

Water is coming up through the bricks, it is nine at night, and forty people walk past it on their way home. Nobody calls anybody. Every single one of them assumes somebody already did.

That same pipe bursts in your basement at nine in the morning. You are standing in an inch of water with a wrench in your hand in about ninety seconds.

Same pipe. Same water. The only variable that changed is who owns the floor.

The Beautiful Matrix That Killed Your Project

You walked in and proved the bottleneck was everywhere.

The legacy data pipeline creates administrative drag on product development. It taxes customer success. It distorts what finance sees. It slows regional operations. You built a clean matrix showing exactly how the friction touches four different business units, and it was, honestly, a good piece of work.

Everyone in the room agreed the situation was less than ideal.

Then they walked back to their desks and did absolutely nothing, and six months later the autopsy blamed budget cuts and competing priorities.

It was neither. You presented a problem in a crowded square.

Only One Person in the Room Is Paid to Care About the Whole

This is the part that is easy to resent and important to accept.

The only executive that gets out of bed looking for ways to improve the overall health of the macro-organization is the CEO. Most all other executives get out of bed looking to defend their own perimeter, protect their headcount, and clear whatever is standing between them and the number they are personally graded on this quarter.

So when you frame a problem as a horizontal tax that erodes margin across four groups, here is what actually happens in the room. Product assumes customer success will champion it. Customer success figures finance will fund it. Finance assumes operations owns the system.

Every leader in the room gets an implicit license to walk past the water, and every one of them takes it, politely.

You did not build a business case. You built a square.

Meet Ray

Ray runs procurement, and Ray is standing in the basement.

Because field fulfillment cannot see real-time warehouse levels, Ray's group has to carry an emergency capital cushion to avoid stocking out. That cushion traps about two million dollars in idle inventory every single week.

It is not a line item anyone else in that room feels. It sits on Ray's balance sheet, it shows up in Ray's numbers, and Ray is the one who has to explain it.

The latency is horizontal. The bill is not. The bill has one name on it.

Find the Basement

Stop presenting the square. Find the one leader who is standing in the water.

You do not open with the four groups that are inconvenienced. You look at the one executive whose quarter is materially worse because this system exists in its current state, and you build the entire narrative on their floor.

Then you say the cost out loud, to them, in front of everyone.

And if we don't move on this, Ray keeps carrying that cushion. Leaving this room without a decision means choosing to tie up roughly eight million dollars in working capital over the next four quarters rather than authorize a system integration we have already scoped.

Watch what happens to the room when you do that. The other executives stop bracing for a pull on their budgets, because you just told them this is not their bill. And then, slowly, they all turn and look at Ray, to see whether he is really going to defend an eight-million-dollar penalty in order to avoid a forty-minute scoping session.

He is not.

The Square and the Basement

The Square is a problem shared by everyone, which is another way of saying it is a problem defended by no one. It is safe, it is polite, it is unanimous, and it never gets funded.

The Basement has an owner. It has a name, a number, and a person who cannot look away from it, because the water is rising on their floor and they are the one holding the wrench.

Your job is not to prove the pipe is broken. Everyone in that square agrees the pipe is broken. Your job is to find whose basement it is flooding.

Monday Mission

Take the initiative that has been stalled the longest and look at the org chart, not the architecture.

Find the single leader whose numbers get materially worse if nothing changes. If you cannot point to one, that is not a resourcing problem or a timing problem. That is why it is stalled, and it will stay stalled until you fix it.

Then throw away the matrix and rebuild the story on that one person's floor.

Stop announcing the leak to the square. Go knock on the basement door.

-BZ