I’ve been thinking a lot lately about what happens to insights after the research is over.
That may sound like a strange place for a researcher to focus. Most of our professional energy is spent getting to the insight in the first place — whether the study is designed well, whether we recruited the right people, whether the questions are framed carefully, whether the analysis is rigorous, whether the story we tell is faithful to what we actually learned. Those concerns matter enormously, and I don't want to minimize any of them.
But the longer I do this, the more I find myself wondering whether some of the greatest threats to insight happen after the work is technically complete.
I’ve seen thoughtful, beautifully executed research produce insights that were clearly true, strategically relevant, and emotionally resonant, and still changed very little. I’ve also seen ordinary research, nothing flashy or especially sophisticated, create disproportionate action inside an organization because it landed at the right moment with the right people in the room. That contrast has stayed with me because it suggests something about our profession: an insight can be accurate, compelling, and timely, and still fail to inspire change. It can be presented clearly, supported responsibly, and delivered with all the right caveats, and still somehow disappear into the machinery of the organization it was meant to influence.
Most insights do not die because the research was flawed. They die because organizations are complicated places, and the path from learning to doing is much longer, messier, and more human than we often pretend.
The long journey from learning to action
Rational thought suggests that better understanding naturally leads to better decisions. It’s a comforting assumption, especially for those of us who have built careers around helping organizations understand people more deeply. If teams could just hear from customers, see the data, feel the emotional texture behind a behavior, surely they would make wiser choices. I’ve seen that happen, but not always.
Here’s another rational truth: organizations are not empty rooms waiting for insight to arrive. By the time research enters the conversation, there are already strategies in motion, budgets approved, roadmaps built, concepts socialized, executive opinions formed, and teams emotionally invested in the direction they’ve been pursuing. The research may be new, but the organization is not. It already has momentum, which is difficult to interrupt.
That’s why insights often face their hardest test not during fieldwork or analysis, but in the meeting where people must decide what the learning means for the business. In that room, the insight stops being just an interpretation of human behavior. It becomes a potential disruption — something that may ask someone to rethink a decision, slow down a launch, revisit a positioning strategy, challenge a beloved idea, or admit that a product, message, or assumption isn't working the way the organization hoped. At that point, the discussion is no longer purely about what people said, did, felt, or needed. It's about consequences.
The cost of accepting an insight
I don’t think organizations reject difficult insights because people are careless or indifferent. In my experience, most clients and stakeholders genuinely want to make good decisions that serve their customers well. The problem is that accepting an insight often creates an obligation, and obligations are much harder to embrace than information.
A confirming insight is easy to love. When research tells a team that consumers understand the message, appreciate the experience, or feel exactly the way everyone hoped they would feel, the organization can move forward with confidence. The research becomes fuel. If consumers do not understand the message, someone has to revisit the strategy. If an experience creates friction, someone has to decide whether the fix is worth the operational burden. If a product concept solves a real problem but not the one the organization expected, someone has to determine whether the team is willing to follow the need instead of the original idea.
That is where great insights often begin to lose oxygen. The conversation shifts from “What did we learn?” to “What momentum is lost if we follow this path?” – and that second question carries budgets, timing, organizational credibility, career risk, and sometimes an admission that a team may have been confidently heading in the wrong direction. Research professionals like to believe that truth has its own force, and in some ways it does. But inside organizations, truth still has to compete with sunk costs, deadlines, incentive structures, personal attachment, political capital, and the very human desire to avoid embarrassment. The insight remains as true as it ever was. It just harder to act on.
The conference room as the final research environment
We spend a lot of time studying consumer behavior and comparatively little studying the organizational behavior that determines whether consumer insight becomes action. That feels like a missed opportunity, because organizations behave in surprisingly human ways. They have habits, protect familiar routines, avoid loss, and seek confirming evidence while overvaluing what they have already built. They develop shared stories about what is true, and those stories can become difficult to revise even when new evidence appears. Plainly: it’s bias at work.
In consumer research, we would never assume that people make decisions based entirely on rational evaluation. We know behavior is shaped by emotion, context, social pressure, habit, and perceived risk. Yet when we step into organizations, we sometimes act as if a well-supported insight should be enough to overcome all of that. But it usually isn’t. A conference room has its own psychology. People are thinking about what the findings mean for their team, their priorities, their next milestone, their boss’s expectations, and the decisions already made in previous rooms. Even when everyone is listening sincerely, they are not listening from neutral ground.
That is why stakeholder engagement matters so much. It is not simply about socializing the findings or giving everyone a chance to feel included – it’s about helping the organization build enough shared context before the readout that the insight does not feel like an external verdict dropped onto the table at the end. When stakeholders have observed the research, heard the consumer language, felt the contradictions, and watched the patterns form over time, the findings become part of the organization's own lived experience rather than someone else's interpretation. Insights rarely survive on logic alone. They survive when people feel enough ownership of the learning to carry it into the next decision, which happens in the next conference room among the next internal audience.
Some insights die because they arrive too late
There are moments when research technically happens before a decision but functionally happens after it. The strategy has already been blessed. The internal narrative has already been built. The creative work is already too far along. The organization asks for learning, but what it really wants is confidence. In those situations, the research can still be valuable, but its ability to influence the direction has already narrowed. If the insight supports the path, it gets amplified. If it challenges the path, it gets managed.
This isn’t anyone’s favorite thing to admit, because it reveals a kind of theater that can creep into organizational research. The study is framed as exploration, but the range of acceptable answers is smaller than anyone wants to say out loud. Stakeholders may not even realize they are doing it. They may sincerely want to learn, but they also want the learning to fit within the boundaries of what is still possible.
That is why the timing of research is a question of integrity as much as project management. If a team isn’t willing or able to act on what a study might reveal, then it is worth asking what role the research is really playing. Is it helping guide a decision, or decorating one that’s already been made? Those are very different assignments, and they call for different approaches.
Some insights die because no one owns them
Another common failure point happens when the insight belongs everywhere and therefore nowhere.
This is especially true in customer experience work, journey work, innovation work, and broader strategic research, where the most meaningful findings often cut across internal structures. A customer problem may involve marketing, product, operations, digital, service, and retail execution all at once. Everyone can see the problem. Everyone may even agree it matters. But if no single person or team owns the next move, the insight becomes a shared concern rather than an active priority. Shared concern is where action goes fade away, never quite making the leap from insight to ownership.
This is one of the reasons I increasingly believe that research deliverables need to do more than communicate what was learned. They need to clarify what kind of action the learning implies and who would need to be involved for that action to become real. That does not mean researchers should overstep into making decisions for the business. It means recognizing that insight without ownership is fragile.
There are several other reasons I could talk about, but I want to unwrap something else…something I think our industry has room to grow into.
Delivery isn’t enough to spur adoption
We are fairly good at talking about insight delivery – storytelling, visualization, executive summaries, workshops, dashboards, activation sessions. All of that is valuable, but delivery isn’t adoption. Delivery asks whether the insight was presented clearly. Adoption asks whether the organization changed what it believed, prioritized, or did.
A beautiful report can still fail. I've watched projects stall because a team became precious about how the readout looked, while stakeholders charged ahead without waiting for it. And even when insights are delivered well and on time, the harder work begins after the readout — which is inconvenient, because most research projects are scoped as if the readout is the end. In reality, it is often the moment when the organization is just beginning to wrestle with the implications of what it has learned.
That wrestling is where teams decide whether an insight is merely interesting or actually important. It is where they determine what must change, what can wait, what is too costly, what is worth fighting for, and who needs to be brought along. It is also where a research team’s credibility and relationships matter most, because stakeholders are more likely to act on challenging insight when they trust the people helping them interpret it. Trust is not a soft benefit of good research. It is the currency that allows research to influence decisions when the answers are inconvenient.
What great insight leaders do differently
The strongest insight leaders I’ve worked with understand that their job is not finished when the findings are accurate and handed over to stakeholders like pills to swallow. They are thinking several steps beyond the report, toward how the organization will actually absorb the truth.
They involve stakeholders early – not for approval, but for exposure. They make sure the business questions are clear enough that the findings have somewhere to land. They resist the temptation to answer everything and instead protect the core decisions the research is meant to support. They are explicit about what the data can say, what it can’t, and what the organization may need to learn next. They understand that a surprising insight may need time to settle before it can become action.
Most importantly, they recognize that insight work isn’t only about understanding consumers. It is also about understanding the organization that must act on behalf of those consumers – a second form of understanding that’s just as important as the first, and far more overlooked.
The work after the work
Early in my career, I thought the hardest part of research was getting to a true and useful insight. I still think that work is difficult and requires real craft that few practice well. But I’ve come to appreciate that the work after the work is every bit as important - what happens when the insight challenges the plan, complicates the story, or asks a team to slow down and admit uncertainty.
To a qual researcher like me, those aren’t just business questions, they’re human questions.
And maybe that is why this topic has been occupying my mind. We often talk about understanding consumers as if the organization itself is purely rational, ready to act once the right information appears. But organizations are made of people, and people bring all of their hopes, fears, incentives, habits, and attachments into the room with them. That means the final mile of insight is not about communication alone. It is about change, and great insights do not create change by themselves. They need people willing to believe them, leaders willing to sponsor them, teams willing to own them, and organizations willing to be altered by what they have learned. That’s something great researchers can design toward. It’s also something client organizations have to work towards.
Without that, even the best insight can become one more thoughtful slide in one more forgotten deck. And that may be the real responsibility for those of us in this profession. Not simply to find the truth, and not simply to present it well, but to help it survive long enough to matter.
JUSTIN SUTTON
CO-FOUNDER
CATAPULT INSIGHTS
Justin Sutton has led qualitative and mixed-method research programs for brands including retail, QSR, CPG, financial services, and durable goods organizations. His work focuses on behavioral drivers, innovation, Moments of Truth, and the intersection of System 1 and System 2 decision-making.
