Every Exception You Let Pass Becomes Your Team’s New Standard
You'll know exactly what to say the next time strong results arrive attached to work that is below standard.
TL;DR
The expectations your team works from aren’t the ones written down in formal documents. They’re the ones you enforce with the behaviors you allow.
Your responsibility to your team is to keep the standard clear and name it when it slips. What they hand in is a reflection of what you have allowed.
In the Room
Four regional directors present their quarterly business reviews. The expectation has been the same for two years: the numbers, the story behind them, in a deck that holds up if somebody above you pulls a slide from it.
Kim goes third. Her numbers are the best in the room, and not by a little. She is why the region cleared its target.
Her deck is a mess. The page numbers restart at four. One chart is labeled by year when the data is monthly. Two others have the wrong locations against the actuals.
The VP sees all of it. She also sees the strongest quarter she'll hear about that day. So she leads with the numbers. “Kim, this is your best quarter yet.” She lets the rest go. Raising page numbers on the back of a quarter like that would feel small.
The next quarter, a deck from a different director carries a headline from the wrong period. The quarter after that, all of them look finished at the last minute with minimal thought. She notices every time, and none of it seems worth the uncomfortable conversation. The numbers are good, the team is hitting its goals, and these are internal reviews, so why criticize something that would feel arbitrary?
In the fourth quarter the SVP asks to sit in, last minute. The team shows up with the same sloppy work they had all come to treat as acceptable. The VP is embarrassed. The SVP asks clarifying question after clarifying question, because her team did not show up ready for senior leadership. When he asks what the standard is for these reviews, she has an answer. She does not have one moment where she held it.
Leaders spend a remarkable amount of energy setting expectations. We state them clearly in the performance review criteria, the SOPs, the onboarding training, and the competency frameworks. What we never account for is a second set of expectations, shaped not by what we require, but what we tolerate. Almost all accountability development focuses on the first, but it's the second that quietly decides whether the standard holds.
The way a leader reacts to work that comes in below the line teaches the team what they can expect and what that leader is willing to tolerate. It doesn't show up in a document. It shows up in how the team adjusts after watching what one of them got away with.
The Real Problem
This is the accountability gap: the distance between the standard you stated and the standard you allow. Every time a leader lets something slide, that gap widens and compounds, because each missed moment makes the next one easier to justify.
And it isn't that senior leaders are indifferent. They care deeply about performance, and about their people meeting and exceeding expectations. It's that nobody ever taught them how loud their silence is.
Here is what makes Kim's version even more difficult. Nobody could argue Kim was underperforming, which is why the pass was so easy to give. The other three directors did not learn that sloppy work is acceptable. They learned it's acceptable if your numbers are good, and they took that to heart.
Why It Keeps Happening
Nobody trains senior leaders for the live moment. Expectations get written down and signed off, and then a gap shows up in a room full of people with no framework for what to do about it right there.
Leaders default to managing the relationship rather than the expectation in the room. Say nothing now, handle it privately later. It feels like good leadership, and it does protect the person. It also lowers the bar for everyone watching, because the room never hears the standard, it only hears the pass. A talented leader can note the gap respectfully in real time.
There's a second reason this one is easy to walk past. It looked like a formatting problem, and page numbers feel small next to a quarter Kim just carried. But two chart labels had the wrong locations against the actuals. That's inaccurate data.
This pattern is so easy to fall into because the cost is never immediate. The moment she let pass in the spring showed up three quarters later, in front of her own boss.
What To Do Instead
The shift isn't complicated, it's just difficult. Decide before you walk into the room that the expectation you stated is the one you'll hold in it, including with the person carrying the quarter.
There's a third option, in two parts. The first happens while she is presenting, and it's a question, not a verdict. “I notice the axis says year, but it looks like we're talking about months. Is that right?” The error is named, in the room, without making the meeting a referendum on Kim.
The second part happens at the end, and it goes to everybody. “Casual feels fine in an internal meeting, but these decks travel upward, and an SVP won't know your business well enough to read between the lines. Anything with your name on it has to be polished and correct.” Nobody was singled out, and the standard is in the room.
If it keeps happening after that, it becomes a performance conversation, and that one happens privately, with specifics and a date.
It will feel odd the first time, and you may get pushback, particularly from the person who just delivered your best quarter. Every act after that gets a little easier, because the expectation has begun to be reset.
What It Takes
Accountability is a skill, and skills require practice, feedback, and doing the difficult thing more than once. Nobody gets that practice by accident, and integrity isn't the missing piece. Repetition is. The hardest person to hold accountable isn't the underperformer. It's the one whose results give you every reason to let it go.
Once a culture of accountability is built, it becomes entrenched. Every new hire after that, leaders and individual contributors alike, gets brought into it. But somebody has to create it first, and it gets created in rooms like this one.
Leader Takeaway
Public or Private: A 3-Part Talk Track
IN THE MOMENT, ASK A QUESTION:
“I notice [specific item, for example: the axis on this one says year, but it looks like we're talking about months]. Is that right?”
AT THE END, SET THE STANDARD FOR THE WHOLE ROOM:
“I know this is an internal meeting and casual feels fine. But these can end up in front of people above both of us, and they won't know your business well enough to read between the lines. Anything with your name on it has to be polished and correct.”
IF IT REPEATS, TAKE IT PRIVATE:
“I want to talk about [specific item], because we've seen it [number] times since I raised it with the team. Here's what I need to be different by [date].”
Use this the next time strong results arrive attached to work you would not want your own boss to read.
Frequently Asked Questions
How do I know when something should be done publicly versus privately?
Ask yourself what the room needs to learn. If it's a standard everybody works from, it belongs in the room. If it's one person's performance, meaning a pattern that repeats after the standard was made clear, it belongs in a private conversation with specifics and a date. The mistake is using a private conversation to fix a public standard. The room never hears it, so the room never changes.
What if I've already let it slide for a year?
Then you're resetting, not enforcing. Say that out loud to the group rather than springing a new bar on whoever presents next. It takes a few cycles before the team believes it.
Isn't this just nitpicking?
The test isn't how small the thing is, it's whether the work holds up once it leaves the room. Page numbers on a deck nobody forwards is preference. A chart labeled by year when the data is monthly is wrong, and it stays wrong when it travels upward. Hold the things that survive the handoff, and when you let something go, say that you're letting it go. A team that hears you choose learns the standard either way.
What if the person pushes back?
Expect it from your strongest performer, because they have been operating with more room than the stated standard actually allows, and you gave them that room. Question the work, not the person, and use the same tone you'd use for a calendar detail. Pushback in the moment is not the same as damage. A relationship that breaks over a named chart error was already resting on you never saying anything.
The Aha! Moment
The VP had a good answer ready. The template is on the intranet. The expectation has been in place for two years. The SVP asked her something else. He asked when she had last said any of it out loud, in the room, while it was happening. She hadn't, and she knew it. She had noticed every time, and every time she chose the easier meeting. Her directors weren't careless. They were working from the standard she handed them in the spring, and the quality of their work was a reading of hers.
Accountability cultures don't get built in culture documents or values workshops. They get built or demolished in the moment a leader decides what to do with the four seconds between hearing something and responding to it. So, the question worth asking before your next leadership meeting isn't “what does our accountability policy say?” It's “what's the standard I'm actually prepared to hold, in public, today?”
