When Agreement Isn’t the Problem

Everyone agreed.

So why is nothing actually changing?

The need was clear. The decision was made. People nodded their heads around the table.

And yet weeks later, the thing everyone agreed needed to happen still hasn’t happened.

A team can be moved by the need for change while in the room, and not be ready for what that change actually requires when Monday arrives.

In the room, the case makes sense. In the moment, the energy is real.

Then there’s readiness for what follows.

What will this actually require of us—not in theory, but in practice?

What behaviors, what habits, what ways of working will have to change?

Who specifically is responsible for what, starting when?

And honestly, are we actually ready for that, or are we ready to say we are?

Most teams might skip the last question. Not because they’re being dishonest. Because in the moment, the distinction doesn’t feel important yet. It does later.

Implementation conversations tend to focus on the plan. The milestones. The timeline. The metrics.

What happens when the plan meets reality and people want to revert?

The moment always comes. The initial energy fades. The complexity surfaces. What looked clear in the planning phase gets muddier in the doing. And without something in place to carry the team through the stretch—not motivation, not another meeting, actual support and structure—the default is to drift back toward what’s familiar.

This is where implementation rises or falls. Not in the quality of the plan. In what’s in place for when things get hard.

And most teams don’t build that in until they’re already needing it.

Underneath the stalled movement is the pull of what was.

What’s familiar has weight. History. Identity. Ways of working that have held things together—imperfectly, but reliably—for a long time.

That pull isn’t weakness or resistance in the negative sense. It’s human. And it’s stronger than most change efforts account for.

When a team is struggling to move, it’s worth asking: is the connection to “what was” stronger right now than the pull toward “what could be?” Not as a judgment, just as an honest read of where the team actually is.

If the answer is yes, the response isn’t to push harder. It’s to understand what makes the familiar feel safer than the possible.

A few questions if your team is in this stretch:

• When you made the decision to move forward—did you name what it would actually require, or did you name what you hoped it would require?

• When things get hard, what’s in place to carry the team through, beyond the plan itself?

• And is there something about what’s being left behind that hasn’t been fully acknowledged yet?

It’s not about perfect answers. The questions are worth asking privately and out loud.

This week’s reflection: Your team agreed. The need is clear. So, what’s actually in the way?

If you’re sitting with that question right now, it may be worth exploring what’s underneath the stalled movement—not just the plan itself.

If you’d like to talk it through, feel free to reach out or schedule a discovery call.