Fifty Shades of Blank

The people doing the work will do exactly what you asked, even when what you asked makes no sense.

Years ago, earlier in my career, I was running an installation project along a pipeline. We were putting in monitoring stations and systems at various points, and every single piece of equipment had to be labeled with a unique identifier. Small brass plates, hand-punched by our production team, one tag per component.

There were over a hundred of them. The client also asked for fifty blank tags for future use.

I wrote up the production order. MS-1, MS-2, MS-3, all the way through the list. At the bottom, I added a line. "Fifty blank tags."

A few days later, the order came back. I went down to do a quick check for accuracy before shipping. There they were. All the unique identifier tags, exactly as ordered. And underneath them, fifty more.

Each one with the word "BLANK" meticulously hand-stamped across the face.

I stood there for a long moment.

It is hard to describe the specific feeling of looking at fifty pieces of brass that have been carefully and patiently stamped with a word that was not supposed to be on them. Each tag took real effort. Someone had set it up, lined up the letters one at a time, B, L, A, N, K, and then done it again. Forty-nine more times. They had not asked. They had not questioned it. They had assumed I knew what I wanted.

I had asked for fifty blank tags. They had delivered fifty blank tags. To the letter.

And somewhere in the production shop, there was a worker who had spent a full afternoon making fifty tags that said BLANK, and they almost certainly went home that night and told their family about the dummy who put in the order.

What it actually taught me

The easy lesson here is about communication. Be specific. Be clear. Do not assume people will read your mind. All true, and I do think about it that way sometimes.

But the lesson that has stayed with me longer is bigger than that. It is about how teams respond to leaders.

The production worker who made those tags was not stupid. They were almost certainly not happy about the assignment. They probably thought, somewhere around tag number fifteen, that this was a strange request. But they did not stop and call me. They did not ask if I really meant it. They did not push back.

They just did what I asked, because I had asked for it.

That is the part worth sitting with. The default in most organizations is that when a leader puts something in writing, especially someone with authority, the assumption is that the leader meant it. The team will execute. Even when the request makes no sense. Even when something is clearly off. Even when the person doing the work knows in their bones that this cannot be right.

I have thought about that a lot in the years since. Because the higher I have gone in organizations, the more this dynamic has shown up in ways that mattered far more than fifty brass tags.

People hesitate to question the request. They assume the boss meant it. They go execute, and they figure it out as they go.

That puts more weight on the leader than most leaders realize. The clarity of what you ask for, the specificity of what you actually want, the explicit invitation to push back if something seems off. None of that is optional. It is part of the job.

Fifty tags that said BLANK was a funny way to learn it. It is not a lesson I have ever needed to learn twice.