Proposal Defense

Proposal Defense

Purpose: Prepare for PhD/Master's proposal defense — the milestone that officially starts your research.

When to use:

• Preparing proposal defense slides
• Practicing Q&A with simulated committee
• Understanding defense logistics
• Planning post-defense actions

Links to:

• phd-proposal — proposal writing
• research-question — RQ formulation
• research-design — methodology design
• defense-prep — thesis defense skills
• milestone-tracker — timeline tracking

Proposal Defense vs Thesis Defense

Slide Structure (20-30 slides, 45-60 min)

Slides 1-2: Title & Outline (1 min)
    - Title, name, advisor, committee
    - Presentation outline

Slides 3-5: Background & Motivation (5 min)
    - Research area overview
    - Real-world problem
    - Why this matters

Slides 6-8: Problem Statement (5 min)
    - Specific gap in knowledge
    - Limitations of current work
    - "However, [gap] remains..."

Slides 9-11: Research Questions (5 min)
    - RQ1: [Primary question]
    - RQ2: [Secondary question]
    - RQ3: [Tertiary question]
    - Relationship between RQs

Slides 12-14: Literature Review (8 min)
    - Taxonomy of approaches
    - Key papers analysis
    - Comparison table
    - Research gaps → map to RQs

Slides 15-19: Proposed Methodology (12 min)
    - System overview (1 slide)
    - Component 1 (2 slides)
    - Component 2 (2 slides)
    - Theoretical foundations

Slides 20-22: Preliminary Results (5 min)
    - What has been done so far
    - Initial findings
    - Validation of approach

Slides 23-24: Evaluation Plan (3 min)
    - Datasets
    - Baselines
    - Metrics
    - Statistical tests

Slides 25-26: Timeline (2 min)
    - Gantt chart or timeline
    - Milestones
    - Expected completion

Slides 27-28: Contributions & Impact (2 min)
    - Expected contributions
    - Theoretical impact
    - Practical impact

Slide 29: Questions (30 sec)
    - "Thank you for your attention"
    - "I welcome your questions"

Slide 30: Backup Slides (if needed)
    - Detailed algorithms
    - Additional related work
    - Extended results

Common Committee Questions

About Problem Statement

• "Why is this problem important?"
• "Who benefits from solving this?"
• "What happens if we don't solve this?"
• "How does this relate to [related problem]?"

About Literature

• "Have you considered [alternative approach]?"
• "How does your work differ from [specific paper]?"
• "What about [recent development in field]?"
• "Why did you exclude [category of work]?"

About Methodology

• "Why this approach over [alternative]?"
• "What are the assumptions?"
• "How will you handle [edge case]?"
• "What if [hypothesis] is wrong?"
• "How scalable is this approach?"

About Evaluation

• "Why these datasets?"
• "Why these metrics?"
• "How will you ensure reproducibility?"
• "What statistical tests will you use?"
• "How many seeds/experiments?"

About Timeline

• "Is this realistic for [N] years?"
• "What's the backup plan if [task] takes longer?"
• "When do you expect first publication?"

About Contributions

• "What's novel about this?"
• "What's the theoretical contribution?"
• "What's the practical impact?"

Q&A Strategy

Before Defense

1. Anticipate questions — list 30+ possible questions
2. Prepare answers — 2-3 minute responses
3. Practice aloud — simulate committee pressure
4. Know your limits — "I don't know, but I plan to address this by..."

During Defense

1. Listen fully — don't interrupt
2. Clarify if needed — "Do you mean [X] or [Y]?"
3. Answer directly — yes/no first, then explanation
4. Be honest — acknowledge weaknesses
5. Take notes — write down suggestions
6. Stay calm — it's okay to think before answering

Response Templates

For "Why this approach?":

"We chose this approach because [reason 1].
Additionally, [reason 2].
Compared to [alternative], our approach [advantage].
We acknowledge [limitation] and plan to address it by [solution]."

For "What if it doesn't work?":

"That's a valid concern. We have a backup plan:
1. [Alternative 1]
2. [Alternative 2]
Additionally, even if [hypothesis] is wrong, we would learn [insight]."

For "I don't know":

"That's an excellent question. I haven't fully explored this yet.
Based on my understanding, [initial thought].
I plan to investigate this further by [plan]."

Post-Defense Actions

Immediately After

• Thank committee members
• Collect written feedback
• Clarify any unclear comments
• Note all suggestions

Within 1 Week

• Send thank-you email to committee
• Document all feedback
• Create action plan for revisions
• Update timeline based on feedback

Within 1 Month

• Address all committee comments
• Revise proposal document
• Submit revised proposal
• Update milestone-tracker

Defense Logistics

Before Defense

• Book room (check availability)
• Confirm committee members
• Send calendar invites
• Prepare presentation laptop
• Test projector/screen
• Print proposal copies (if required)
• Prepare water/snacks

Day of Defense

• Arrive 30 min early
• Set up presentation
• Test microphone (if large room)
• Have backup USB with slides
• Bring water bottle
• Bring notebook for feedback

What to Bring

• Laptop + charger
• USB backup of slides
• Printed proposal (optional)
• Notebook + pen
• Water bottle
• Snacks (for long sessions)

Integration Flow

phd-proposal (write proposal)
    ↓
research-question (refine RQs)
    ↓
research-design (design methodology)
    ↓
proposal-defense (this skill)
    ├── Prepare slides
    ├── Practice Q&A
    ├── Defense logistics
    └── Post-defense actions
    ↓
[After successful defense]
    ↓
thesis-writing (start writing chapters)
    ↓
experiment-tracking (conduct experiments)
    ↓
conference-paper (publish findings)
    ↓
progress-report (report to advisor)
    ↓
defense-prep (prepare for thesis defense)