Maastricht University

Thinking about thesis structure from the examiner's side of the table changes what each section is for. At the defense or viva stage, reviewers at public research universities are typically checking that the introduction actually sets up a question the rest of the document answers, that the literature review earns the methodology that follows it, and that the results and discussion stay in their own lanes — findings first, interpretation second. The conclusion gets checked against the introduction almost line by line: does it answer what was actually asked? The remaining parts — title page, abstract, acknowledgements, table of contents, references and appendices — matter for a different reason: they're what makes the document usable and verifiable by someone who wasn't in the room while it was written.

Treating a thesis less like a single long essay and more like a managed project tends to produce steadier progress. That means keeping a source log with full citation details from the first day of reading (not after), writing analytical or methodology chapters close to when the underlying decisions were made, and separating revision into distinct passes — first for argument and structure, then for evidence and analysis, and only then for sentence-level clarity and proofreading.

None of this replaces the actual thinking a thesis requires, but it removes a lot of the friction that turns a manageable project into a rushed one.

Program type has a real effect on what a thesis at this level typically involves. Based on the programs Maastricht University is generally known for — Business, public policy, health — students here are likely working within one of a few common shapes: technical and data-heavy programs usually push methodology and results chapters toward statistical or computational analysis, while applied or professional programs (business, management, public-facing fields) more often lean on case-study framing, stakeholder analysis or applied recommendations instead of raw data collection.

Either way, the general principle holds: methodology should match what the research question actually needs, not what looks most impressive on paper.