Most teams have a written set of standards somewhere — a values document, an onboarding guide, a set of stated expectations. Far fewer teams actually behave according to what’s written. The gap between a stated standard and a genuinely upheld one is one of the more common, quietly corrosive failures in leadership, and it’s worth understanding why it happens, because the fix isn’t writing a better document.
Why Written Standards Often Don’t Stick
A standard becomes real not when it’s written down, but when it’s consistently, visibly enforced — rewarded when met, addressed when missed, applied evenly regardless of who’s involved. A document that states a standard but is never referenced again, never checked against actual behaviour, and never enforced when violated, quickly becomes background noise. People learn, correctly, that the document describes an aspiration rather than an actual expectation.
What Actually Makes a Standard Real
Consistency, especially with people it’s inconvenient to hold accountable. A standard that’s enforced with junior team members but quietly overlooked for a senior, high-performing, or well-liked person isn’t actually a standard — it’s a suggestion that applies selectively. Nothing undermines a stated norm faster than visible inconsistency in how it’s applied.
Modelling from leadership first. A standard that leadership itself doesn’t visibly meet has essentially no chance of being genuinely upheld by anyone else — people calibrate their own behaviour heavily on what they observe from the top, regardless of what’s officially stated.
Clarity specific enough to actually guide behaviour. A vague standard — “we value excellence” — provides little practical guidance for an actual decision in the moment. A more specific standard — “client responses go out within one business day” — gives people something concrete enough to actually meet or visibly fall short of.
Genuine, prompt acknowledgement when the standard is met. Standards that are only ever discussed when violated, never noticed when met, create an environment that feels purely punitive rather than genuinely aspirational.
A clear, proportionate response when the standard is missed. Consistently addressing a missed standard — calmly, directly, and proportionately to the actual severity — signals that the standard is real. Letting violations slide, even occasionally, teaches everyone watching that the standard is negotiable.
The Specific Damage of Inconsistent Enforcement
It’s worth dwelling on inconsistency specifically, because it does more damage than having no standard at all. A team with no stated standard at least knows where it stands — expectations are informal and understood to be flexible. A team with a stated standard that’s inconsistently enforced experiences something worse: a sense of arbitrary unfairness, where the actual rule seems to depend on factors nobody can quite name — who you are, how visible the violation was, or how the leader happened to be feeling that day. That sense of arbitrariness erodes trust far more than the absence of a formal standard ever would.
Building Standards the Team Actually Owns
Standards imposed entirely from above, without any input from the people expected to meet them, tend to generate more resistance and less genuine adherence than standards built with real participation from the team. This doesn’t mean every standard needs to be democratically decided — some genuinely need to be set by leadership. But wherever there’s room for it, involving the team in defining what a standard should actually look like in practice tends to produce both a more realistic standard and considerably more buy-in to actually meeting it.
A Practical Scenario
A team has a longstanding, written standard about response times to client requests, which is consistently enforced for most of the team — except for one senior team member whose slower responses have quietly become accepted as simply how they operate. Over time, other team members notice the inconsistency, and the standard’s credibility erodes broadly, not just with respect to that one person.
The manager addresses it directly — a private, respectful conversation about the standard applying evenly, without exception, and a specific, time-bound expectation for improvement. The fix isn’t dramatic, but it’s necessary: within a few weeks, response times across the team, including from the previously exempt team member, come back into line — and, notably, so does general morale, which had been quietly affected by the sense that the standard wasn’t actually being applied fairly.
Common Mistakes
Writing a standard and never referencing it again. A document that isn’t actively used to guide and evaluate behaviour becomes background noise rather than a genuine expectation.
Enforcing standards inconsistently based on seniority or likeability. This does more damage to trust than having no standard at all, because it introduces a sense of arbitrary unfairness.
Leadership exempting itself from standards it expects others to meet. A standard leadership doesn’t visibly follow has little chance of being genuinely upheld elsewhere in the team.
Only discussing standards when they’re violated. This creates a purely punitive association with the standard, rather than a genuinely aspirational one.
Action Steps
- Review a written standard currently in place on your team, and honestly assess whether it’s being consistently enforced across everyone, regardless of seniority.
- Identify one instance where a standard has been quietly overlooked for a specific person, and address it directly and fairly.
- Make sure you, as a leader, are visibly meeting the standards you expect from your team.
- The next time someone genuinely meets a standard well, acknowledge it specifically and promptly, not just when it’s missed.
- Where appropriate, involve your team directly in defining what a specific standard should look like in practice.
Key Takeaways
- A standard becomes real through consistent enforcement, not through being written down.
- Inconsistent enforcement, particularly favouring senior or well-liked people, damages trust more than having no standard at all.
- Leadership needs to visibly model a standard for it to have any real chance of being upheld elsewhere.
- Standards that are only discussed when violated create a purely punitive association rather than a genuinely aspirational one.
- Standards built with genuine team input tend to generate more buy-in than standards imposed entirely from above.
Conclusion
The gap between a written standard and a genuinely upheld one comes down almost entirely to consistency — whether the standard is applied evenly, modelled from the top, and reinforced both when it’s met and when it’s missed. A standard that meets these conditions shapes behaviour. One that doesn’t becomes just another document nobody quite takes seriously, regardless of how well it was written.
Frequently Asked Questions
How specific should a team standard be to actually work?
Specific enough to guide an actual decision in the moment — a vague aspiration like “be excellent” provides little practical direction, while a concrete standard tied to a measurable behaviour is easier to meet and easier to enforce fairly.
What’s the fastest way to damage a team’s trust in a stated standard?
Enforcing it inconsistently, particularly exempting senior or well-liked people, which introduces a sense of arbitrary unfairness that’s more damaging than having no standard at all.
Should leaders be held to the same standards as their team?
Yes, and visibly so — a standard leadership doesn’t model has very little chance of being genuinely upheld by anyone else on the team.
How do you introduce a new standard without it feeling imposed?
Involving the team in shaping what the standard should look like in practice, where genuinely possible, tends to produce both a more realistic standard and considerably more buy-in.
What should happen when someone misses a standard?
A calm, direct, and proportionate response — addressed consistently regardless of who’s involved — reinforces that the standard is real, without needing to be harsh or punitive.
Is it ever appropriate to adjust a standard rather than enforce it as originally written?
Yes — if a standard proves unrealistic in practice, it’s better to revise it explicitly and communicate the change than to quietly stop enforcing it while leaving the original version formally in place.