When Silence Becomes the Standard

What did I do wrong?

Not because the presentation had gone poorly. Because by that point in my career, I’d gotten used to silence. If I was doing my job, nobody called. Nobody debriefed. Nobody told me what had worked or where I could be better.

The unspoken assumption was simple: If there was a problem, I’d hear about it. Otherwise, I’d keep going.

So, when my phone rang after an important client meeting, I instantly assumed something must have gone wrong. Instead, he spent a few minutes telling me what worked and pointing out one opportunity I’d missed to show up more like a trusted advisor.

Then we moved on.

He did it again after another important meeting. And another. It took me a few rounds for my brain to realize that I wasn’t getting more criticism.

I was getting more calibration.

He wasn’t waiting for issues to arise. He was helping me understand where the standard was while the experience was still fresh. And I’d clearly gotten completely out of practice with that.

Looking back, I think I confused silence with certainty. Silence told me I wasn’t failing. Silence told me I wasn’t in trouble. Silence told me I was producing acceptable results. But acceptable isn’t the same thing as clarity.

I knew I wasn’t failing. What I didn’t know was whether I was growing. Silence told me I wasn’t failing – but it also didn’t tell me whether I was getting better.

At one point, I spent nearly a year without a manager, continued delivering, and even earned a promotion. By every visible measure, I was succeeding. But I was also carrying around a surprising amount of uncertainty. There was a constant, low-level question running underneath all that autonomy: Am I actually doing this right?

I knew I could do the work. The question was whether I was operating at the standard expected of me.

• Was I making good judgment calls?
• Was there a better way?
• Was I growing?
• Or was I simply avoiding mistakes?

And living in that uncertainty is stressful.

When people don’t know where the guardrails are, they have to assess the risk themselves.

• Was that okay?
• Did I push too far?
• Is no news actually good news?
• What happens when I finally cross a line I didn’t know was there?

Do that long enough and you’ve created more than a feedback gap – you’ve created a culture where people can perform well and still operate in a persistent state of uncertainty.

That’s not psychological safety. Because psychological safety isn’t simply the absence of criticism, it’s confidence that you understand what’s expected of you. That’s the paradox I’ve started thinking about: Micromanagement gives people too little trust. But autonomy without reinforcement can create so much uncertainty that people end up carrying the burden of constant self-calibration and slow or cease growing.

The best leaders I’ve worked with sit somewhere in between. They give you room to operate, but they don’t make you guess where the guardrails are.

The restaurant insight isn’t more feedback. It’s faster reinforcement.

Before consulting, I spent nearly two decades in restaurant operations. Looking back, I don’t think we reinforced behavior constantly because restaurants had somehow cracked the code on employee development. We did it because we were responsible for maintaining a standard.

• Guest experience.
• Food quality.
• Cleanliness.
• Labor.
• Culture.

And reinforcement has a shelf life.

If I watched a manager mishandle a guest interaction, waiting until our next one-on-one a few weeks later, or worse, the next review cycle to address it would have been almost useless. By then, they might have handled another hundred guest interactions the same way.

The behavior didn’t need feedback eventually. It needed reinforcement now.

The same was true when someone did something exceptionally well. I wanted them to know right then: That’s the standard. Do that again. The correction didn’t need to become a coaching session.

“Next time, try this.” The recognition didn’t need to be elaborate.

“Exactly. That’s what I was looking for.” Then we moved on.

If the same issue kept appearing, that deserved a bigger conversation. Now we had a pattern worth understanding.

Correct the moment. Coach the pattern.

Somewhere in my transition to Corporate America, I realized those two things often get collapsed into one. We treat every piece of corrective input like feedback. Something that needs context, explanation, reflection, and sometimes even a scheduled conversation. But sometimes a behavior doesn’t need feedback yet. It needs reinforcement.

Feedback and reinforcement aren’t the same thing. Feedback helps someone understand a behavior. Reinforcement helps shape it.

Feedback asks: What happened? Why? What can we learn from it?

Reinforcement says: Yes. Do that again. Or: No. Try this instead.

You could argue reinforcement is simply a type of feedback. Maybe it is. But I think the distinction matters because reinforcement introduces urgency. Feedback can happen later and still create insight. Reinforcement loses value the longer it waits. Both matter, but reinforcement is uniquely dependent on timing. Its value decays the farther it gets from the behavior.

The organization pays a price during that delay.

Every repetition between the behavior and the conversation is another opportunity for uncertainty to grow. Every repetition is another chance for employees to guess. And people rarely stop guessing on their own. They create their own answers.

That’s why silence isn’t neutral.

Every time a leader observes something and chooses not to address it, the employee still learns something: “Apparently, that’s okay.”

Do something once without correction? Maybe nobody noticed. Do it twenty times? You’ve started building a habit. Do it a hundred times? Don’t be surprised when the response is: “But I’ve always done it this way.”

Because at some point, what leadership repeatedly allowed became the standard, regardless of what the official standard said. People don’t rise to the standard that’s documented. They rise to the standard that’s reinforced.

Reinforcement can actually create more autonomy, not less.

This does not mean leaders should narrate every decision an employee makes. Reinforcement isn’t constant commentary. It’s noticing the moments that establish standards and responding while those moments are still meaningful. The goal isn’t to create dependence. The goal is to create clarity.

There’s a big difference between reinforcement and micromanagement. Micromanagement says: “I don’t trust you enough to operate without me.”

Good reinforcement says: “I trust you to operate, and I’m going to make sure you understand the standard.”

That’s what I’ve experienced with my current manager. Because he tells me when I’ve nailed something and when I’ve missed an opportunity, I have a much clearer understanding of where the guardrails are. That lets me push further, not less. I don’t need him making every decision. I need enough information to calibrate my own. And increasingly, I can recognize those moments myself.

Great leaders don’t make people dependent on their feedback. They use reinforcement to teach people how to evaluate themselves. That’s what the best leaders did for me. They reduced uncertainty. They created clarity. And then they gave people room to run.

Change makes the reinforcement gap impossible to ignore.

This is where my restaurant experience and my work in Organizational Change Management collide. During an implementation, we’re intentionally asking people to replace existing behaviors with new ones. We spend enormous amounts of effort defining those behaviors. We communicate them. We demonstrate them. We train them. Then people go back to work.

And that’s where the real work begins.

An employee uses the old process. Their manager sees it and says nothing.

Silent okay.

Another employee struggles through the new process instead of taking the familiar shortcut. Their manager doesn’t acknowledge it.

Missed reinforcement.

Someone tries the new behavior, gets something slightly wrong, and nobody redirects them until weeks later.

Expired reinforcement.

None of those moments are dramatic. That’s exactly why they’re easy to miss. Those moments are where uncertainty either disappears or grows. They’re where employees learn which behaviors truly matter. They’re where the written standard either becomes the operational standard or quietly loses to the old way of working.

The longer a leader waits to reinforce a new behavior, the more opportunities the old behavior has to become the standard again.

The real standard is what leaders reinforce.

A policy can define a standard. Communication can explain a standard. Training can teach a standard. Leaders operationalize the standard through what they notice, what they reinforce, and what they allow – and that has me thinking differently about the role managers play during organizational change.

We often prepare managers to communicate the change. We give them talking points, FAQs, key messages, training. But none of these things determines what happens Monday morning when someone falls back into the old way of working.

Their manager does.

We spend a lot of time preparing managers to communicate change. We spend far less time preparing them to reinforce it. Yet those everyday moments of reinforcement are where uncertainty is reduced, standards become habits, and change either sticks or fades. If managers have that much influence over whether new behaviors stick, why do we spend so little time preparing them for those moments?

More on that next.