The Capstone Project Lifecycle
Session at a Glance
The three-phase capstone lifecycle — planning, execution, communication; retrospective proposal review: comparing planned vs. actual methodology; integrating findings into the dissertation framework; project management for the final stretch
Retrospective proposal review and gap analysis; dissertation chapter mapping and integration planning; analysis/artefact development continues
2 hrs Lecture + 12 hrs Lab/Project
Retrospective review + dissertation chapter map complete
Learning Objectives
By the end of this session, you will be able to:
- Map your capstone journey against the three-phase lifecycle — planning (Weeks 1–12), execution (Weeks 13–20), and communication (Weeks 21–30) — identifying which phase you are in, what remains, and how the phases connect
- Conduct a systematic retrospective review of your approved proposal against your actual methodology execution, documenting and justifying every deviation, and identifying gaps that must be addressed before submission
- Structure your complete dissertation by mapping your work from all prior weeks onto the standard chapter framework, identifying material you already have (proposal → Chapters 1–3), material in progress (findings → Chapter 4–5), and material you still need to develop
- Develop a realistic final-stretch project plan with specific milestones, buffer time, and contingency strategies, recognising the common pitfalls that derail capstones in the final 12 weeks
- Execute the transition from "doing research" to "writing the dissertation" — shifting mental models from data collection and analysis to synthesis, argumentation, and scholarly communication
Session Planner
Suggested breakdown of the 4-hour contact session.
| Time | Segment | Activity | Mode |
|---|---|---|---|
| 0:00–0:10 | Opening | Transition to Unit 4 — "You've planned. You've executed. Now: the final phase — bringing it all together into a dissertation that tells the story of your research." Overview of Weeks 18–30. | Whole class |
| 0:10–0:30 | Lecture 1 | The three-phase capstone lifecycle — planning (Weeks 1–12: from research onion to methodology outline), execution (Weeks 13–20: from data collection to preliminary findings), communication (Weeks 21–30: from analysis to viva). Where we are now and what each phase demands. | Lecture |
| 0:30–0:50 | Lecture 2 | Retrospective proposal review — comparing planned vs. actual methodology. Documenting deviations: what changed, why, and what the implications are. The dissertation chapter map: from proposal sections to dissertation chapters. Identifying what you already have and what you still need. | Lecture |
| 0:50–1:05 | Activity | Retrospective review: take your approved proposal and your actual methodology. Identify every deviation. For each: was it justified? Is it documented? Does it affect your findings? Exchange with a partner for a second opinion on gaps you may have missed. | Pairs |
| 1:05–1:20 | Discussion | Share patterns: what kinds of deviations are most common? Which are legitimate (adaptive responses to reality) and which signal methodological drift? How to write about deviations honestly without undermining confidence in your findings. | Whole class |
| 1:20–1:35 | Break | — | — |
| 1:35–1:55 | Lecture 3 | The final-stretch project plan — milestones for Weeks 18–30; buffer allocation (20% minimum); the writing sprint strategy; common final-phase pitfalls (perfectionism paralysis, scope creep, avoidance, isolation); when and how to escalate problems | Lecture |
| 1:55–2:10 | Demo | Dissertation chapter mapping walkthrough — take a sample proposal and sample findings and demonstrate how they map onto the complete dissertation structure. Show a completed dissertation table of contents as the target. | Demo |
| 2:10–3:45 | Lab Work | Part A: Complete retrospective proposal review; Part B: Build dissertation chapter map; Part C: Develop Weeks 18–30 project plan; Continue analysis/artefact development | Individual |
| 3:45–4:00 | Exit Ticket | Submit retrospective review and chapter map | Individual |
1. The Three-Phase Capstone Lifecycle — Where You Are and What Comes Next
The SEC701 capstone is structured as a three-phase journey: planning, execution, and communication. Week 18 sits at the transition from execution to communication — analysis is well underway, preliminary findings are emerging, and the dissertation must begin to take shape. Understanding where you are in the lifecycle helps you allocate your remaining time and energy to the tasks that matter most.
The capstone lifecycle is the structured progression from research planning through execution to scholarly communication. It is not a linear path — findings send you back to literature, analysis reveals gaps in data, writing exposes weaknesses in methodology. But the phases provide a conceptual map: you should know which phase you are in, what that phase demands, and when it is time to move to the next phase. The most common capstone failure mode is phase confusion — still planning when you should be executing, still collecting data when you should be writing, still perfecting analysis when you should be communicating.
1.1 The Three Phases in Detail
| Dimension | Phase 1: Planning (Weeks 1–12) | Phase 2: Execution (Weeks 13–20) | Phase 3: Communication (Weeks 21–30) |
|---|---|---|---|
| Core Question | "What will I study, why, and how?" | "What am I finding, and what does it mean?" | "How do I communicate my research convincingly?" |
| Key Activities | Understanding research foundations; formulating RQs; reviewing literature; designing methodology; writing and defending the proposal | Collecting data; running analyses; developing artefacts; evaluating models; coding transcripts; constructing themes; generating preliminary findings | Writing the complete dissertation — all chapters; revising based on supervisor feedback; preparing the defence presentation; submitting; defending at viva voce |
| Primary Outputs | Approved research proposal; methodology chapter outline; ethics approval; instruments developed and piloted | Complete dataset; analysis scripts and outputs; preliminary findings; joint displays (MM); artefact evaluation results; Progress Report 1 | Complete dissertation (all chapters); defence presentation; final approved dissertation |
| Mindset | Exploratory, learning, decision-making. You are designing the research. | Systematic, disciplined, documenting. You are doing the research. | Synthetic, argumentative, communicative. You are telling the story of the research. |
| Biggest Risk | Scope creep; analysis paralysis (never settling on a design); proposal that doesn't anticipate execution challenges | Data collection delays; analysis skill gaps; discovering that the data cannot answer the RQs; losing momentum in the long middle | Perfectionism paralysis; writing avoidance; poor time management; discovering gaps in the literature or methodology that require substantial rework; isolation |
| Success Indicator | Approved proposal that is specific, feasible, and well-justified | Complete, quality dataset analysed according to plan; findings that address RQs; documented deviations from proposal | Submitted dissertation that is coherent, well-argued, and defended successfully |
1.2 Week 18 — The Transition Point
Week 18 is not an arbitrary point in the calendar. It marks the shift from Phase 2 (Execution) to Phase 3 (Communication). By now: data collection should be complete or very nearly complete; primary analysis should be substantially done; you should have a clear picture of what your findings are. If you are still collecting data or have not begun analysis, you are behind the Phase 2 timeline — and you need a recovery plan (Section 3). If you are on track, the task now is to begin the mental transition from "doing research" to "writing the dissertation." These require different mindsets, different skills, and different daily practices.
The most important mental shift between Phase 2 and Phase 3: in Phase 2, you are discovering what your data says. In Phase 3, you are constructing an argument about what your research means. A dissertation is not a chronological report of what you did ("First I reviewed the literature. Then I designed a survey. Then I collected data. Then I ran regressions."). It is a structured argument: "Here is a problem worth solving. Here is what we know and what we don't know. Here is how I investigated it. Here is what I found. Here is what it means — for theory, for practice, and for future research." The transition from "reporting" to "arguing" is the difference between a competent dissertation and a compelling one. Begin making this shift now — in how you think about your work, how you talk about it with peers, and how you write about it.
2. Retrospective Proposal Review — Planned vs. Actual
Every capstone deviates from its proposal. The question is not whether there are deviations but whether they are documented, justified, and their implications understood. The retrospective proposal review is a systematic comparison of your approved proposal against what you actually did — identifying every divergence, evaluating whether it was a legitimate adaptation to reality or methodological drift, and planning how to write about it in your dissertation.
2.1 The Retrospective Review Framework
| Methodology Element | What Was Planned (Proposal) | What Was Executed (Actual) | Deviation? | Justification | Impact on Findings |
|---|---|---|---|---|---|
| Research Design | e.g., Convergent mixed-methods (QUAN + QUAL concurrent) | ||||
| Population & Sample | e.g., 200 IT professionals in Bangalore, stratified by experience | ||||
| Instruments | e.g., Adapted UTAUT2 survey (28 items) + semi-structured interview protocol | ||||
| Data Collection | e.g., Online survey (4 weeks) + 20 interviews (concurrent) | ||||
| Analytical Approach | e.g., Hierarchical regression + Braun & Clarke thematic analysis | ||||
| Ethics | e.g., Institutional ethics approval; consent forms; anonymisation |
2.2 Classifying Deviations — Legitimate Adaptation vs. Methodological Drift
| Deviation Type | Definition | Example | How to Write About It |
|---|---|---|---|
| Legitimate Adaptation | A change made in response to genuine practical constraints, new information, or superior methodological understanding. The change is justified, and the rationale strengthens the methodology rather than weakening it. | Proposed 200 survey respondents from Bangalore. Achieved 140 from Bangalore but added 60 from Chennai because response rates in Bangalore were lower than expected. The populations are comparable (both Tier-1 South Indian IT hubs), and the expanded sample actually improves generalisability. | "The original sampling plan targeted 200 IT professionals in Bangalore. During data collection, response rates in Bangalore were lower than anticipated (23% vs. the expected 35%). To achieve adequate statistical power while maintaining population comparability, the sampling frame was expanded to include Chennai — a comparable Tier-1 South Indian IT hub. This adaptation increased the sample to 200 (140 Bangalore, 60 Chennai) while preserving the target population characteristics. The inclusion of Chennai respondents may modestly increase geographic generalisability; differences between Bangalore and Chennai respondents were tested and found non-significant for all demographic and substantive variables (see Appendix C)." |
| Methodological Compromise | A change that weakens the methodology but was necessary due to insurmountable constraints. The researcher acknowledges the compromise and discusses its implications honestly. | Proposed 20 interviews but could only complete 12 due to participant dropout and recruitment difficulties. The sample is smaller than planned, and saturation may not have been fully achieved for all themes. | "The original plan proposed 20 semi-structured interviews to achieve thematic saturation. Despite extended recruitment efforts (additional 4 weeks), only 12 interviews were completed — 8 participants withdrew or became uncontactable. Guest, Bunce, and Johnson (2006) suggest 12 interviews can be sufficient for thematic saturation in relatively homogeneous populations, which characterises this sample (all participants were middle managers in Indian manufacturing, with 8–15 years of experience). However, the reduced sample may not have fully saturated themes related to cross-functional dynamics, which participants described with substantial variation. This limitation is acknowledged: findings related to cross-functional dynamics should be considered indicative rather than definitive, and future research should specifically sample for this theme." |
| Methodological Drift | A change made without clear justification — the methodology shifted because of convenience, pressure, or insufficient planning. This is the most concerning category and must be addressed transparently. | Proposed a quasi-experimental design with a comparison group. However, the comparison organisation withdrew access after Week 2. Instead of seeking an alternative comparison group, the student analysed the treatment group only (pre-post, no control) — a substantially weaker design. | "The original proposal specified a quasi-experimental design with a matched comparison organisation. During data collection, the comparison organisation withdrew access due to internal restructuring (not related to the research). Multiple attempts to recruit an alternative comparison organisation within the remaining timeline were unsuccessful (see Appendix B for documentation). Consequently, the study was modified to a pre-experimental one-group pre-post design. This is a significant methodological limitation: without a comparison group, observed changes cannot be confidently attributed to the intervention rather than to history, maturation, or testing effects. The findings should be interpreted as exploratory evidence of the intervention's potential, not as evidence of its effectiveness relative to alternatives. This limitation is the primary threat to internal validity in this study and is discussed further in Section 5.4." |
The most serious writing error in the methodology chapter: describing the PLANNED methodology from the proposal rather than the EXECUTED methodology. The methodology chapter must reflect what was actually done. Deviations must be documented and justified. A student who describes a stratified random sample when they actually used convenience sampling is not "following the proposal" — they are misrepresenting their research. The retrospective review ensures your methodology chapter is an honest account of your research, not a restatement of your aspirations. The evaluation committee will compare your proposal to your dissertation. They expect deviations. They will not accept undocumented or unjustified deviations.
3. The Dissertation Chapter Map — From Fragments to a Coherent Document
Over Weeks 1–17, you have produced a substantial body of work: a proposal, a methodology outline, analysis scripts, preliminary findings, joint displays, coded transcripts, thematic maps, and more. The dissertation chapter map is the process of organising these fragments into the standard dissertation structure — identifying what you already have (which is more than you think), what needs to be adapted (proposal prose is not dissertation prose), and what still needs to be created.
3.1 The Standard Dissertation Structure
| Chapter | Content | Source Material (from Prior Weeks) | Status |
|---|---|---|---|
| Chapter 1: Introduction | Background, problem statement, RQs, significance, scope, dissertation structure | Proposal Sections 1–3 (Introduction, Problem, RQs) — expanded and updated | ☐ Have draft / ☐ Need to write |
| Chapter 2: Literature Review | Thematic synthesis of literature, theoretical framework, gap articulation | Proposal Section 4 (Literature Review) — significantly expanded; Week 4–5 synthesis matrix and thematic paragraphs | ☐ Have draft / ☐ Need to write |
| Chapter 3: Methodology | Paradigm, design, population/sample, instruments, procedures, analysis plan, ethics, limitations | Proposal Sections 5–7 + Methodology Outline (Week 12) — updated to describe ACTUAL methodology, not planned | ☐ Have draft / ☐ Need to write |
| Chapter 4: Results / Findings | QUAN: descriptive statistics, assumption checks, main analyses, tables/figures. QUAL: thematic narrative with quotes. MM: joint displays. DSR: artefact description and evaluation results. | Week 13–15 analysis outputs; coded transcripts; thematic maps; joint displays | ☐ Have draft / ☐ Need to write |
| Chapter 5: Discussion | Interpretation of findings in context of literature and theory; implications for theory and practice; connecting findings back to RQs | Meta-inferences from joint displays; the "so what" of your findings — largely new writing | ☐ Have draft / ☐ Need to write |
| Chapter 6: Conclusion | Summary of the study; contributions; limitations; recommendations for future research; final reflections | New writing — this chapter is the capstone of the capstone | ☐ Have draft / ☐ Need to write |
3.2 What You Already Have — More Than You Think
Students consistently underestimate how much material they have already produced. Your proposal (Week 7) contains the skeleton of Chapters 1–3. Your methodology outline (Week 12) contains the structure of Chapter 3. Your analysis outputs (Weeks 13–15) are the evidence for Chapter 4. Your joint displays and thematic maps (Weeks 15–16) are the raw material for Chapter 5. The task now is not to write a dissertation from scratch — it is to assemble, expand, adapt, and polish the substantial body of work you have already created.
Key adaptation needed: Proposal prose is written in the future tense and describes what you PLAN to do. Dissertation prose must be in the past tense and describe what you ACTUALLY did. "This study will employ a survey design" → "This study employed a cross-sectional survey design." "The target sample is 200 IT professionals" → "The final sample comprised 187 IT professionals." This transformation — future to past, plan to reality — must be applied systematically to all proposal-derived material.
4. The Final-Stretch Project Plan — Weeks 18–30
The final 12 weeks of the capstone are the most demanding. The tasks are intellectually complex (synthesis, argumentation, writing), psychologically challenging (sustained focus, isolation, perfectionism), and time-pressured (multiple chapters, revisions, defence preparation). A realistic, structured project plan is not optional — it is the difference between submitting a completed dissertation and submitting a rushed draft.
4.1 A Week-by-Week Roadmap for the Final 12 Weeks
| Week | Phase | Primary Focus | Key Deliverable |
|---|---|---|---|
| 18 | Transition | Retrospective review; chapter mapping; final-stretch planning | Chapter map; retrospective review document |
| 19 | Complete data collection and primary analysis | Dataset finalised; all primary analyses complete | |
| 20 | Complete Chapters 3 (Methodology) and 4 (Results/Findings) draft | Full draft of Chapters 3 and 4 | |
| 21 | Intensive Writing | Complete Chapter 2 (Literature Review) expansion | Full draft of Chapter 2 |
| 22 | Complete Chapter 1 (Introduction) update | Full draft of Chapter 1 | |
| 23 | Complete Chapter 5 (Discussion) draft | Full draft of Chapter 5 — the intellectual core | |
| 24 | Complete Chapter 6 (Conclusion); assemble complete first draft | Complete first draft of all chapters | |
| 25 | Revision | Supervisor review of full draft; begin revisions | Supervisor feedback received |
| 26 | Major revisions based on supervisor feedback | Revised draft addressing all major feedback | |
| 27 | Polish — formatting, proofreading, reference checking | Submission-ready dissertation | |
| 28 | Defence Preparation | Prepare defence presentation; rehearse | Complete slide deck; at least 2 full rehearsals |
| 29 | Mock defence; final revisions based on mock feedback | Mock defence completed; final corrections made | |
| 30 | Final defence (viva voce); submit final dissertation | Defence passed; dissertation submitted |
4.2 Common Final-Phase Pitfalls and How to Avoid Them
| Pitfall | What It Looks Like | Prevention / Remedy |
|---|---|---|
| Perfectionism Paralysis | "I can't write Chapter 4 until every analysis is perfect." Analysis iterations continue indefinitely; writing never starts. Month after month of "just one more test." | Write while analysing. The act of writing reveals gaps in analysis more efficiently than running endless additional tests. Write a draft of the results with what you have. If an analysis is genuinely incomplete, note "[To be updated with final sample]" and keep writing. A complete draft with placeholders is infinitely better than no draft. |
| Scope Creep in the Discussion | The discussion chapter keeps expanding as the student discovers "one more paper I need to cite" — the literature review never closes. Each new paper generates new ideas that require new analyses. | Declare the literature review closed. The discussion engages primarily with the literature ALREADY REVIEWED in Chapter 2. New citations should be rare and justified (e.g., a paper published during your capstone that is directly relevant). Set a rule: no more than 5 new citations in the discussion chapter without supervisor approval. |
| Writing Avoidance | The student finds endless other tasks — formatting references, adjusting figure colours, reorganising data files — to avoid the cognitively demanding work of writing prose. "I'll start writing once I've organised everything." | Write first, format later. Use the Pomodoro method (50-minute writing blocks). Produce "ugly drafts" — content over presentation. Perfect formatting applied to an unwritten chapter is wasted effort. The first draft's job is to exist; the second draft's job is to be coherent; the third draft's job is to be polished. |
| Isolation | The student works alone for weeks, avoiding supervisor contact because "I don't have anything good to show." Problems fester. The supervisor discovers major issues at Week 27 that could have been fixed at Week 20. | Schedule regular, short supervisor check-ins. Even 15 minutes every two weeks to say "Here's where I am, here's what I'm struggling with" prevents catastrophic drift. Send partial drafts — a chapter, a section, even a problematic paragraph. Feedback on imperfect work is more valuable than perfect isolation. |
| Neglecting the Defence | The student focuses entirely on the dissertation and begins preparing the defence presentation 3 days before. The presentation is rushed, the rehearsal non-existent, and the Q&A preparation absent. | Begin defence preparation at Week 26, not Week 29. The defence presentation is NOT a summary of the dissertation — it is a separate communication task requiring its own preparation time. Draft slides while writing the discussion chapter — the intellectual clarity required for a good presentation is the same clarity required for a good discussion. |
Think Deeper — Cross Questions
Discuss in pairs before sharing with the class.
Conduct a "pre-mortem" on your capstone. Imagine it is Week 30, and your capstone has failed — you did not submit, or you submitted something significantly below your capability. What went wrong? Work backwards from that failure to identify the 2–3 most likely causes. Now: what specific actions can you take THIS WEEK to prevent those causes from materialising?
Your retrospective review reveals that your executed sample (n = 140, convenience sample from your professional network) differs substantially from your planned sample (n = 200, stratified random sample of IT professionals in Bangalore). A peer suggests you write the methodology chapter as planned — "everyone does it, and the evaluator won't check." Your supervisor suggests you document the deviation honestly. What are the ethical, methodological, and practical consequences of each approach? What does your choice reveal about your identity as a researcher?
Your dissertation chapter map reveals that you have substantial material for Chapters 1–4 (proposal + findings) but almost nothing for Chapter 5 (Discussion) and Chapter 6 (Conclusion). This is typical — the discussion and conclusion are largely new writing. How will you approach these chapters? What is the relationship between your findings (Chapter 4) and your discussion (Chapter 5) — is the discussion a separate step, or should it be drafted alongside the findings? What strategies will you use to ensure your discussion goes beyond restating the findings?
Reflect honestly on your capstone journey from Week 1 to Week 18. What is the single most important thing you know NOW about research that you did not know when you started? What would you do differently if you could start over? What advice would you give to a student beginning SEC701 next year — one piece of advice about the research process, and one piece of advice about managing yourself through the capstone?
Quick Check — Lifecycle Diagnosis
Diagnose the phase confusion or pitfall in each scenario.
1. At Week 22, a student is still refining their interview protocol and has not conducted any interviews. They explain: "I want to make sure the questions are perfect before I start. The quality of the data depends on the quality of the instrument."
2. A student's methodology chapter describes a "stratified random sample of 250 consumers" with detailed stratification procedures. The actual sample was 140 respondents recruited through social media posts (convenience sample). The student argues: "The proposal was approved with stratified sampling. I'm committed to that methodology. I'll describe it as planned."
3. A student has been "analysing data" for 8 weeks. They have run 47 variations of their model, explored 12 different variable combinations, and generated 200+ pages of SPSS output. They have written zero words of their results chapter. When asked why, they say: "I haven't found the definitive analysis yet. There might be a better specification."
4. At Week 26, a student emails their supervisor a complete dissertation draft — the first written work the supervisor has seen since the proposal at Week 8. The supervisor identifies a fundamental flaw in the analysis approach that requires re-running all analyses and rewriting Chapter 4. The student had been working in isolation for 4 months.
Knowledge Check — Interactive Quiz
Test your understanding of the capstone lifecycle and final-phase execution.
Q1. Which of the following best describes "phase confusion" in the capstone lifecycle?
Q2. What is the primary purpose of the retrospective proposal review?
Q3. In the standard dissertation structure, which chapter is the "intellectual core" — where findings are interpreted in the context of literature and theory?
Q4. A student's capstone pre-mortem identifies "I ran out of time because I spent too long perfecting the analysis and started writing too late" as the primary cause of failure. What is the BEST preventative action?
Q5. What is the most significant risk of working in isolation during the final phase of the capstone?
Lab Activity — Retrospective Review & Chapter Mapping
Part A: Complete Your Retrospective Proposal Review (45 min)
- Open your approved proposal and your actual execution records (data, analysis scripts, field notes).
- Complete the retrospective review table (Section 2.1) for ALL methodology elements.
- For each deviation: classify it as legitimate adaptation, methodological compromise, or methodological drift (Section 2.2). Write a 2–3 sentence justification for each.
- Identify the deviation with the most significant implications for your findings. Draft the paragraph you will write in your methodology chapter to address it transparently.
Part B: Build Your Dissertation Chapter Map (45 min)
- Use the dissertation structure template (Section 3.1). For each chapter, list the specific source material you already have from prior weeks.
- For each chapter, mark status: ☐ Have complete draft / ☐ Have partial draft / ☐ Need to write from scratch.
- Identify the chapter that will require the MOST new writing. Identify the chapter where the gap between what you have and what you need is largest.
- Write the first sentence of each chapter. This forces you to articulate the core argument of each chapter. If you can't write the first sentence, you don't yet know what the chapter is about.
Part C: Develop Your Weeks 18–30 Project Plan (30 min)
Using the roadmap template (Section 4.1), create a personalised week-by-week plan. For each remaining week: identify the primary deliverable, estimate the hours required, and note any dependencies or risks. Include at least 20% buffer — if your plan has zero slack, it is not a plan; it is a hope.
Exit Ticket
Submit with your retrospective review and chapter map.
- Submit your completed retrospective review. What is the most significant deviation from your proposal, and how will you address it in your methodology chapter?
- Submit your dissertation chapter map. Which chapter will require the most new writing? Where is the largest gap?
- Conduct a pre-mortem (CQ 1). What is the most likely cause of failure, and what specific action are you taking this week to prevent it?
- Are you in Phase 2 (Execution) or Phase 3 (Communication)? Be honest. If you are still in Phase 2, what is your plan to transition?
- One thing you need from your supervisor to successfully complete the final phase:
Key Takeaways — Week 18
Phase confusion is the most common capstone failure mode. By Week 18, you should be transitioning from execution to communication. If you are still planning or still collecting data, acknowledge the delay and create an explicit recovery plan. Denial is not a project management strategy.
Every capstone deviates from its proposal. Acknowledged and justified deviations strengthen your methodology. Undocumented deviations — or worse, describing the planned rather than executed methodology — undermine trust in your entire dissertation. Your methodology chapter must be an honest account.
Your proposal, methodology outline, analysis scripts, coded transcripts, and preliminary findings are the raw material for your dissertation. The task now is to assemble, expand, adapt, and polish — not to write from scratch. The chapter map makes visible what you already have.
The first draft's job is to exist. The second draft's job is to be coherent. The third draft's job is to be polished. Start writing before you feel ready. Share imperfect work with your supervisor. The antidote to perfectionism paralysis is momentum — and momentum comes from producing text, not from perfecting analysis.
Facilitator Notes
Preparation Checklist
- Prepare an exemplar retrospective review — take a real (anonymised) proposal and a real executed methodology from a previous cohort student and demonstrate the review process. Students learn the framework by seeing it applied, not by hearing it described.
- Prepare a completed dissertation chapter map exemplar showing all chapters with source material annotations. Use an anonymised previous student's work if available, or a constructed example.
- Review the Progress Report 1 submissions from Week 15. Identify students whose progress reports indicated significant delays — these students need priority attention during this week's lab and a follow-up supervision meeting scheduled.
- Prepare the "first sentence of each chapter" exercise — have discipline-specific examples of strong and weak opening sentences for each chapter type. A strong Chapter 1 opening: "Despite substantial investment in employee wellness programmes, turnover in Indian IT companies has increased 34% since 2020 (NASSCOM, 2024) — this study investigates why." A weak one: "This chapter introduces the research."
Common Student Difficulties
- Phase denial: Students who are significantly behind may resist the Week 18 framing because it makes their delay visible. Handle this sensitively but honestly — acknowledging the delay is the first step to recovering from it. A 15-minute private conversation is more effective than public pressure.
- Underestimating what they already have: Students look at the blank "Discussion" and "Conclusion" chapters and feel overwhelmed. The chapter map exercise demonstrates that Chapters 1–4 already have substantial source material — the gap is smaller than it appears. This is motivational as much as it is practical.
- Overestimating how much needs to be "perfect": Students believe the dissertation must be flawless. It must be competent, honest, and well-argued. The evaluator expects a capstone, not a Nobel Prize. Normalise the standard: "Your dissertation should be the best research you can do within the constraints of the capstone. It does not need to be the best research ever done on your topic."
- Reluctance to document deviations: Students fear that acknowledging deviations will lower their grade. The opposite is true: documented, justified deviations strengthen the methodology; undocumented deviations (or describing the planned rather than executed methodology) raise questions about the entire dissertation's integrity.
Pacing Tips
- This week is as much psychological as it is practical. The transition from "doing" to "writing" is anxiety-provoking. Acknowledge this. The retrospective review, chapter map, and project plan are tools for managing this anxiety — they transform an overwhelming, amorphous task ("write the dissertation") into structured, manageable components.
- The pre-mortem exercise (CQ 1) can be uncomfortable but is valuable. Frame it constructively: "We're not imagining failure to be pessimistic. We're identifying the most likely causes of failure so we can prevent them. This is risk management, not negativity."
- Schedule individual check-ins with students whose Progress Report 1 indicated delays. Week 18 is the last reasonable point for a recovery plan — after Week 20, significant delays become very difficult to recover from without compromising quality.