Here's a pattern I've seen repeat across multiple organizations: a company publishes a thoughtful, well-written code of ethics. It's posted on the website. New employees read it during onboarding. A training module is completed. The document sits in a shared drive and is updated once every few years.
Meanwhile, in actual daily operations, a senior manager steamrolls a junior employee's concern in a meeting and nothing happens. A team lead takes credit for a report someone else wrote. A sales team is given targets so aggressive that the only way to hit them involves misleading customers, and everyone knows it, and nobody says anything.
The gap between what an organization says it values and what it actually rewards is where workplace ethics either lives or dies. And in my observation, most organizations have a much larger gap than they'd like to admit.
Why Written Values Aren't Enough
The instinct when building an ethical culture is to start with documentation: a values statement, a code of conduct, a reporting policy. These things matter, but they're not where culture is formed. Culture is formed in what happens after someone does something.
When a high performer is caught cutting corners and receives no consequences because "we can't afford to lose them right now," that's a cultural signal. Every person who witnessed that moment now knows the real rules. The written code becomes irrelevant — the actual code has just been clarified through action.
The same logic applies in the positive direction. When someone speaks up about a problem in a meeting and the response from leadership is genuine curiosity rather than defensiveness or dismissal, that's also a cultural signal. People notice. They update their mental model of whether it's safe and worthwhile to say something next time.
This is why ethics programs that consist primarily of training modules tend to underperform. Training tells people what the rules are. Observed behavior tells them which rules are real.
What Psychological Safety Actually Means
The term "psychological safety" has become so common in management discussions that it's started to lose its meaning. Amy Edmondson, who coined the concept in organizational research, was very specific: psychological safety is the belief that you won't be punished or humiliated for speaking up, asking questions, or reporting mistakes.
That's a high bar. It means that when someone says "I think this project is going in the wrong direction," the response from their manager cannot be visible irritation, a sudden loss of face time, or being left off the next important email thread. Even one or two instances of that kind of response are enough to teach an entire team that silence is safer.
Building genuine psychological safety requires leaders to actively model being wrong. When a senior person says "I made a mistake, here's what I got wrong, here's what I'm changing" — not in a performative way, but in a factual, non-dramatic way — it gives everyone else permission to do the same. This is what people mean when they say ethics has to start at the top. It's not about leaders being morally superior. It's about them establishing the norms through their own behavior.
The Conflict of Interest Problem
Conflicts of interest are one of the most common and most mishandled ethics challenges in organizations. The standard approach is to require disclosure — employees sign a form saying they have no relevant conflicts, or they disclose if they do.
The problem is that conflicts of interest are often invisible to the person who has them. We're not very good at recognizing when our judgment is being shaped by personal interest. Someone evaluating a vendor who happens to be run by their college friend genuinely believes they're being objective. The research on this is pretty consistent: self-interest affects decision-making below the level of conscious awareness, which means good-faith disclosure doesn't solve the problem.
More effective approaches include structural separation — the person with the relationship is simply not involved in the decision — and explicit discussion at the decision-making stage, where someone other than the evaluator asks "who here has any relationship with any of these vendors?" out loud, in the room, not just on a form.
When Someone Raises a Concern
The moment someone reports an ethics concern is one of the most fragile and consequential moments in an organization. How it's handled either builds or destroys the entire reporting system.
The most common failure is slow or absent response. Someone raises a concern, weeks pass, nothing visibly changes, and then they hear through informal channels that "it was looked into." This is almost worse than no response, because it tells people that the system exists but doesn't function.
What actually works: acknowledge receipt within 24 hours, give a realistic timeline for next steps, follow up even when the conclusion is "we investigated and found the concern wasn't substantiated." If action was taken but can't be disclosed due to HR confidentiality, it's worth saying "action was taken" even if you can't say what. The person who raised the concern doesn't need all the details. They need to know the system isn't a black hole.
The Accountability Gap
Applying rules consistently regardless of seniority or performance is genuinely hard. Not because leaders don't know it's right, but because there are always short-term reasons to make exceptions. The star performer who's abrasive toward junior staff. The manager whose team consistently hits its numbers but who everyone is afraid of. The senior person who bends expense policies in small ways.
The rationale for making exceptions is always framed around disruption: "we're in the middle of a critical quarter," "they're the only person who knows this system," "it's not that bad." But these calculations ignore what the non-action teaches everyone watching. The cost of not addressing an ethical violation isn't just the violation itself — it's every future violation that becomes normalized by the precedent.
Accountability doesn't require dramatic action every time. Sometimes the right response to a first offense is a direct, private conversation where expectations are clearly restated. What matters is that the conversation happens, that it's documented, and that subsequent violations are treated as violations rather than surprises.
What Actually Changes Culture
If I had to summarize what separates organizations where ethics functions from organizations where it's decorative, it would be this: ethics is treated as a behavioral system, not a values system.
Values are statements. Behavior is what happens when a leader is in a difficult room making a real decision with real consequences. Culture is what gets reinforced in those moments, repeated thousands of times across thousands of interactions over years.
The work isn't writing better values statements. The work is building a system where ethical behavior is genuinely safer than unethical behavior — where the incentive structures, the feedback mechanisms, and the observable responses from leadership all point in the same direction.
That's harder than publishing a code of conduct. But it's the only thing that actually works.
Tags
Taresh Sharan