Get AI summaries of any video or article — Sign up free
PhD Student Advice - 15 Things I Wish I Knew Before Starting a PhD thumbnail

PhD Student Advice - 15 Things I Wish I Knew Before Starting a PhD

Ciara Feely·
6 min read

Based on Ciara Feely's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

PhD assessment in many European systems includes thesis submission followed by a viva voce with internal and external examiners, typically lasting one to three hours.

Briefing

A PhD isn’t mainly a test of how much research output someone can produce—it’s a structured assessment of whether a candidate can carry out independent research, and that reality shapes everything from the viva to how corrections work. In Europe, the thesis is read in detail by examiners before a viva voce, typically lasting from about one to three hours (with a short 10–15 minute presentation at the start). The panel usually includes an internal examiner from the candidate’s own university and an external examiner from another institution, with the candidate and supervisor having more say over the external appointment. Passing can come with minor corrections—often framed as small fixes like a few missing paragraphs or typos, sometimes amounting to roughly five pages—while major revisions can require a longer resubmission window (around six months). A full pass without corrections is described as extremely rare, and failing can still leave the candidate with a research master’s degree rather than a PhD.

Beyond the mechanics of assessment, the advice centers on psychological and practical survival: most PhD students feel inadequate at some point, and that feeling often doesn’t disappear even for accomplished academics. The work also comes with unavoidable delays—examples include major disruptions like a global pandemic—and there’s no reliable way to predict what will derail timelines. That uncertainty makes planning and documentation more important, not less. Keeping a research diary (tracking what was tried, what happened, and why) is presented as a major safeguard for later write-up, preventing the “blank page” problem when it’s time to reconstruct decisions from months or years earlier. For coding-heavy work, organizing code and files early reduces the time cost of revisiting old results.

The transcript also stresses that PhD trajectories vary wildly, so comparing oneself to other students is a trap. Early momentum can fade, and later momentum can return; others may experience the reverse. The goal is finishing, not matching someone else’s pace. Similarly, the PhD is described as more than scientific contribution: supervisors and research processes matter because the evaluation looks for the capacity to conduct research independently going forward. That means building a strong supervisor relationship and, where possible, a network of advisors so support exists if the primary relationship becomes strained.

Practical productivity advice runs alongside the emotional realism. People outside academia often misunderstand what a PhD job entails, assuming it’s flexible or not full-time, and they may repeatedly ask when it will end in ways that treat the timeline like a burden. Inside the PhD, taking time to plan projects—mapping action steps before starting—can prevent procrastination and reduce time spent staring at a screen without direction. Finally, learning how one learns is framed as a competitive advantage: for this candidate, writing and outlining thesis content before jumping into programming helps clarify what tasks are needed, boosts motivation, and avoids getting stuck on implementation without a clear structure. Overall, the message is that smooth progress comes less from having perfect conditions and more from knowing how assessment, uncertainty, documentation, and personal workflow actually work.

Cornell Notes

The core takeaway is that a PhD is assessed as a test of independent research capability, not just scientific contribution. In many European systems, the thesis is read by internal and external examiners before a viva voce, where a short presentation is followed by extended questioning; outcomes range from minor corrections to major revisions, with full passes without corrections described as rare. The transcript pairs that institutional reality with personal survival strategies: expect feelings of inadequacy, plan for unexpected delays, and document decisions through a research diary and organized code. It also argues that PhD paths differ, so comparison is counterproductive, and that planning plus learning one’s own workflow can reduce procrastination and make write-up faster.

How does the viva voce typically work in European PhD assessment, and what does it mean for a candidate’s preparation?

After thesis submission, examiners get a few weeks (or up to about a month) to read the work in detail. A viva voce then follows, usually lasting roughly one to three hours (with a minimum around 30 minutes and a maximum up to four hours). At the start, the candidate gives a short 10–15 minute presentation, then enters a long question-and-answer period. The internal examiner is from the candidate’s own university, while the external examiner comes from another university; the supervisor and candidate typically have more influence over the external examiner. The Q&A can feel like criticism, but it’s also described as a chance to discuss research in depth and generate ideas for future work.

What are the most common outcomes after examination, and how do correction timelines affect the PhD status?

A full pass without corrections is described as extremely rare. The more typical outcome is passing with minor corrections—often characterized as small fixes such as missing paragraphs or typos, sometimes totaling around five pages. Even with minor corrections and a resubmission requirement, the candidate is still considered to have passed the PhD. If revisions are more major, the timeline can extend (around six months). Failing a portion can lead to a longer process and, in the worst case, a research master’s degree instead of a PhD.

Why does the advice warn against comparing PhD progress to other students?

No two PhDs are the same, and journeys can move in opposite directions. One person might have a strong first year and weaker middle years, while another might experience the reverse. Comparing oneself to others can distort motivation—feeling worse when others look ahead early, or worse later when one’s own momentum drops. The transcript frames the real target as finishing the PhD, not matching another student’s trajectory.

What role does documentation play in reducing write-up pain later?

Keeping a research diary is presented as crucial because write-up often requires recalling why a method was chosen. Without tracked notes and personal interpretations, a candidate may need to re-investigate earlier decisions, losing time and repeating work. The diary also helps prevent “blank page” starts by providing ready-to-use context when writing chapters.

How should a candidate approach coding and file organization during a PhD?

Organizing code and files early is emphasized as a time-saver. The transcript describes learning this late: earlier code was “shockingly” disorganized, making it harder to revisit old work. More organized notebooks and structured code reduce the time needed to find and understand prior results, especially when returning to earlier chapters or datasets.

What planning and learning workflow changes can reduce procrastination and getting stuck?

Planning is framed as a direct antidote to procrastination: mapping action steps before starting prevents time spent staring at a computer without direction. For learning, the transcript highlights a workflow where thesis writing and outlining come before programming. Writing out steps clarifies what tasks are needed, which then guides implementation and helps avoid getting stuck when coding without a clear structure. The candidate also notes that motivation increases when there is already written material rather than a blank page.

Review Questions

  1. What elements of the viva voce process (format, timing, examiner roles) most directly influence how a candidate should prepare?
  2. Which documentation practices are described as preventing repeated work during thesis write-up, and why?
  3. How does the transcript connect planning and workflow choices to motivation and reduced procrastination?

Key Points

  1. 1

    PhD assessment in many European systems includes thesis submission followed by a viva voce with internal and external examiners, typically lasting one to three hours.

  2. 2

    Passing outcomes commonly include minor corrections (often small fixes) or major revisions, while a full pass without corrections is described as rare.

  3. 3

    PhD students often feel inadequate at some point, and that feeling may persist even for highly accomplished researchers.

  4. 4

    Unexpected delays are unavoidable, so candidates should build flexibility and avoid relying on perfect timelines.

  5. 5

    Keeping a research diary and organizing code/files early can dramatically reduce write-up time and prevent redoing decisions.

  6. 6

    PhD progress varies widely, so comparing oneself to other students can undermine motivation; finishing is the shared endpoint.

  7. 7

    Planning action steps before starting work and aligning tasks with one’s learning workflow can reduce procrastination and help avoid getting stuck.

Highlights

In a typical European viva, a short 10–15 minute presentation is followed by extended questioning, and the discussion can generate ideas for future work even when the format feels intimidating.
Minor corrections can still mean the candidate is considered to have passed, with resubmission often framed as small fixes rather than a full restart.
No two PhDs follow the same curve—early success doesn’t guarantee smooth later years, and early struggles don’t doom the outcome.
Keeping a research diary helps reconstruct “why” decisions were made, preventing time-consuming rework during thesis writing.
Planning project steps before starting can turn a blank, avoidable task into a clear sequence of actions—reducing screen-staring and procrastination.

Topics

Mentioned