AcademiansWorldWide

There is a particular kind of dread that settles over a PhD student the moment the examiner leans forward and asks: “Why this method?” Not why qualitative research in general. Not why your field uses surveys. But why this specific method, for this specific question, at this precise moment in your study. Knowing how to write a methodology chapter that survives your viva transforms that question into the opening of a confident conversation. Not knowing how leaves you facing something more brutal, an interrogation you cannot recover from, the kind that haunts researchers for years..

The uncomfortable truth is that supervisor approval and examiner approval are not the same thing and they never have been. A supervisor’s job is to guide you through the process. An examiner’s job is to assess whether your decisions can withstand independent intellectual scrutiny. These are fundamentally different standards, and your methodology chapter must be written to meet both simultaneously. Most aren’t. Most methodology chapters are written to satisfy the person in the room, not the person at the viva table.

Your methodology chapter is not a description of what you did. It is a defence of why every decision you made was the right one.

This article is for PhD students who have already drafted a methodology chapter and suspect (or have been told) that something isn’t quite landing. It is also for those who haven’t started yet and want to build something watertight from the beginning. What follows is not a template. It is a way of thinking about methodological writing that changes how you approach every section.

Good supervisors protect their students. They guide them toward manageable designs, help them avoid scope creep, and reassure them when anxiety peaks. But protection has a shadow side: it can insulate students from the harder questions that examiners are trained to ask. A supervisor who says “that’s fine, move on” may be entirely correct in terms of project management. But examiners are not project managers. They are gatekeepers of disciplinary standards, and they will ask questions your supervisor never raised, not because your supervisor failed you, but because their role required them to prioritise your progress over interrogating your epistemology.

Crotty (1998) highlighted this gap decades ago, arguing that research methodology is tied to its theoretical foundations. A method makes sense only when linked to clear epistemological commitments. When an examiner asks “why qualitative?” they want to see if you understand this. Asking “why thematic analysis over IPA?” tests if you chose deliberately, not by default. A strong methodology chapter reveals these choices, showing the reasoning behind them. It documents the intellectual journey from question to design, inviting scrutiny rather than avoiding it.

The most common failure mode in methodology chapters is description without justification. A student writes three pages about the history of grounded theory, correctly defines constant comparative analysis, accurately describes their data collection procedures and then never explains why grounded theory was the right choice for their specific research problem. The examiner already knows what grounded theory is. What the examiner needs to know is why you chose it over phenomenology, over thematic analysis, over a straightforward qualitative content analysis. The gap between what was chosen and why it was chosen is where most chapters collapse.

A second failure mode is methodological borrowing, using the terminology of a tradition without adopting its intellectual foundations. Braun and Clarke (2006, 2019) have addressed this issue regarding reflexive thematic analysis, warning many researchers misuse it as a generic coding method instead of a theory-based framework. Their view has grown stronger recently: responding to AI-assisted tools, Braun and Clarke and many co-signatories have stated generative AI cannot replicate the interpretive, reflexive work this method requires. An examiner familiar with this literature will quickly spot if your chapter treats reflexive TA just as coding. This is not a minor error but a fundamental misrepresentation of your analysis.

A third failure mode is the absent audit trail. Your methodology chapter must allow a reader to reconstruct your reasoning. Why these participants? Why this sample size? Why semi-structured rather than structured interviews? Why thematic saturation at that point? Why that software? Every answer should be traceable to a clearly articulated methodological logic, and that logic should be internally consistent from beginning to end.

When an examiner reads a methodology chapter, they are asking a sequence of questions that most students never fully grasp. The first is whether the research question and the chosen methodology are genuinely aligned. Creswell and Creswell (2018) describe this as the coherence between worldview, design, and methods, a kind of methodological harmony that, when present, makes a chapter read with quiet authority and, when absent, produces a persistent sense of unease that examiners cannot always articulate but immediately recognise.

The second question is whether the student has demonstrated sufficient understanding of the tradition they are working within to have made a genuine choice. There is a significant difference between a student who chose IPA because they read three papers that used it and one who chose it because they understood how its phenomenological roots, its idiographic focus, and its small sample logic made it uniquely suited to their interest in how individual participants construct meaning around a specific lived experience. The chapter must make clear which student you are.

The third question (and this one is rarely discussed in methodology textbooks) is whether the design is defensible against its own limitations. Acknowledging limitations in a methodology chapter is not a sign of weakness. It is a sign of intellectual maturity. An examiner who finds you have honestly engaged with the constraints of your approach, and explained why you chose to proceed despite them, is an examiner who trusts your judgement. An examiner who finds no acknowledgement of limitations at all suspects you either didn’t notice them or hoped no one else would.

Acknowledging limitations is not weakness. It is the examiner’s signal that you can think critically about your own work, which is precisely what a doctorate demands.

Rather than thinking about a methodology chapter as a series of sections to fill, consider it as the written answer to nine questions that your examiner will implicitly pose as they read. What philosophical position underpins this research? What research tradition or design has been adopted and why? What were the criteria for participant or data selection? How was data collected and why that way? How was data analysed and why that approach? How was quality, rigour, or trustworthiness ensured? What ethical considerations shaped the process? What are the limitations of this design? And finally, the question that holds all the others together, how does every element of this design serve the research question?

Notice that this is not a list of headings. It is a logic. Each question follows from the one before it, and the answer to each should be legible in your chapter whether or not you have organised it under those exact headings. A chapter that answers all nine coherently is a chapter that survives examination. One that answers six and gestures vaguely at the remaining three is one that generates the questions you dread.

The Research Strategy Audit that I offer to PhD students is structured around exactly this logic. Working through it reveals not just what is missing from a chapter, but why it is missing, which is almost always a gap in reasoning rather than a gap in word count.

There is a second survival problem that methodology chapters face, and supervisors almost never raise it: whether the research design is one that the journals you are targeting will be willing to publish. This is not a cynical observation about disciplinary gatekeeping. It is a practical reality that shapes whether your PhD produces not just a passed thesis but a publishable body of work.

Different journals carry different epistemological expectations. A study designed within a constructivist framework, drawing on reflexive thematic analysis, may find a warm reception at Qualitative Health Research or Qualitative Research in Psychology, and a much cooler one at journals that privilege hypothesis-testing designs and statistical generalisation. This is not a judgment on the quality of either tradition. It is a recognition that journal fit is part of research design, and students who do not consider it early are students who spend years attempting to publish work in venues that were never going to accept it.

Your methodology chapter should be written with an awareness of where this research is going after the viva. That does not mean distorting your design to fit a target journal. It means being explicit enough about your epistemological position, your design rationale, and your analytical approach that a reviewer can immediately recognise whether your work belongs in their conversation.

One of the most transformative shifts a PhD student can make is to change who they imagine reading their methodology chapter. Most students write for their supervisor, the person who already knows the context, has been present throughout the project, and is willing to fill in gaps from memory. Examiners are strangers. They come to the chapter without shared history, without goodwill built from supervision meetings, and with a formal obligation to assess whether the work is independently defensible.

Writing for an examiner means making nothing implicit. It means explaining the connection between your ontological position and your choice of method, even if that connection seems obvious to you. It means defining terms that feel settled within your discipline but may carry different meanings across methodological traditions. It means, above all, writing as if every decision you made required a reason, because to an examiner, it did.

Paltridge and Starfield (2020) observe that the methodology chapter is one of the most discipline-specific sections of a doctoral thesis, with conventions varying significantly across fields. This is important: what reads as adequately justified in education may be considered underdeveloped in psychology, and vice versa. Understanding those disciplinary norms (and demonstrating that you have internalised them) is part of what examination is assessing.

If your study is qualitative (particularly if it uses reflexive thematic analysis, IPA, grounded theory, or any approach that positions the researcher as an interpretive instrument) your methodology chapter must include a serious engagement with reflexivity. Not a paragraph. Not a brief acknowledgement that your positionality may have influenced data collection. A genuine, theoretically grounded account of how your perspective shaped every stage of the research process, and what you did to remain aware of that shaping.

Finlay (2002) argues that reflexivity in qualitative research is not a procedural add-on but a fundamental epistemological commitment, a recognition that the researcher is not a neutral observer but an active participant in the construction of knowledge. Examiners who work within qualitative traditions know this literature. They will recognise a reflexivity section that has been written as a box-ticking exercise, and they will ask the questions that such sections invite: How specifically did your background influence your interpretation? Can you give an example of a moment where your positionality was in tension with the data? What did you do about it?

These are not trick questions. They are genuine disciplinary inquiries. And the students who answer them fluently in the viva are always the students who engaged with them seriously in the writing.

The methodology chapter that earns your supervisor’s approval and survives your examiner’s scrutiny is not a longer chapter or a more technical one. It is a more honest one. It is a chapter that traces the full arc of your methodological reasoning, from the philosophical commitments that shaped your worldview to the specific procedural choices that followed from them. It is a chapter that acknowledges its own limitations with confidence rather than concealing them with silence. It is a chapter that positions your work within a disciplinary conversation and makes clear why you are contributing to that conversation in the way you chose.

That kind of chapter does not write itself, and it does not emerge automatically from following a template. It emerges from a process of thinking through your methodology as a series of connected decisions, each of which can be justified, each of which coheres with the others, and each of which serves your research question. When that thinking is clear, the writing follows naturally. When the thinking is unclear, no amount of additional length will substitute for it.

If you are uncertain whether your methodology chapter is doing this work, that uncertainty is worth taking seriously. The Research Strategy Audit exists precisely for this moment, to help you identify where the reasoning is solid, where the gaps are, and what needs to be addressed before you submit. A methodology chapter is not the place to hope for the best. It is the place to be certain.

Disclosure: As an Amazon Associate, I earn from qualifying purchases. Thanks for supporting this blog and helping me stay caffeinated in the post-grad world.