The two questions every insight team should ask before the debrief

There's a lot of thinking that goes into a research debrief. The story arc. The insight hierarchy. Which slide goes first. Whether to lead with what's surprising or what's actionable. How to handle the finding that's going to be uncomfortable.

All useful thinking.

And none of it is the thing that most often determines whether the insight gets acted on.

The part that determines that usually happens – or doesn't happen – in the weeks before the debrief. Not in the building of the deck. In two specific questions that most insight teams never ask.

Why insight fails before the meeting starts

When insight doesn't move organisations, we usually blame the results, and sometimes the report. The presentation was too dense. The decision-maker wasn't in the room. The timing was off. Ultimately, the stakeholders went quiet.

These are real problems. (I've written about four of them before). But they share an upstream cause that a better presentation, on its own, can't fix: the insight team didn't map the territory it was walking into before it walked in.

The debrief isn't a neutral space. It lands in an organisation that already has a theory about what the research will show. Often one that the commissioning team quietly needs to be confirmed. The insight is then presented into that expectation – and either confirms it (useful, but rarely transformative) or contradicts it (which is when the room goes quiet and the qualifications begin).

If you want the insight to move the organisation rather than sit on a slide, you need to do two things before you walk into the room. Ask two questions. Not of the data. Of yourself, and of the people being presenting to.

Question 1: What is the decision this insight actually needs to move?

Not the research objectives. The decision.

Research objectives describe the questions the fieldwork was designed to answer. They're necessary. They're also, almost always, one step removed from what the insight is actually commissioned to enable: a decision that is already sitting somewhere in the business, waiting for evidence to make it easier, harder, or irreversible.

That decision might be about a product, a pricing structure, a channel investment, a market to enter or exit. It might be the difference between renewing a contract and not renewing one. In most cases, the people who commissioned the research know exactly what it is. They just haven't named it explicitly, because naming it would mean being honest about the stakes and exposing themselves to being proven wrong - and that can be scary.

Before the debrief, ask: "What is the decision this work was really trying to inform? And who owns that decision?"

The answer changes how you structure the debrief entirely. It changes which finding leads. It changes what you leave out. It changes whether you need a 40-slide deck or three slides and a conversation.

This is the thinking behind the Unite phase of our Truth Is Human ® Method – the session we run at the start of every project to understand and express the commercial decision before fieldwork begins. We ask this question in week one, not in week six. But even if the project has already run, asking it the week before the debrief is better than not asking it at all.

Question 2: What does the person who needs to act already believe – and what would it take to shift them?

This one is less comfortable, which is why it tends to get skipped.

Every debrief lands in a room where the most important person has already formed a view. Probably before the research started. They've been running the business, or the function, or the market, for years. They have a working model of what their customers think and do. That model might be wrong, or incomplete, or right about some things and quietly wrong about others. The insight you're about to present is either going to confirm it or challenge it.

The question to ask is: "What does this person already believe, and what would it take – specifically – for them to update their view?"

Not in a cynical way. Not to soften the findings or hedge the conclusions. But because if you know what they believe, you can design the moment of contact with the truth more carefully. You can decide whether to ease the reader in from the side they're already standing on, or to lead with the contrast. You can make sure the evidence is robust enough to carry the weight of the thing it's being asked to shift.

Insight that lands badly isn't usually wrong. It's usually structurally unprepared for the belief it arrived to challenge.

What changes when you ask them

The strange thing about these two questions is that they don't change the research. The truth is the truth. What they change is the judgement applied to the delivery – the sequencing, the framing, the level of evidence brought to bear on the findings that are going to require the most from the room.

An insight team that has answered both questions before the debrief is not a team delivering findings. It's a team conducting a change conversation. The difference isn't subtle. And it shows.

The insight either reaches the decision it was built for, or it doesn't. The meeting, the deck, the story arc – they all matter. But they matter downstream of these two questions.

Ask them first.

At Embark Insight, the Unite phase is built into every project we run – because commercial alignment at the start is the reason insight lands at the end. If you're thinking about how to make your next piece of research more actionable from the brief stage, reach out directly or book a 30-minute call.