The Data You Already Have and Never Read

What your exit interviews, complaint files, and survey notes were always trying to say

Jun 19, 2026

Somewhere in most organisations there is a folder, a shared drive, or an archived system containing several years of things people said. Exit interview notes. Customer complaints in their original form, before they were categorised and counted. Free-text responses from the bottom of annual surveys. Messages sent to a service team that were resolved, closed, and filed. Forum posts from an internal platform that was replaced two years ago and whose contents were migrated to storage rather than deleted.

None of it has been read systematically. Most of it never will be.

This is not a data problem. The data exists. It is a processing problem — or rather, it was. For most of the period in which this material was accumulating, there was no practical way to analyse it at scale without a significant investment in qualitative research that most organisations could not justify for data they had not planned to use. So it was treated as administrative residue: kept because deletion felt risky, ignored because analysis felt impossible.

That calculation no longer holds.

The signal that was never treated as data

The gap between what organisations collect and what they analyse has always been widest in the qualitative register. Numbers get processed. Text gets filed.

This is partly a legacy of the tools available. Survey platforms were built to aggregate ratings, not to synthesise narratives. CRM systems were built to track transactions, not to find patterns in how customers described their experience. HR systems were built to record headcount and performance scores, not to make sense of what people wrote in the comments field at the bottom of the appraisal form. The architecture of most organisational data infrastructure assumes that what matters can be counted.

The consequence is that organisations have spent years collecting a secondary record of their own reality — the version in which people spoke in their own words, described their own experience, and articulated what the numbers could not carry — and treating it as noise.

Exit interviews are the clearest example. Most organisations conduct them. Most collect the responses in some form. Very few analyse them across a period long enough to identify patterns — which managers people were leaving, which structural conditions were driving attrition, which aspects of the culture were named repeatedly by people who had decided to leave but no longer had any reason to be diplomatic. The data exists. The analysis that would make it useful never happens, because exit interview findings are processed as individual cases rather than as a cumulative record.

Customer complaints follow the same logic. The categorised version — number of complaints by type, by channel, by product — reaches a dashboard. The original text, in which customers described in specific terms what had gone wrong and what it had cost them, is archived after the case is closed. Organisations that have been collecting complaints for five years have five years of precise, unsolicited qualitative description of the gap between what they promise and what they deliver. Almost none of them have read it.

What changes when the analysis becomes possible

The shift that is underway is not primarily about new data. It is about the retroactive value of data that already exists, and the prospective design of data collection with analysis in mind from the start.

AI-assisted qualitative analysis has made it practical to process large volumes of unstructured text in ways that were previously either manual and expensive, or automated and crude. The earlier generation of text analytics tools — keyword frequency, sentiment scoring — reduced qualitative data to a thin quantitative proxy. What is becoming possible now is closer to genuine synthesis: identifying themes, finding patterns, distinguishing between types of concern that look similar in aggregate but are structurally different in cause.

The organisations best placed to use this capability are not necessarily the ones with the most sophisticated data infrastructure. They are the ones that recognise they have been sitting on material with analytical value and begin treating it as such. A charity with three years of service user feedback in a case management system. A professional services firm whose client debrief notes have been saved but never reviewed across engagements. A healthcare trust whose patient letters — the ones written by people who felt strongly enough to put something in writing — are archived in a folder that no analyst has opened.

The design question for new data collection is equally important. When an organisation understands that qualitative responses have analytical value, it changes how it structures the collection. Open-response questions get asked more deliberately. Free-text fields get positioned earlier in a survey, not appended as an afterthought. Platforms are chosen with synthesis in mind rather than just with response rates in mind. Tools such as Gobby.io, which combines open response with peer-powered voting — where participants indicate which responses reflect their own experience — produce data that is both richer and more efficiently analysable than free text alone, because the participants have done part of the synthesis work before the data reaches an analyst.

What the evidence was saying all along

The most significant implication of this shift is not operational. It is about what organisations know about themselves, and what they have chosen not to know.

An organisation that has been collecting qualitative signal for years and never analysed it has, in practice, been making decisions without a significant part of the available evidence. That is not a neutral position. It means that the version of reality reaching leadership has been shaped by what the data infrastructure was designed to draw out — typically the quantitative, the recent, and the aggregated — and has excluded everything the data infrastructure was not built to carry.

When that material becomes analysable, organisations sometimes discover that the patterns were visible all along. The attrition problem that presented as a compensation issue in the survey data was described, repeatedly and specifically, in exit interview notes as a management culture problem in a particular division. The customer satisfaction decline that appeared as a score movement in quarterly reporting had been articulated, in precise terms, in complaint correspondence two years earlier. The service redesign that failed to achieve adoption had generated, during its consultation phase, a clear account of the operational reality it failed to account for — an account that was collected, filed, and never read.

None of this means that quantitative data is wrong or that qualitative analysis is always right. It means that organisations have been working with a partial picture and treating it as complete. The data to fill that picture, in many cases, already exists.

The question is whether the organisation is prepared to read it.

My Opinion

I have been through more exit interviews than I can count, and almost all follow the same pattern: questions designed to measure the process, not to capture what the person leaving actually thought. I have asked to read exit interviews from people who left teams I was responsible for and been met, more than once, with a blank look or a direct refusal. A genuine caveat applies: this data is shaped by why someone left, which means it needs to be read in context rather than taken at face value. But there is a difference between data that requires careful reading and data that is never read at all. The true voice of people is the thing most organisations consistently arrange not to hear.

The Next Evolution

Discussion about this post

Ready for more?