Beyond AI: Why the Future of Research Depends on Trust, Not Just Technology

Everywhere in the insights industry, the conversation increasingly dominated by what AI can do.

AI can summarize interviews in minutes. It can detect patterns across thousands of data points. It can generate personas, draft reports, sharpen recommendations, and also accelerate tasks that once took researchers days or weeks.

For the insights team under pressure to move faster and prove business impact, this is truly a big shift. Only, there is one problem AI does not solve.

It cannot make stakeholders believe the research.

It cannot build the trust required for a product manager to change direction, a business leader to take a risk, or a leadership team to act on findings that challenge their assumptions. It can read the quiet hesitation in a meeting, or even navigate the internal politics that often determine whether an insight is acted upon or quietly ignored.

And this is where the real problem begins.

In many organizations, research does not fail because the analysis is weak or the report is poorly written. It fails because the people who need to act on it do not feel enough trust, ownership, or emotional commitment to move it forward.

The result, unfortunately not always an open rejection. More often, it is a situation where stakeholders listen to our presentation, nod, ask a few questions, and then return to business as usual.

This is what I call silent rejection.

Why Silent Rejection Happens?

Silent rejection usually does not happen because of one single reason. In many APAC organizations, especially in cultures where relationships and context matter a lot, insights are not judged only by the quality of the data. They are also judged by who delivers them, how they are delivered, and whether people feel included in the process.

In Indonesia, for example, authority is often social before it is technical. The source material refers to Hofstede’s Individualism Index, where Indonesia scores only 14 out of 100. This shows how strongly collectivist Indonesian culture is. In simple terms, people often value group harmony, shared agreement, and relationships more than individual opinion.

For researchers, this matters. A recommendation can be very strong from a research perspective. But if the recommendation feels like it comes only from “the researcher,” not from “the group,” stakeholders may hesitate to act on it.

They may not openly disagree. In many organizations, saying “I reject this” directly can feel uncomfortable or too confrontational. But they may also choose not to move forward, because they do not feel enough ownership over it.

Second, many organizations are built on relationship-based trust. In Indonesia, there is a familiar idea called kekeluargaan, or a family-like way of working. In this kind of environment, people often need to trust you as a person before they fully trust your expertise.

Stakeholders may ask something like: “Do you understand our situation?”, “Are you trying to help us, or are you judging us from the outside?”, “Do you respect the business reality we deal with every day?”

If the answer is unclear, the researcher may struggle to gain influence.

There is also another factor: stakeholders often want their contribution to be visible. In complex organizations, visibility is linked to responsibility. If stakeholders are expected to act on a recommendation, they need to feel that their perspective has been considered.

When they do not feel involved, the recommendation can feel like something imposed to them. Even if the research comes from an internal team, it can still feel distant. In some research teams, they only involve stakeholders at the beginning and at the end of the research process.

The problem is, trust is not built only at the end. It is built throughout the process.

From Research Service to Research Participatory

This is why I believe research needs to move from a service model to a participatory model.

In the research service mode, researchers often act like internal vendors. A stakeholder sends a request, then the researchers work on it. After that, the researcher comes back with findings and tries to convince the business to act.

In the participatory model, the relationship is different.

Stakeholders are not only requesters or audiences, they become collaborators. They help shape the objective, review the research plan, involve in the field research, even join the analysis process. In summary, they take part in our decision process.

The research process becomes more open.

The rigor becomes visible. The reasoning becomes easier to follow. The research becomes connected to the business reality stakeholders face every day.

This shift may sound simple, but it changes how research is received. The final recommendation is no longer seen as “the research team’s finding.” It becomes “our finding.”

And once stakeholders feel that the insight belongs to them, they are more likely to act on it.

Trust Building Research Framework

The Trust-Building Research Framework works through five key touchpoints. Each touchpoint is designed to build trust before the final presentation happens.

1. Kick-off Meeting: Turning Requests into Decision Conversations 

The first touchpoint is the kick-off meeting. This is where research request becomes a real business conversation. Instead of only asking “What do you want to know?”, the researcher should ask deeper questions, like:

• Why does this matter now?
• What decision will this research support?
• What risk are we trying to reduce?
• What will change if we find the answer? 

These questions help shift the conversation from task execution to decision support. They also show stakeholders that their context matters.

The researcher is not just collecting data because someone asked for a study. The researcher is trying to understand the decision behind the request.

And this is important because many research projects fail when the decision is unclear. A strong kick-off helps prevent that. It creates shared clarity from the beginning.

2. Research Planning Review: Making the Process Visible

After the kick-off, the researcher prepares a draft research plan. This may include the objective, method, timeline, sample criteria, participant profile, and key questions.

Then, instead of keeping the plan only within the research team, the researcher shares it with stakeholders. I know, maybe some researchers may feel uncomfortable with this. The goal in this step is not to let stakeholders weaken the method. Rather, the goal is to help them understand how the research will work.

When stakeholders see the plan, they begin to understand the logic behind the study. They see why certain users are selected, why the sample is designed in a certain way, why some questions are asked, and why good research needs time.

It also reduces surprise later. When findings are presented, stakeholders are less likely to question the process, because they have already seen how the research was designer.

In summary, when the process is being visible to them, the conclusion becomes easier to trust.

3. Field Involvement: Letting Stakeholders See the User Reality

The third touchpoint is field involvement. This means inviting stakeholders to observe user interviews, usability tests, field visits, or customer listening sessions.

For many stakeholders, this can be eye-opening. They may know the metrics, dashboard, and the business targets. But, they may have never watched a real user struggle with a product, feel confused by a service flow, or hesitate before making a decision.

A report can explain user pain points. A chart can show where users drop off. But, seeing a real person struggle creates a different kind of understanding.

That is the power of field involvement. When stakeholders see what researchers see, they are more likely to believe what researchers believe.

4. Collaborative Analysis: Combining User Evidence with Business Context

After data collection, the research team should not disappear completely and return only with final conclusions. Instead, researchers may invite stakeholders into the synthesis process.

This can be done through a workshop, a discussion session, or a collaborative board where key observations, key quotes, patterns, and tensions are reviewed together.

And this does not mean stakeholders will decide the findings based on their opinion. It means researchers and stakeholders combine two important types of knowledge. Researchers bring behaviour patterns, pain points, motivations, and insights from the field. And stakeholders bring technical limitations, operational constraints, commercial goals, and internal priorities.

We know that good recommendations often need both.

It also creates stronger buy-in. When stakeholders help make sense of the data, they understand how the conclusion was formed. They do not just receive the answer, they become part of the thinking process behind it.

5. Shared Decision-Making: Moving from Insight to Action

The final touchpoint is shared decision-making. By the time the findings are presented to leadership, the key stakeholder should not be hearing the story for the first time. Ideally, they have already been part of the journey.

In some cases, they can even present the findings together with the researcher. Or, the stakeholder can present the business recommendation, while the researcher supports with evidence.

This will change the dynamic in the room.

When a researcher presents alone, the recommendation can feel like an external critique. But when a stakeholder presents with the researcher, the recommendation feels like a shared business agenda. The language changes from “researcher found this” to “we found this.”

Shared decision-making also helps decisions move faster. Because stakeholders have been involved throughout the process, alignment has already happened step by step. Objections have been discussed earlier. And implementation becomes easier because ownership already exists.

Why This Framework Works?

This framework works because it follows how trust is actually built. Based on Mayer’s Trust Theory, trust is built through three things: ability, benevolence, and integrity.

In research, ability means stakeholders can see that the researcher is capable. In the traditional model, stakeholders often see only the final deck. They do not see the thinking, the planning, the fieldwork, or the analysis behind it.

In a participatory model, research ability becomes visible across the process. Stakeholders see how the study is planned, how users are engaged, how data is interpreted, and how recommendations are shaped.

Benevolence means stakeholders feel that the researcher cares about their needs and constraints. This is important because research can sometimes feel like judgment. It can make teams feel exposed, especially when findings show that a product, service, or decision is not working well.

By involving stakeholders, listening to them, and respecting their context, researchers show that the goal is not to blame. The goal is to help the business make better decisions.

Integrity means stakeholders believe the process is honest and transparent. The five touchpoints help them follow the logic. They can ask questions, challenge assumptions, and understand how the conclusion was reached. This makes the final insight feel less sudden and less threatening.

The framework also builds psychological ownership. People are less likely to reject findings they helped uncover. They are more likely to defend recommendations they helped shape. And when others question the findings, they can explain the reasoning because they were part of the process.

This is especially important in high-context and relationship-oriented cultures. In these environments, participatory research is not just a research method. It is a way to build alignment, trust, and change inside the organization.

The New Role of Researchers in the AI Age

AI will continue to change research. It will make many tasks faster, cheaper, and more automated. It will help researchers summarize data, find patterns, draft reports, and generate ideas more quickly.

But this also means that basic research outputs may become easier to produce.

So, the value of researchers cannot depend only on their ability to collect data or create reports. The real value will come from their ability to build belief around evidence.

This is where human researchers still have a critical role.

Researchers can understand organizational nuance. They can build relationships. They can sense resistance before it becomes rejection. They can facilitate difficult conversations. They can help stakeholders move from knowing the insight to owning the decision.

For insights leaders across APAC, this is the shift we need to take seriously. Research must move beyond being a function that only delivers answers. It must become a participatory system that builds shared ownership around decisions.

Because the future of insights will not belong only to those who can produce findings faster. 

It will belong to those who can make findings matter.