A few days back, I posted a short note, and it landed more than I expected:
The calendar is full. The output is visible.
The team needs decisions. Nothing about the day looks like avoidance.
The reason action-oriented procrastination works so well on high performers is that the alibi is real.
Meanwhile, the question that keeps returning is the only thing that never makes it into the metrics. Which is exactly why it keeps returning.
Which made me think about what happens when that pattern runs not just with one person but inside an organization.
Because when a leader carries an unasked question, it does not stay with them. It travels.
Behavioral economists O’Donoghue and Rabin described this already in 1999: present bias makes us systematically overweight what is happening now and discount everything else, including the questions we know matter.
The immediate task is concrete. The deferred question is abstract.
The choice is not conscious. It is structural.
At the individual level, this is uncomfortable. At the organizational level, it is consequential.
A leadership team is a remarkably accurate reading instrument. Not of what the leader says but of what the leader consistently doesn’t say.
When a CEO systematically routes around a particular topic — the underperforming partnership, the structural cost that has been "temporary" for eighteen months, the team dynamic that everyone in the room already knows about — the organization doesn’t miss it. First, it registers it, and then it adapts.
People stop bringing things that belong to that category. Not because they were told to. Because they learned, through repetition, that those things don’t move:
In my experience, both in-house and as a consultant, employees have withheld important information from their manager because they feared the consequences of speaking up. The fear is rarely about formal punishment. It is about reading, accurately, what the leader is and is not prepared to engage with.
The unasked question doesn’t disappear. It becomes the organizing principle around which everything else quietly arranges itself.
Action-oriented procrastination works precisely because the alibi is real. The calendar is genuinely full. The priorities are genuinely urgent. There is no obvious moment of avoidance — only a sustained pattern of it.
At the organizational level, the same mechanism runs with additional cover: the metrics look fine, the team is executing, the board deck shows progress on the things that were tracked. The question that was never asked is, by definition, not in any report.
This is where the cost accumulates invisibly. Not in the numbers that are tracked — in the gap between those numbers and what is actually generating them.
Most organizations measure outputs well. They measure the behavioral layer that produces those outputs almost not at all. The unasked question lives in that layer. It is rarely about strategy or people. It is about what is producing the pattern that neither one explains. And it compounds there, until the gap between reported performance and actual performance becomes impossible to explain away.
The same topic gets "tabled for next time" across more than two consecutive meetings. Once is scheduling. Twice is coincidence. Three times is a decision, even if no one named it as one. Scan your last six meeting notes for repeated follow-ups without resolution. The pattern is usually visible before the problem surfaces.
Your team prepares differently for certain topics than for others. When a subject consistently arrives with unusually thorough documentation, pre-aligned positions, and minimal spontaneous discussion — that preparation is protective. People have learned this topic requires armor. The question worth asking: what are they protecting against?
The explanation for a recurring problem changes, but the problem doesn't. Different quarter, different reason, same outcome. When the explanation is always new and the result is always familiar, the explanation is functioning as cover. The pattern underneath it has not been addressed because the question that would surface it has not been asked.
You know what the question is. This is the most reliable signal. There is usually not much mystery about which question has been waiting. The CEO who has been meaning to revisit the partnership structure knows. The one who has been meaning to have a direct conversation with a specific leader knows. Knowing and asking are two separate events. The distance between them is where the cost lives.
Not always what you expect. Sometimes the answer is less alarming than the avoidance suggested. Sometimes the structural problem turns out to be smaller than the silence around it.
When leaders model direct attention to difficult topics, the category of things the team is willing to surface expands. People start bringing things earlier: before they become the kind of problem that requires a perfectly prepared explanation.
The question that keeps returning does so for a reason. It is not going away because the calendar is full. It goes away when it gets answered.
Every month it doesn’t is a decision. Like any decision, it has a cost. Unlike most decisions, this one rarely shows up in the metrics.
Until it does.
Yours truly,
Irina
Find your next edge
Subscribe to the weekly newsletter
to see The Behavioral Yield in action.