What do you wish your supervisor understood?
The four situations that come up in every room where this gets discussed:
- The feedback lottery. Some meetings you get gold; some you get “looks fine” on a chapter you sweated over. The variance isn’t random — it’s steerable.
- The vanishing supervisor. Three weeks for an email reply while your milestone clock keeps ticking. Waiting silently is the worst available strategy.
- The mind-reading trap. You expect direction; they expect independence; nobody ever said either out loud. Most friction is mismatched, unspoken expectations.
- The power asymmetry. It’s hard to push back on the person who examines your progress. But polite pushback is a skill they expect a PhD to develop — often without ever saying so.
Make the implicit explicit
The single most useful idea in this session: nearly everything that goes wrong here goes wrong because something reasonable was never said out loud.
Negotiate the ground rules
Two things are worth agreeing on explicitly, early, and in writing:
- The hours you’ll devote to each activity — writing, lab work, teaching, the side project they keep suggesting.
- When and how often you’ll show progress — weekly email, monthly meeting, chapter by chapter.
Worth adding: the role of each committee member, what resources you can expect, and which conferences you’re aiming for.
Agree the feedback contract
For the thesis: the dates you’ll send drafts, how many versions they’ll comment on, their turnaround time — and yours. For articles: who drafts first, what each person contributes, and author order.
In writing. Not because you distrust anyone, but because two people remember a hallway conversation differently in eighteen months.
Own the meeting cycle
You can run this unilaterally; it doesn’t need anyone’s permission and it changes the quality of supervision immediately.
- The day before: send a short agenda — done / stuck / need from you.
- In the meeting: ask scoped questions. Not “what do you think?” but “does the argument in §2 hold?”
- Afterwards: two lines of minutes by email — what was agreed, who does it, by when.
That last one is thirty seconds of typing and it is the single highest-return habit in this whole session. It creates a shared record, it surfaces misunderstandings while they’re still small, and it quietly makes deadlines real.
Keep records, and escalate well
Save the email trail. Raise problems with your supervisor first. Compare notes with other students — you will usually find the thing you thought was uniquely your failing is a known feature. If it doesn’t resolve, your postgraduate coordinator or program director exists precisely for this. Knowing your rights isn’t betrayal.
Decoding supervisor-speak
Every vague comment is an invitation to ask a sharper question.
| What they say | What to do with it |
|---|---|
| “This section needs work” | Ask which of structure, evidence or prose — make them choose one |
| “Have you considered [entire other field]?” | Ask: “Is that essential for the thesis, or an interesting aside?” Scope creep dies in the open. |
| “Looks fine.” | Ask one targeted question anyway. “Fine” often means “didn’t read closely.” |
| “Why isn’t this done yet?” | Show the plan, renegotiate the timeline out loud, and minute the new date. |
Do this now — 15 minutes
1. Write the agenda for your next supervision meeting. Three headings, three bullets each, no more:
DONE since last time
· …
STUCK on
· …
NEED FROM YOU
· … (be specific: a decision, a signature, feedback on §2 by Friday)2. Draft one scoped feedback ask. Take the thing you’re about to send and replace “let me know what you think” with a question that names the section and the kind of feedback you want.
3. Answer the two ground-rule questions for yourself — how many hours on what, and how often you’ll show progress — then put them on the agenda as something to confirm. If your answer and theirs differ, you’ve just found the thing that was going to cause trouble in month nine.
Templates you can steal
Chasing a silent supervisor — after two weeks, not four:
Hi [Name], following up on the draft I sent on [date]. I’m planning to submit the chapter to the committee on [date], so it’d help to have your comments by [date] — even partial ones, or just on §2 if that’s easier. If that timing doesn’t work, let me know what does and I’ll replan around it.
Two-line minutes — send within the hour, every time:
Thanks for the meeting. To confirm what we agreed: I’ll [task] by [date]; you’ll [task] by [date]. Next meeting [date]. Shout if I’ve mis-remembered anything.
Pushing back on scope creep:
That’s an interesting angle. Before I take it on — is it essential for the thesis argument, or a good idea for a later paper? I’m trying to keep [current chapter] on track for [date], and I’d rather park it deliberately than let it drift.
Where to go next
Surviving peer review is the same idea aimed outward: what actually happens to a paper after you submit it, and how to write a response to reviewers — including Reviewer 2.