Academic writing
Your Lab Report Discussion Is an Apology Letter (And It Shows)
A discrepancy between your data and the textbook is not a failure. It is the entire reason your discussion section exists.
The moment your data comes back and it doesn't match the textbook, your brain goes to one place: apology. You start typing 'Unfortunately, our results deviated from theoretical predictions due to experimental error' and you have just written a letter to your mum explaining why you got in trouble. That is the single most common mistake in lab report discussions. Your professor does not want your guilt. They want your analysis. And the word 'unfortunately' tells them you are still in the apology mode.
A discussion section is not a confession. It is an argument about what your data means. Yes, your values do not line up with the idealized numbers in your lecture slides. Good. That gap is the entire reason the discussion section exists. Theoretical values assume perfect conditions—no contamination, no instrument drift, no human hands. Your experiment had all three. Treating the discrepancy as a failure puts you on the defense. Treating it as a finding puts you in the analyst's chair.
Four moves. One: state the deviation objectively. Not 'unfortunately,' just the numbers. 'Our measured value of X was Y, representing a Z% deviation from the theoretical prediction.' Two: list two to three plausible explanations, ranked by likelihood—systematic error, a specific operational variable, instrument precision. Three: state what this deviation does to your conclusion. Directional or magnitude? Four: if you reran it, what specific parameter would you change. Step two is where most students collapse.
Here is what the difference looks like. ❌ 'The results were not as expected due to many possible sources of error in the experiment.' → ✅ 'The measured activation energy (42.3 kJ/mol) was 18% lower than the literature value (51.6 kJ/mol), most likely attributable to underestimation of the reaction temperature at the onset of decomposition.' The first sentence dumps the blame into a vague bin. The second gives you a number, a percentage, and a specific mechanism. ❌ 'This may be because of human error during the measurement process.' → ✅ 'The 12% mass loss at 350°C is consistent with premature thermal degradation onset, suggesting the thermocouple lagged by approximately 3–5 s during the initial heating ramp.' 'Human error' is the academic equivalent of shrugging.
One more. ❌ 'Further experiments should be conducted to verify these results.' → ✅ 'A follow-up using a calibrated thermocouple with response time <1 s, combined with triplicate runs at 340–360°C, would isolate whether the discrepancy is instrumental or mechanistic.' You have written 'further experiments should be conducted' a hundred times. Your professor has read it a hundred times. It carries zero information. You need to say: what experiment, which parameter changes, and why it resolves the specific problem you just identified.
Before you submit, do not check grammar. Check tone. Read your discussion aloud and count how many times 'unfortunately,' 'regrettably,' and 'it is worth noting that' appear. More than two? Cut them. You should sound like a calm analyst, not a student being called into the office. If you have revised twice and still cannot tell which sentences are too defensive, push it through easydue once—it flattens the over-apologetic register without touching your technical content. Use the saved time to verify your data citations.
A discrepancy between your data and the textbook is not a failure. It is the entire reason your discussion section exists. If every run matched theory perfectly, your discussion would be filler. The gap is raw material. Your analysis is the product. Stop throwing the raw material in the bin.