What the Discussion Section Is (and Is Not)

  • It is: your interpretation of the results, placed in the context of the field — what the data mean, whether they support your hypothesis, why they might differ from expectations, and what the study contributes or leaves open.
  • It is not: a rewrite of the results ("the temperature rose and then fell" — that belongs in Results), a place for new data, or a vessel for your feelings about the experiment.

The governing metaphor: Results says what you found; Discussion says so what. If a sentence in your discussion can stand in the Results section, move it.

The Five-Step Discussion Pipeline

Professional discussions follow an inverted funnel: start narrow (your results), widen (interpretation and context), and end broad (implications). Build yours in these five moves, in this exact order:

Step 1: Open with the answer

The first paragraph should state, plainly, what your data show relative to your hypothesis. One or two sentences. No throat-clearing, no "in this experiment we investigated." Directly:

"The results support the hypothesis that enzyme activity increases with temperature up to 40°C, above which activity declines sharply. This pattern is consistent with thermal denaturation of the enzyme at elevated temperatures."

Notice: claim first, then the brief interpretation. If your results rejected the hypothesis, own it with equal directness: "The data do not support the hypothesized relationship."

Step 2: Interpret the findings (the analysis move)

Now explain why you observed what you observed — this is your chance to demonstrate mechanistic understanding. Ask and answer: what biological, chemical, physical, or social mechanism accounts for this pattern? Tie each observation to its plausible explanation, and connect your results to specific prior findings (cite them!):

"The sharp decrease above 40°C aligns with the classical finding that hydrogen bonds stabilizing tertiary structure weaken as kinetic energy rises, as reported in standard enzyme kinetics literature (Smith, 2021). The 15% lower maximum activity in trial 3 may reflect pipetting error or partial enzyme degradation during storage."

Step 3: Compare with expectations and the literature

Address discrepancies explicitly — this is the move graders hunt for. Structure it:

  • Did the results match what the literature predicts? Name the agreement.
  • Where they diverged, say so and propose explanations: uncontrolled variables, instrument precision, sample size, methodological differences from the original study.
  • Avoid hand-waving: "results differed from the expected values, likely due to experimental error" is the most overused, least informative sentence in lab-report history. Replace vague error claims with specific, plausible sources tied to your actual procedure.

Step 4: Acknowledge limitations honestly (the credibility paragraph)

Every study has limits; pretending otherwise destroys credibility. Include a short, specific limitations paragraph: sample size, measurement precision, uncontrolled variables, time constraints, equipment issues. The sentence frame that signals maturity: "The primary limitation of this study is…, which means the conclusions are strongest for… and should be generalized cautiously to…" — then move on. Do not grovel; one clean paragraph suffices.

Step 5: Implications and future directions (the close)

End by answering: so what? What do your findings imply for the theory, the applied problem, the method? And what experiment should come next — the one your study can't answer but points toward? A strong final sentence lands the contribution: "Future work varying substrate concentration would clarify whether the observed plateau reflects saturation, and would extend these findings toward realistic industrial conditions."

The Discussion's Sentence Frames (Steal These)

Having trouble with phrasing? Use the frames that professional discussions share:

  • "The results are consistent with…"
  • "This finding supports/contradicts the hypothesis that…"
  • "A plausible explanation is that…"
  • "This discrepancy may arise from…"
  • "These results are qualitatively similar to those of [Author], who found…"
  • "The primary limitation of this study is…"
  • "Future research should examine…"
  • "Taken together, these findings suggest that…"

Frames are scaffolding, not content — fill them with your analysis, and do not let template sentences outnumber real thinking.

Length and Concision: The Right Budget

A lab report discussion typically runs one to three paragraphs per hypothesis/objective, or 300–700 words total for standard undergraduate reports — but the exact length depends on your instructor's guide, which always trumps general advice. The concision rules that matter:

  1. One idea per paragraph. If a paragraph contains two unrelated interpretations, split it.
  2. Cut every sentence that repeats Results. Reread those two sections side-by-side; any sentence appearing in both belongs in one only.
  3. Use precise quantitative language when possible: "increased by 22%" beats "increased significantly" — significance is a statistical claim, not an adjective.
  4. Avoid the filler openers: "It should be noted that," "It is important to mention that," "In conclusion" — every one of these signals that the sentence beneath it didn't earn its place. Delete the opener; keep the sentence; it will be stronger.

Common Mistakes That Sink Discussions (with Fixes)

  • Result-rewriting: paragraph-long recap of data. Fix: one sentence of data per finding, followed by interpretation.
  • Overclaiming: "This proves enzymes denature at high temperatures" from a single trial. Fix: temper to what the design supports — "consistent with," "supports," "suggests" — and let the limitations paragraph carry the humility.
  • Causation from correlation: observing association but asserting mechanism, discussed in our companion guide on correlation vs. causation. Fix: match claims to design; if you did not manipulate the variable, you observed association, not cause.
  • Source-free interpretation: interpreting results with no citation to prior work. Fix: every mechanism you propose should have a literature anchor, even "textbook-level" ones.
  • The missing limitations: pretending perfection. Fix: one honest paragraph; graders reward the confession.
  • Speculative overreach in future directions: promising to "cure disease with more trials." Fix: future directions must be precise and plausible offshoots of your actual study.

A Discussion-Section Pre-Draft Drill (5 Minutes)

Before writing, answer these three prompts in note form:

  1. The answer: "My data show ___ relative to my hypothesis."
  2. The why: "The most plausible mechanism is ___ because ___."
  3. The context: "My findings agree/disagree with ___ (cite), and the difference likely stems from ___."

These three notes are the spine of the whole section. If you can write them on a sticky note, every paragraph that follows has a home.

Conclusion

The discussion section is not a mystery genre — it is a five-move logic: state the answer, interpret the mechanism, compare with the literature, confess limitations, point forward. Write claim-first paragraphs, support each mechanism with citations, temper every claim to what your design actually supports, and delete any sentence that belongs in Results. The students who score highest on lab reports are not the ones who understand the experiment best — they are the ones who can show the grader, in a clean inverted-funnel sequence, exactly what the data mean and why they matter. Run the five-step pipeline on every report, and the discussion stops being the section you dread and becomes the section where you finally tell the story of your experiment — with the confidence of someone who knows the story belongs to them.

Your next step: Before your next report is even finished, draft the discussion's three sticky-note prompts: the answer, the why, and the context. Writing the interpretation immediately after the experiment — before grades, before exhaustion — captures the thinking that makes discussions great, and the five-step pipeline will have far less work to do when the report deadline arrives.