Customer Signal Framework

Not every observation in a customer conversation is a signal.

Most are noise — specific to one customer, one context, one moment. Useful for that customer. Not useful for building a strategic narrative.

The Customer Signal Framework provides a structure for distinguishing between the two — and for connecting genuine signals to the narratives they support.

What makes an observation a signal?

An observation has potential strategic value when it meets one or more of these criteria:

Recurrence — The same observation appears across multiple customers, in similar language, describing similar experiences. Recurrence suggests a pattern rather than an individual circumstance.

Cross-source validation — The observation echoes something already present in research data, practitioner interviews, or market evidence. When a customer describes a problem that the research has already identified, both pieces of evidence become stronger.

Strategic relevance — The observation connects to a position the organisation is trying to own or a narrative it is trying to develop. Not all genuine patterns are strategically relevant — the framework focuses on those that are.

Tension or surprise — The observation reveals something unexpected, contradicts an assumption, or exposes a gap between how the organisation understands the problem and how customers experience it. Tension often indicates the most valuable signals.

The signal classification

When reviewing customer conversations, observations can be classified into four categories:

Core signals — Recurrent, validated, strategically relevant. These feed directly into narrative development.

Emerging signals — Appearing in more than one conversation but not yet validated across sources. Track these for recurrence.

Contextual signals — Specific to one customer but rich enough to inform future interview design or product thinking. Useful, but not yet narrative material.

Noise — Individual observations with no apparent pattern or strategic relevance. Document briefly, do not develop further.

Connecting signals to narratives

A signal is only as useful as the narrative it feeds.

The connection process works in both directions. An existing narrative should generate questions: what signals would confirm this narrative, and are we finding them? A new signal should generate questions: what narrative could this support, and do we have enough evidence to develop it?

The Hidden Hours narrative developed through this bi-directional process. The narrative emerged from signal recurrence — accountants consistently describing the same operational pressures. But the narrative then shaped subsequent signal collection: interviews and surveys designed to test and extend the position, not just to gather general feedback.

Practical application

The framework is most useful in three contexts:

Interview design — Structuring customer conversations to surface signals that connect to existing narratives, while remaining open to emerging ones.

Evidence review — Periodically reviewing accumulated customer observations to identify patterns that have been missed or that have grown stronger over time.

Narrative validation — Testing whether a proposed narrative is supported by sufficient customer signal, or whether it is still primarily assertion.

In each context, the goal is the same: to move from individual customer observations to structural insights that support strategic positions the organisation can own and develop over time.