MockDefense
Guide

Methodology Defense Questions: How to Justify Your Research Design

Methodology is the most probed area of almost any defense or viva. Examiners are not looking for the "best" possible design — they want to know that you understood your options, made deliberate choices, and can articulate the trade-offs. The question is not "why didn't you do X?" — it's "why was your approach the right one for your problem?"

Last updated

Why examiners spend so much time here

Methodology is where the integrity of your findings lives. A conclusion is only as strong as the process that produced it. If an examiner can shake your design, they can shake everything that follows — so they test it.

This is not adversarial for its own sake. Examiners need to satisfy themselves, and any future reader of your work, that the research design was fit for the research question. They are also checking whether you, the researcher, can own the choices rather than recite them.

The candidate who says "I used a case study design because it was appropriate" will get a follow-up. The candidate who says "I used a case study design because my research question was about process and context in a bounded setting, and a survey instrument would have flattened exactly what I needed to see" is doing the work the examiner was hoping for.

The questions examiners ask — and what they're really checking

Why did you choose this methodology?

The most common opening gambit. They want to hear a logical chain from your research question to your design. State the question, state what kind of answer you were after (explanatory, descriptive, interpretive), and show how the design was suited to producing that kind of answer. If it also happened to fit your access constraints, say that too — honesty about pragmatics is not a weakness.

What alternatives did you consider, and why did you reject them?

This is a genuine intellectual question, not a trap. Name one or two plausible alternatives, say what they would have been good for, and explain specifically what they would have failed to capture or what they would have required (data, time, access) that was not available. "I considered a longitudinal survey but my research question was about individual meaning-making, not population-level trends" is a stronger answer than "it wasn't feasible."

How did you approach sampling / participant recruitment, and why those criteria?

In qualitative work, defend purposive or theoretical sampling by connecting it to what you needed: heterogeneity, depth, particular expertise or experience. In quantitative work, explain your sampling frame and any known non-response issues. Don't pretend convenience sampling is something grander — examiners have seen every version of that. Acknowledge the limitation and say what it means for scope of claim.

How do you know your analysis is credible?

Quantitative candidates: report your reliability checks, model diagnostics, and how you handled violations of assumptions. Qualitative candidates: member-checking, thick description, negative case analysis, audit trail — use whichever apply and explain what each actually added rather than listing them as a ritual. Credibility checks only land if you can say what they would have revealed had they gone differently.

Could your findings be an artefact of the method rather than the phenomenon?

A sharper version of the validity question. The right response is not denial. Acknowledge which parts of your findings are method-sensitive, name the specific risks (observer effects, demand characteristics, measurement instrument choices), and explain what you did to reduce them. Then hold the line on what the method can legitimately claim.

Defending trade-offs made under real constraints

No doctoral candidate designs their study in a vacuum with unlimited time, funding, and access. Examiners know this. What they want to see is that you made your constraints visible, made principled choices within them, and were honest about what those choices cost you in terms of scope.

A smaller sample is not a fatal flaw if you are explicit about what it limits. A single-site study is not automatically weak if you explain why depth at one site served your question better than breadth across five. The flaw is pretending the constraint doesn't exist or claiming more generalisability than the design supports.

Defending a choice versus apologising for it

The single most common failure mode in methodology questioning is what might be called pre-emptive contrition: the candidate flags every limitation as a flaw and talks about the study as though it should have been something else entirely. This is the opposite of ownership.

Limitations are not apologies. A limitation is a bounded, specific statement about what your design can and cannot support. "This study cannot be generalised beyond the professional context studied, because recruitment was purposive and not representative" is a limitation. "My sample was really small and the study is probably not very useful" is an apology. Examiners want the former.

Equally, do not over-defend. If an examiner points to a genuine weakness you hadn't named, acknowledge it. Candidates who argue against clear critiques lose credibility faster than candidates who say "that's a fair point — here's how it affects the scope of my claim."

  • Name your limitations before the examiner does — it shows you understand them.
  • Frame each one as a bound on your claim, not a verdict on your competence.
  • When pushed on a choice, stay with it if it was justified; concede the point if it wasn't.
  • Never present a constraint (small budget, limited access) as a methodological virtue it wasn't.

How to prepare

Re-read your methodology chapter as though you didn't write it. Every claim about why you did something is a potential question. Every place where you hedged or used passive voice to avoid justifying a choice is where an examiner will pause.

For each major design decision, write a two-sentence justification — one connecting the choice to the research question, one naming the alternative you rejected and why. If you can't write those two sentences, you need to think the decision through before the exam.

Then practise saying these answers aloud. Reading a justification and saying it under questioning are not the same cognitive task. Practice in conditions that approximate the real thing.

Frequently asked questions

What if an examiner asks about a method I didn't use at all?
They are usually probing whether you considered it. Have a sentence ready for any major methodological alternative in your field: what it would have been suited for, and what your own question required instead. You don't need exhaustive knowledge of every method — just enough to explain why yours was the better fit.
Is it acceptable to say my sample size was limited by access rather than by design?
Yes — access constraints are real and examiners understand them. The key is to say so explicitly, explain what you did to make the most of the sample you had, and be precise about what the size limitation means for the scope of your claims. Pretending a convenience sample was theoretical sampling is more damaging than just naming the constraint.
My methodology has a known limitation I'm worried the examiner will probe heavily. How should I handle it?
Raise it yourself, before they do. Acknowledge it briefly, state specifically what it limits (not "the whole study" but the specific inference it affects), and say what you did to mitigate it. Candidates who identify their own limits clearly are demonstrating exactly the critical ownership examiners want to see.
Can I say I would do something differently if I were starting over?
Yes, and it can be a strong answer — if it's specific and doesn't undermine your core findings. "With more time I would have added a second fieldwork phase to test the emerging themes" is intellectually honest. Answering every methodology question with "I'd do it all differently" reads as lacking confidence in the work you actually did.

The MockDefense Committee

Doctoral defense preparation, MockDefense

MockDefense builds AI examiners that rehearse the questions a real doctoral committee asks — on methodology, contribution, and the gaps you haven't patched yet. Our guides are written from that examiner's-eye view of what defenses actually test.

Keep preparing

Practise before the real thing

Describe your dissertation in two minutes and let a simulated committee question you the way real examiners will. Start with a free drill.