Skip to main content

Compliancy vs Commitment

I don't see criticism and (a certain level of) conflict as unhealthy in an organization. The contrary! It is when people stop raising their voice and sharing their feedback that you need to start worrying. It could be a sign that people no longer care and have decayed from commitment to compliance.

Beyond following orders

As leaders we are constantly seeking ways to drive results. But there's a fundamental distinction worth understanding on how to achieve this: 

If we collaborate, the result is commitment. If we coerce, the result is compliance.

Commitment comes from within, whereas compliance is forced by an external source. When people comply, they're simply following orders. They do just enough to get by, meet the bare minimum requirements, or check the box. There's no personal investment in the outcome.

Commitment, on the other hand, invites full participation, engagement, and discretionary effort.

The language of Commitment

L. David Marquet states in his book ‘‘Leadership is language’ that our language reflects and reinforces this distinction in powerful ways. In the book he gives the example on how you talk to yourself when trying to change a habit

  • "I can't eat sweets" (compliance) vs. "I don't eat sweets" (commitment)
  • "I can't miss this deadline" vs. "I don't miss deadlines"
  • "I can't spend my time that way" vs. "I don't spend my time that way"

The word "can't" suggests an external restriction—something is preventing you from doing what you actually want to do. "Don't," however, reflects an internal choice and identity. You're the kind of person who doesn't do that thing. This subtle shift in language creates a remarkable difference in results.

Choice: The foundation of commitment

For commitment to exist, there must first be choice.

If a person has no choice but to say yes, then what we have is compliance. 

This explains why common workplace initiatives to "inspire" and "empower" employees often fall flat—if people don't genuinely feel they have a choice, their response will be compliance at best.

Compliance also:

  • Gives people a pass on thinking
  • Removes personal responsibility ("I was just following orders")
  • Creates fragile operations due to lack of context

Building a culture of commitment

The key is creating conditions where people can make genuine commitments rather than merely complying with directives.

How can we foster commitment rather than settling for compliance?

  1. Provide context, not just directives. When people understand the "why" behind a request, they're more likely to commit.
  2. Create genuine choice. Even when options are limited, finding ways to give people some agency in how they approach their work fosters commitment.
  3. Use the language of commitment. Pay attention to how requests are framed and how decisions are discussed.
  4. Recognize that commitment is personal. Groups don't make commitments—individuals do. Honor the personal nature of commitment.

So the next time you're facing resistance or lackluster results, ask yourself: Am I seeking compliance or commitment? The answer might reveal exactly why you're not getting the engagement you desire.

More information

Discontinuous improvement

Appreciate, don’t evaluate

Trust & Inspire instead of Command & Control

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

.NET 9 - Goodbye sln!

Although the csproj file evolved and simplified a lot over time, the Visual Studio solution file (.sln) remained an ugly file format full of magic GUIDs. With the latest .NET 9 SDK(9.0.200), we finally got an alternative; a new XML-based solution file(.slnx) got introduced in preview. So say goodbye to this ugly sln file: And meet his better looking slnx brother instead: To use this feature we first have to enable it: Go to Tools -> Options -> Environment -> Preview Features Check the checkbox next to Use Solution File Persistence Model Now we can migrate an existing sln file to slnx using the following command: dotnet sln migrate AICalculator.sln .slnx file D:\Projects\Test\AICalculator\AICalculator.slnx generated. Or create a new Visual Studio solution using the slnx format: dotnet new sln --format slnx The template "Solution File" was created successfully. The new format is not yet recognized by VSCode but it does work in Jetbr...