How to Discuss the Limitations of Your Study in a Defense or Viva
Treat every limitation as a bounded claim about scope, not a confession of failure. State what the constraint is, say what it does and does not affect, and leave the examiner with a clear picture of what your study can legitimately claim. That is what they are looking for.
Last updated
What the examiner is actually checking
When an examiner asks about limitations, they already have candidates in mind. One has clearly thought about where the study's claims end. The other has treated limitations as something to get past quickly, or worse, as accusations to rebut. The question is designed to tell the two apart.
They are not trying to find out whether the study is flawed. They assume every thesis has constraints — that is the nature of doctoral research conducted under real conditions of time, access, and funding. What they want to know is whether you understand the boundaries of your own evidence, and whether you made proportionate claims given those boundaries.
In UK vivas the question often arrives fairly early and without much preamble: 'What do you see as the main limitations of your study?' In US committee defenses it may come as a follow-on after a finding has been pressed: 'Doesn't the single-site design limit what you can claim here?' Different packaging, same test.
Two failure modes are common. The first is treating limitations questions as an attack, answering defensively, and in the process telegraphing that you haven't thought carefully about what the study can and cannot support. The second is volunteer-listing every imperfection in a bid to seem rigorous — which instead signals that you can't distinguish what matters from what doesn't.
Limitation, weakness, flaw — the distinction that affects how you answer
These three words are used interchangeably in casual conversation about research. In an examination room they carry different weight, and conflating them is one of the more common ways candidates concede more than they need to.
A limitation is a deliberate or unavoidable constraint on scope. You collected data in one country, over six months, from a particular professional group. The study doesn't claim to generalise beyond that. The limitation is built into the design; it narrows the claim but doesn't threaten it.
A weakness is something remediable — a gap in the literature review that, in retrospect, should have been included, a secondary analysis that could have been run, a theoretical thread left underdeveloped. It reflects a decision that might reasonably have gone differently. Acknowledging a weakness means saying 'this could have been done better,' which invites a follow-up about whether it undermines the thesis. Be precise about the implication.
A flaw is a design or execution problem that materially undermines the central claim. A measure that doesn't validly capture the construct being studied. A comparison that isn't actually comparable. A missing literature stream that directly contradicts the theoretical framework. If a flaw is present and goes unacknowledged, examiners will surface it. If it is acknowledged, the honest response is to assess how much of the central argument survives it — which is a harder conversation than discussing a limitation.
The categories to prepare for — and how to bound each one
Limitations cluster into recognisable types. Knowing the type matters because the appropriate bounding language differs between them.
- Sample and scope: who or what you studied. The bound is a statement about who the findings do and don't apply to. 'These findings describe the experience of senior nurses in acute NHS trusts in England during 2022–23. I make no claim about primary care staff, private sector settings, or earlier periods.' That is a complete limitation statement for scope.
- Method and design: the research approach chosen and the trade-offs it carries. Cross-sectional designs cannot establish causal direction. Single-case studies don't support statistical generalisation. Ethnography is subject to researcher positionality. The bound is to restate what kind of claim the design does support — association rather than causation, theoretical generalisation rather than population generalisation — and be explicit about it.
- Measurement: whether your instruments, interview protocols, or observational categories captured what you intended. The bound requires being specific: which construct, which operationalisation, and what the likely direction of any mis-measurement would be. 'Self-reported time spent on task tends to over-estimate actual time, so my estimates of workload should be read as upper bounds.'
- Generalisability: the reach of your findings beyond the study context. This overlaps with sample/scope but extends to theoretical claims as well. The question is not just who you studied but whether the mechanism or concept transfers. State the conditions under which you believe transfer is plausible and the conditions under which it isn't.
- Time and access: when data were collected and what that means for currency, and whether access constraints shaped the sample in ways that affect the conclusions. These are often easy to state and bound: 'Data collection predates the 2024 policy change, so the findings reflect pre-reform conditions.' That sentence both acknowledges the constraint and bounds it precisely.
Prepare a short bounding statement for each limitation present in your thesis. You don't need to deliver all of them in the examination — but having them ready means you can pick the right one when the question lands, rather than improvising.
One practical note on qualitative work: generalisability is sometimes the wrong frame. If your study is making theoretical rather than statistical claims, the relevant question is transferability — whether the conceptual categories or mechanisms you developed can be applied by readers in comparable contexts. This isn't a weaker form of generalisation; it's a different kind. Being clear about which you are claiming prevents a long and unproductive exchange about sample size.
The structure of a good limitations answer
A reliable structure has four moves. They don't need to be announced or performed as a template — the logic just needs to be present in the answer.
- Name it. One sentence, no softening. 'The main limitation is the single-country sample — all data come from UK secondary schools.'
- Bound it. Say what it affects and, more precisely, what it does not. 'This means the findings cannot be taken as representative of school systems with different funding structures or curriculum regimes. It does not affect the internal relationships I found between teacher workload and reported autonomy, which are likely to appear in comparable institutional contexts.'
- Mitigate or explain. Either describe what you did to address the limitation, or explain why you accepted it. 'A multi-country comparison would have required separate ethical approvals and translation work beyond the scope of a single PhD. The UK context was chosen deliberately because it allowed depth of access.'
- State the scope of your claim. Close the answer by restating what you are and aren't claiming. 'My argument is about the mechanism in this context, not about universality. I think the mechanism is plausible elsewhere, but that needs testing.'
The fourth move is often skipped, and that is the most common reason answers trail off rather than land. Restating the scope of the claim — what you are asserting, given the limitation — closes the loop. It shows the examiner you know exactly what the evidence supports.
Weak answer — over-apologising
'Yes, I know the sample is quite small and only from one setting, which is a significant problem, and I should probably have recruited more widely, and the generalisability is quite limited, and I did try to get more participants but couldn't...' — Four concessions and no bounding. By the end the examiner knows the candidate regrets the study but still has no idea what it can and can't claim. The answer invites a much harder follow-up.
Strong answer — same limitation
'The sample is drawn from one NHS trust, so the findings are specific to that institutional context. What I can claim is how the process worked in that setting, in detail, over eighteen months. I can't claim it operates the same way elsewhere. What I'd expect to transfer to comparable acute trusts is the general pattern — the mechanism — but the specific organisational conditions would need to be accounted for in any replication. The thesis makes that scope explicit in the discussion chapter.'
Four traps that cost candidates marks
Each of the following is common enough that examiners see them regularly. They are worth naming plainly.
- Over-apologising. The candidate who treats every limitation as a confession undermines the thesis faster than any examiner would. Limitations describe the scope of the study; they are not moral failures. The framing should be confident: you understood the trade-off, you accepted it, and you know what it means for the claim.
- Listing everything. Producing six limitations in rapid succession signals that you haven't decided which ones matter. Pick the two or three that are most consequential, bound each one carefully, and stop. A list without bounding is just itemised anxiety.
- Claiming no limitations. A small number of candidates attempt this, either through genuine overconfidence or because they confuse 'limitation' with 'flaw'. Every study conducted in real conditions has scope constraints. Claiming otherwise does not impress examiners — it tells them you haven't engaged with the question.
- Conceding limits that collapse the core claim. This is the inverse of over-confidence, and it is worse in practice. If, under pressure, you agree with an examiner's framing that a particular limitation makes the main finding unreliable, you have done their job for them. Before entering the examination, know which limitations affect scope and which would — if they were real problems — undermine the central argument. For the latter, be clear about why you believe they are not in that category. Then hold that position.
The trap most worth preparing for specifically is the last one. Examiners sometimes press hard on a limitation to see whether the candidate will break. 'But doesn't that mean you can't really claim X?' is not always a genuine challenge — sometimes it is a test of whether you know how far the limitation reaches. If X is genuinely unaffected by the limitation, say so and explain why. That takes more confidence than agreeing, and it is the right answer.
One final point: the limitations section of the written thesis and the oral defense are different situations. In the text you are writing for a general scholarly audience and covering the ground comprehensively. In the examination you are responding to a specific question from a specific examiner with a specific concern. The oral answer should be targeted, not a recitation of the limitations chapter. Read the question before delivering the prepared answer.
Frequently asked questions
- How many limitations should I mention in the defense?
- Two or three, at most. Each needs to be named, bounded, and connected to its implication for the claims. A longer list, delivered quickly, signals that you can't distinguish which limitations matter — and gives the examiner more threads to pull on. Lead with the one that is most consequential or most obvious to a reader of your methods chapter.
- Should I mention limitations proactively, or wait for the examiner to raise them?
- Wait. Raising limitations before you've established the positive case inverts the persuasive order. Present your contribution and findings first. When the examiner asks about limitations — and they will — you answer from a position of having already demonstrated what the thesis achieved. Some candidates briefly note in their opening summary that they'll address limitations when asked; that's fine, but don't lead with the problems.
- What's the difference between a delimitation and a limitation?
- A delimitation is a deliberate scope decision you made at the outset — choosing to study one country, one method, one time period. It is a boundary you drew, not a constraint imposed on you. A limitation is a constraint that reduced what you could claim, whether by design or circumstance. In practice the distinction matters for how you talk about each: delimitations are defended as appropriate choices; limitations are bounded and explained. Conflating them, or treating all scope decisions as limitations, can make the thesis sound weaker than it is.
- An examiner says my limitation undermines the whole finding. How should I respond?
- Don't agree reflexively, and don't get defensive. Restate the finding precisely, then trace what the limitation actually does to it. Often a limitation constrains how far the finding reaches, or adds uncertainty about mechanism, without making the finding itself unreliable. If the examiner has correctly identified a genuine flaw, the right move is to engage honestly: assess what the thesis still contributes at a reduced claim level, and hold that ground. Agreeing that the whole finding is undermined is almost never the accurate answer — and it is rarely a good one strategically either.
- Does any of this differ between a UK viva and a US dissertation defense?
- The underlying expectations are the same: bounded claims, honest assessment of scope, no over-apologising, no denial. The format differs. UK vivas go directly into detailed questioning, often with just two examiners, so there is less opportunity to establish the positive case before limitations come up. US defenses usually involve a public presentation before the closed examination, which means you've already framed the work on your own terms before questions begin. In both contexts the answer structure — name, bound, mitigate, scope — works the same way.
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
Practice bounding your limitations out loud
Reading about this is straightforward. Doing it under questioning from an AI examining committee — one that will press on your answer — is different. MockDefense runs the examination; you find out where your bounding breaks down before the real thing.