Key Takeaways — Chapter 13: Lab Reports and Technical Reports

The summary card. Use it to re-ground before the quiz, or to review weeks later.

The one idea

Results report what happened; Discussion reports what it means — and the boundary between them is the discipline of the genre. A report exists to let a reader who wasn't in the room understand what you did, trust your findings, and build on them. Everything else follows from keeping the observation (what the instruments recorded) separate from the interpretation (what you claim it means), so the reader can judge your evidence before judging your spin on it.

🚪 Threshold concept: Results and Discussion are two different cognitive acts kept in separate rooms. Before you cross this, saying what a finding means feels inseparable from reporting it. After, you state the bare observation so neutrally that a rival who disagrees with your interpretation would still accept every sentence — then argue the meaning in a clearly labeled place where the reader knows to be skeptical.

IMRaD: four questions in a fixed order

The order isn't arbitrary: it's the logical chain by which a skeptic evaluates evidence — you can't judge a finding without the methods, or an interpretation without the finding. The report is an hourglass: broad Introduction → narrow Methods/Results (the waist) → widening Discussion. Write the sections out of order — Methods first (most mechanical), Abstract last (you can't summarize what you haven't finished).

The section-by-section discipline

• Introduction = a funnel: context → gap → what this study does. State the purpose in the first short paragraph. The gap is the hinge — background without a gap is just a literature dump.
• Methods = replicable: the standard is that a competent peer could reproduce your work from the text alone, without asking you anything. Specify every parameter that changes the result. (Passive voice is fine here — put the sample, not you, in the subject position.)
• Results = observation only: report measurements neutrally; no judgment words, no causal claims, no "as expected." Curated, not a data dump.
• Discussion = interpret without overclaiming: make sense of the finding (don't restate it), relate it to prior work, bound the claim, and state limitations honestly — which makes readers trust you more. Calibrate language to evidence: suggests / is consistent with, not proves.
• Title & Abstract: the most-read parts. The title is informative (names the system and finding); the abstract delivers the actual numbers, not "results are presented and discussed."

Workplace technical reports: same bones, recommendations first

The academic reader evaluates evidence and wants the conclusion last; the workplace reader (a busy manager) must act and wants it first. So a technical report inverts the order (BLUF):

• Lead with a stand-alone executive summary — the recommendation, the key reasons, the action-with-deadline.
• Make findings scannable (a short list or small table).
• Demote the methodology to an appendix — keep it (someone will check), but don't make the decision-maker read it to reach the decision.
• It's a spectrum, not a binary: a detailed test report sits near the academic end; a recommendation memo sits at the far workplace end. Read your specific reader.

Themes this chapter surfaced: #5 structure-serves-the-reader (IMRaD's order and the recommendation-first flip both answer "how does the reader use this?") · #2 audience-is-everything (peer evaluator vs. workplace decision-maker) · #1 writing-is-thinking (drafting the Methods reveals a step you can't reconstruct; the report is part of the science, not its packaging).

Threshold concept: Results report what happened; Discussion reports what it means.

Back to: Chapter 13 · Exercises · Quiz · Further Reading