Why Your Team Ignores What You Say and Copies What You Do — and Where Your Lever Is

Your team ignores what you say and copies what you do because a team doesn't take its cues from what its owner says, but from what the owner tolerates and does. Culture is the sum of the behaviors that carry no consequences. Your instruction is information. Your behavior is the rule. And when they contradict, the rule always wins.

You say one thing — and your team does another

You know the situation. In the meeting, you said proposals have to go out within 48 hours. Three weeks later, proposals are sitting there for five days again. You said client appointments start on time. They start five minutes late. You said everyone makes their own decisions. The emails asking "How should we handle this?" keep coming anyway.

The obvious explanation: the team isn't listening. Or doesn't care. Or you hired the wrong people. Each of these explanations is convenient, because it places the lever outside of you. And each is wrong — not because your team is flawless, but because they overlook the mechanism by which a team learns.

A team doesn't learn from instructions. It learns by watching. And what it watches is you.

Takeaway: Your team hears what you say. It learns what you do.

What is culture — and why does it form without your input?

The term first. Culture is the sum of the behaviors that carry no consequences in your company. Not what's on the website. Not what you say in the Christmas speech. What happens when someone shows up late, lets a proposal sit, or falls short of a standard — and nothing follows.

Why does culture form without your input? Because people in groups are constantly answering one question: What's normal here? And they don't answer it with rules. They answer it by watching. They see what the boss does. They see what happens when a rule is broken. They see which behavior gets rewarded and which doesn't. From these observations they build a map of what really applies here. That map is the culture. And it gets updated every day, whether you want it to or not. A new hire has it in their head after two weeks without anyone explaining a thing — they just watched what happens here and what goes without consequences. They read your onboarding folder too. But they go by what they've seen.

The pair of opposites that carries this piece: instruction and standard. An instruction is what you demand. A standard is what you enforce — with others and with yourself. A team can forget an instruction. It doesn't forget a standard, because it experiences it every day.

Takeaway: Culture isn't what you announce. Culture is what goes without consequences.

What wins when instruction and behavior contradict each other?

This is where the actual mechanism sits, and it's uncomfortable because it applies without exception.

When your instruction and your behavior match, each reinforces the other. You say "on time", you're on time, the team is on time. When they contradict each other, behavior wins. Every time. Not because the team wants to annoy you, but because behavior carries more information than words. Your instruction says what you'd like. Your behavior says what costs you nothing. And the team goes by what costs nothing.

Add a second factor: a contradiction between instruction and behavior isn't neutral. It doesn't just devalue that one instruction, it devalues every one that follows. If you announce something three times and fail to keep it yourself three times, the team hears your fourth instruction differently. It hears: the boss would like something. It doesn't hear: this applies from now on.

An example I went through myself. I told my team that decisions within their own area were theirs to make — I no longer wanted to be the bottleneck. Two weeks later, someone made a decision I would have made differently. I corrected it. Politely, factually, with reasons. From that day on, the questions came back. Not because the team didn't want to decide. Because it had learned: decisions get corrected here, so you ask first. My instruction had held for two weeks. My correction set the rule.

The same goes for standards. If you say no proposal goes out unchecked, and in a packed week you wave one through without review, the team hasn't learned that there was an exception. It has learned where the line really is: at pressure. And anyone can claim pressure for themselves. From then on, your standard is no longer "reviewed". It's "reviewed when there's time" — and that isn't a standard, it's a statement of intent.

Takeaway: When they contradict, the instruction loses. Without exception.

Where do you model the opposite of what you ask for?

So this doesn't stay abstract, here are the four places where it catches almost every business owner. Check honestly which ones you recognize.

Punctuality. You demand that appointments start on time. You yourself walk into the team meeting three minutes late because a client was still on the phone. The team learns: punctuality applies, unless you have a reason. And everyone has a reason.

Responsiveness. You demand that client inquiries get answered the same day. You yourself often reply to messages from your team only after two days. The team learns: response time is a question of importance, not of rule.

Postponing decisions. You demand fast decisions. The decision on the new price list has been sitting on your desk for six weeks. The team learns: important things can wait if they're difficult.

Standards under pressure. You demand quality. In the week when three projects were due at once, you waved through a half-finished proposal because it had to go out. The team learns: quality applies as long as there's no pressure. And there's almost always pressure.

None of these behaviors is a character flaw. Each had a reason in the moment. But the team doesn't see reasons. It sees behavior. And from behavior it builds the standard.

Takeaway: The team doesn't know your reasons. It only knows your behavior.

What does a single tolerated behavior cost you in a year?

Let's do the math. Not with invented studies, but with a calculation you can plug your own numbers into.

Take a team of five and a single tolerated behavior: proposals don't go out in 48 hours, they go out in five days. Suppose everyone on the team writes two proposals a week. That's ten proposals a week, and in a year with 46 working weeks, 460 proposals. Each one sits three days longer than it needs to.

What does that cost? Suppose one in ten proposals doesn't turn into an order because the client committed elsewhere in the meantime. That's not an invented rate, it's an assumption you can check against your own experience — plug in yours. With 460 proposals, that's 46 lost orders. At an average order value of €1,800, that's €82,800 in revenue in one year. For a behavior you never ordered. Only tolerated.

Now the before-and-after picture. Before: proposals after five days, 46 lost orders, €82,800 less revenue. After: proposals after 48 hours, and the client compares your proposal while they're still with you. The difference between the two pictures isn't a new rule. It's a standard you enforced — with yourself first.

And that's only the revenue. Add your own time: the hours you spend giving the same instruction for the fourth time, chasing, following up. Suppose that's two hours a week, at an hourly rate of €150 that's €300, over 46 weeks €13,800. One tolerated behavior, one year, a team of five: €96,600 — revenue and your time combined. That's not an opinion. That's arithmetic.

Takeaway: A tolerated behavior costs nothing on the day you tolerate it. It costs for a whole year.

Why do more meetings and new rules reinforce the pattern?

Now the first objection, and it comes almost reflexively: "Then we need clearer rules. And a meeting where I address this."

That's the weaker alternative, and here's why. A new rule is another instruction. In this pattern, instructions have just lost — against your behavior. One more instruction changes nothing about the behavior it loses to. It only raises the number of instructions the team doesn't take seriously.

Worse: every rule that gets set and not enforced is one more piece of evidence for the team that rules are optional here. With each new rule, you expand the very body of evidence you're trying to shrink. After the third rule without consequences, the team stops listening at the fourth. Not out of defiance. Out of experience.

And the meeting? It reinforces the pattern in a quieter way. You raise the topic, everyone nods, everyone agrees. Then the team watches what changes — with you first. If nothing changes, the meeting has accomplished one thing: it proved that meetings have no consequences. Next time, everyone nods faster.

Takeaway: A rule without behavior behind it isn't a rule. It's one more proof that rules mean nothing here.

How do you apply the lever to yourself?

Here's the second objection, and it's the most important one: "I can't model everything myself. I'm only human."

Correct. And that's why this isn't about everything. It's about one thing. A team doesn't expect you to be flawless. It expects consistency between what you say and what you do — and it doesn't check that consistency on everything, only on what you're currently demanding.

The lever has three properties: one behavior change, visible, without exception. One, because several at once aren't credible. Visible, because the team only learns what it sees. Without exception, because a single exception resets the rule — the exception is the information, not the rule.

Here's how you go about it. Pick the one behavior doing the most damage in your team — the math above helps you choose. Then model exactly that behavior for 30 days without a single exception. Don't announce it. Do it. If it's response time, you reply within one day for 30 days, even when your day is full. If it's punctuality, you're there two minutes early for 30 days, even when the client is still on the phone. If it's postponed decisions, the price-list decision gets made this week.

And only once the team has watched it for 30 days do you set the standard for the others too — not as a new rule, but as an expectation you've already met yourself. Now the instruction is no longer information. It's a description of what already applies here.

You might be thinking: 30 days without a single exception, that's unrealistic. But the exception is precisely the point. For your team, the information isn't the average, it's the outlier. 29 punctual days and one late one tell the team: being late is possible if the reason is good enough. 30 punctual days say: there's no reason good enough here. The difference between the two comes down to a single day — and that day decides whether your behavior becomes a standard or a statistic.

Takeaway: Model first, then demand. One thing, visible, no exceptions.

What do you do differently tomorrow?

Three steps, each under an hour.

First: take the one thing about your team that bothers you most. Write it down. Then go through your last 30 days and look for the moments where you did exactly that. You'll find them — that's not an accusation, it's the mechanism this piece describes.

Second: do the math. How often does the behavior happen per week, what does a single instance cost, times 46 weeks. Write the number down. It's the reason the effort of the next 30 days is worth it.

Third: start modeling tomorrow. Not with the instruction, not with the meeting. With your own behavior, in that one spot, without exception. The team will notice in the first week and copy it in the third. Not because you demand it, but because it has seen what applies here.

That's why your team can't overtake you, only mirror you — and why every bottleneck in the team is first a bottleneck in the person leading it. How far this law reaches is in the piece on why your business grows exactly as far as you do. Here, one conclusion is enough: if you want a different team, you don't need a different rule. You need different behavior — yours first.

If the pressure is already there and you want to apply the lever to yourself instead of to the next rulebook: the free 4-day Challenge at impruvement.com/en/challenge is the way to work on yourself — 15 to 25 minutes a day, sign-up with an account, usually via Google login. We don't motivate there. We show you who you need to become so your team follows you.