What You Tolerate, You Cultivate

The Lesson You're Teaching Right Now

There's a phrase I come back to constantly when I'm working through a team dynamics problem: what you tolerate, you cultivate.

It doesn't sound complicated. But the implications are uncomfortable in a way that most management frameworks try to avoid, because it puts the problem directly in the manager's lap. Whatever behavior you've let slide, whatever standard you've declined to enforce, whatever pattern you've watched for three months without saying a word, you've been quietly teaching your team that this is what acceptable looks like. The lesson lands whether you meant to teach it or not.

I've seen this play out so many times that the scenarios start to blur together. The manager who lets one person miss deadlines repeatedly and then acts genuinely surprised when the rest of the team stops treating their own deadlines as serious commitments. The leader who watches a senior IC be condescending in meetings, says nothing, and then spends six months wondering why the team has stopped pushing back on bad ideas. The director who watches one team's metrics erode for three straight quarters and then books an offsite to diagnose why the whole org's standards have slipped. In every case, the answer is upstream of the visible problem. You cultivated this. Maybe not on purpose. But you cultivated it.

How Drift Compounds

Here's what makes this particularly hard to catch in the moment. The first time you let something go, it feels like a reasonable call. Maybe the person was going through something difficult. Maybe the deadline wasn't actually critical. Maybe you were picking your battles. Those are legitimate reasons to exercise judgment, and good managers exercise judgment all the time.

The problem is what happens in the six months after that first exception. The behavior becomes the baseline. Not loudly, not with any announcement, just gradually and inevitably. The person who missed the deadline files it away as "fine to miss." The team watching files it away as "deadlines are negotiable here." Nobody talks about it explicitly. They don't need to. The standard just quietly shifts.

By the time the pattern is visible enough to address, you're not addressing one missed deadline. You're addressing a cultural norm that has been in place long enough that people have organized their behavior around it. That conversation is significantly harder than the conversation you could have had in month one. And that asymmetry is the whole ballgame.

The cost of early intervention feels high because it's immediate and awkward. The cost of late intervention is also high, but it's spread out and invisible until it suddenly isn't. Managers consistently underweight the late cost because they never see the counterfactual. You see the difficult conversation you have to have today. You don't see the three-year org culture problem you're building in the background.

How to Spot What You're Currently Tolerating

The tricky part is that the things you're tolerating are, almost by definition, the things you've stopped noticing. You've adapted. Your team has adapted. The new baseline just feels like baseline.

There are a few signals worth looking for. The first one is silence. When your team stops raising a particular type of problem, it's usually not because the problem went away. It's because they've raised it before and nothing happened, so they stopped. If there's a category of issue you haven't heard about in a while, that's worth sitting with. Either things improved (great, let's understand why), or the team concluded that raising it wasn't worth the effort.

The second signal is the workaround that's become standard practice. When people stop expecting a process to work and just build the detour into their routine, that's a tolerance signal. The thing that was supposed to work, didn't, nothing changed, and now the detour is invisible because it's normal.

The third signal is the conversation that everyone is having outside the room but nobody is having inside it. If you're close enough to your team, you'll notice when the candid version of a conversation and the meeting version of that conversation have diverged significantly. That gap is usually a tolerance problem. Someone or something is off-limits for direct feedback, and it's been off-limits long enough that people have stopped trying.

The Flip Side: What You Reinforce, You Also Cultivate

The same mechanism runs in the other direction, and that's worth understanding just as clearly.

When you notice someone doing something right and you say so, specifically and promptly, you're not just thanking them. You're teaching the team what gets recognized here. When you publicly back someone who pushed back on a bad idea in a meeting, you're teaching people that dissent is safe. When you hold a standard firmly in a moment where letting it slide would have been easier, you're teaching people that the standard is real.

This is why "culture" isn't some separate track of work that you do in addition to real management. Culture is the accumulation of every tolerance decision and every reinforcement decision you've made, stacked up across months and years. You're building it constantly whether you're paying attention to it or not. The question is just whether you're building it on purpose.

Tolerance Versus Patience

There's a line worth drawing here, because I've watched managers collapse this distinction in both directions.

Patience is giving someone room to develop. It means you've identified a gap, you've had an explicit conversation about it, you have a shared understanding of what growth looks like, and you're giving the person time to close the gap with your support. That's a deliberate developmental decision. There's accountability embedded in it, even if the timeline is generous.

Tolerance is watching the same problem recur without having the conversation or creating the accountability. It looks like patience from the outside. It feels like patience from the inside. But the person on the other end doesn't have a development conversation to work from. They have a manager who seems fine with how things are. And they will reasonably conclude that things are fine.

The way to tell the difference is whether you've had the direct conversation. If you have, and there's a clear agreement in place, you're practicing patience. If you haven't, you're tolerating. The distinction matters because the action that follows is completely different. Patience continues with support and check-ins. Tolerance has to start with a conversation.

The Standard Is What You Enforce, Not What You Announce

This is the part that most management writing doesn't say plainly enough. Your team does not learn your standards from your words. They learn them from what happens when someone doesn't meet them.

You can run all-hands about excellence and accountability and high performance. You can post values on the wall. You can write a management philosophy document that would make a business school professor weep with admiration. None of it matters as much as what you do the next time a standard is violated in front of you.

If you say something, the standard is real. If you don't, the standard is decorative.

The conversation only gets harder the longer you wait, and the team only gets better at working around a standard that doesn't actually exist.

That's worth being honest with yourself about. Look at the gap between the standards you believe you hold and the standards you actually enforce. Whatever lives in that gap is what you've been cultivating.

The good news is that you can start closing the gap today. Pick the thing you've been tolerating and decide to stop tolerating it. Have the conversation this week, not next month. Hold the line the next time it matters.

You're teaching your team something right now whether you intend to or not. Might as well teach them something useful.