“And the Recommendation?” — Conclusion First or Data First?

Presentation room. Tomasz opens with assumptions, methodology, and data context. After several slides, Zofia interrupts.

— First, two assumptions and the context behind the data.
— Tomasz, what’s the recommendation?
— I’m getting there.

Tomasz believes a conclusion without foundations will sound arbitrary. Zofia cannot tell why the foundations matter until she knows the conclusion.

What really happened

Tomasz believes a sound argument should build the foundation first: assumptions, data, constraints, then the conclusion. Zofia needs the conclusion first because without it she does not know what to pay attention to in the detail. Each person experiences the other’s sequence as less logical. Yet both can be reasoning perfectly well. They differ in how they want information delivered: from foundations to decision or from decision to justification.

What the research says

Research does not give a universal answer such as “always give the conclusion first” or “always build from the data.” We do know that the fit between information presentation and the task affects how easily people can use that information — cognitive fit (Vessey, 1991). The original research focuses mainly on different ways of presenting data, so here it is a useful model rather than direct evidence for this exact conversation. The practical distinction is what matters: Zofia wants a map of the destination; Tomasz wants to show the road that leads there.

How to handle it

A robust default is a two-layer format: “Recommendation: B. Now the three reasons.” The person who wants the conclusion quickly knows where the conversation is going; the person who needs the full rationale gets it immediately afterwards. In high-risk analysis, you may deliberately reverse the order when avoiding premature anchoring on a conclusion is important. The general rule is: the order of information is a tool; choose it for the purpose of the conversation instead of treating your preferred sequence as the only sign of logical thinking.

How Empatyzer and Em can help

Empatyzer can spot that Tomasz and Zofia do not need different information; they need the same information in a different order. The assessment and profile comparison can help Em anticipate that Tomasz naturally wants to build the foundation before giving the conclusion, while Zofia first needs to know where the conversation is heading. Before the presentation, Em can suggest a simple format to Tomasz: “Recommendation: B; now the three reasons and limitations.” He keeps the analytical depth while earning Zofia’s attention faster. If similar differences appear across a wider group, team-level insights can show that some people work better with “conclusion → evidence” and others with “evidence → conclusion.” Micro-lessons build the ability to switch structure for the audience, so good analysis more often turns into a usable decision.