A Leader's Tolerance Becomes the Team's Standard

Before becoming a leader, saying that something is "okay" can feel like a personal decision.

Perhaps the work is not exactly how I would have done it, but it is usable. Correcting it would take time. The gap does not feel serious enough to create another conversation, so I let it pass.

Once I lead a team, that same decision is no longer entirely personal.

What I accept becomes information.

The team watches which work passes, which deadlines can move, which details matter, which problems need to be raised, and how much ownership is expected. They do not learn the real standard only from what I say. They learn it from what I repeatedly allow.

A leader's tolerance becomes the team's standard.

Leadership changes the meaning of "okay"

My natural response may be to feel that something is good enough.

That may come from patience, flexibility, or a desire not to make every small issue bigger than it is. These are not bad qualities. A leader who is dissatisfied with everything will exhaust the team and eventually make people afraid to act without approval.

But leadership requires me to examine my instinct more carefully.

Am I accepting this because the result truly meets the standard needed for the situation? Or am I accepting it because giving clear feedback is uncomfortable, correcting the pattern takes effort, and "okay" allows everyone to move on?

I have written before that okay is not always okay. In leadership, the word can do more than end one conversation. It can quietly redefine the bar for every similar piece of work that follows.

The team learns from what passes

A standard written in a document is useful. A standard repeated in a meeting is useful too.

But the most powerful standard is the work that passes without correction.

If a late update is accepted repeatedly, the team learns that early visibility is optional. If an unclear recommendation is accepted, the team learns that presenting information may be enough even when a decision is needed. If the leader silently repairs every weak result, the team learns that the leader owns the final gap.

None of these lessons may have been spoken. They are still being taught.

This is why a leader sets more than quality.

A leader also sets speed, momentum, ownership, and the seriousness with which commitments are treated. The team may occasionally exceed the leader's example, but it is difficult for a whole team to maintain a standard that its leader does not consistently model or protect.

Raising the standard is not perfectionism

There is a dangerous version of this idea.

A leader can decide that raising standards means rejecting more work, controlling more details, or making every preference non-negotiable. The team then spends its energy trying to predict the leader rather than producing a good result.

That is not a higher standard. It is a moving target.

Different work requires different levels of precision. A quick internal draft does not need the same polish as a final client recommendation. A reversible decision does not need the same scrutiny as one with serious consequences. Sometimes speed is part of quality because waiting for a perfect answer creates a larger cost.

The leader's responsibility is to make these differences clear.

"Good enough" can be a valid standard when the stakes, purpose, and trade-offs make it appropriate. The problem is when good enough is not chosen deliberately. It simply becomes whatever happened to arrive.

Raising standards is not the refusal to accept imperfection.

It is the refusal to let convenience decide the standard without thought.

Saying "not okay" is only the beginning

It is easy to tell someone that a result is not good enough.

That alone does not create a useful standard.

If I say "this is not okay" without explaining the gap, I may create anxiety instead of improvement. People know that I am unhappy, but they do not know what a stronger result looks like or how to produce one next time.

Useful correction should make at least four things visible:

1. What outcome was needed?
2. What specifically is missing from the current work?
3. Why does the gap matter?
4. Who owns the next action, and by when?

This turns dissatisfaction into direction.

The purpose is not to prove that the leader has a higher standard. It is to make that standard clear enough for the team to reach without guessing.

Do not raise the bar by taking the work back

There is another temptation.

When a result falls below the bar, the fastest response may be to fix it personally. The standard is restored for that one piece of work, but the team has not necessarily become stronger.

As I learned through the difficult managerial work of letting go, taking work back can solve the immediate problem while teaching the team that difficult work eventually returns to the manager.

A raised standard should make the team more capable, not more dependent on the leader.

That means giving the feedback, explaining the reasoning, and leaving ownership of the correction in the right place. It may be slower today. It creates the possibility of stronger work tomorrow without the leader becoming the final editor, fixer, and decision-maker for everything.

The leader has to meet the standard too

It is difficult to ask for early updates if I routinely give late direction.

It is difficult to demand ownership if I change the outcome without explanation. It is difficult to ask the team to prepare carefully if I enter discussions unprepared. It is difficult to create momentum if my own decisions remain unresolved.

Leadership makes personal inconsistency more expensive because it is multiplied through other people.

This does not require a leader to become flawless. It requires the humility to notice that the team's behaviour may sometimes be a response to the environment the leader created.

If I want the standard to rise, I have to ask what I need to model, clarify, reinforce, and stop accepting in myself as well.

This is also why systems matter. In what I would do differently if I started an agency again, I wrote about weekly updates, accountability, business outcomes, and the leader's responsibility to build systems rather than remain inside every task. A standard becomes sustainable when it is supported by a repeatable way of working, not only by the leader's personal attention.

Standards are built through repeated moments

Pulling my standards up is easier to agree with than to practise.

The difficult moment is rarely when I am thinking calmly about leadership. It is when I am busy, the work is almost acceptable, another conversation will take energy, and saying "okay" would be easier.

That is where the standard is being set.

I do not need to turn every small issue into a confrontation. I do need to decide intentionally whether the result fits the purpose, whether the gap is likely to repeat, and what my acceptance will teach.

Sometimes the right answer will still be, "This is good enough. Move forward."

Sometimes it has to be, "This is not ready yet. Here is what needs to change."

The important part is that the decision is deliberate.

A leader's standard is not the highest level they can imagine. It is the level they make clear, model consistently, and help the team achieve.

The team will not remember every statement about excellence.

It will remember what passed.