The Problem

Nobody knows what good looks like except me.

The work comes back technically complete and somehow wrong. You fix it, or you explain it again, and both of you leave the exchange a little more tired. The standard is real, it is consistent, and it exists in exactly one place: your head.

You’ll recognize it by these

• You can tell within ten seconds whether something meets the bar, and you cannot say why in a sentence anyone could apply.
• People bring you work for approval that they should be able to approve themselves.
• Two people doing the same job produce visibly different quality and neither of them thinks they are wrong.
• New hires take far longer to become useful than their experience suggests they should.
• You have said “you’ll know it when you see it” and meant it sincerely.

The reframe: your judgment is real, and that is the problem

This is not a case of a leader with impossible standards. Usually the standard is excellent, hard-won, and the reason the company got here. The failure is that it was never externalized, so it cannot be taught, delegated, hired against, or held.

An unwritten standard is not a standard. It is a preference that people are graded against after the fact, and being graded on a rule you were never given is the fastest way to make a capable person stop trying to own anything.

What’s actually causing it

The standard stays in your head for reasons that are all individually reasonable:

Writing it feels like it would take longer than doing it. For any single instance, that is true. Across a year and four people it is wildly false, and the compounding runs the wrong way the whole time. This is the ignorance tax, paid weekly.

You do not think it is teachable. Most tacit standards decompose into three or four checkable conditions once someone forces the question. Genuinely irreducible taste exists but it is rarer than leaders assume, and assuming it is what keeps the whole company routed through one person.

Nobody is measured against it. When the bar exists only as your reaction, people are working toward a scoreboard they cannot see. They learn the rules by breaking them, which is expensive and slightly humiliating, and it teaches them to check with you rather than to decide.

Approving is faster than defining. Every approval you give is a vote to keep the standard private for another week. The approvals feel like leadership. They are the mechanism by which everything continues to run through you.

What to do next

Pick the one output you review most often. Next time you reject or fix a piece of it, write down what specifically was wrong, in the plainest terms available. Do that four or five times and you will be looking at your actual standard, in writing, without ever having had to sit down and author it.

Turn that into a checkable definition and hand over the approval with it. The first two rounds will come back imperfect. Correct against the written standard rather than against your reaction, and update the document when the correction reveals something the document missed.

Then make it structural: every core outcome gets a named owner and an expectation that is a number or a dated binary state with a source. That is what the Core Accountability System does, and the accountability chart guide is the working method.

As an operator I had field crews making calls that cost real money, and I treated it as a judgment problem in the people. It was a definition problem in me. They were deciding without a standard because I had never written one, and they were not going to stop deciding just because I had not.

Getting the standard out of your head and onto paper your team can run is the first quarter of most Executive Coaching engagements. If the work keeps coming back technically complete and somehow wrong, book a conversation.