The Unspoken Rule About Asking Why?

There are two ways to answer a question at work, and most leaders default to the wrong one.

Someone asks "why do you want me to do it this way," and the leader answers with steps. Again. Slower this time, maybe with more detail, but still steps. The person asking wasn't confused about the sequence. They were asking a different question entirely, and it went unanswered.

This is the third unspoken rule I want to name in this series on clarity of instruction: "if you need it explained, you're not ready."

It shows up as impatience when someone asks for context instead of just executing. We intend it to say "just trust the process", but it actually means "you're not allowed to be in the know". The rule assumes that asking why is a sign of resistance, or worse, a sign that someone can't handle the job. In my experience, it's usually the opposite. People who ask why are trying to do the job well. They're trying to understand the purpose, alignment or mission driving the instruction itself, so that when a judgment call comes up later, they know which way to lean.

What I saw on the floor

I recently trained a shift team on a production floor where the culture between shifts was openly competitive. Each shift protected its numbers. Information didn't transfer well at handoff, and there was an underlying assumption that the other shift was the reason for whatever went wrong. It wasn't hostile, exactly. It was just built that way, and nobody was asking why it worked that way, because it had always worked that way. The new Plant Manager wanted to lead differently.

Part of the training focused on what a handoff is actually for. Not the checklist version of a handoff, the mechanical "here's where we left off," but the purpose underneath it: process continuity and working together as a team for ultimate customer retention. Once that distinction landed, the behaviour started to shift too. Shifts began treating each other as partners in the same outcome rather than competitors measured against each other. That's a collaborative behaviour change, and it came from explaining the reasoning, not from adding another step to the handoff procedure.

Shortly after, the plant manager identified a record production day over 24 hours. I want to be careful here, because I don't have a controlled study proving the training caused that number. What I know is the sequence: culture shift toward collaboration, then a record day identified by someone who watches those numbers closely and had no reason to overstate it. It's a signal that something changed.

Why the why matters more now

Here's where I'll offer a generational lens: A lot of Millennials and Gen Z came up through a school system built on rubrics. Assignments came with explicit criteria. Grading explained itself. Purpose was attached to task as a matter of course, because that's how the instruction was designed to be received. So when someone from that generation asks "why does this matter," it's frequently not defiance. It's the same reflex that used to work in a classroom: find the task's place in the larger goal, then proceed with confidence.

When a leader skips the why, the instruction still lands, but the confidence doesn't come with it.

What follows can look like hesitation, or slower execution, or a question that seems to circle back to something "obvious." It's easy to read that as attitude, or as incompetence, or as somebody who just wants to be difficult.

I'd ask leaders to consider a different read first: missing context. Not every generational gap needs a diagnosis. Sometimes it's simply that one side was trained to expect purpose attached to instruction, and the other side was trained to give instruction without it.

This isn't a hard line between generations, and I don't think it should be treated as one. Plenty of people from every generation ask why. Plenty of people execute without needing it. The generational framing is one way to understand why the same missing why lands differently depending on who's standing in front of you, not a rule about who's right or wrong.

The practical shift

In our Clear Conversation Model, the why isn't an optional add-on to an instruction. It's part of what makes the instruction clear. "Do this because it matters for that" is a complete instruction. "Do this" is half of one. The other half is what the person is left to guess at, or worse, left to assume incorrectly.

If you're giving direction this week, try adding the sentence that is easy to skip. Not a speech, just the reason. "I need this by Thursday because the client review is Friday morning". It takes four extra seconds and changes how the person interprets the deadline. They stop treating it as arbitrary and start treating it as real and important.

The floor I trained didn't need more procedure. They needed to understand what the procedure was building towards. Once they did, the competition between shifts stopped making sense to them, on their own terms, without anyone forcing it.

That's the difference between compliance and understanding. Compliance follows steps. Understanding follows reasoning, and it tends to keep following it even when no one's watching.

Next week, I'll look at what happens when leaders assume a commitment was made just because nobody objected out loud.