Hanyang University

Most of the structural problems examiners flag at private research universities show up in predictable places. A common one: an introduction that describes a broad topic rather than a specific, answerable question. Another: a literature review that summarizes sources one by one instead of showing where they disagree or where a gap remains — which then leaves the methodology chapter with nothing clear to justify. Results sections sometimes drift into interpretation that belongs in the discussion instead, and conclusions occasionally introduce new claims that were never actually argued in the body of the thesis. Knowing the twelve-part shape (title page, abstract, acknowledgements, contents, introduction, literature review, methodology, results, discussion, conclusion, references, appendices) is only useful once each part is doing the specific job it's meant to do, not just occupying the expected slot.

A few patterns account for a disproportionate amount of lost thesis time: rereading sources because citation details weren't captured the first time, rewriting an introduction repeatedly before the research it introduces is actually finished, and trying to fix grammar and structure in the same editing pass.

The fix for each is roughly the same idea — capture details once, in the right order: log full citations as you read; draft the introduction properly only after the analysis and discussion are largely settled, since it needs to describe the thesis you actually wrote; and revise structure and evidence before you touch sentence-level wording, since a paragraph that gets cut doesn't need its grammar fixed first.

Thesis scope tends to track the kind of program a student is in more than almost anything else. Given the programs typically associated with this institution — Engineering, business — a thesis here plausibly sits somewhere on a spectrum from data- and methodology-heavy (common in technical, engineering or computing programs) to applied and case-study-driven (common in business, management and other professionally oriented fields). Knowing roughly where your own program sits on that spectrum is more useful early on than any generic length or difficulty guideline.