In almost every doctoral thesis defense the committee asks the same things: why you chose that design, how you justified your sample size, whether your instruments were validated in your population, whether you checked the assumptions of your analyses, whether you controlled for multiple comparisons, whether you report effect sizes, how far you can generalize, what your work adds to what is already published, and what its real limitations are. Those are twelve questions that come up defense after defense, whether you work in psychology, biology, economics, education or nursing. Below you have all twelve, why the committee asks them and how to approach each answer.
A defense feels unpredictable, but it rarely is. A competent committee keeps returning to the same fronts: the decisions you made and did not justify, the limits of what you can actually conclude, and your real command of the methods. If you prepare those questions in advance, you arrive with thought-out answers instead of improvising under pressure. And if you want the ones for your specific thesis, with your objectives and your analyses, there is a free defense simulator that generates them from your summary.
Why a defense is more predictable than it looks
The committee is not trying to catch you out on a trick: it wants to confirm that you understand what you did and that you recognize its limits. Almost every question comes from one of three places: a methodological decision that was never justified in the text, a conclusion that goes beyond what the data allow, or an analysis whose assumption or alternative you did not consider. Knowing those patterns is half the work.
On the theoretical framework
The committee wants to confirm you know the field beyond the references you cited. Typical questions: Why this construct and not a related one that could also explain the phenomenon? Which prior study contradicts your findings, and how do you account for it? Where does your contribution sit against the dominant theory in the area?
The best preparation is not memorizing more citations. It is having your introduction’s argument straight: what gap you identified, why it matters, and why your design is a reasonable way to address it. Not the only way, a reasonable one.
On design and justification
1. Why did you choose this design and not another? They want to see that the choice answers your question, not that it was convenient. Tie design to objective: what your design can answer and what it rules out, and why the alternatives fit worse.
2. How did you justify your sample size? The flagship question. If you ran an a priori calculation (G*Power, simulation), walk them through it; if not, reason about the minimum effect you could detect. What does not work is "it was what I could get." Use the free sample size calculator if you need the logic.
3. Is your sample representative? Who can you generalize to? Be honest about the sampling limits (convenience, a single institution) and bound who your conclusions apply to. A committee punishes overgeneralizing more than admitting a limit.
On measurement and instruments
4. Why these instruments, and are they validated in your population? Cite validation in your language and population; if you used an adapted version, explain the process. If reliability in your sample was modest, raise it yourself first.
5. How did you ensure measurement quality? This is where reliability (alpha, omega) lives, and in psychometric work the factor structure and measurement invariance if you compare groups. If you compared groups without testing invariance, be ready to justify it.
On the statistical analyses
6. Did you check the assumptions of your analyses? Be clear on what each test required (normality of residuals, homoscedasticity, sphericity, multicollinearity) and how you verified it. If one failed, explain what you did (transform, robust test, non-parametric alternative). If you want to go through them one by one before the defense, there is a checklist in the guide on how to verify statistical assumptions.
7. Why this analysis and not an alternative? A member will often propose the model they would have used (a mixed model instead of repeated-measures ANOVA, an ANCOVA instead of comparing groups). Do not get defensive: acknowledge the alternative, say what it adds and why your choice was reasonable for your question and data.
8. Did you control for multiple comparisons? If you ran many tests, explain the correction (Bonferroni, FDR) or why you did not apply one. No control without justification is an easy criticism.
9. Do you report effect sizes, not just significance? A significant p with a trivial effect is not a finding. Keep your effect sizes and their practical interpretation in your field ready. If you are unsure how to read them out loud, here is the interpretation guide for Cohen's d, eta² and r.
On interpretation and contribution
10. You use causal language with a design that does not support it. If your design is cross-sectional or correlational, watch the verbs: "predicts", "produces", "causes". The answer is not to retract but to show you distinguish association from causation and to reframe your conclusions accordingly.
11. What does your thesis add that was not already in the literature? Prepare a two-sentence answer: the specific gap you fill and why it matters. It is surprising how many defenses stumble here for lack of a clear one.
12. What are the limitations and what would you do differently? Make your limitations the real, relevant ones, not the textbook ones. Showing you know exactly where your work is weak signals research maturity, not weakness. To walk in with that list already written, review the most common statistical errors in a thesis first: a good share of the limitations you end up defending start there.
Title, research and final defense questions
In the Philippines, and in many programs that follow the same model, a thesis is defended three times, and each panel asks different things. These are the questions that come back at each stage.
Title defense
The panel is deciding whether the topic deserves a study at all. Expect: Why this topic, and what gap does it fill? Is the title specific enough, with the variables, the population and the setting in it? Can you finish it with the time, the participants and the access you actually have? Who benefits from the results? Bring three title options ranked, each with a one-sentence statement of the problem.
Research (proposal) defense
This is the defense of Chapters 1 to 3: the problem, the review of related literature and the methodology. The questions are the ones in the design and measurement sections above, plus a few that come up in almost every proposal:
- Does each statement of the problem have a matching hypothesis and a matching statistical treatment?
- What does your conceptual framework predict, and which arrow in it does your design actually test?
- How did you compute your sample size? If you used Slovin’s formula, know what it assumes: it fixes a margin of error for a proportion, and it is not a power analysis, so a panel member may ask what effect your sample can detect.
- Was your questionnaire validated? Who were the expert validators, was there a pilot test, and what reliability did it reach?
- Why this statistical tool and not another, and what will you do if its assumptions fail?
Final defense
Now the panel checks Chapters 4 and 5: results, discussion, conclusions and recommendations. Expect: Do your findings answer every statement of the problem, in order? How large are your significant results, not only whether they are significant? Do your conclusions say more than the data allow? Does each recommendation follow from a finding, or would it have been written without the study? What would you do differently? If you want to rehearse with the questions your own chapters raise, paste your summary into the thesis defense simulator.
Mistakes that sink a defense, even when the thesis is good
- Improvising instead of admitting you do not know. “That is outside the scope of this thesis, but it would be a good next study” beats a weak justification invented on the spot.
- Getting defensive. Most critical questions are not attacks; they are how the committee checks that you command the work rather than just executed it.
- Generic limitations. “Convenience sample, replication needed” is the answer the committee has heard hundreds of times. Name which limitation affects which conclusion, and why it does not sink the main finding.
- Reading the slides. Have your thesis and notes at hand for figures, but answer questions of substance from understanding.
- No answer ready for the data that did not behave. Keep a hidden slide with the sensitivity analysis or the result that went against you. The difference between improvising and having it ready shows.
The curveball
There is almost always an unexpected question that is not on any list: a twist on your mechanism, an alternative explanation of your results, an implication you had not considered. You do not prepare it by memorizing; you prepare it by knowing your thesis so well that you can reason live. If you have the twelve above covered, the curveball stops being scary.
Prepare the questions for YOUR thesis
Before the defense: this list is the general pattern, but what really changes the outcome is seeing the questions your specific work raises. That is why I built the Thesis Defense Simulator: paste your thesis summary (objectives, method and results) and it returns the questions the committee will most likely ask, why they ask them, and how to approach each answer. It is free and it works whatever your discipline. And if what you are defending is an undergraduate or master's dissertation rather than a PhD, use the simulator's dissertation version instead, tuned to that committee's level of demand.
Frequently asked questions
How long does a thesis defense last?
It varies by university and country, but a typical defense runs 45 to 90 minutes: 20 to 30 minutes of presentation followed by questions from the committee. Check your program’s regulations, because some panels also hold a private deliberation before announcing the result.
Can I bring notes or consult my thesis during the defense?
Generally yes: nobody expects you to memorize every figure. What counts against you is reading to answer questions of substance, such as why you chose a design or what your results mean. Those should come from understanding, not from the page.
What if I do not know how to answer a question?
Acknowledge it with confidence instead of improvising badly. Saying that the question falls outside the scope of the thesis but would be a valuable future direction is a far better answer than a weak justification. Committees value intellectual honesty.
Is it a problem if my results did not confirm my hypothesis?
No. Null or unexpected results are valid contributions. The committee evaluates your methodological rigor and your ability to interpret what you actually found, not whether the results came out the way you expected.
And if what you are facing is a journal submission rather than the defense, its peer-review counterpart is Previum. If you would rather prepare the statistical side with someone who has sat on committees, you can ask for a fixed quote through my statistical consulting.