A leader tells the team that meetings start on time. Nothing controversial about it — punctuality signals respect for other people’s schedules, and everyone nods. The next meeting starts four minutes late because the leader is finishing another conversation. So does the one after that. No one says anything. The standard was never withdrawn. It simply stopped applying to the person who wrote it.

Nobody has to announce that leadership is exempt. The exemption announces itself.

The moment a leader departs from a stated standard without explanation, he teaches the organization something more durable than the written rule: what actually governs here, and who it governs.

Teams Learn the Real Standard From Behavior

Every organization operates on three standards, not one. The declared standard is what leadership says. The observed standard is what leadership repeatedly does. The enforced standard is what actually produces consequences when violated. When these align, the written policy is trustworthy. When they diverge, people do not average the three — they adapt to the strongest signal, which is almost always behavior plus enforcement.

Leadership Is Not Sameness

None of this argues that leaders and team members must perform identical work. Authority legitimately creates different decision rights, access, schedules, and approval thresholds. A director may hold broader scheduling discretion, approve exceptions, or carry different deadlines than the people who report to her — that is ordinary role differentiation, not inconsistency. The issue is never whether responsibilities match. It is whether the underlying principle still holds. If everyone is expected to communicate a schedule change, leadership should communicate schedule changes too — even where the approval process differs.

Different authority does not require different integrity.

Unexplained Exceptions Become Cultural Signals

A single exception, explained, is not a problem. Repeated exceptions taken without explanation are. When leadership routinely departs from a standard and says nothing, the team draws its own conclusions: standards are negotiable, status changes accountability, relationships outweigh process, urgency justifies bypass, and rules mainly constrain people with less authority. This is not simply a fairness complaint. It is an operational failure. Once people stop knowing which standards are real, they stop planning around any of them — and the organization loses the predictability the standard existed to protect.

Selective Enforcement Is More Damaging Than a Weak Rule

An imperfect standard, applied consistently, is more trustworthy than a strong standard applied selectively. When high performers skip reporting, friends receive extensions, difficult conversations get avoided, and juniors are corrected for what seniors routinely escape, the standard stops functioning as an operating rule and starts functioning as a relationship test. People begin asking who they know, who will protect them, and who actually has to comply. That question, once it becomes normal, is the definition of unhealthy governance.

Self-Exemption Often Begins With Rationalization

Leaders rarely decide the rule does not apply to them. They decide, one instance at a time, that this particular case is different: I know the context. This is urgent. I am responsible for the outcome anyway. It is faster if I just handle it. Some of these are occasionally true. The danger is not the exception — it is using the same reasonable-sounding exception repeatedly, without ever submitting it to review. Authority supplies an almost limitless stock of plausible reasons to bypass the normal path. The discipline required is not eliminating discretion. It is governing it.

Explain the Exception When the Exception Is Legitimate

When a leader must legitimately depart from a standard, a short explanation preserves what silence destroys: “Normally we require three bids. Because the equipment failed and operations are stopped, I authorized an emergency purchase under the exception provision. We will review the decision Friday.” That single sentence confirms the standard still exists, names the authority invoked, bounds the deviation, and commits to review.

Leaders Need Accountability Above Their Own Discretion

If the leader can always approve the exception, interpret the standard, and excuse the failure, accountability is structural only on paper. Depending on the organization’s size, real accountability may come from a board, an owner, a peer leader, an elder structure, or a documented review process — the mechanism should be the smallest one that is still credible, not the most elaborate.

Who can question this leader’s exception without paying a relational penalty for asking?

The Team Does Not Need a Perfect Leader

None of this requires flawlessness. Teams trust leaders who miss deadlines, misjudge decisions, and communicate imperfectly, provided the leader responds honestly when it happens. The credibility sequence is simple: miss, name it, repair it, return to the standard. A leader who says, “I asked everyone to prepare by Tuesday. I did not. That was my miss, and here is what I am changing,” typically gains more credibility than the leader who lets the inconsistency pass unmentioned. Accountability is not weakened by an admitted miss. It is weakened when authority is used to make the miss invisible.

Build Standards Leaders Can Actually Live Under

If leadership repeatedly violates the same standard, character is not always the explanation. Sometimes the rule is impractical — the reporting cadence too frequent, the documentation burden excessive, the deadline unrealistic for the way decisions actually get made. Preserving the appearance of compliance while quietly working around the rule solves nothing. The better response is to revise the standard openly and say why. A realistic standard applied consistently outperforms an idealized one everyone quietly violates.

The Mirror Test

Choose one standard you currently expect from others. Answer plainly, in writing.

Standards are not credible because they are written well. They become credible when people watch leadership submit to them — consistently, with explanation when it departs, and with repair when it fails. Your team does not need you to be flawless. It needs to know that authority does not place you above the principles you ask others to carry.