The quality of a business decision is capped by the quality of the information that reached the person deciding. Most poor decisions are blamed on judgment when the failure happened earlier, along the path the information travelled. Listening is not a courtesy in that path. It is the mechanism that determines what the decider knows.
Judgment Gets Blamed for an Input Failure
Post-mortems on bad decisions follow a familiar shape. The decision is examined, the reasoning is reconstructed, and the conclusion is that someone misjudged the situation.
That conclusion is usually wrong in an important way. The reasoning was often sound given what the decider knew. What was missing was a fact that existed inside the business and never arrived.
Somebody knew the supplier had been late three times running. Somebody knew the new process was being bypassed. Somebody knew the customer had already threatened to leave.
None of that reached the meeting where the decision was made. The information existed, it was accurate, and the path from the person holding it to the person needing it was broken.
The misattribution persists because judgment is a satisfying explanation. It identifies a person, assigns responsibility, and closes the review without requiring anything structural to change.
An input explanation is less satisfying and more useful. It names a route that failed, and routes can be repaired by people other than the one who made the call.
Treating that as a judgment failure guarantees repetition. Better judgment cannot compensate for absent inputs, and training decision makers to think more carefully does nothing about what they are thinking with.
What Filters Information on the Way Up
Information degrades as it travels upward, and the degradation is systematic rather than random.
The first filter is relevance. Each person passing information along decides what matters, and those decisions are made without knowing the question the decider is trying to answer.
A detail that seems minor at one level can be decisive at another. The person who trims it is not careless. They lack the context that would reveal its importance.
The second filter is consequence. People assess how a piece of information reflects on them before deciding whether to pass it on. Bad news about work someone owns travels slower than bad news about work they do not.
The third filter is effort. Raising a concern costs time and social capital, particularly when the concern is provisional. Where the cost of raising something exceeds the perceived chance of it mattering, it stays unraised.
The fourth filter is history. People who have raised concerns before and watched nothing happen stop raising them. That silence is frequently mistaken for agreement.
A fifth filter operates in the opposite direction and is less discussed. Information that confirms a direction already announced moves upward quickly, because carrying good news is rewarded.
The combined effect is a distorted picture rather than an incomplete one. Optimistic material arrives promptly while contradicting material arrives late, which makes the distortion hard to detect from the top.
Every filter operates quietly, and none of them announce themselves. What arrives at the top is a cleaned, flattened version of reality that feels complete because nothing visible is missing.
Listening as a Structural Function
Listening is usually discussed as an interpersonal skill, which underplays what it does inside an organisation.
Its practical function is to reverse the filters. A person who asks the right question at the right moment recovers information that the transmission chain removed.
The skills involved are specific rather than general warmth. Asking about disconfirming evidence rather than supporting evidence. Asking what would have to be true for a different conclusion to hold. Waiting through silence instead of filling it.
The most productive question in most operational conversations is what someone would do differently if the decision were theirs. It surfaces reasoning rather than conclusions, and reasoning is where the useful detail sits.
A grounded account of how attentive questioning recovers information that reporting lines strip out treats these behaviours as operating technique rather than manner.
What people are asked also shapes what they can give. General invitations to share thoughts produce reassurance, since nobody knows which of the many things they know is wanted.
Specific questions produce specific answers. Asking what worried someone about a plan retrieves more than asking whether they have any concerns, because the second version invites a simple denial.
The distinction matters because manner is optional and technique is not. A leader can be warm and still receive nothing useful, and can be blunt while extracting exactly what the situation required.
Building Inputs Into the Decision Itself
Relying on individual attentiveness leaves the input problem unsolved, because attentiveness varies with mood, workload, and the pressure of the day.
The durable answer is to build input collection into the decision process, so that it happens regardless of who is deciding or how busy they are.
One practice is to name, before the decision, who would know if this were a bad idea. Those people are then asked directly rather than waiting for their view to surface on its own.
Another practice is to ask the same question of people at different levels. Agreement across levels is informative. Divergence is more informative still, and it is invisible when only one level is consulted.
A third practice is to separate the gathering of inputs from the making of the choice, with time in between. Compressing both into one meeting means the first opinion voiced anchors everything after it.
A fourth practice is to record what was known at the time, alongside the decision. Reviewing that record later distinguishes bad judgment from missing information, which are two problems with entirely different remedies.
None of these practices require additional meetings. They require the existing preparation time to be spent differently, on retrieval rather than on assembling a case.
Structured approaches to how a business should organise the steps around a significant choice place input gathering ahead of analysis for exactly this reason.
Which Decisions Are Most Exposed
Some decisions are far more vulnerable to filtered information than others, and knowing which ones focuses the effort.
Decisions about people are the most exposed. Performance problems and departures are preceded by signals that everyone nearby noticed and nobody escalated, because escalating carries a personal cost.
Decisions about customers rank next. Sales teams have accurate information about dissatisfaction and strong incentives to present it optimistically until it becomes undeniable.
Decisions about process changes are exposed differently. The people who know why a step exists are usually junior, and the people redesigning the process usually do not ask them.
Decisions about vendors and systems are exposed through enthusiasm. Whoever championed a tool becomes invested in it, and their reporting on its performance stops being neutral without anyone acting in bad faith.
Decisions about pricing sit in a category of their own. The people who hear objections are the furthest from the pricing decision, and their observations arrive summarised into a single claim that the price is too high.
That summary destroys the useful content. Which customers objected, at what stage, and against which alternative are the details that would change the decision, and they rarely travel intact.
Decisions made under time pressure are exposed across every category, since the first thing dropped when a decision is urgent is the consultation that would have improved it.
What Changes When Inputs Improve
Businesses that fix the input path notice the effect in the pattern of surprises rather than in any single decision.
Bad news arrives earlier and smaller. Problems get raised while they are still cheap to address, rather than after they have grown large enough to be undeniable.
Meetings change character. Less time goes to establishing what is happening and more goes to deciding what to do, because the establishing part has already occurred.
Reversals become less frequent. Decisions that were made with the relevant objection already on the table tend to survive contact with reality, since the obvious failure modes were considered rather than discovered.
Confidence in decisions changes character too. Certainty built on consultation holds up under challenge, while certainty built on a clean report collapses the moment a contradicting fact appears.
Staff behaviour shifts as well. People who see their input change an outcome raise things sooner, and the effect compounds without any policy encouraging it.
The change is also measurable in a rough way. Counting how often a decision was later described as obvious in hindsight gives a usable signal, since hindsight obviousness usually means somebody knew.
The visible result looks like better judgment at the top. What actually improved was the supply chain feeding it.
The framing here is deliberately unflattering to decision makers, and that is the point. Attributing outcomes to judgment places the entire explanation inside one person, where it cannot be examined or fixed by anyone else. Treating it as an input problem makes it an operating problem, with observable causes and available remedies. A business cannot make its leaders wiser on demand. It can change who gets asked, when they get asked, and what happens to what they say, and those changes are available immediately.
Frequently Asked Questions
How do you tell a judgment failure from an input failure?
Ask whether anyone in the business knew the missing fact at the time. If someone did, the failure was in transmission rather than reasoning, and the remedy is structural. If nobody knew, the question becomes whether the information was obtainable and whether anyone was assigned to obtain it. Recording what was known at the moment of decision makes this distinction possible later.
Why do people withhold information from senior leaders?
Rarely from disloyalty and usually from a reasonable calculation. Raising a concern costs time, invites scrutiny, and may reflect badly on the person raising it or on someone they work with daily. Where previous concerns produced no visible response, the calculation shifts further toward silence. The behaviour responds to consequences rather than to encouragement.
What single question improves input quality most?
Asking what someone would do differently if the decision were theirs. It bypasses the instinct to agree and surfaces reasoning rather than a verdict. Follow-up questions about what would have to be true for a different answer to hold tend to expose assumptions nobody had stated. Both questions work better in private than in a group.
Does this apply in a small business where everyone talks daily?
Proximity helps and does not eliminate the filters. Consequence and effort still operate, and in a small company the social cost of raising a concern about a colleague can be higher rather than lower. What smaller businesses gain is speed of correction once something is raised. What they lack is any formal route when the informal one feels risky.
How should input gathering fit into an urgent decision?
By shortening the list rather than skipping the step. Naming two or three people who would know if the decision were wrong, and asking them directly, takes very little time. Urgency removes the possibility of broad consultation and does not remove the need for the most relevant objection. Decisions made fast and blind are the most reliably reversed.
What if the information arriving is simply wrong?
Inaccurate input is a different problem from absent input and needs a different response. The remedy is asking how someone knows, rather than whether they are certain, since confidence and accuracy correlate poorly. Tracing a claim back to its source usually reveals whether it is observation, inference, or repetition. Doing this consistently also teaches people to arrive with the basis for what they assert.
No comments:
Post a Comment