The meeting goes well. People ask sensible questions. Nobody objects. Someone even says, “This makes sense.” You leave with that quiet relief that comes from feeling aligned.

Then you wait for the new behavior to show up.

And it doesn’t.

This is one of the most common (and most expensive) misunderstandings in change work: we treat alignment as if it’s the same thing as follow-through. It isn’t. Agreement is real, and still nothing changes—because the practical conditions for adoption never changed.

When agreement becomes a social event

Here’s a recognizable version of the pattern.

A cross-functional group meets to “align” on a new way of handling work intake: fewer ad-hoc requests, a clearer pathway, a single shared template. Everyone agrees it’s needed. People are tired of chaos. The current way creates rework and frustration. The direction is right.

But when the meeting ends, the old pathways still exist. The same people still get pinged on chat. The same urgent escalations still cut the line. The same stakeholders still expect exceptions. The old behavior remains the fastest way to get things done, and it is still socially rewarded.

So people return to what works.

Not because they disagree, but because the system still pays them for the old pattern—through speed, reduced risk, fewer negotiations, or simply because “this is how we survive the week.”

In other words: alignment can be true without being usable.

Adoption is a design problem, not a motivation problem

When follow-through is missing, the typical reaction is to reach for stronger communication: repeat the message, clarify the “why,” reinforce the expectation, ask for commitment.

Sometimes that helps. Often it just creates more noise around a problem that is mostly practical.

Most stalled change efforts don’t fail because people didn’t understand. They fail because the change was added on top of existing work, or because it asked for a new behavior without removing the old one. Capacity doesn’t appear because a plan is approved.

If the practical environment stays the same, you end up with a familiar situation:

• Leaders interpret agreement as progress.
• Teams interpret agreement as “we’ll figure out how later.”
• Nobody resolves the “how,” so everyone returns to default.

The change leader feels misled. The teams feel pressured. The next meeting becomes a little more cynical than the last.

The core issue is simple: adoption depends on conditions, not conclusions.

The questions that reveal whether adoption is even possible

The most useful move here is to stop diagnosing attitude and start diagnosing feasibility.

Once you’ve developed the direction in prose and people genuinely agree, ask what must become true in the work for the change to actually happen. In my experience, these practical questions surface the real blockers quickly:

• What existing work does this replace? (If it replaces nothing, it competes with everything.)
• What becomes easier for the people expected to adopt it? (If nothing becomes easier, adoption depends on pressure.)
• Who carries the extra coordination while the change is still new? (Someone always does.)
• Where does the change conflict with current priorities, measures, or habits? (The system will choose the old rewards.)
• What would make the first step easier to take? (Not the whole change—just the first step.)

Notice what these questions do: they move the conversation away from persuasion and toward work design. They also reduce the risk of the “alignment trap,” where everyone leaves the meeting with a pleasant feeling and incompatible assumptions.

A practical move that works surprisingly well

If you only take one thing from this, take this question to one affected team—the people who have to live with the change, not the people who approved it:

“What would need to be removed, simplified, or clarified for this to become easier to adopt?”

You may not love the answer. It might reveal that the change is heavier than it looked from the outside. It might expose a dependency you hadn’t seen, or a measure that quietly punishes the new behavior.

But it will usually give you something more valuable than another round of alignment: it will show you what adoption is currently competing with.

And that’s where follow-through becomes realistic—not when people agree, but when the new way becomes possible, useful, and easier to live with than the old one.

Closing reflection

A good meeting can create clarity. It can even create genuine agreement. But if nothing changes in the practical environment—capacity, priorities, handoffs, incentives, old pathways—then agreement is simply where the conversation ended.

If you want follow-through, don’t only ask, “Are we aligned?” Also ask, “What needs to change in the work so this can actually happen?”