The Unspoken Rule: You Should Already Know What "Good" Looks Like

When my eldest was two, I asked them to bring the dish from the TV table to the kitchen.

They came back with a toy.

I remember standing there for a second, confused. Impatience and frustration began to mount I'd said "dish." I'd pointed, sort of, in the general direction. To me, the instruction was complete. Obvious, even. But my two-year-old came back with something else entirely, and it wasn't because they were being difficult or not listening. It was because the word "dish" hadn't landed the way I meant it. Whatever picture formed in their head when I said that word, it wasn't a dish. They were eager to help, but I hadn't given enough context. I made an assumption.

That gap between the word in my head and the picture in theirs is the same gap I see in workplaces every week.

Leaders ask for "good work." They ask for something "done well." They want "quality"; they want people to be "professional." They assume, often without ever examining the assumption, that everyone hearing those words is picturing the same finished result they are.

They're not.

There's an unspoken rule sitting underneath a lot of workplace frustration: I don't need to define "good" because obviously everyone knows what I mean. It feels so self-evident that it doesn't even register as a rule. It just feels like common sense. Of course people know what good looks like. Of course "professional" means something universal.

Except it doesn't. Not automatically, and especially between generations. Here's why this rule sticks around so persistently. Leaders can see the finished result. They've built it, or watched it get built, dozens or hundreds of times. The picture in their head is vivid, detailed, complete. It is easy to assume the clarity is contagious, that simply saying the word "quality" will transmit the whole picture to the other person, the way a photograph transmits an image just by existing.

But a word is not a photograph. A word is a container, and different people fill it with different contents based on what they've seen, what they've done, and what "good" has meant to them in every previous context where that word showed up.

This is where the real cost lives. Not in incompetence. Not in people not trying hard enough. The cost shows up as redone work, as a leader quietly frustrated that something "obvious" wasn't delivered, as an employee quietly frustrated that they did what was asked and it still wasn't right. Nobody's wrong here. Nobody's careless. Two people are just operating off two different definitions of the same word, and neither one took the time to speak the details or ask for clarifications.

Someone who came up through an apprenticeship-style environment, watching the same tasks done the same way for years before ever being asked to do them independently, absorbs an enormous amount of unstated standard simply through repetition and osmosis. Someone newer to a role or a field hasn't had that same runway. It's not about effort or attitude. It's about how many hours a person has logged watching "good" happen (and how consistent that demonstration was) before being asked to produce it themselves.

Inside Our Clear Commitment Process, identifying what "done" or "good" actually looks like, in specific and observable terms, before the work begins rather than after it disappoints someone.

This is week four of our five-week series on the invisible rules quietly running workplace instruction. Next week, we bring all four rules together and look at what they actually cost when left unexamined.