Your first year of a PhD: what it really is, and how to use it well

A PhD is not a longer master's degree. It is training in one specific skill: producing new knowledge that survives expert scrutiny. The first year is where the habits behind that skill are formed, and most of the hard years later on trace back to habits that were never built.

What a PhD actually trains you to do

Strip away the paperwork and a doctorate asks three things of you. Ask a question nobody has answered yet. Answer it with evidence. Defend that answer in front of people who know the field better than you do. The thesis is simply the proof that you can do all three.

This is a real shift. Until now, most of your education rewarded right answers. Research rewards calibrated answers: claims that are exactly as strong as the evidence behind them, no stronger. Learning to say "this is what we can conclude, and this is where it stops" is the core of the job.

The three jobs of your first year

1. Map the field

Read widely before you read deeply. Your goal is a mental map: the main groups, the landmark papers, the methods everyone uses, and the problems people keep listing as future work. Write short notes for every paper you read. A pile of highlighted PDFs is not a map.

If reading feels slow, that is normal. The three pass method will save you a lot of time.

2. Find your question

Your topic will be vague at the start. By the end of year one it should become a research question you can state in one sentence. That narrowing is the most important intellectual work of the year. I cover how to do it in how to choose a PhD research question.

3. Build your toolkit

Every field has its tools: statistics, a programming language, lab or clinical protocols, a way of writing. Identify the ones your question will need and start learning them now, on small problems, while the stakes are low.

Working with your supervisor

Your supervisor is your most important collaborator, and the relationship works best when you take responsibility for it.

• Agree on a rhythm. Regular meetings, even short ones, beat long silences followed by a crisis.
• Arrive with an agenda. What you did, what blocked you, what you need decided.
• Write it down afterwards. Send a short summary of decisions and next steps. It prevents misunderstandings and becomes a record of your progress.
• Share drafts early. A rough page this week is more useful than a polished chapter in three months.
• Disagree with evidence. Supervisors respect a well argued alternative far more than silent compliance.

Habits worth building from week one

• A research log. A few lines a day: what you tried, what worked, what failed and why. Future you will rely on it when writing methods sections.
• A reference manager from day one. Zotero or a similar tool. Retrofitting references in year three is painful.
• Weekly writing. Even a few hundred words. Writing is how you discover what you actually think.
• Version control. Keep code, and ideally data processing scripts, under Git. Reproducibility starts here.
• A claims and evidence file. Each time you believe something new about your problem, write the claim and the evidence that supports it. It is the seed of every paper you will write.

Common first year mistakes

• Reading for months without writing anything.
• Keeping a topic so broad that no experiment could ever answer it.
• Hiding problems from your supervisor until they become emergencies.
• Measuring your progress against other students on different projects.
• Treating rest as optional. A PhD is long, and sustainable pace matters more than heroic weeks.