Proposal Defence
Session at a Glance
Formal presentation and defence of the research proposal before a review panel; demonstration of readiness to proceed to execution phase
15-minute oral presentation + 10–15 minutes of panel Q&A; structured feedback on proposal strengths and revision requirements
2 hrs Prep Workshop + Individual Defence Slot + Revision Time
Proposal formally approved for execution
Learning Objectives
By the end of this session, you will be able to:
- Construct a concise, persuasive 15-minute oral presentation that communicates the core argument of your research proposal — problem, gap, RQs, methodology, and contribution — to an academic review panel
- Anticipate the questions a review panel is likely to ask and prepare substantive, evidence-based responses that demonstrate depth of understanding
- Defend your methodological choices by articulating the rationale behind your research design, sampling strategy, and analysis plan — including why plausible alternatives were rejected
- Receive, interpret, and prioritise panel feedback — distinguishing between mandatory revisions, suggested improvements, and stylistic preferences
- Transition from proposal approval to methodology execution, using panel feedback to strengthen the research design before data collection begins
Week 8 Planner
This week is structured around the defence event. The opening workshop prepares you; the defence is the focal point; the post-defence work converts feedback into an approved, strengthened proposal.
| Time / Phase | Activity | Details | Mode |
|---|---|---|---|
| 0:00–0:30 | Defence Prep Workshop | Presentation structure and slide design; anticipating panel questions; handling Q&A; common defence mistakes; mock Q&A demonstration | Whole class |
| 0:30–1:00 | Presentation Rehearsal | Each student delivers a 10-minute condensed version to a peer. Peer provides timed feedback: was the problem clear? Were RQs justified? Was methodology convincing? | Pairs |
| 1:00–1:30 | Anticipated Questions Exercise | For your proposal, write down the 5 hardest questions the panel could ask. Draft responses. Exchange with a partner — they try to find the question you didn't anticipate. | Pairs |
| 1:30–1:45 | Break | — | — |
| 1:45–2:00 | Panel Logistics Briefing | Defence schedule; panel composition; evaluation criteria; what happens after the defence (approval, conditional approval, revision); professional conduct | Whole class |
| Day 2–3 | Individual Defence Slots | 15-minute presentation + 10–15-minute Q&A before a panel of 2–3 faculty. Panel deliberates and provides immediate verbal feedback; written feedback follows within 48 hours. | Individual |
| Day 3–5 | Post-Defence Revision | Incorporate panel feedback into the proposal. Submit revised proposal for formal approval. Begin preliminary methodology reading if approval is confirmed. | Individual |
1. The Purpose of a Proposal Defence — Beyond Approval
The proposal defence is often misunderstood as an examination where you must "pass" or face rejection. A more accurate framing: it is a structured scholarly conversation designed to strengthen your research before you commit months to executing it. The panel's job is not to find reasons to reject your proposal — it is to identify weaknesses now, while they can still be fixed, rather than during the final viva when it is too late.
A proposal defence is a formal oral presentation and Q&A session in which a student presents their research proposal to a faculty review panel, demonstrates mastery of the relevant literature and methodological reasoning, and receives expert feedback intended to strengthen the research design before execution begins. The outcome is typically: approved, conditionally approved (with specified revisions), or referred for major revision and re-defence. Outright rejection is rare and indicates fundamental problems that should have been caught long before the defence.
1.1 What the Panel is Actually Evaluating
| Dimension | What the Panel Asks Themselves | What This Means for You |
|---|---|---|
| Problem Significance | "Is this a genuine problem worth a capstone? Does the student understand why it matters — not just that it exists?" | Open with evidence of the problem's significance, not just its existence. Cite data. Show who is affected and at what scale. Make the panel care. |
| Intellectual Ownership | "Does this student understand the literature they're citing, or are they reciting? Can they discuss authors, debates, and gaps without reading from slides?" | Know your literature well enough to discuss it conversationally. If the panel asks "How does your study differ from Sharma (2022)?" you should be able to answer without flipping through notes. |
| Methodological Reasoning | "Has the student thought through their methodology, or did they pick the first method that came to mind? Can they explain why they chose X over Y?" | For every methodological choice, know the alternative you rejected and why. "I chose semi-structured interviews over structured surveys because my RQs are exploratory and I need to understand the 'why' behind behaviours, not just measure their frequency." |
| Feasibility Awareness | "Can this actually be completed within the capstone timeline and resource constraints? Does the student understand what they're committing to?" | Be realistic about scope, sample size, and timeline. A panel would rather hear "I've scoped this to three organisations to ensure depth and feasibility" than "I'll study the entire Indian retail sector." |
| Ethical Maturity | "Has the student identified the ethical dimensions of their research? Do they have a plan, or is ethics an afterthought?" | Proactively address ethics — don't wait for the panel to ask. Include a dedicated slide. Show you've completed the self-assessment and have specific mitigation strategies. |
| Coachability | "Does this student listen to feedback and engage with it thoughtfully, or do they become defensive? Can they be supervised for the next 22 weeks?" | When the panel offers criticism, listen. Take notes. Ask clarifying questions. Never say "But my supervisor said..." or "That's not what the textbook says." Say "That's a helpful observation — I'll strengthen that section." The panel is assessing your ability to be supervised, not just your proposal. |
A proposal defence is not an adversarial proceeding. The panel members are faculty who want the capstone programme to produce strong research. They are not trying to fail you — they are trying to ensure that the research you spend the next 22 weeks executing is well-designed, feasible, and ethical. The worst outcome is not a conditional approval with revisions; it is an unconditional approval of a weak proposal that will produce a weak dissertation. The panel's criticism is an investment in your project's success. Treat it as such.
2. Designing the Defence Presentation
A 15-minute academic presentation is a distinct genre with its own constraints. You cannot simply read your proposal aloud or display every section on slides. You must make strategic choices about what to include, what to emphasise, and what to leave for the Q&A.
2.1 The Defence Presentation Structure — Slide by Slide
| Slide | Content | Time | What to Include — and What to Leave Out |
|---|---|---|---|
| 1 | Title Slide | 0:30 | Working title, your name, course (SEC701), supervisor's name. Keep it clean — this is not where you impress the panel. |
| 2 | The Problem | 2:00 | Include: A single, sharp problem statement. Evidence that the problem is real (1–2 key statistics or citations). Who is affected and at what scale. Why existing solutions or prior research haven't solved it. Leave out: Broad background on the industry/sector. History of the problem. Multiple competing definitions of the problem. You have 2 minutes to convince the panel this matters — don't spend it on context they already know. |
| 3 | Research Questions | 1:00 | Include: Primary RQ and 2–4 sub-RQs, clearly stated on one slide. A brief statement connecting RQs to the problem: "Given this problem, my study asks..." Leave out: The full problem statement again. Hypotheses in statistical notation (save for methodology). Justifications for each RQ (these should emerge from the literature review, which comes next). |
| 4–5 | Literature & Gap | 3:00 | Include: 3 themes from your synthesis matrix — one slide each or organised visually. For each theme: what the literature collectively shows, where consensus and debate lie. A clear gap statement: "What we don't know is..." that leads directly to your RQs. A visual synthesis matrix (simplified) can be very effective. Leave out: Individual paper summaries. A list of "Author X found Y." More than 6–8 key citations on screen at once. The literature review should demonstrate command of the field, not enumerate everything you read. |
| 6 | Theoretical / Conceptual Framework | 1:30 | Include: Name the theory. Show the conceptual framework diagram (boxes and arrows). Briefly explain why this theory: "I use TAM because it explains the cognitive mechanisms through which users evaluate new technology, which directly maps to my RQs about adoption barriers." Leave out: A full history of the theory. Alternative theories you considered (save for Q&A — it's a common question). |
| 7–8 | Proposed Methodology | 3:30 | Include: Research paradigm and design. Population, sample, sampling strategy — specific numbers. Data collection methods and instruments. Data analysis plan — name the specific techniques. Validity/reliability/trustworthiness strategies. A timeline visual (Gantt chart or simplified roadmap). Leave out: The full survey questionnaire. The complete interview protocol. Detailed statistical formulas. You can refer to these as available if asked, but don't put them on slides. |
| 9 | Ethics | 1:00 | Include: Key ethical considerations specific to your study. Consent and confidentiality procedures. Data security measures. Ethics approval status. Leave out: Generic statements about "following ethical guidelines." The Belmont principles explained from scratch — the panel knows them. |
| 10 | Expected Contribution & Timeline | 1:30 | Include: What will this study contribute — to theory, to practice, to methodology? Who will use the findings? A high-level timeline showing major phases. Leave out: Overclaiming ("This will revolutionise..."). Week-by-week detail (the proposal has the detailed timeline; the presentation needs the big picture). |
| 11 | Thank You / Questions | 0:30 | Your name, contact information, and "Questions and Discussion." Consider putting your conceptual framework or RQs on this slide as a visual anchor during Q&A. |
2.2 Slide Design Principles for Academic Presentations
If a slide contains two distinct ideas, split it into two slides. The panel should be able to grasp each slide's message in under 10 seconds. If a slide takes 2 minutes to read, the panel is reading instead of listening to you.
Replace text with diagrams wherever possible. A conceptual framework as a diagram is far more effective than a paragraph describing it. A synthesis matrix as a simplified table shows the literature landscape instantly. A Gantt chart communicates the timeline in seconds. The rule: if it can be a visual, it should be.
Aim for 20–30 words per slide maximum (excluding references and tables). Use bullet points of 5–7 words, not full sentences. The slides are visual support for your spoken narrative — they are not a teleprompter. If the panel can get everything they need by reading your slides without listening to you, your slides have too much text.
Use one font family, one colour palette, one slide layout. The panel should not notice your slide design — they should notice your content. Fancy transitions, animations, and decorative elements signal that you spent time on aesthetics that could have been spent on substance. Academic panels prefer clean, professional, consistent slides.
Fifteen minutes forces you to identify what is truly essential about your proposal. If you cannot explain your research in 15 minutes, you may not understand it well enough yet. The constraint is not a burden — it is a diagnostic tool. Students who struggle to fit their presentation into 15 minutes often have scope problems: too many RQs, too broad a literature review, too complex a methodology. Use the time constraint to force clarity: if it doesn't fit, it may not belong.
3. The Q&A — Where the Defence is Won or Lost
The presentation demonstrates that you can communicate your research plan. The Q&A demonstrates that you understand it. Panels form their judgement primarily during the Q&A, because that is where they discover whether you have genuine intellectual ownership of your project or have simply memorised a well-designed set of slides.
3.1 The Question Categories — What to Expect
| Category | Example Questions | What the Panel is Testing | How to Prepare |
|---|---|---|---|
| Clarification Questions | "Could you clarify how you defined 'customer engagement' in your RQs?" "You mentioned a sample of 200 — is that 200 individuals or 200 organisations?" | Whether you've thought through the operational details, not just the high-level concepts. | These are the easiest questions. Answer concisely and directly. Don't over-explain — the panel just needs the specific detail they asked about. |
| Methodological Probing | "Why did you choose purposive sampling over snowball sampling for this population?" "You're using thematic analysis — which specific approach? Braun and Clarke's reflexive TA or a different variant?" | Whether your methodological choices are reasoned decisions, not defaults. Whether you know the alternatives. | For every method you chose, prepare: (a) what you chose, (b) the main alternative you considered, (c) why you chose what you did over the alternative, with specific reasoning (not just "it's more common"). |
| Scope and Feasibility | "Your sample requires access to senior executives at 30 firms. How will you secure that access?" "Training this model on 8,000 instances with 3 PEFT methods × 2 models × 3 seeds — have you estimated the total GPU hours required?" | Whether your plan is realistic. Whether you've identified and planned for practical obstacles. | Be honest about challenges. "Access to senior executives is a known challenge. I've identified three firms through my supervisor's professional network and will use snowball sampling from initial contacts. My contingency plan is to expand to middle managers if executive access proves infeasible." This answer demonstrates planning, not weakness. |
| Gap and Contribution | "Sharma (2023) also studied ESG disclosure in Indian manufacturing. What specifically does your study add that Sharma didn't?" "If LoRA already achieves 95% of full fine-tuning performance, what is the practical value of comparing three PEFT methods?" | Whether your gap is genuine. Whether you can articulate your contribution precisely. | Know the 2–3 closest studies to yours in detail. Be ready to explain: what they did, what they didn't do, and exactly how your study differs. If you can't distinguish your study from the closest prior work, the gap may not be real. |
| Theoretical Grounding | "You're using the Technology Acceptance Model, which was developed in 1989 for workplace technology. Why is it appropriate for consumer mobile banking in 2025?" "The Lottery Ticket Hypothesis was proposed for image classification — what evidence supports its application to NLP tasks?" | Whether you've critically evaluated your theory, not just adopted it. Whether you understand its boundary conditions. | Know the origins, assumptions, and boundary conditions of your theory. Be ready to explain: (a) why the theory is a reasonable fit despite differences between its original context and yours, (b) what modifications or extensions you're making (if any), and (c) what the theory cannot explain (and how you'll handle that). |
| Ethical and Practical | "You're interviewing employees about their managers' leadership styles. How will you ensure participants feel safe being candid?" "Your hate speech detection model will be publicly released. What prevents someone from using it to generate hate speech that evades detection?" | Whether you've thought through the human and societal implications of your research, beyond the formal ethics checklist. | Move beyond generic ethics statements. Show you've thought about the specific ethical dimensions of YOUR study in YOUR context. For BCA: always address dual-use. For BBA: always address power dynamics in organisational research. |
3.2 The Q&A Response Protocol
- LISTEN: Let the panel member finish their question completely. Do not interrupt. Do not start formulating your answer while they're still speaking. If you need a moment to think, say "That's an important question — let me gather my thoughts for a moment." This is professional, not weak.
- ACKNOWLEDGE: Start your response by acknowledging the question. "Thank you for raising that — it's a critical methodological consideration." Or: "That's a very helpful observation about the scope." This buys you 3–5 seconds to organise your thoughts and signals respect for the panel's expertise.
- ANSWER: Give a direct, substantive response. If you don't know something: "That's an aspect I haven't fully explored yet. Based on what I do know, my initial thinking is [X], but I will research this further and strengthen that section of the proposal." Never invent an answer. Academic integrity includes admitting the boundaries of your current knowledge.
- CHECK: If the question was complex, check: "Does that address your question, or would you like me to elaborate on any aspect?" This is not required for every question but is valuable when a question had multiple parts or the panel member's expression suggests uncertainty.
3.3 Handling Difficult Moments
| Situation | What NOT to Do | What to Do Instead |
|---|---|---|
| You don't know the answer | Panic. Invent an answer. Get defensive. Say "That's not relevant to my study." | "That's a valid question that I need to explore further. My current understanding is [X], but I recognise this as an area where my proposal needs strengthening. I'll address this in my revision." |
| The panel points out a genuine flaw | Argue. Justify. Insist your approach is correct despite the evidence. Blame your supervisor. | "Thank you — I see the issue now. I had approached this from [perspective], but your point about [specific flaw] reveals a gap in my reasoning. I will revise this section to address [specific issue]." |
| Two panel members disagree with each other | Take sides. Try to adjudicate. Look to your supervisor to resolve it. | "I can see there are different methodological perspectives on this. My approach was based on [reasoning]. I'm taking notes on both perspectives and will discuss with my supervisor how best to address this tension in the revised proposal." |
| The question is unclear or seems irrelevant | Say "I don't understand the question." Give an answer to what you think they might have asked. | "Could you help me understand the specific concern you're raising? I want to make sure I address it directly." This politely asks for clarification while demonstrating your willingness to engage. |
| You realise mid-answer that you're going off track | Keep talking, hoping you'll circle back. Trail off awkwardly. | "I realise I'm going broader than your question. Let me refocus — the specific point is [concise answer]." Self-correction demonstrates composure and self-awareness. |
The single most impressive thing a student can do in a defence is to say: "That's an excellent point that I hadn't considered. Here's how I'll address it." This response demonstrates: (a) you listen to feedback, (b) you can think on your feet, (c) you prioritise getting the research right over being right, and (d) you will be a good supervisee for the next 22 weeks. The student who defensively argues every point, no matter how valid, signals to the panel that they will be difficult to supervise. The student who engages thoughtfully with criticism signals that they are ready to execute a capstone.
4. Common Defence Pitfalls — and How to Avoid Them
| Pitfall | What It Looks Like | Prevention |
|---|---|---|
| Over-Running | "I have 10 more slides but I've already used 17 of my 15 minutes." The panel is visibly checking the time. The chair interrupts to ask you to conclude. | Rehearse with a timer at least 3 times. Aim for 13–14 minutes to leave buffer. Identify which 3 slides you can compress or skip if you're running long. Never go over 15 minutes — it signals poor preparation, not enthusiasm. |
| Reading Slides | You face the screen, not the panel. You read bullet points verbatim. The panel could have read your proposal instead. | Slides are visual anchors, not a script. Know your narrative well enough to speak from bullet points. Face the panel. Use presenter view (notes on your laptop screen, slides on the projector) if available. |
| Defensive Body Language | Crossed arms, avoiding eye contact, sighing at questions, interrupting panel members, arguing every point. | Maintain open posture. Make eye contact with the questioner. Nod to show you're listening. Take notes during questions — it signals engagement and gives you a moment to compose your response. Your body language communicates as much as your words. |
| The Kitchen Sink Literature Review | "I reviewed 87 papers, and here are all of them on one slide in 8-point font." The panel cannot read the slide and stops trying. | Present themes, not papers. A synthesis matrix visual is far more effective than a list of authors. If the panel wants to know about a specific paper, they'll ask — your job is to demonstrate thematic command, not enumerate everything you downloaded. |
| Underselling the Gap | "There is limited research on this topic." No evidence. No specificity. The panel is not convinced the gap exists. | Show the gap — don't just state it. "As the synthesis matrix shows, studies consistently examine X in context A (citations), but no published study has examined X in context B (India, Tier-2 cities, post-pandemic). This is the gap my study addresses." |
| Vague Responses to Specific Questions | Panel: "What's your plan if you can't reach your target sample of 200?" You: "I'll try harder to recruit participants." | Have contingency plans for: low response rates, data access delays, technical failures, participant dropout. "If I cannot reach 200 survey respondents, I'll extend the data collection window by 2 weeks and expand recruitment channels to include LinkedIn. If the sample still falls below 150, I'll acknowledge the reduced statistical power and frame the study as exploratory rather than confirmatory." |
| Ignoring Non-Verbal Cues | The panel member is leaning forward, about to ask a follow-up, but you keep elaborating on your answer. The chair is glancing at the clock. | Watch the panel while you speak. If a panel member looks satisfied, stop. If they look confused, pause and ask: "Would it be helpful if I elaborated on that point?" Reading the room is a presentation skill that applies as much to defences as to boardrooms. |
5. After the Defence — Feedback, Revision, and Approval
The defence does not end when you leave the room. What happens next determines whether you receive formal approval and how strong your research design will be when execution begins.
5.1 Understanding the Possible Outcomes
| Outcome | What It Means | What You Need to Do |
|---|---|---|
| Approved | The proposal is accepted as presented. The panel identified no substantive issues requiring revision. Your research design, RQs, and methodology are approved for execution. | Celebrate briefly — then get to work. Approval means your plan is sound, not that it's perfect. Continue refining your methodology as you enter Weeks 9–12. Document any changes you make to the approved proposal and discuss them with your supervisor. |
| Conditionally Approved | The proposal is fundamentally sound but requires specific revisions before formal approval is granted. This is the most common outcome — and it is a positive one. The panel has identified issues now that would have caused problems during execution. | Within 48 hours of receiving written feedback, create a revision plan: list each required revision, the specific change you will make, and the section(s) affected. Share this plan with your supervisor to confirm your interpretation of the feedback is correct. Complete revisions within the specified timeframe (typically 1–2 weeks). Submit the revised proposal with a cover letter explaining how each point of feedback was addressed. |
| Major Revision & Re-Defence | The proposal has significant weaknesses — typically in problem clarity, methodological rigour, or scope feasibility — that cannot be addressed through minor revisions. A second defence is required after substantial reworking. | This is serious but recoverable. Schedule an immediate meeting with your supervisor to understand the specific concerns. Do not rush to fix everything at once — identify the root issues. Re-defence is typically scheduled 2–4 weeks later. Use every available resource: supervisor consultations, methodology textbooks, exemplar proposals. The second defence must demonstrate that you have genuinely strengthened the proposal, not just made superficial changes. |
5.2 Converting Panel Feedback into a Revision Plan
| Panel Feedback | Type | Specific Action | Section(s) Affected | Priority | Status |
|---|---|---|---|---|---|
| Example: "Sample size justification is weak — 30 is too small for regression with 5 predictors" | Mandatory | Recalculate minimum sample size using Green (1991) formula N ≥ 50 + 8k; adjust target to 100; update power analysis (G*Power) | Section 6 (Methodology) | High | ☐ |
| Example: "Literature review reads as annotated bibliography in places — strengthen synthesis" | Mandatory | Restructure Section 4 around 3 themes from synthesis matrix; ensure every paragraph cites multiple sources; remove single-paper paragraphs | Section 4 (Lit Review) | High | ☐ |
| Example: "Consider adding TPB as a complementary theoretical lens" | Suggested | Evaluate whether TPB adds explanatory value beyond TAM for this context; discuss with supervisor; if yes, integrate into Section 5 | Section 5 (Theory) | Medium | ☐ |
| (Your feedback item 1) | ☐ | ||||
| (Your feedback item 2) | ☐ | ||||
| (Your feedback item 3) | ☐ |
Type: Mandatory (must be addressed for approval) | Suggested (panel recommends but does not require) | Optional (mentioned in passing; your judgement). Priority: High (blocks approval) | Medium (strengthens proposal) | Low (minor improvement).
5.3 From Defence to Execution — The Transition
Once your proposal is approved, you cross a significant threshold. The focus shifts from planning to executing. The next phase — Weeks 9–12 — will deepen your methodology design: developing instruments, piloting, refining sampling strategies, and preparing for data collection. But before you move forward:
- Archive your approved proposal. Save the final, approved version with a clear filename and date. This is your baseline — the document against which future changes will be measured.
- Schedule your first post-approval supervisor meeting. Establish the rhythm for Weeks 9–30: regular check-ins, draft reviews, and milestone tracking.
- Identify your first execution task. What is the single most important thing you need to do to move from plan to action? For BBA: it might be finalising your survey instrument or securing organisational access. For BCA: it might be setting up your development environment or accessing your dataset. Do that thing first.
Proposal approval is an important milestone — but it is the end of the beginning, not the beginning of the end. You have 22 weeks of execution ahead of you. The approved proposal is your map, but the terrain may differ from the map. When you encounter unexpected challenges — and you will — return to the proposal. It documents not just what you planned but why you planned it that way. When you need to change course, that documentation of rationale is what enables you to change course intelligently rather than arbitrarily.
Think Deeper — Cross Questions
Discuss in pairs before sharing with the class.
You are a panel member evaluating a proposal defence. The student presents a clear problem and well-justified RQs, but their methodology section proposes a survey of "consumers in India" without specifying: which consumers, how many, selected how, or why this population. During Q&A, the student says: "I'll figure out the sampling details later — right now I'm focused on the bigger picture." As a panel member, what would your response be? What does this answer reveal about the student's readiness to execute the research?
During a defence, a panel member says: "Your literature review doesn't cite Rao (2024), which is the most recent comprehensive study in this area. How does your gap claim hold up given that Rao already addressed the question you're proposing?" The student has not read Rao (2024). What should they do? Draft the response you would give in this situation — one that maintains intellectual honesty while demonstrating professionalism.
A BCA student proposes to develop a machine learning model for predicting student dropout using institutional data including caste, gender, family income, and academic history. During the defence, a panel member asks: "Even if your model is technically accurate, is it ethical to build a system that could reinforce existing inequalities by labelling certain students as 'likely to drop out' based on demographic characteristics?" The student answers: "That's a policy question, not a technical one — my project is about model accuracy." Evaluate this response. If you were the student, how would you reframe the answer to demonstrate ethical maturity while maintaining the technical validity of the project?
After your defence, you receive feedback that appears contradictory: one panel member praised your theoretical framework as "well-integrated," while another's written comments say the theoretical framework "needs more development." How do you interpret and act on contradictory feedback? What process would you follow to determine whether this reflects a genuine tension in the panel's assessment or two different interpretations of the same section?
Quick Check — Defence Response Diagnosis
Each scenario describes a student's response during a proposal defence Q&A. Diagnose the problem.
1. Panel: "You've proposed semi-structured interviews with 40 participants. Why 40, and not 20 or 60?" Student: "Forty is the standard sample size for qualitative research. All the methodology textbooks recommend it."
2. Panel: "Your RQs examine 'leadership effectiveness,' but you haven't defined what you mean by effectiveness — is it employee satisfaction, team performance, financial outcomes, or something else?" Student: "I'm using a well-established definition from the literature." Panel: "Which literature? Which definition?" Student: "The general leadership literature. It's a standard concept."
3. Panel: "Your timeline allocates 4 weeks for data collection through surveys. What if after 4 weeks you've only received a 15% response rate?" Student: "That won't happen. I've designed a very engaging survey and I'll send multiple reminders. People in my network are responsive."
4. Panel: "You've cited the ACM Code of Ethics in your proposal, but your project involves scraping data from a platform whose Terms of Service explicitly prohibit automated access. How do you reconcile this?" Student: "The data is publicly visible. I'm not hacking into anything. Besides, academic research is exempt from ToS restrictions — it falls under fair use."
Knowledge Check — Interactive Quiz
Test your understanding of proposal defence preparation and execution.
Q1. What is the primary purpose of a proposal defence?
Q2. During Q&A, a panel member identifies a genuine methodological flaw in your proposal. What is the BEST response?
Q3. In a 15-minute defence presentation, approximately how much time should be allocated to the methodology section?
Q4. Which of the following is the most common outcome of a capstone proposal defence?
Q5. A panel member asks a question you don't know the answer to. What is the most professional response?
Lab Activity — Defence Preparation & Rehearsal
Part A: Build Your Defence Presentation (60 min)
- Create your slide deck following the 11-slide structure in Section 2.1. Start with a blank presentation — don't copy-paste from your proposal document. The presentation is a distinct communication genre.
- Apply the 20-30 word rule: After drafting each slide, count the words. If any slide exceeds 30 words (excluding references), cut it down. Replace text with diagrams, tables, or bullet points where possible.
- Design your conceptual framework diagram (Slide 6). This is the most important visual in your presentation. It should be clear enough to stand alone — the panel should grasp your theoretical model from the diagram even without your verbal explanation.
- Create your timeline visual (Slide 10). A simple Gantt chart or phased roadmap. Include key milestones: ethics approval, instrument finalisation, data collection start/end, analysis phase, writing phase, submission.
Before presenting, verify:
- Total slides: 10–12 (not including title and thank-you slides)
- No slide has more than 30 words of body text
- Every slide has a clear, single message
- Diagrams are used for the conceptual framework, synthesis matrix, and timeline
- Font size is ≥ 24pt for body text, ≥ 32pt for headings
- Colour contrast is sufficient for projection (dark text on light background is safest)
- All citations on slides appear in your proposal reference list
Part B: Anticipated Questions — The Hardest Five (30 min)
Write down the five hardest questions the panel could ask about your proposal. These should be questions you genuinely hope they don't ask — the ones that make you uncomfortable because they expose uncertainties in your thinking.
| # | Hardest Question | Question Category | Your Draft Response |
|---|---|---|---|
| 1 | |||
| 2 | |||
| 3 | |||
| 4 | |||
| 5 |
For each question, draft a response following the LISTEN-ACKNOWLEDGE-ANSWER pattern (Section 3.2). Exchange your five questions with a partner. Try to answer each other's questions. Then try to think of a sixth question — the one your partner didn't anticipate.
Part C: Timed Rehearsal with Peer Feedback (30 min per person)
- Present a 10-minute condensed version of your defence to a peer. Your peer times you strictly and notes when you hit 8 minutes (warning) and 10 minutes (must stop).
- Peer provides structured feedback using this rubric:
- Problem clarity (1–5): After hearing the presentation, can you state the problem and why it matters in one sentence?
- Gap articulation (1–5): Is it clear what prior research shows and what it doesn't show? Do the RQs emerge from the gap?
- Methodology comprehension (1–5): Do you understand what the student will actually DO — who, how many, how selected, what method, what analysis?
- Slide quality (1–5): Are slides clear, readable, and supportive of the narrative (not a script)?
- Overall confidence (1–5): Does this student sound like they understand their own research?
- Peer asks 3 unscripted questions as if they were a panel member. Student responds to each without preparation. This simulates the Q&A experience.
You are ready for your defence when:
- You can deliver the full presentation in 13–14 minutes without rushing
- You can explain your conceptual framework diagram without reading from notes
- You can answer the "Why this method and not [alternative]?" question for every methodological choice
- You can name the 3 closest studies to yours and explain what your study adds
- You have rehearsed at least twice with a live audience (not just alone in your room)
Exit Ticket
Submit after your defence rehearsal.
- Submit your slide deck (even if incomplete). Identify which slide you found most difficult to design and why.
- What is the hardest question you anticipate from the panel? Provide your drafted response.
- After peer rehearsal: What was the most valuable piece of feedback you received? What will you change before your actual defence?
- Self-assess your readiness on a scale of 1–10. If below 7, what specific preparation do you need to complete before your defence?
- Looking ahead: After your proposal is approved, what is the FIRST execution task you will tackle, and when will you start it?
Key Takeaways — Week 8
The panel's goal is to strengthen your research, not to fail you. Approach the defence as a scholarly discussion with experts who are invested in your project's success. The Q&A is where you demonstrate intellectual ownership — not where you are interrogated.
The strongest response to a difficult question is often: "That's an important point I hadn't fully considered — here's how I'll address it." This demonstrates coachability, critical thinking, and research maturity. Defensiveness signals the opposite.
The presentation gets you to the Q&A. The Q&A determines the outcome. Spend at least as much time preparing for questions — anticipating, drafting responses, practising with a live audience — as you spend on your slides.
Proposal approval is a milestone worth celebrating — but it marks the transition from planning to execution, not the end of the journey. The approved proposal is your map for the 22 weeks ahead. Guard it, follow it, and adapt it intelligently when the terrain demands it.
Facilitator Notes
Preparation Checklist
- Constitute the review panels at least one week before the defence. Each panel should have 2–3 faculty members with relevant domain and/or methodological expertise. Avoid panels where all members share the same methodological preference — diverse panels produce richer feedback.
- Distribute the proposal evaluation rubric (Week 7, Section 5) to all panel members before the defence. Consistent criteria across panels ensure fairness and enable meaningful comparisons.
- Prepare the defence schedule with clear time allocations: 15 minutes presentation + 15 minutes Q&A + 5 minutes panel deliberation + 5 minutes buffer between slots = 40 minutes per student. Communicate the schedule at least 3 days in advance.
- Brief panel chairs on their role: introduce the student, manage time, moderate Q&A, ensure questions are constructive, deliver the verbal outcome at the end of the session. The chair sets the tone — if the chair is adversarial, the defence becomes an interrogation; if the chair is developmental, the defence becomes a scholarly conversation.
- Prepare a feedback form template for panel members to complete during the defence. Include sections for each evaluation criterion plus space for mandatory revisions and suggested improvements. Written feedback should be returned to the student within 48 hours.
- For the prep workshop: prepare a short (3-minute) mock "bad defence" demonstration — reading slides, vague responses, defensiveness — followed by a "good defence" version of the same content. Students learn more from seeing both than from hearing about both.
Common Student Difficulties
- Extreme anxiety about the defence format: For many students, this is their first formal oral examination. Normalise the experience. Explain exactly what will happen, in what order, and who will be in the room. Uncertainty amplifies anxiety. Consider offering an optional "mock defence" session with a faculty member who is NOT on the student's actual panel.
- Over-preparing the script and under-preparing for questions: Students spend hours perfecting their slide narrative and almost no time anticipating what the panel will ask. The Q&A exercises in Part B and Part C of the lab are designed to correct this imbalance — do not skip them.
- Treating "I don't know" as failure: Students believe they must have an answer for everything. Teach them that "That's a valid question I need to explore further" is a strong, professional response — far stronger than a fabricated answer. Intellectual honesty is evaluated positively, not penalised.
- Rushing through the presentation: Anxiety accelerates speech. Students who rehearsed at 14 minutes in practice deliver at 10 minutes in the actual defence because they speak faster under pressure. Teach students to deliberately pause after each slide transition — it regulates pace and projects composure.
- Misinterpreting panel silence during Q&A: When the panel is quiet after a student's response, the student often thinks they gave a wrong answer and keeps talking to fill the silence. Often, the panel is simply processing the response or formulating the next question. Teach students: answer the question, then stop. If the panel wants more, they will ask.
- Post-defence emotional crash: The defence is emotionally intensive. Students may feel elated, devastated, or numb — regardless of the actual outcome. Acknowledge this. Encourage students not to make major decisions about their research in the 24 hours after the defence. Sleep on the feedback before starting revisions.
Pacing & Panel Management Tips
- The panel chair is responsible for time management. At 12 minutes, the chair should signal a 3-minute warning. At 15 minutes, the chair should politely but firmly transition to Q&A: "Thank you — let's move to questions." Do not let presentations run to 18 or 20 minutes — it is unfair to the student (less Q&A time) and to subsequent presenters.
- Panel members should aim for 2–3 questions each during Q&A, with the chair moderating to ensure all panel members have an opportunity. If one panel member dominates Q&A, the chair should intervene: "Let's hear from Dr. Sharma before we continue on that line of questioning."
- Panel deliberation should happen immediately after the student leaves the room, while the presentation and Q&A are fresh. The chair should lead a structured discussion: (1) What were the proposal's strengths? (2) What revisions are needed? (3) What is the outcome — approved, conditionally approved, or major revision? The chair records the consensus and any dissenting views.
- When delivering the outcome to the student, be specific. "Conditionally approved" without specific revisions is unhelpful. "Conditionally approved — the panel requires: (1) stronger sample size justification with a power analysis, (2) clarification of your construct definitions in Section 5, and (3) a contingency plan for low survey response rates. Written feedback with details will follow within 48 hours." Specificity reduces anxiety and enables immediate action.
- For students receiving "major revision and re-defence," schedule a follow-up meeting with the supervisor within 48 hours. These students need structured support — a clear revision plan, prioritised actions, and a realistic timeline. Do not leave them to interpret the feedback alone.