The Good Question
and the Cost That Wasn't

I was in the middle of a meeting when his message arrived.

I didn't read it yet. I felt it.

My attention was already allocated. A team member dealing with something real. A project with a deadline that didn't move. Three things I hadn't finished from the day before. And now another message, from someone who, by all measures, was doing fine.

The nervous system doesn't read. It categorizes.

One more thing to process.

I opened it.

He had noticed something I hadn't thought about. Next week had an unusual number of public holidays. The standard procedure called for time reporting on Monday. Under normal conditions, that works. But these weren't normal conditions. The Monday report would fall in the middle of the holiday window. People would be scattered. Some would miss it. The data would be incomplete, and someone would have to chase it down afterward.

He wasn't writing to tell me about the problem.

He was writing to tell me he had a solution.

His proposal: ask the team to report their hours by Friday this week, partially in advance. Not a workaround. A prevention. He had seen the gap between the procedure and the actual week ahead, decided the procedure wouldn't hold, and came to ask for permission to deviate reasonably.

He didn't ask me to think.

He asked me to say yes.

I wrote back: very good idea, let's follow your plan.

He replied: Thank you :)

The conversation lasted maybe ninety seconds. I returned to everything else.

But I kept thinking about that reflex. The one that happened before I opened the message. The quiet categorization: another demand, another thing, another piece of attention going somewhere it hadn't planned to go.

It was wrong.

Not morally. Just mechanically. The reflex had misfired.

His message wasn't a demand on my attention. It was a deposit into future attention. He used sixty seconds of my time to absorb a problem that would have needed much more, later, under worse conditions. Incomplete timesheets. Follow-up messages. Frustrated people who thought they'd already submitted.

The math was backwards from what I had felt.

A question can look like a cost and function like a saving. The difference is invisible before you read it. And the reflex doesn't wait.

This is how well-functioning people disappear from a manager's radar.

Not because they leave. Not because they stop performing. But because they don't generate noise. The team member who is struggling pulls attention. The project that is failing pulls attention. The deadline that is approaching pulls attention. The person who is quietly handling things, seeing things ahead of schedule, managing the gap between policy and reality before the gap becomes a problem: that person sends the message that gets pre-categorized as load.

I know managers who have lost good people and not understood why. The exit interview said something vague. The real reason was quieter. For months, maybe longer, the person had been sending signals that kept getting filed in the wrong queue.

A good question isn't the one that is easiest to answer.

It's the one where the thinking was already done before it arrived.

That takes something specific. Not enthusiasm. Not competence in the generic sense. It takes the ability to read the system ahead of its next failure. To see that a procedure assumes a normal week and this is not a normal week. To propose a deviation without breaking the thing the procedure was designed to protect.

He did all of that.

And my first reaction was mild irritation.

I told him it was a very good idea.

He sent back a smile.

And the week will run more cleanly because of sixty seconds I almost classified as overhead.