Instruction Audit: Why Your Organization Gets the Behavior It Instructs
I have watched leaders stare at a problem and ask the same question enough times that I can finish the sentence before they do.
“Why won’t they do what we asked them to do?”
Across boardrooms, team meetings, and one-on-one conversations, the same frustration surfaces. The Instruction Audit, one of the core frameworks I use in my work with organizations, gets underneath that frustration by asking a different question.
What have we actually instructed them to do?
Not what we said. Not what we put in the memo, on the slide deck, or in the all-hands meeting. The real instruction lives in what the system rewarded, tolerated, ignored, and taught people to learn from watching what happened to someone else.
The premise of the Instruction Audit is simple: people may be responding exactly as the leadership environment has trained them to respond, even when leadership hates the result.
A Team I Inherited
A few years ago, I took over a team that had landed on a corrective action notice. The company was close to losing that line of business entirely.
When I looked at what was actually happening, the problem had very little to do with competence. The team was not incompetent. They were not indifferent. Their operating environment had taught them something very specific: do what you are told, do not deviate, and above all, do not get noticed for the wrong reasons.
Nobody had ever spoken those words out loud. But the previous leadership had rewarded compliance, punished initiative, and treated questions like insubordination. So the team adapted. Keeping their heads down became instinct. Waiting for direction became the default. Staying invisible felt like the safest move anyone could make.
And then leadership sat confused about why nobody was taking ownership.
The instruction came through loud and clear. It just was not the instruction anyone thought they were giving.
Where the Real Instruction Shows Up
I see this everywhere. In the mid-market technology companies I work with, in teams I have observed, and honestly, in my own leadership when I am not paying close enough attention.
Innovation Meets Self-Protection
A leader says they want innovation. But when someone takes a risk and it does not pan out, that person quietly fades from view. Not fired. Not formally reprimanded. Just removed from the interesting work, passed over for the next opportunity, or left out of the conversations that matter.
What did the organization just teach everyone else?
Stay safe.
Innovation is not actually welcome here.
And the thing is, the leader probably means it when they say they want innovation. They really do want new ideas. But they also want those new ideas to work every time, without costing anything or embarrassing anyone.
That is not how innovation works. Most people in the building know that. The system teaches them what the speech does not.
The Trap of Availability
A leader says they want work-life balance. Meanwhile, the person answering emails at ten o’clock at night keeps getting promoted. The person who leaves at five to pick up their kids gets described as “not committed.” The person who takes all their vacation days starts to carry a reputation for not being a team player.
Nobody says any of this in the performance review. But everyone knows.
The instruction is not subtle: availability beats sustainability. Boundaries will cost you.
The Performance of Candor
A leader says they want people to speak up. But the last person who raised a real concern in a meeting heard they were being negative. Not in those words. The leader said something like, “Let’s focus on solutions, not problems,” or “I appreciate the perspective, but let’s stay constructive.”
It sounded reasonable. But every other person in that room heard the signal.
Agreement is safe. Candor is not.
The path forward becomes nodding along and bringing the real concerns up later, privately, with people who already agree with you. The meeting becomes theater. The real conversation happens in the hallway afterward.
Hiring for Comfort, Not Contribution
The same pattern plays out in hiring. An organization says it wants diverse thinking. It says it wants people who will challenge the status quo.
But when the interview process actually runs, the candidates who get hired are the ones who made everyone feel comfortable. The ones who did not push back. The ones who fit.
The organization hires for cultural alignment, not cultural contribution, and then wonders why every new hire looks and thinks like the people they already had.
The instruction was clear: conformity gets the offer. Difference gets the polite rejection email.
The Feedback That Never Reaches the Top
Feedback systems reveal the same dynamic.
An organization rolls out a 360-review process and announces that feedback matters, that candor drives improvement, and that continuous learning defines the culture. But when someone gives honest upward feedback about their manager, and that manager’s next move is defensiveness, the system teaches everyone something.
Downward candor is leadership. Upward candor is career risk.
The review process itself becomes a compliance exercise. People fill out the forms. They say what is expected. And the organization loses the very information it claimed to want.
None of these instructions were written down. They were never stated. But they traveled through the organization with perfect clarity.
The System Beneath the Speech
You can change the language on the wall. You can rewrite the mission statement. You can give the quarterly kickoff speech with more conviction.
But if the underlying system is teaching something different, the speech becomes decoration. The organization will keep doing what the organization is built to do.
The Instruction Audit is not just about what the system is doing. It is about what the system is doing to the person receiving the instruction.
That is where the work gets more honest.
How Belief Interprets the Instruction
Here is how I think about it.
An instruction comes in. A person hears it consciously. They process it in their thinking mind.
“They say they want innovation.”
“They say they want candor.”
“They say they want work-life balance.”
That conscious thought is real. But before that thought becomes action, it passes through something else. It passes through belief.
Belief acts as an interpreter. It does not just receive the instruction. It translates it.
And here is what matters: that belief might have nothing to do with the current environment. Someone might have walked into your organization already believing that authority figures are not safe, that speaking up gets you punished, or that the way to survive is to keep your head down.
They did not learn that from you. They brought it with them.
When the Environment Validates the Belief
The Instruction Audit becomes critical at exactly this point.
The current environment can either challenge that belief or reinforce it. If someone arrives already believing that initiative is dangerous, and then they watch the first person who takes a risk get quietly sidelined, the belief is not just confirmed. It is cemented.
The environment did not create the belief, but it validated it. It told the person, “You were right to be afraid.”
That is the moment the belief becomes the organization’s problem. Not because the organization caused it, but because the organization’s behavior made it true here.
The belief, wherever it came from, triggers an emotional response. Fear. Anxiety. Resignation. Then that emotion drives the behavior. Not the original instruction. The filtered version. The version that survived the belief check.
This is closely connected to where performance is actually decided. Performance does not begin at the visible behavior. It often begins in the space between what was said, what was believed, and what the person decided was safe to do next.
Why Clearer Instructions Will Not Fix It
Then behavior produces results. The results reinforce the belief. The belief strengthens. The loop closes. The organization gets the behavior, and the behavior keeps confirming the belief that produced it.
Most leaders miss this entirely.
Clearer instructions will not change the behavior. Saying the same thing louder will not change it. You have to find the belief that is interpreting the instruction.
You have to ask: what does this person believe is actually true here?
And you have to be willing to look at whether your environment is reinforcing a belief someone brought in the door, or worse, whether your behavior is creating new beliefs that work against everything you say you want.
An organization that says it wants ownership but has people who believe initiative is dangerous will not get ownership. The belief is stronger than the speech. Unless you uncover it and address it, the instruction will never reach behavior the way you intended.
That is why Instruction Audit work sits so close to Leader of One. Leadership begins with the individual, but the individual is always operating inside a system of signals, expectations, consequences, and beliefs.
How to Conduct an Instruction Audit
Knowing what an Instruction Audit is matters less than knowing how to run one.
Start with a simple question: what do people actually learn to do here?
Not what the handbook says. Not what leadership intends. What the environment itself teaches every day through what it rewards, what it punishes, and what it quietly allows.
Sit down with a notebook and ask yourself a handful of questions. Be honest. This only works if you are.
The Promotion Question
Who receives the promotion, and why?
Do not start with the official criteria. Look at the last five people who moved up. What did they actually have in common?
Were they the ones who took risks, or the ones who managed risk? The ones who spoke hard truths, or the ones who supported the current direction? The ones who delivered results at any cost, or the ones who delivered results while protecting the team?
Whatever those five people share, that is your real promotion criterion. Everything else is language.
The Failure Question
What happens when someone fails?
Not catastrophic failure. Just a project that did not go well, a target they missed, or a decision that turned out wrong.
Does that person receive support and development, or does their influence shrink? Do people talk openly about what they learned, or does the person quietly disappear from visible work?
The answer to this question reveals the organization’s actual stance on risk.
The Tolerance Question
What behavior persists that should not?
Every organization has conduct that everyone knows is a problem but nobody addresses. The senior leader who belittles people in meetings but drives results. The manager who takes credit for their team’s work. The person who has coasted for years and nobody will confront.
Whatever you tolerate, you instruct.
If the behavior continues without consequence, you have told everyone that it is acceptable. Not in words. In the only language that counts.
The Meeting-and-Hallway Question
What surfaces openly, and what only surfaces in the hallway?
Pay attention to the gap between what people say in meetings and what they say afterward. If the real conversation consistently happens after the official conversation ends, you have a meeting culture problem. More than that, you may have a safety problem.
People are telling you, with their behavior, that the room is not safe for honesty.
Listen to that.
After the Audit
Once you have answered these questions honestly, you will have a list.
It will not be comfortable. Some of it will sting. But that list is your Instruction Audit. It tells you what your organization is actually reinforcing.
Not what you intended. Not what sounds good. What is.
The next step is the hardest one. Pick one thing on that list and change it.
Not all of them. One.
If promotion rewards availability over sustainability, change what you celebrate. If failure gets punished instead of learned from, model something different the next time a project goes sideways. If candor is unsafe, ask a hard question in a meeting and actually listen to the answer without defending yourself.
The system will not change because you announced a new value. It will change because you started reinforcing something different, consistently, over time.
This is also why the Instruction Audit belongs inside the larger work of DUMB Leadership Labs™. The Labs are not about giving leaders another slogan. They are about helping leaders examine the instructions, beliefs, aspirations, and behaviors that are already shaping performance, often before anyone names them.
What the Audit Taught Me
The Instruction Audit is about looking at the real code of the organization. It means getting honest about what the organization is actually reinforcing, not what it claims to want.
That honesty is harder than it sounds, because most leaders genuinely believe they are communicating one thing while their systems are communicating something else.
I have been that leader.
I have caught myself reinforcing things I claimed to oppose. Not because I was insincere. Because I had not stopped to look at what my own behavior and my own systems were actually teaching.
It is humbling. But it is also where the work starts.
The question that changed things for me was not, “How do I get people to do what I say?”
It was, “What have I actually been instructing them?”
Because once you see the instruction, you can change it. Start rewarding what you say you value. Stop tolerating what you say you oppose. Bring what the system does into alignment with what the mission board claims.
That same distinction shows up in the way leaders set goals. SMART goals can fail without DUMB goals because execution alone cannot fix a direction people do not believe in, do not own, or do not understand. The instruction underneath the goal still matters.
But you have to do the audit first.
Look at what people actually receive as instruction. Not what ought to be. Not what was intended. Not what sounds good in the strategy document.
What matters is what is.
If your organization keeps producing behavior you say you do not want, the odds are good that somewhere, somehow, you instructed it.
The question is whether you are willing to look.
If Something Is Not Translating, Start There
If you can feel the gap between what leadership says and what people actually do, do not start by assuming people are lazy, resistant, or careless. Start by examining the instruction they have actually received.
That is the bridge between the Instruction Audit and the practical work of DUMB Leadership Labs. Leaders need space to examine what they are reinforcing, what their people are believing, and where the system has drifted away from what they say they want.
The Leadership Friction Snapshot is a simple place to begin. Ten questions about one leadership situation you are navigating. Free. Private. Not a newsletter.