Why Your Team Won't Follow the Standards You Set

You set a standard. You explained it in a meeting, everyone nodded, and for a week or two the team kept to it. Then, quietly, they drifted back to how they worked before. If that's a pattern you keep living, the reason usually isn't that your people don't care or won't listen. It's more specific than that, and once you see it, it works in your favor.

Here's why the standards you set don't stick, and what actually makes them real.

Why won't my team follow the standard I set?

Because your team learns how to behave from watching what you do, not from what you announce. You can write a standard and say it clearly, and the team will still take its real cue from your actions, especially in a hard moment.

Picture a standard like "we make decisions at the level closest to the work." You say it, you mean it. Then a tense week hits, a decision comes up, and you step in and make the decision yourself to save time. Nobody says anything, but the team just learned something: the standard is real when things are calm, and optional when they're not. They learned that faster than they learned the words, because a hard moment teaches louder than a meeting.

That's the catch with leadership. You're always teaching the team how to behave, every day, through what you do. The only question is whether you chose the lesson.

You're always modeling something

This is the part most leaders miss. It isn't that you sometimes model behavior and sometimes don't. You're modeling something all the time, whether you picked it or not. Your team watches how you run a meeting, how you handle bad news, whether you do the thing you asked them to do when it's inconvenient. All of it teaches.

So a standard the team sees you break under pressure isn't neutral. It actively teaches the opposite of what you wrote. The good news is that this works both ways: when the team sees you keep a standard in exactly the moment it would be easy to drop it, that teaches too, and it teaches more than any handbook.

Why does repeating it louder not work?

When a standard doesn't stick, the instinct is to say it again, more firmly, maybe add a policy. But repetition of the words isn't the problem, because the team already heard the words. What they're waiting to see is whether the words match your own behavior when it counts.

More announcements without matching action actually widens the gap, because now there's an even clearer standard on record that the team has watched you set aside. The fix isn't louder communication. It's showing the standard in what you do, first and consistently.

The fix: pick two or three behaviors and go first

You can't model everything at once, and you don't need to. Pick the two or three behaviors that matter most for how you want the team to work, and commit to living them yourself, on purpose, before you ask anyone else to.

Two or three is the right number, because a short list you actually keep to teaches more than a long list you can't. And they should be behaviors, not ideals: "I make a decision within a day of having what I need, or I say when I'll decide," not "I'm more decisive." The team can copy an action. They can't copy a good intention.

What does "going first" look like?

You live each behavior in your own work for about thirty days before you ask the team to pick it up. In that window, your only job is to be consistent, because consistency is what tells the team the standard is real. A few simple habits keep you honest: use the behavior every day, name it out loud at least once a day so the language spreads, meet the same expectation you ask of others, and keep it especially when the week gets tight, because that's when the team is watching most closely.

Expect some early friction. When people slow down or ask clarifying questions in the first couple of weeks, that isn't resistance, it's a sign the standard is taking hold. By about day thirty, the team tends to use it without being prompted, even in a hard week, because they've watched you do the same.

A quick example of modeling one behavior

Say you want the team to raise problems earlier, while they're still small. The announced version is "be more proactive," which gives no one anything to do. The modeled version is a specific behavior you go first on: in your own updates, you name one risk you're watching before anyone asks about it, every week, out loud. You do it when things are calm, and you do it when the week is ugly and you'd rather not.

For the first few weeks, not much visibly changes. Then someone on the team names a risk early in a meeting, the way they've watched you do it, and no one treats it as bad news. That's the behavior spreading, and it spread because they saw you do it consistently, not because you asked them to.

What changes when you go first

Modeling on purpose changes two things at once. The standard finally sticks, because the team has watched you keep it through a hard week, which is the only proof they actually trust. And the way you spend your own attention shifts, because instead of repeating standards that fade, you set them once in your own behavior and let the team copy what they see. It's slower for a month, and far less tiring after that.

Choose the behaviors worth copying

If the standards you set keep fading, the fix is to model two or three of them on purpose. Our free Leadership Modeling Reference Card gives you the four rules for choosing a behavior worth copying, a daily check for your first thirty days, and space to name your two or three.

→ Download the free Leadership Modeling Reference Card: loyaltyops.com/leadership-modeling

FAQ

Why won't my team follow the standards I set?

Usually because they take their real cue from what you do, not what you announce. If a standard gets dropped the moment a week gets tight, the team learns it's optional. Standards stick when the leader models them consistently, especially under pressure.

How do I make a new standard stick?

Model it yourself first. Pick two or three specific behaviors, live them in your own work for about thirty days before asking the team to, and keep them especially when it's inconvenient. Consistency from you is what tells the team the standard is real.

Is my team resisting me, or is something else going on?

Usually something else. When capable people drift back to old habits, it's rarely defiance; it's that the new standard wasn't yet modeled long enough or consistently enough to trust. The fix is on the leader's side, and it's doable.

Why do new behaviors fade after a few weeks?

Because the behavior was announced but not modeled through a hard moment yet. The team waits to see what happens under pressure. Once they watch you keep the standard when it's costly, it starts to take hold.

How long does it take for a standard to take hold?

About thirty days of the leader modeling it consistently. Early friction, like slowdowns and clarifying questions, is a normal sign it's working, and by around day thirty the team tends to use it without being prompted.