What Commitment Actually Looks Like

Stop aiming for buy-in, it's the wrong goal. Here's what to aim for instead, and how you know when you have it.

Keith Laplante

Thirty-five years leading inside organizations (TD Waterhouse, BMO, HomeEquity Bank) and advising alongside them (Accenture, ExperiencePoint, The Refinery Leadership Partners). Facilitated leadership programs at Harvard, Duke, and Stanford. Read more about Keith

"Buy-in is a transaction. Commitment is a stance."

Over the past twelve weeks, I've written eleven articles about leading change. About why people aren't really resistant, they're loss averse. About the performance dip that derails most initiatives. About how organizations quietly teach their people to wait things out. About the difference between compliance and commitment, and why leaders so often mistake one for the other.

I want to close the series by putting all of that in one place, and by making the case for something many leaders don't realize they should be aiming for.

Stop trying to build buy-in.

It's the wrong goal. And I think chasing it is one of the reasons so many well-intentioned change initiatives produce mediocre, short-lived, disappointing results.

What buy-in actually is

Buy-in is a form of agreement. It's what leaders get when they've made a case, answered the objections, and secured the willingness of their people to go along with what's being proposed. It sounds like consent. It looks like alignment. And it's what most change communication is designed to produce.

The problem with buy-in is that it's a permission structure, not an engagement structure. It gets you people who won't openly oppose the change. It doesn't get you people who'll actively shape it, own its success, or push through the inevitable moments when it would be easier to quietly disengage.

I've watched leaders declare victory when they've secured buy-in and then be genuinely puzzled when the change initiative underperforms. The buy-in was real. The compliance was real. The metrics indicated adoption was happening. And yet the results never quite materialized the way they were supposed to.

What was missing was the thing buy-in was standing in for. Commitment.

What commitment actually is

Commitment is different in kind, not just in degree. It's not agreement plus enthusiasm. It's something else entirely.

Committed people don't need to be sold on the change. They're not agreeing to something someone else has designed. They've either helped design it themselves, or they've engaged with it deeply enough that they've made it their own. They understand not just what's being asked but why, and they've done the work of connecting the change to something they care about.

That connection is what produces the behaviour compliance can't. Committed people apply the change even when nobody's watching. They surface problems early because they want the change to succeed. They ask hard questions because they're invested in getting it right. They advocate for it with others, not because they've been asked to, but because they believe in it. And when the inevitable hard moments come, they push through them, because their motivation isn't external.

None of this shows up in the buy-in framework. Buy-in is a transaction. Commitment is a stance.

The forms of compliance we mistake for commitment

Across the earlier articles in this series, I've named several forms of compliance that look enough like commitment to fool experienced leaders.

There's technical compliance. People do what's required, use the new system, complete the training, hit the metrics, and nothing more. The moment the measurement stops, so does the behaviour.

There's the shadow spreadsheet version. People appear to be using the new system while quietly doing the real work somewhere else. The dashboards look good. Underneath, nothing has actually changed.

There's blind compliance. The most dangerous form. People agree, sometimes with genuine enthusiasm, because their loyalty to the leader has quietly displaced their willingness to challenge. Everyone nods. Nobody says the difficult thing. The change proceeds, unopposed and unimproved by the honest input that would have made it stronger.

There's the wait-it-out version. Experienced employees who've watched enough initiatives come and go to know that the smartest response to a change announcement is to do nothing. They don't resist. They just outlast.

Each of these can be mistaken for commitment if the leader isn't looking closely. And each of them, once it takes hold, quietly ensures the change won't produce what it was designed to produce.

What commitment produces

I want to be specific about the difference commitment actually makes, because it's easy to talk about this in abstract terms without being clear about what's at stake.

In one of the earlier articles in this series, I told the story of a team that went from third quartile performance to number one in the country in six months and stayed there for two years. That result didn't come from a compliance push. It came because the team, once we understood the real problem together, helped design the solution. They weren't executing someone else's plan. They were living inside their own.

In another article, I told the story of a small team's counter-strategic initiative that produced four times the expected growth in a single year and then spread across the organization on its own because other regions saw the results and started building their own versions. Nobody pushed adoption. Nobody managed the change. The initiative spread because it was working, and because the people encountering it recognized something they'd been waiting for.

Both of those outcomes are what commitment produces. Not incremental improvements. Not modest lifts. Dramatic, sustained, self-reinforcing results that most compliance-driven initiatives can't come close to.

The gap between what buy-in gets you and what commitment gets you isn't small. It's the difference between change that transforms an organization and change that just exhausts it.

How you know when you have commitment

Commitment can be hard to see from a leadership vantage point, especially in the early stages when it's still forming. But there are signals worth paying attention to.

Committed people ask hard questions. They probe assumptions. They surface edge cases. They push back on parts of the plan that don't make sense to them. If your change rollout feels suspiciously smooth, with very few difficult conversations, that's not a sign that things are going well. That's a sign people have decided the conversation isn't worth having.

Committed people surface problems early. They tell you when something isn't working, when a piece of the plan isn't landing, when there's friction in the system you haven't seen. They don't hide issues. They don't wait for the postmortem. They act like people invested in the outcome, because they are.

Committed people apply the change without being watched. They use the new system when the old one would be faster. They follow the new process when nobody would notice if they didn't. Compliance stops the moment the measurement does. Commitment doesn't.

And committed people become advocates. They bring others with them. Not because they've been asked to, but because they believe in where things are going. That advocacy is what turns individual commitment into organizational momentum, and it's the thing compliance can never produce.

What it takes to build commitment

There isn't a formula for this. But every one of the articles in this series has pointed at some piece of what it requires.

It requires understanding that your people are loss-averse rather than resistant and engaging with what they think they're going to lose before you try to sell them on what they might gain.

It requires naming the hard parts of the change in advance, so nobody experiences the predictable difficult moments as evidence that the change is failing.

It requires resisting the temptation to declare victory when you've secured compliance. The dashboards look good. The metrics are moving. And that's not the same as the change actually taking hold.

It requires diagnosing the real problem before launching the change, rather than acting on the surface story of what looks wrong.

It requires bringing your people into shaping the solution, not just informing them of the decision. Change done by them lasts. Change done to them doesn't.

It requires speaking to both halves of the room, the ones who move toward opportunity and the ones who move away from threat. Neither framing alone reaches the whole audience.

And it requires the discipline, when the inevitable hard moments come, to hold your nerve. To resist the urge to tighten controls, apply pressure, or reverse course. To trust that the change will take, if you've done the work of building the commitment underneath it.

The final thought

Twelve articles ago, I made a claim that some readers found provocative and others found uncomfortable. Your people are not the problem. How you lead them through change very often is.

I want to close by extending that claim in one direction.

Your people are also not the ceiling. What they're capable of, when they're genuinely committed to a change rather than merely compliant with it, is dramatically more than what most organizations ever get from them. The teams that go from third quartile to number one. The initiatives that spread on their own because they're too good to ignore. The transformations that hold, long after leadership has moved on to the next thing.

All of that is available to you. But it doesn't come from buy-in.

It comes from commitment. And commitment has to be earned, not requested.

The change you're leading is almost certainly better than what came before. That's not the question. The question is whether the people you're leading will bring their full selves to it or will simply comply with it and wait to see what happens next.

That answer is up to you.

Stop aiming for buy-in.

Aim higher.