The most dangerous “yes” in change work is the one that ends the conversation.

Not because people are lying. Not because they are secretly resisting. But because agreement can quietly push the cost of the change into the future — and into someone else’s workday.

You see it after a steering committee, a leadership alignment, or a “quick sync” that went unusually smoothly. Everyone understands the direction. Nobody objects. Someone even says, “Great. Let’s do it.”

Then the weeks pass, and the old behavior keeps winning.

Where the debt comes from

When people agree quickly, the meeting often skips the messy part: what has to move in the system for the new way to become the default.

In practice, adoption is rarely blocked by belief. It is blocked by the hidden mechanics around the work: exception paths, handoffs, measures, and the small local risks nobody wants to inherit.

So the “yes” becomes a kind of debt. It postpones the negotiation of tradeoffs. It delays the moment someone has to say: If we want this, what are we willing to stop, remove, or change to make it real?

A familiar scene

A leadership group agrees to a new way of handling escalations.

The intent is good: fewer ad-hoc interruptions, clearer thresholds, less noise. Everyone has lived through the chaos of “just one more urgent request.” The new standard sounds like relief.

But the first time a high-status stakeholder pings someone directly, the old shortcut still works. The direct route still feels safer than the proper route. And the person receiving the ping still has an incentive to be helpful — because being helpful is rewarded more reliably than protecting a process.

Nothing dramatic happens. The system simply returns to what works fastest.

The Yes-to-Work Test

When you hear agreement, don’t treat it as momentum. Treat it as a cue to test the path, not celebrate the conclusion.

Here’s a simple tool that shifts the conversation without turning it into a debate:

• Which old path are we closing? If the old path stays open, it will keep winning under pressure.
• Who does the first “real use” with the change, and when? Not rollout. First use.
• What small friction will we remove for that first use? A template, a permission, a handoff, a meeting.
• What will we do when the first exception shows up? Because it will.
• What are we asking people to risk by trying it once? Time, reputation, quality, control.

These questions do not make the change softer. They make it accountable to reality.

A practical move that changes the odds

If you want one concrete step: pick one team and design a “first use” that can happen inside a normal week.

Close one old pathway (even temporarily), protect a small pocket of time for the first attempt, and make it obvious what “good” looks like for that one instance. Then watch what breaks — not to blame anyone, but to find the hidden debt early.

Because the debt is always there. The only question is whether you surface it while you still have room to adjust.

Closing reflection

Agreement is not nothing. It can be real, honest, and valuable.

But in many organizations, the moment people say “yes” is exactly when the real work begins: turning intent into a path that holds up on a Tuesday afternoon, when the calendar is full and the old shortcuts are calling.