How to defend your methodology in a PhD viva

Why methodology questions matter

Methodology is one of the most common — and most demanding — areas of PhD viva questioning. Examiners spend significant time on it because research design is where many of the most consequential decisions in a thesis are made. Every methodological choice has implications for the validity, reliability, and generalisability of your findings. Examiners want to know whether you understand those implications, and whether you can justify the choices you made.

The challenge for most candidates is not that they don't know their methodology — it's that they haven't articulated the reasoning behind it out loud, under questioning. These are decisions that often felt obvious at the time and that have since become implicit. Making them explicit and precise again is what methodology preparation is about.

What examiners are looking for

When examiners ask about your methodology, they are generally looking for four things:

• Justification of your approach. Not just "I used thematic analysis" but "I used thematic analysis because my research question was exploratory and I was not seeking to test a predefined theoretical framework."
• Awareness of alternatives. What other approaches did you consider? Why did you not use them? Being able to articulate this shows intellectual breadth and deliberate decision-making.
• Understanding of your method's limitations. Every method has constraints. Knowing yours — and being able to explain how they affect your conclusions — is a mark of rigour, not weakness.
• Evidence of consistent application. Did you follow through on your methodological commitments? If you claimed to use a particular approach, did you use it, and can you describe how?

How to explain your methodological choices

The clearest answers to methodology questions follow a structure: state the choice, give the reason, acknowledge the trade-off. For example:

"I chose semi-structured interviews rather than a survey because my research question required in-depth exploration of participant experience. A survey would have given me breadth but not the depth I needed to address that question. The limitation is that this restricts generalisability, which I address in the limitations chapter."

That is a complete answer: what, why, and what it costs. Practising this structure out loud — for each of your main methodological decisions — is one of the most efficient forms of viva preparation.

How to discuss limitations

Limitations are not failures. They are the honest acknowledgement of what your research design could and could not do. Examiners expect you to know them precisely and to be able to contextualise them.

When discussing a limitation, the most effective approach is:

• Name it clearly.
• Explain why it exists (what constraint led to it).
• State its scope (how much does it affect your findings).
• Place it in context (is it a limitation of your specific study, or a known limitation of this approach generally?).

Candidates who struggle with limitations questions usually try to minimise them. The more effective response is to acknowledge them precisely and confidently — demonstrating that you understand your own research clearly enough to describe its edges.

How to compare alternatives

A common follow-up after any methodology question is: "Why didn't you use [alternative]?" This is a question about your decision-making process, not a criticism of your choices. The best answers describe what the alternative would have given you, what it would have cost you, and why the trade-off favoured your choice.

For example:

"Grounded theory would have been appropriate given the exploratory nature of my question, but it would have required a much larger dataset and a longer iterative process than my timeframe allowed. Thematic analysis gave me a structured, rigorous approach to the same kind of exploratory question within those constraints."

How to practise follow-up questions

The hardest part of methodology questioning is not the initial question — it's the follow-up. "Why did you use thematic analysis?" is manageable. "And why inductive coding rather than a predetermined framework?" followed by "And how did you ensure consistency in your coding process?" is where the pressure builds.

Practising follow-up sequences — not just individual questions — is essential. You can do this by asking a colleague to press further on each answer, or by using a practice tool that generates follow-ups based on what you said.

Defensia's Methodology Focus examiner is specifically designed for this: it asks about your methodology, listens to your answer, and generates follow-up questions based on what you said. The session is spoken and real-time — which is the format that actually builds the flexibility the viva requires.