How to write the discussion chapter in research paper? Single most important tip
Based on Qualitative Researcher Dr Kriukow's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Build a comparison framework before analyzing data: create an expectations list after the literature review but before conclusions are formed.
Briefing
Writing the discussion chapter gets stuck when researchers try to “comment on the literature” only after they’ve already become deeply immersed in their own findings—so the comparison feels artificial and, worse, they can’t clearly remember what they should be comparing against. The core fix is to prepare a structured expectations list before analyzing the data, using what the literature most commonly suggests is likely to emerge.
The discussion chapter still needs to do the usual job: connect the study’s findings to prior research, highlight similarities and differences, and add some reasoned personal perspective. But the practical problem is timing. By the time analysis is complete, it’s easy to lose the broader map of the literature and the “anchor” ideas that would make comparisons feel grounded rather than repetitive. Researchers often end up re-stating findings and then awkwardly repeating whether they match the literature—without a clear sense of which specific strands of literature should be used as the reference point.
The tip offered here works only if the literature review is done but the data analysis and conclusions have not started. At that stage, the researcher should create a document (or write on paper) that records reflections and expectations based on the literature—not what they personally hope will happen, but what is likely to happen given the patterns the literature reports. The approach is intentionally “machine-like”: treat the literature as a statistical guide and list the most common themes, strategies, or challenges that appear across studies.
For instance, if the literature on leadership strategies repeatedly identifies certain strategy types, the researcher should list those strategies as the most likely to surface in the upcoming study. Similarly, if prior work consistently describes particular challenges leaders face, those challenges can be listed as expected outcomes to check later. The key is that the list is built from what the literature says is common or probable, not from the researcher’s intuition about what the study will reveal.
Once the data are analyzed and findings are written, the researcher revisits the pre-made list. That revisit restores objectivity and makes the discussion easier to structure: each finding can be checked against the earlier expectations to determine whether results align, diverge, or produce surprises. It also helps the researcher articulate how the study’s direction may have felt before the findings were known—because the expectations document captures that “before” perspective.
The method is presented as a repeatable workflow that reduces confusion about what to compare, prevents the discussion from turning into a loop of restated results, and clarifies whether the study is confirming, contradicting, or extending the literature. It’s framed as a practical tool for researchers who feel the discussion chapter is unusually difficult to write and need a clearer comparison framework before analysis begins.
Cornell Notes
A discussion chapter becomes hard to write when researchers wait until after data analysis to decide what literature to compare against, making comparisons feel repetitive or artificial. The proposed solution is to create an expectations list after finishing the literature review but before analyzing data. The list should reflect what is likely to emerge based on patterns in the literature (not personal hopes), such as the most common themes, strategies, or challenges. After analysis, the researcher revisits the list to map each finding to prior expectations, making it easier to write similarities, differences, and “surprising vs. unsurprising” outcomes. This restores a broader, more objective view and gives the discussion a clear structure.
Why does the discussion chapter often feel artificial once data analysis is complete?
What timing condition makes the strategy work?
What should the expectations document contain?
How does the method avoid relying on personal bias?
How does revisiting the list after analysis improve the discussion chapter?
Review Questions
- What specific problem occurs when researchers try to compare findings to literature only after becoming immersed in their own results?
- How should expectations be generated from the literature before data analysis begins, and what should they avoid?
- After analysis, what steps should be taken to use the expectations list to structure similarities, differences, and surprising outcomes?
Key Points
- 1
Build a comparison framework before analyzing data: create an expectations list after the literature review but before conclusions are formed.
- 2
Base expectations on what the literature suggests is likely, not on what the researcher hopes will emerge.
- 3
List the most common themes, strategies, or challenges reported in prior studies so the discussion has clear anchors.
- 4
After analysis, revisit the expectations list to map each finding to prior expectations and decide whether results align, diverge, or surprise.
- 5
Use the expectations document to restore objectivity when writing similarities, differences, and interpretations.
- 6
Avoid turning the discussion into a loop of restating findings; instead, use the literature-based checklist to guide commentary.