Double Standards

Newsletter Infographic

This visual compresses the full issue into one operating picture: the three faces of double standards, the damage sequence they trigger, Juran’s accountability frame, and the five practices required to restore one standard for all. Click the image to enlarge it.

The War Story

Kelton Manufacturing’s attendance policy looked precise. Three unexcused absences in ninety days triggered a written warning, four a performance improvement plan, and five a termination review. Terri, a machine operator, hit her third absence and received the written warning the same day.

Wade, a senior process technician with long-standing plant relationships, reached four absences in the same quarter and received only a counseling conversation. The explanation was that his tenure and institutional value justified flexibility. The operators who observed both cases did not need a formal investigation to understand what had happened. They updated their working model of how the place actually worked.

People do not need a handbook audit to detect a double standard. They need about thirty seconds of observation. After that, behavior changes to match what they have been shown.

The Three Faces of the Double Standard

The source document defines three operating forms. That matters because each one hides differently and damages trust differently.

Form	How It Operates	Who Sees It	Damage Pattern
Explicit Seniority Exception	Rules are openly applied differently based on tenure, title, or standing.	Everyone sees it because the differential treatment is visible.	Immediate loss of policy credibility. The standard becomes a tool against the less powerful.
Invisible Favorite Exception	Standards shift based on relationship with the decision-maker while the inconsistency is denied.	Usually visible from below even when invisible from above.	Slower but deeper trust erosion because the pattern cannot be discussed cleanly.
Convenience Exception	Standards are enforced when easy and waived when enforcement would create disruption or conflict.	Most obvious to the people directly affected and to the leader’s immediate team.	The standard stops functioning as a standard and becomes an unpredictable guideline.

Kelton’s case is mainly the first form. It is often tolerated precisely because the explanation sounds plausible enough to the person making the exception.

Juran’s Quality Trilogy Applied to Accountability

The strongest move in the PDF is using Juran’s Quality Trilogy as the corrective frame. That makes the issue bigger than fairness language. It places double standards inside the language of quality: requirements, variation, control, and improvement.

Quality Planning

Requirements must be defined precisely enough that two supervisors looking at the same facts will reach the same conclusion. If terms such as “unexcused,” “appropriate,” or “contextual” are left vague, variation enters through interpretation. That is not good management. It is a design defect.

Quality Control

Most organizations audit whether employees comply with standards. They do not audit whether supervisors apply those standards consistently. That missing audit is exactly what allows double standards to survive below the surface.

Quality Improvement

Recurring inconsistency is not mainly a character issue. It is a chronic process problem caused by weak definitions, poor training, missing audit logic, and absent consequences for inconsistent application. Juran’s point is direct here: fix the system and most people will perform correctly.

A requirement waived for some and enforced for others is not a requirement. It is a preference enforced selectively, which creates exactly the variation quality systems are supposed to eliminate.

Why Double Standards Persist

The article’s rationalization table is useful because it shows why leaders often believe their own exception logic.

Rationalization	Why It Sounds Plausible	Why It Fails
“I’m using contextual judgment.”	Good management does require context sensitivity.	If the same categories of people are consistently favored, this is bias wearing professional language.
“Their institutional value justifies flexibility.”	Some people do have unusual knowledge or relationship value.	Institutional value is a compensation or retention question, not a standards question.
“The policy doesn’t account for all situations.”	Policies do often contain gaps.	If the gap is real, close it in the written policy instead of creating informal exceptions.
“They’ve earned some flexibility.”	Tenure and loyalty do deserve recognition.	If tenure-based flexibility is legitimate, it belongs in the visible standard and must apply consistently.
“I know this person and what they’re dealing with.”	Personal context can matter.	If context modifies the standard, it must do so for anyone in comparable circumstances, not just favorites.

The Damage Sequence

The article lays out the sequence cleanly and it is worth preserving because each stage gives leaders a chance to intervene.

Observation and registration: multiple people witness the inconsistency at the same time.
Model recalibration: employees update their mental model of the “real” policy.
Behavioral adjustment: discretionary effort drops because the burden of the standard is no longer shared.
Quality degradation: outputs slide in ways that are real but causally distant from the original event.
Misdiagnosis: leadership treats the output problem while missing the accountability failure that produced it.

That is why line six’s disengagement was not a motivation problem. It was a rational response to observed inconsistency.

Five Practices for One Standard for All

The fix is not harsher punishment. The fix is designing a system in which consistent enforcement is easier than inconsistent enforcement.

1. Define Standards with Objective Criteria

Remove interpretive gaps. Any term that produces different supervisor answers to the same scenario needs clarification in the written standard, not in private judgment.

2. Audit Enforcement Consistency

Audit not only whether employees comply, but whether enforcement outcomes cluster by tenure, role, shift, or supervisor. Consistency data belongs inside the standard-management process.

3. Move Judgment Upstream

Supervisors may judge whether a case meets a defined exception criterion. They should not have discretionary control over the consequence once the criteria are or are not met.

4. Make Consistency a Supervisory Performance Standard

Supervisors should be evaluated on whether they apply standards consistently, not only on their team’s output metrics. Without that, selective enforcement remains costless to the person creating it.

5. Create a Safe Naming Mechanism

Employees need a visible, low-risk path for naming specific instances of differential treatment. If concerns disappear into a channel with no visible response, the mechanism will stop being used.

One Standard in Practice

Double Standard in Action	One Standard Applied
Senior employee misses four days and receives undocumented counseling.	Fourth absence triggers the written consequence regardless of tenure or relationships.
High-performing team is exempted from a safety audit during a busy period.	Audit schedules apply to all teams because production pressure is not an exemption criterion.
Executive submits a late expense report and finance ignores it.	Late-submission handling follows the same process regardless of title.
Veteran operator’s error is blamed on ambiguity while a new hire’s becomes a disciplinary issue.	Root-cause analysis and consequence follow the actual cause, not the person’s seniority.
Improvement participation is tracked for hourly workers but waived for salaried managers.	Participation expectations are defined by role in advance, not adjusted after the fact.

The Double Standard Diagnostic

This is the quarterly check worth running against enforcement records. Any “yes” answer is a consistency defect, not just a management anecdote.

Diagnostic Question	If Yes
Do enforcement outcomes differ by tenure, role, shift, or supervisor?	Run root-cause analysis on policy definition, training, and enforcement structure.
Does any policy rely on undefined terms that different supervisors interpret differently?	Clarify the written standard and close the interpretive gap.
Has an exception been granted on a criterion not written into the policy?	Either formalize the criterion visibly or retract the exception logic.
Are supervisors evaluated on enforcement consistency, not just output?	Add consistency as a supervisory review criterion.
Is there a functioning, trusted way for employees to name inconsistency?	Create it or redesign it until people actually use it.
Have the same concerns been raised more than once without structural resolution?	Escalate to Juran’s Quality Improvement process as a recurring system failure.

The Bottom Line

Kelton’s metrics declined gradually enough that leaders could explain the movement away with easier stories. But the deeper issue was already set. Terri no longer invested discretionary energy in a system that had shown her the standard was not shared. That is the part leaders often miss: a double standard does not merely create resentment. It teaches people what kind of effort is and is not worth giving.

A standard applied to some and not others is not a standard. It is a preference enforced selectively, understood universally, and trusted by no one.

Call to Action

Forward this issue to a leader who believes culture problems mainly come from attitude. Often they come from observation. People watch how rules are applied and then decide how much of themselves the system deserves.

Newsletter replies and questions: [email protected]
Follow updates on X.com: @kaizen_6sigma

Series Navigation

Previous: Series 2 Part 3 Back to Newsletter Archive

Series 2, Issue 5 will examine the leadership failure behind “we don’t have time to train” and why deferred learning quietly compounds quality risk.