How to Validate a Customer Insight Before Acting on It

Discovery produces raw material — observations, quotes, patterns, frustrations — that needs to be tested before it can be trusted. Acting on an unvalidated insight is a common and costly error in customer experience work: it produces solutions to problems that may not be real, or may be real in a different way than the initial observation suggested.

The three-tier confidence system is designed to make the validation status of every insight explicit. By tagging each insight as an assumption, an internally reasoned inference, or a validated finding, journey management builds a practice of epistemic honesty into the map itself. The confidence tag is not decorative — it determines what kind of action the insight justifies.

Assumptions: What We Think We Know

An assumption is an insight that has not yet been tested against customer evidence. It may come from internal experience ("we know that customers find the onboarding confusing"), from logic ("customers who don't activate within 48 hours tend not to convert"), or from domain knowledge ("users in this category typically have low technical confidence"). These may be true. They may also be significantly wrong.

Assumptions belong on the journey map because they structure thinking and reveal where inquiry is needed. But they should not be the basis for Big Solution development without further investigation. An assumption-backed Big Solution is a significant organizational investment in an unconfirmed hypothesis — and the history of product development is full of solutions that were built with conviction and then discovered to solve the wrong problem.

"Treating an assumption as a validated insight is not confidence — it is the absence of curiosity about whether you are right."

Internally Reasoned: Making the Logic Visible

An internally reasoned insight is one that has been examined by people with direct knowledge of the domain — customer service teams, sales teams, account managers, experienced designers — and found to be credible, consistent with what those people know, and coherent in its logic. It is not yet validated through customer research, but it has been stress-tested internally.

This tier occupies a specific and valuable position. It is stronger than a raw assumption because it has been examined; it is weaker than a validated insight because the examination has not included the customers themselves. In practice, internally reasoned insights are often the basis for the first round of Big Solution development — there is enough confidence to invest in a test, but not yet enough to invest in deployment.

The key requirement for this tier is making the reasoning explicit. "We believe this is true because [specific evidence or argument]." When the reasoning is visible, it can be challenged, refined, or confirmed by subsequent customer research.

Validated: Evidence from the Source

A validated insight is one that has been confirmed through direct customer research — interviews, surveys, behavioral data, usability tests, or some combination. It is not necessarily final: customers change, contexts shift, and new evidence can revise validated findings. But it represents the organization's most reliable current understanding of the customer experience.

Validated insights justify the highest levels of investment. A Big Solution addressing a validated insight should expect to see experience score improvement, because the pain or need it addresses has been confirmed as real. If the score does not move as expected, the question is not whether the insight was real — it is whether the solution addressed it effectively.

How to Move Between Tiers

Validation is not a single event — it is a process. Moving an insight from assumption to internally reasoned requires internal examination: bringing the insight to the teams closest to customers and stress-testing it against their direct experience. Moving from internally reasoned to validated requires customer research: conversations, observations, or data that confirm the insight against its source.

The validation cycle is iterative. An internally reasoned insight that gets challenged in customer research may turn out to be partially right, right about a different customer segment, or systematically wrong in a way that reveals something more important. The journey map should be updated to reflect what was learned, not just whether the original hypothesis was confirmed.

The practice of making confidence levels explicit is ultimately a practice of humility: acknowledging that organizational knowledge about customers is always provisional, always in need of renewal, and always improved by returning to the source.