Compliance Cannot Carry Commitment | Goggans Consulting
I have watched leaders try to create commitment by asking for more effort from a system that is already tired.
People still have to do the work. Standards still matter. Deadlines still matter. I do not believe a leader can abandon the baseline just because people are under pressure. There are moments when the responsible thing is to clarify the expectation, name the gap, and hold the line.
But I also think there is a limit to what compliance can carry. Compliance cannot create commitment by itself.
Compliance can help people meet the minimum standard. It creates structure, protects the business from chaos, and helps the necessary work stay necessary. I do not see compliance as the enemy. In my work, I describe compliance as the foundation. It is the baseline and the guardrails. The distinction that matters for leadership is this: compliance is structural. It is not motivational.
That distinction is easy to understand and hard to lead from.
When performance is slipping, the visible problem usually looks behavioral. One person looks disengaged. Another is not taking ownership. A third follows instructions without bringing judgment or ownership to the work. Someone else has stopped bringing ideas forward. The body is in the meeting, but the person is absent from the work.
So the leader presses harder.
The response becomes more reminders, more check-ins, more accountability language, and more conversations about attitude, ownership, urgency, or commitment.
Some of that may be necessary. A leader who never reinforces a standard does not really have one. But if the only leadership tool available is more pressure on the visible behavior, I think the organization may be trying to get commitment from a structure that can only produce compliance.
That is where effort stops being enough.
The leadership development problem is not a lack of activity
Organizations are not ignoring leadership development. Many are spending money, running programs, buying platforms, scheduling workshops, and sending managers through training. The activity is there.
The results are less convincing.
McKinsey's article "What's missing in leadership development?" reported that only 11 percent of more than 500 executives strongly agreed that their leadership-development interventions achieve and sustain the desired results. The same article points to several conditions that matter, including context, transfer of learning, and system reinforcement.
That should give leaders pause.
Not because McKinsey has the final word on leadership. It does not. But the finding names a friction I hear often: leadership development can look busy while daily leadership practice remains unchanged.
A person attends the session, agrees with the material, and returns to the same calendar, same pressure, same incentives, same unclear authority, and same habits. The program may have been useful. The environment may still be stronger.
The manager layer carries the daily signal
Gallup makes the manager layer even harder to ignore. In "Why Managers Need Leadership Development Too", Gallup notes that managers influence 70 percent of a team's engagement and that many organizations underinvest in manager development. It also reports that only a little more than one in three managers understand how their performance affects their opportunities to move into leadership roles, and only 8 percent strongly agree their performance reviews inspire them to improve.
Those numbers matter because the manager is often where aspiration meets daily reality.
Senior leaders may write the strategy. The all-hands meeting may name the values. HR may build the development program. But the manager shapes the daily experience of work: what they clarify, what they ignore, what they reward, what they coach, what they protect, and what they make meaningful.
If that layer operates only through compliance, I do not think the organization should be surprised when people give compliant effort without deeper commitment.
Commitment starts with a different question
Compliance starts with this question: "What is required?"
That question matters. People need to know what the job demands. Teams need shared standards. Organizations need baseline expectations that do not shift with every mood or preference.
But commitment asks a different question.
Commitment asks, "Why does this matter enough for me to bring more of myself to it?"
That is not a sentimental question. It is a practical one.
A person may comply because the job requires it. They may commit because the work connects to something they want to become, build, contribute to, master, or protect. That does not mean every task will feel inspiring. Most real work includes ordinary, repetitive, inconvenient, and frustrating parts. Commitment does not remove those parts.
It gives them a place to land.
This is one reason my Aspiration Advantage work keeps returning to aspiration before behavior. If all I know about a person is the behavior I want corrected, I will probably lead through correction. If I understand what that person wants, why it matters, and what they believe is standing between them and that future, I have a different kind of leadership conversation available.
The standard still matters
That does not make the standard disappear. A different connection changes how the standard lands.
When I talk about the leadership shift from directing to discovering, the questions are plain: "What do you need from me to be successful?" "What do you want from your career?" "Why do you want it?" "Why don't you have it yet?"
Those are not soft questions. They are diagnostic questions.
They help a leader find out whether the issue is skill, confidence, clarity, belief, support, aspiration, trust, or something else. They can also help the person hear the daily work differently. A task that felt like a requirement may become practice for a capability they actually want.
That is a different kind of energy.
Daily work has to become relatable to commitment
One of the more useful distinctions in my material is the adjustment to SMART goals. I do not throw structure away. I question when leaders bring in structure too early and what they attach it to.
In the DUMB Leadership Labsâ„¢, aspiration comes before method. DUMB is Dream-Driven, Uplifting, Method-Neutral, and Big and Bold. The point is not to make the person reckless. The point is to stop shrinking the aspiration around the person's current self-image before the aspiration has had a chance to do any developmental work.
After that, structure becomes useful again.
I also talk about making the daily goal relatable to the person's larger aspiration. Anything in the daily goal has to be relatable to the aspirational goal. The leadership move sounds like this: "The way you show up in this task that we have to do every single day, this is going to help you get to where you want to go."
Relatable does not mean easy
That is a subtle shift, but it changes the conversation.
The leader is no longer saying, "Do this because I told you." The leader is also not saying, "Only do the work that feels personally meaningful to you." Both extremes miss the point.
The better move is to connect necessary work to development the person can recognize.
For the person who wants to lead people, follow-through on a boring operational task may become practice in reliability. A move into client-facing work might make a difficult internal conversation practice in listening under pressure. Someone who wants to build a business someday may need to document a process because transferable knowledge matters outside the current role too.
The task is still the task. The standard is still the standard. Meaning changes when the person can see how the work relates to who they are trying to become.
That is not manipulation if it is honest.
It becomes manipulation when the leader pretends every organizational need is secretly the employee's dream. People can feel that. They know when a leader uses aspiration language to dress up extra labor. The connection has to be real enough for the person to recognize it, question it, and own it.
A leader cannot demand commitment into existence
This is where a lot of leadership language gets sloppy.
Leaders say they want ownership, but what they often mean is, "I want people to care about this as much as I do, without needing me to keep reminding them."
That may be a fair desire. Carrying all the energy for a team exhausts people. A leader can quickly grow frustrated when every improvement depends on their push.
But ownership does not usually appear because a leader demanded more ownership. Using the word commitment more often does not create commitment.
Commitment grows when a person begins to see the work as connected to a direction they have accepted as their own.
That does not mean the organization has to become an individual fulfillment machine. The business still has a mission, constraints, customers, financial realities, and standards. Individual aspiration and organizational aspiration are not the same thing.
The leadership question is whether they can occupy enough shared space for the person to bring more than minimum effort.
That shared space is where my Aspiration Advantage work lives. It is concerned with the relationship between what the organization is trying to accomplish and what the people inside the organization aspire toward. When leaders treat those as unrelated, they end up relying on pressure, perks, slogans, or compliance systems to close the gap.
Sometimes those tools produce motion.
They do not necessarily produce alignment.
The leader also has to grow
There is one part of this conversation that leaders may not enjoy.
If a leader wants people to connect work to aspiration, the leader has to do some version of that work too.
I cannot expect the growth in my team to have this aspirational advantage if I do not have that myself. If I shrink, my team shrinks. If I expand, my team expands.
A leader does not have to be endlessly confident or personally transformed before helping anyone else. Still, the leader cannot hide behind development language while avoiding their own identity gap.
A leader who has stopped growing usually turns development into supervision.
They may still run the meeting, inspect the metrics, and hold people accountable. But if they are not also examining their own aspiration, assumptions, fears, and patterns, the ceiling becomes visible. People learn what kind of growth is actually safe from the leader's own example.
This is especially important in mid-market organizations where managers are close enough to the work that their patterns spread quickly. People do not only listen to the leadership message. They watch the leader's range.
Does the leader invite development but avoid feedback?
When people stretch, does the leader punish the mistakes that come with stretching?
Do leaders discuss aspiration in one setting while every real conversation returns to short-term output?
Is the leader asking for commitment while creating room only for compliance?
Those questions are uncomfortable because they move the issue from "How do I get them to try harder?" to "What kind of environment am I asking effort to survive in?"
A better commitment question than effort
Effort still matters. There is no serious leadership practice where effort becomes irrelevant.
But effort by itself is a poor diagnostic. One person may be trying hard in the wrong direction. A team can burn energy against misalignment. A manager may use all their effort to keep a shaky system moving. An employee may comply exactly as required and still be nowhere near committed.
The better question is not simply, "Are they trying hard enough?"
A better question asks, "What is this effort connected to?"
If the answer is only fear, pressure, approval, habit, or avoidance, the leader has information. If the answer is aspiration, identity, development, contribution, commitment, and a believable path forward, the leader has a different kind of energy to work with.
Compliance can hold the baseline.
It cannot carry the whole weight of commitment.
Leaders who understand that do not abandon standards. They stop pretending standards are enough by themselves. They begin doing the harder work of discovering what people want, why it matters, what they believe is in the way, and how today's work can become part of who they are becoming.
That is slower than another reminder.
That also moves closer to the work leadership was supposed to do in the first place.
