What the hour is for
A committee approves a date because the work is close. What remains is a conversation about judgment: why this design and not another, what the limitations mean for the claims, and what a reader should take away. The document proves the study happened. The defense proves the thinking was yours.
That distinction should change how you prepare. Rereading your own chapters is comforting and low value. Preparing to explain and defend the twenty decisions inside them is the actual work of the fortnight before.
The presentation has a fixed job
Twenty minutes, or whatever the committee allots, and the sequence is close to identical everywhere.
Keep the slide count low enough that you never read from them. A committee watching someone read has stopped listening, and the questions get sharper when attention drifts.
- The problem, in two slides, ending with why it still matters.
- The gap, stated as what is not yet known rather than as what has not yet been written about.
- The question and the design, side by side, so the fit between them is visible.
- The sample and procedures, briefly, with anything unusual explained before it can be asked about.
- Findings, one slide per finding, in the order the questions were asked.
- Interpretation, limitations and implications, with the limitations spoken by you first.
Four kinds of question
Almost everything asked falls into four types, and each has a shape of answer. Clarification wants a shorter version of something already in the document, so answer briefly and stop talking. Justification asks why you chose one path over another, so name the alternative, name the reason, and acknowledge the trade-off rather than pretending there was none.
Extension asks what the findings would mean somewhere else, and the honest answer usually begins by naming the boundary of your sample. Challenge questions the foundations, and the right response is neither defensiveness nor collapse. Restate the objection accurately, say what the study can and cannot claim in light of it, and where it is a genuine limitation, agree and point to where it sits in the document.
Rehearse with someone who interrupts
Practicing alone rehearses the presentation, and the presentation is the part that will go fine.
Not knowing is not a failure. An answer that names the limit, offers what the data can support, and says where you would look next is a doctoral answer. Inventing one is the only response that costs you anything.
- Give the talk once to somebody who has not read the document and can ask what a term means.
- Give it again to someone who will interrupt in the middle of a slide, because a committee will.
- Write the twenty hardest questions about your own study and answer each aloud in under a minute.
- Rehearse three sentences for the moment you do not know something, because that moment arrives for everyone.
The verdict is a list
Most defenses end in a pass carrying required revisions. Write every requested change down during the meeting, including who asked and what exactly they asked for, because memory of an hour like that is unreliable. Read the list back before leaving so the committee agrees with your version of it.
Then treat the revisions as a project with dates rather than a formality, since the degree is not finished until they are accepted. Where a document has already been through several rounds, a reader who has sat on committees is worth more than another pass by the author, which is what dissertation coaching provides at this stage.
Questions
How long should the presentation run?
Whatever the committee sets, and slightly under it. Running long is the most common avoidable mistake, and it eats the discussion, which is the part being assessed. Time a full rehearsal with a clock in view. If you are over, cut findings slides rather than the design explanation, because the design is what generates the questions worth answering.
Should I bring the full document to the defense?
Bring it, tabbed or searchable, with a one-page summary of your own tables. Turning to a page in five seconds when someone asks about a specific number is worth more than any slide. Committee members read at different times, and a question sometimes refers to an earlier version of a chapter than the one in front of you.
What should I do the week before?
Rehearse questions rather than slides. Reread the methods and limitations chapters closely, since that is where most questions come from, and settle the practical arrangements so nothing distracts you on the day. Sleep is part of preparation. A defense is an hour of precise recall, and tiredness costs more there than one extra rehearsal returns.
What happens if the committee asks for major revisions?
It is a normal outcome and not a rejection. Ask for the requirements in writing, agree a resubmission date with your chair, and answer each item as a numbered response so the committee can see its own list addressed. Most major revisions are structural rather than fundamental, and the second reading nearly always goes faster than the first.
Can a defense genuinely be failed?
It is uncommon, because committees do not usually schedule a defense for work that is not ready, and that is worth remembering on the morning. Where it does happen, the outcome is normally a deferral with a list attached rather than an ending. Ask what has to change, agree a new date, and treat it as a longer revision round.
