Insight
Distance Creates Certainty, Proximity Creates Humility
Distance creates certainty. Proximity creates humility. In most executive rooms, the confidence and the customer contact belong to different people.
Listen to who hedges
Sit in a product strategy review and listen for qualifiers. The researcher who ran last month’s usage sessions says “the customers we observed” and “we don’t know yet whether this generalizes.” The support lead talks about specific tickets. Then the senior leadership in the room states what customers want, flatly, with no hedge at all, speaking from a picture built entirely of other people’s summaries.
The room treats the flat statements as seniority and the hedged ones as inexperience. Read it the other way. The hedging tracks contact. The people who talked to customers this month know exactly how messy the picture is. The people who read a two-page summary of a forty-page synthesis of a thousand tickets received a picture with the mess removed, and clean pictures produce clean convictions.
The false read
The usual diagnosis is personal: our executives are out of touch, and the fix is a listening tour or a customer-advisory board slot on next quarter’s calendar. That reading blames individuals for a condition the structure manufactures. Executive calendars fill with board meetings, investors, and planning because that is what the role demands. Direct customer contact loses that scheduling contest by default, so exposure falls precisely as authority rises. Swapping the executive changes nothing; the next one inherits the same calendar and the same summaries.
The mechanism: filtered pictures feel finished
Summarizing is necessary. Nobody at the top can read every ticket or attend every session, so each layer writes a shorter account for the one above. The problem is what the shorter account leaves out. Contradictions, outliers, context, and sample sizes are exactly what a good summary trims, and they are also exactly what would justify doubt. Each layer hands upward a picture that is smaller, cleaner, and more coherent than the one it received.
By the top of the ladder, the picture contains no visible reason to hesitate. So nobody hesitates.
That is the inversion. A leader who talked with ten customers yesterday speaks carefully, because they met the mess firsthand: they know what those ten said and they know it might not generalize. A leader briefed on a thousand customers speaks with total assurance, and what they actually possess, as the book puts it, is what one analyst thought after reading fifty support tickets. The confidence is real. The knowledge behind it is not. And an illustration like this pair is generous to the organization, because it assumes the summary was even accurate.
What the certainty costs
The expensive failures are the confident ones. Doubt triggers validation: a prototype, a test, another round of customer conversations. Certainty skips straight to commitment. When the certainty came from filtered reports, the organization makes its largest bets on its thinnest evidence and discovers the mismatch only after launch, when the market delivers the feedback the reporting chain could not. Leadership builds for the customer they imagine, not the customer that exists, and pays twice: once for building the wrong thing, and again for the recovery cycle that proximity would have made unnecessary.
The subtler cost is cultural. When flat certainty reads as executive presence and hedging reads as weakness, people learn to strip the qualifiers from what they pass upward. The organization starts selecting for confidence at exactly the altitude where confidence is least earned.
What changes when you flip the signal
Treat expressed certainty about customers as a proxy for distance from them. In practice that means asking one question before any significant customer claim settles a decision: when did the person making it last talk to a customer directly? The point of the question is calibration. A hedged report from someone fresh out of customer sessions deserves more weight than a confident summary three layers removed, and a decision process that weights them the other way is steering on the wrong signal.
Then shorten the distance for the decisions that matter most. The durable form is a standing rule: the people making a strategic product decision have recent, direct, unfiltered customer contact relevant to that decision, before they make it. A quarterly listening tour does not clear that bar.
Applied Test: measure the distance
The whole measurement is one number: the average days since your decision-makers last spoke with a customer directly. Take your last five strategic decisions, find that date for each person who made them, and average the gaps. Past thirty days, the confidence in the room is coming from the filtering rather than from customers. The inputs are calendar entries and a few direct questions, so the number is available inside a week, and it is the fastest read you have on how much abstraction your strategy is running on. The reusable procedure and its recognition cues live on the Customer Distance concept page linked above.
Sources and validation
This Insight applies the Customer Distance concept from Applied End-to-End Flow: Enterprise, in the Broken Feedback barrier. The ten-customer and thousand-customer contrast and the reporting-chain examples are illustrative constructions from the book, not empirical studies. The thirty-day threshold is the book’s diagnostic calibration.
Curtis Hibbs and Joshua Barnes are co-creators of Applied End-to-End Flow and co-authors of Applied End-to-End Flow: Enterprise. Their work combines enterprise diagnosis, value-delivery mechanics, and practical intervention patterns across strategy, portfolios, value streams, and teams.