The results chapter of a quantitative dissertation presents the author with a problem that is deceptively simple in description and genuinely difficult in execution: the numbers need to tell a story, and numbers do not naturally tell stories. They answer questions. They confirm or disconfirm hypotheses. They reveal relationships, differences, and distributions. But the movement from what the statistics show to what the statistics mean — from the output of the analysis to the contribution of the study — requires an act of interpretation that is the author's responsibility and that no statistical software will perform.
This is the gap that the results chapter must bridge, and bridging it requires a clear understanding of what the chapter is supposed to accomplish. The results chapter is not a statistical report. It is a presentation of findings — an organized, narrative account of what the analysis revealed, written for a reader who is capable of evaluating the statistics but who is relying on the author to explain their significance.
The organization question. Results chapters should be organized by research question, not by statistical test. The reader should be able to read the chapter as a series of answers — here is what the analysis revealed about research question one, here is what it revealed about research question two — rather than as a sequence of tests — here are the descriptive statistics, here are the correlations, here are the regression results. Organization by research question makes the relationship between the analysis and the study's purpose explicit throughout the chapter, rather than leaving the reader to reconstruct it at the end.
Presenting descriptive statistics. Descriptive statistics should be presented before inferential statistics, as a characterization of the sample and the distribution of the key variables. The presentation should include the information that the reader needs to evaluate the inferential analyses that follow — sample size, means, standard deviations, and relevant distributional information — without reproducing every piece of output that the software generated. The rule is relevance: include what the reader needs, omit what the software produced but the argument does not require.
Integrating tables and text. Tables present statistical information efficiently, but they do not interpret it. Every table in the results chapter should be introduced in the text before it appears, identified by its table number, and followed by a narrative that highlights the findings most relevant to the research question. The text should not simply repeat the numbers in the table — it should direct the reader's attention to the specific values that matter and explain why they matter.
The transition to discussion. The results chapter ends and the discussion chapter begins at the point where the author moves from reporting what the analysis found to interpreting what the findings mean. The boundary between these two activities should be explicit. Results chapters that drift into interpretation — that begin explaining why the results came out as they did before the discussion chapter — and discussion chapters that continue reporting results rather than interpreting them are among the most common structural problems in quantitative dissertations.
The statistical analysis is the engine of the quantitative study. The narrative is the vehicle that carries the findings to the reader. Both need to be built with care, and the narrative, because it requires judgment as well as technical skill, is frequently the one that benefits most from a second pair of eyes.
