Fontys University of Applied Sciences

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 technical and engineering-focused institutions 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.

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.

Program type has a real effect on what a thesis at this level typically involves. Based on the programs Fontys University of Applied Sciences is generally known for — ICT, engineering, business — 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.