When Findings Sit Still: A Discussion-Chapter Review for Adding Interpretation Without Overreach

Many discussion chapters do not fail because the research is thin. They fail because the writing stays too close to the findings. A paragraph reports that participants valued flexibility, or that Theme A diverged from Theme B, and then stops. The reader is left to work out why that matters. In a UK dissertation, some of that work belongs to the reader, but not all of it. The candidate has to show how the findings answer the research question and why they deserve a place in the argument. The review routine below is a stress test for that moment. It is not a licence to inflate claims; it is a way of making measured interpretation visible.

Description is not a failure, but it is not the finish line

A findings chapter reports what was found. A discussion chapter explains what those findings mean, how they relate to existing work, and what follows from them. When a discussion chapter drifts back into description, it is usually not because the writer is careless. It is often because description feels safe. Reporting a theme exactly as participants expressed it avoids the risk of overclaiming. That instinct is ethically sound. The problem is that it can leave the chapter underpowered, with clear findings but an unclear contribution.

As 2026 dissertations move into their final drafting stages, it is worth treating the discussion chapter as an argument rather than a summary. The aim is not to make every paragraph dramatic. The aim is to make the interpretive step visible, proportionate and grounded in the data.

Step one: choose paragraphs that represent the pattern

Before revising whole chapters, select a small sample of discussion paragraphs. Choose three or four that seem typical rather than exceptional. Include one paragraph that reports a main finding, one that reports an unexpected or contradictory finding, and one that connects findings to literature. This keeps the review manageable and prevents the common trap of rewriting the most confident paragraph while leaving quieter paragraphs untouched.

For each paragraph, label what it currently does. Is it reporting? Comparing? Explaining? Evaluating? A paragraph can do more than one of these, but naming the dominant function makes the gap easier to see. If every sample paragraph is doing only the first, the chapter is probably describing rather than discussing.

Step two: apply three plain-English prompts

The core of the review is a simple audit. For each paragraph, ask three questions.

• So what? Why does this finding matter for the research question? What would be lost if the paragraph were removed? This prompt pushes the writer beyond repetition and towards significance.
• Compared with what? How does this finding compare with the literature, policy, professional practice, or the assumptions set out earlier in the dissertation? Comparison does not require agreement. A finding can qualify, complicate or contradict earlier work.
• Now what? What follows for theory, practice, methods or future research? This prompt should be answered carefully. A small qualitative study rarely supports sweeping recommendations, but it can point towards a question worth asking next.

These prompts are deliberately plain. They are not a formula for jargon. They are a way of checking whether the chapter has earned its interpretive claims.

Step three: revise for measured interpretation

Revision should add interpretation without turning the paragraph into a series of assertions. A useful discipline is to distinguish between what the data show and what the writer thinks they may mean. Phrases such as 'the data suggest', 'this appears consistent with', 'one possible reading is' and 'this qualifies rather than confirms' can help. They do not weaken the discussion. They show that the writer understands the difference between evidence and inference.

It also helps to keep a simple evidence boundary in view. If the study is small, contextual or exploratory, the discussion should say so where it matters. If the design cannot support causal language, avoid words such as 'proves', 'causes' or 'demonstrates conclusively'. Measured interpretation is not timid. It is precise.

A short worked example

A descriptive paragraph might read: 'Participants described the new booking system as quicker, but some missed speaking to a person.' That is a finding, but it is not yet a discussion.

A revised version might read: 'Participants generally described the new booking system as quicker, although several valued the option of speaking to a person. This suggests that efficiency and reassurance were not competing priorities so much as separate conditions for a good experience. The pattern is consistent with the service-quality literature reviewed in Chapter 2, but the small sample means it should be treated as an indication rather than a generalisable finding.'

The revision does three things. It interprets the pattern, compares it with existing work, and limits the claim. That is the kind of measured discussion that UK examiners tend to reward.

Keep the audit ethical

The purpose of this review is not to make the discussion sound more confident than the evidence allows. It is to make the reasoning clearer. There is an ethical difference between saying 'this may indicate' and saying 'this proves'. There is also a difference between linking findings to literature and forcing them into a pre-existing argument.

Before moving on, check each revised paragraph against three simple tests. Can you point to the finding that supports the interpretation? Have you avoided claims that the design cannot sustain? Would a careful reader see the link between evidence and inference? If the answer to all three is yes, the paragraph is doing the work of a discussion chapter rather than the work of a results chapter.

The so what? audit is not a quick fix, but it is a calm one. It asks the writer to slow down, look at what the findings are actually doing, and explain their significance with care.