Insight doesn't create change. Decisions do.

There is a predictable frustration in organisations that invest seriously in research and insight. The work is good. The findings are clear. The implications are well-articulated. And then, six months later, almost nothing has changed.

This is not unusual. It is, in fact, the norm. Most organisations are significantly better at generating insight than acting on it. The capability to understand has outpaced the capability to decide.

Understanding why this happens - and what to do about it - matters more than most organisations realise.

Where insight goes to die

The most common fate of insight is the report. A well-produced, carefully written document that presents findings, draws conclusions, and makes recommendations. It is read by some, skimmed by others, and filed by most. Occasionally it is referenced in a presentation. Rarely does it become the basis for a specific decision with a clear owner and a defined timeline.

This is not a failure of insight quality. It is a structural problem. Research and insight functions are typically designed to produce outputs, not to drive decisions. The implicit contract is that the insight team generates understanding, and the business unit or leadership team converts it into action. This handoff rarely works as intended.

The reason is that making a decision is harder than receiving information. A decision requires commitment. It requires accepting trade-offs. It creates accountability. It can be wrong in a way that a report cannot. And it often requires navigating internal disagreement about what the findings actually imply.

When insight is presented as a deliverable rather than as an input to a structured decision process, it sits at the start of that harder work. Without a mechanism to move it forward, it tends to stay there.

The gap between knowing and doing

Behavioural science has a name for the broader phenomenon: the intention-action gap. People and organisations consistently overestimate how reliably understanding produces behaviour change. Knowing that something is true does not automatically produce the motivation, coordination, or follow-through required to act on it.

In an organisational context, this gap is compounded by several structural factors.

Insight often arrives without a clear decision attached to it. It is produced because it seemed like useful knowledge to have, not because a specific choice was pending. When there is no decision waiting to receive it, the insight floats. It may eventually connect with a decision, or it may not.

Insight often arrives too late. By the time research is complete and findings are presented, the relevant decision has already been made on the basis of intuition and available information. The insight confirms or complicates what was decided, but does not change it.

And insight often arrives without the framing needed to drive action. Presenting findings is different from presenting a decision. A decision has options, trade-offs, a recommended direction, and an identified owner. Most insight outputs do not include these elements, which means the translation work has to happen separately - if it happens at all.

Designing for decision, not for delivery

The organisations that close the gap between insight and action tend to do one thing consistently differently: they start with the decision, not with the research.

Before any research is commissioned, they ask: what decision does this need to support? Who makes that decision? What would they need to believe to go in a particular direction? What information do they not currently have that this research could provide?

This changes the nature of the research brief fundamentally. The output is no longer a report presenting findings. The output is a recommendation - a clear position on what the organisation should do, supported by evidence and analysis, framed in terms of the specific choice being made.

This also changes what the insight function is accountable for. The measure of success is not whether the report is good. It is whether the decision was made, and whether the decision was better as a result of the insight.

The role of insight in the decision process

Treating insight as an input to decision-making rather than a deliverable in itself requires rethinking where the insight function sits in organisational processes.

Insight should be involved earlier - at the point where decisions are being framed, not after they have been partially made. The most valuable contribution of an insight function is often not the research itself but the framing: helping decision-makers understand what question they are actually trying to answer, and what would constitute a satisfying answer to it.

Insight should also be involved later - in the implementation and learning cycle, tracking whether the decisions that were made are producing the expected results, and feeding back what is being learned. This creates the kind of institutional knowledge that makes future decisions faster and better.

The handoff model, in which insight produces a report and passes it to a decision-maker, is the least effective version of how this can work. The most effective version is a continuous conversation in which insight is woven into the decision process from framing to outcome.

What this requires of leadership

None of this happens without leadership that treats decision-making as a process that deserves investment.

That means creating structured decision points with clear owners and timelines, rather than allowing decisions to drift or be made informally without documentation. It means demanding that insight be connected to a specific choice, not produced as general knowledge. It means holding the insight function accountable for influencing decisions, not just producing outputs.

It also means being willing to make decisions on the basis of insight even when that insight is incomplete or uncomfortable. The alternative - waiting for more information, or ignoring findings that complicate the preferred direction - is how organisations end up with expensive research libraries and unchanged behaviour.

Insight is necessary. It is not sufficient. The gap between knowing and doing is closed by decision, not by understanding. Designing organisations to make that connection reliably is harder than commissioning research. It is also where the real value lies.