The Difference Between Findings and Insight

Your p-value came back significant. Odds ratio 2.4, 95% CI crosses nowhere near 1.0. Your model fits the data. The statistics are clean.

So why does your Discussion section feel hollow?

Because findings and insights are two different things — and most researchers conflate them.

What a Finding Actually Is

A finding is what your data shows. It is a factual output of your analysis. "Patients in the intervention group had a 40% reduction in complication rate compared to controls (p = 0.03)." That is a finding. Accurate, verifiable, bounded by your methodology.

Findings live in the Results section. They do not carry meaning on their own. They are raw material.

A surprising number of Discussion sections read like extended Results sections — restating numbers, describing the direction of associations, summarizing what the tables already show. Reviewers notice. Editors notice faster.

What Insight Requires

Insight requires an act of interpretation. It is the step from "what we found" to "what this means" — and that step demands courage.

When you write "our findings suggest that earlier intervention may be beneficial," you are almost there but still hedging. Insight is more specific: why does earlier intervention appear beneficial in this population? What mechanism explains this? How does this fit with or contradict what Zhou et al. found in a different population? Where does your finding sit in the broader conversation?

Interpretation is not speculation. It is reasoned positioning. You are a domain expert who has spent months studying this question. You owe readers your actual judgment — not a list of statistically significant associations.

The Gap Most Researchers Leave

Read your last Discussion section. Count how many paragraphs start by restating a result. Then count how many paragraphs actually take a position on what that result means for clinical practice or future research.

That ratio tells you where your Discussion stands.

The gap between findings and insight is where papers get rejected. Reviewers who write "the Discussion lacks depth" or "the authors do not adequately contextualize their findings" are pointing at exactly this problem. They do not want more words. They want sharper thinking.

A Practical Test

After writing a Discussion paragraph, ask yourself: could a reader have predicted this paragraph from the Results section alone?

If yes, you have restated a finding. You have not produced an insight.

Insight should be something the reader could not construct without your expertise. Your knowledge of the field, your understanding of the mechanism, your judgment about clinical relevance — that is what belongs in the Discussion.

The Reframe That Helps

Think of findings as evidence. Think of insights as arguments.

Your Discussion is an argument. Evidence alone does not make an argument. You need a claim, evidence supporting it, and reasoning that connects the two.

"Complication rates were lower in the intervention group" is evidence.

"The reduction in complications likely reflects improved tissue handling during the critical 48-hour post-operative window, consistent with the inflammatory cascade model proposed by Kim et al. — and this argues for protocol revision in centers currently using delayed intervention" is an argument.

Same data. Entirely different Discussion.

Why This Step Feels Risky

The hesitation to interpret is understandable. Academic culture punishes overreach. Reviewers cite "speculation" and "unsupported claims." So researchers retreat to safe, hedged language that says nothing.

But there is a difference between overreaching and taking a reasoned stance. The goal is not to claim more than your data supports. It is to claim everything your data does support — clearly, directly, with appropriate caveats where needed.

If you have a well-designed study, you have earned the right to interpret your results. Use it.

The Link Between Results and Discussion

The Results section answers: what did we find?

The Discussion section answers: what does it mean, and so what?

These are different questions. Answering the first does not automatically answer the second. That transition — from finding to insight — is where your paper either succeeds or fails.

If you want a structured approach to building this argument, the post on why most discussion sections fail walks through the full framework. And for the broader question of how to structure the paper so your findings lead naturally into insights, see how to turn raw results into an argument.

If your Discussion regularly gets flagged for "lacking depth," the problem is almost never a shortage of data. It is the gap between what you found and what you said it means. The Discussion Section Playbook gives you a 6-block framework for closing that gap — so your next submission reads like the work of a researcher who knows exactly what their data says.

---

---

If you are currently drafting your manuscript, you might find my Checklist: Idea to Submission helpful.