Nobody Told You They Were Looking

Your feature was reviewed, critiqued, and discussed by senior leadership. Nobody told you.

A feature is in flight. Not done. Not stable. Still being shaped. A small group of directors or VPs pulls the code, reviews it privately, and picks it apart. Maybe they want to stay ahead or help. What they don’t do is loop in the people accountable for it.

Most senior leaders who do this aren’t acting maliciously—and that’s what makes it dangerous. The intent is fine. The opacity isn’t. When visibility happens without the knowledge of those accountable for delivery, the system creates a distortion field.

What Actually Breaks

Trust erosion. Delivery leaders learn that work can be surfaced or critiqued without them. Once that belief sets in, early sharing drops and defensiveness grows.

Expectation debt. Someone upstream now has context about a feature that isn’t ready. Even if nothing was promised, expectations exist. When reality doesn’t match that early exposure, someone absorbs the gap—and it’s never the people who created the expectation.

I’ve been on the other side of this. A feature my team was shaping surfaced to an executive sponsor during a private review I didn’t know about. By the time I learned it had been shown, the sponsor was already asking about timelines for something without a committed scope. The next two weeks weren’t spent building. They were spent reconciling a perception gap I didn’t create—firefighting instead of collaborating. The feature shipped late, not because the work was behind, but because the goalpost moved before my team knew.

Authority inversion. People without delivery ownership begin forming a narrative around readiness and risk. Those accountable for outcomes lose control over timing, framing, and expectations. That’s not collaboration. That’s control disguised as help.

Shadow governance. When this behavior works once, it becomes a pattern. Decisions move to private channels. Formal structure remains, but influence shifts. That’s how organizations quietly fracture.

If this happened in the open, someone would ask: “Should we loop in the delivery lead?” Private channels remove that check. That’s why the pattern persists.

Why Good Organizations Let This Happen

This pattern survives because it’s unintentionally rewarded. Visibility is praised more than stewardship. Early access is mistaken for leadership.

Sometimes it persists because trust in the delivery chain is weak. Leaders burned by late surprises may feel routing around accountability is pragmatic. But even when accountability is immature, bypassing it compounds the problem. You don’t fix a broken feedback loop by building a second one in private.

Cleanup work is invisible to those who caused it. Launches get delayed. Teams scramble to fill gaps between what was shown and what’s ready. The efficiency was borrowed time.

What Strong Senior Leaders Do Differently

The fix isn’t more process. It’s clearer norms.

Pull accountability into visibility. Before looking at delivery work, ask: “Who owns this, and are they included?”

Protect in-progress work. Make it explicit that early artifacts are for shaping, not judging.

Make curiosity explicit. A VP once pulled a delivery leader into a thread where directors were reviewing early code: “Looping you in. We’re exploring, not judging readiness—feel free to share context or tell us if this isn’t helpful.” What could have been a shadow evaluation became collaborative shaping. “This is exploratory, not evaluative” is a powerful sentence when spoken aloud.

Shut down shadow loops. If delivery work is being discussed, it happens in the open—or not at all.

And this cuts both ways. Delivery leaders who discover that in-flight work was reviewed without their involvement aren’t being territorial when they call it out. They’re doing their job. Surfacing a broken feedback loop is stewardship, not defensiveness—and strong senior leaders recognize it as such.

◇ ◇ ◇

The fastest organizations aren’t the ones with the most access. They’re the ones where nobody has to wonder who else is looking at their work, why they’re looking, or whether they’ll be surprised later.

That’s not culture. That’s leadership discipline.