The short version
A top producer treats a colleague badly. Leadership does nothing. The real message is now clear to everyone. A case study in what consequences actually teach.
This is a composite case drawn from a pattern that shows up in nearly every organization: a leader brings in a brilliant revenue producer, and within two quarters, two strong employees quietly ask about transfers. The number on the dashboard is green. The culture is bleeding.
The situation
The company's values included respect, and the onboarding deck said people leave every meeting treated with dignity. The new sales director was undeniably good — a 30% pipeline lift in her first two quarters. She was also dismissive in team meetings, claimed colleagues' work as hers, and once reduced a junior analyst to tears in a review that half the floor could hear.
Her manager's response evolved in three stages, and each stage taught the organization something:
- 1First, nothing. The rationale: 'She's closing deals the rest of the team can't.' Everyone watching concluded that respect is negotiable if your numbers are good.
- 2Second, private coaching. A reasonable step — but because nothing changed and no one could see it, the team read it as 'she was told and chose not to care, and nothing happened.'
- 3Third, a clear standard. After a second incident, leadership put it in writing: respect is a requirement of the role, not a preference. They documented the behavior, set a 60-day improvement plan with specific behaviors, and — critically — told the team, in general terms, that standards apply to everyone.
What the outcome taught
The director improved in some areas and not others. Two months later, leadership moved her out of people leadership into an individual contributor role with real autonomy and no reports. The pipeline dipped for one quarter. Regretted attrition on the sales team stopped rising.
The lesson was not 'be tough.' It was that a value only exists to the extent that it costs something to violate. Every organization has values it enforces and values it merely prints. Employees can tell the difference within weeks — and they calibrate their own behavior to the enforced list.
A response framework leaders can use
- 1Separate performance from conduct in your own head. Her numbers were real; the behavior was also real. Refusing to weigh one against the other is the actual failure mode.
- 2Name the violation in value language, not personality language. 'That review was disrespectful' is a standard. 'She's difficult' is an opinion.
- 3Act visibly enough that the team learns something true. Privacy protects the individual; visibility protects the standard. You don't need to disclose details — you need the team to see that something happened.
- 4Design a consequence ladder in advance: coaching, documented feedback, formal plan, role change, exit. The team watches which rung a star performer reaches.
- 5Rebuild with the harmed people, not around them. The analyst who was humiliated needs a conversation, and the colleagues who watched need to hear leadership name what happened.
The question to ask your own team
Ask a trusted group this: 'Is there anyone here whose performance makes us excuse behavior we wouldn't accept from others?' If the pause before they answer is long, you already know which values govern — and it isn't the ones on the wall.
The values you enforce become your culture. The values you excuse become your reputation.
Related resource
Core Values Worksheet
Turn abstract values into observable behaviors, decision rules, and clear we-do / we-don't commitments.
Get the Core Values Worksheet