Before the meeting: prepare a one-page agenda
A useful agenda can include: progress since last time, one or two obstacles, decisions needed, files or figures to review, and proposed next steps. If a draft needs close reading, send it early enough for the advisor to realistically read it.
Lead with the decision, not the backstory
Instead of spending ten minutes narrating everything that happened, state the decision point: “The model is unstable with this specification; I see two reasonable alternatives and need guidance on which assumption is more defensible.” Context can follow as needed.
Ask questions that can be answered
“What do you think?” often produces less useful feedback than “Is the research question narrow enough for this dataset?” or “Which of these analyses should be treated as primary?” Specific questions help the advisor allocate attention.
End by converting discussion into actions
Cornell’s advising guides recommend keeping written plans and meeting notes. Record what you will do, what the advisor will do, and when the next check-in should occur. If a deadline depends on feedback, name the date explicitly.
Advisor meetings are part of project management
National Academies work on mentorship emphasizes intentionality and shared expectations. A meeting is not only a place to receive expertise; it is also a coordination mechanism for a long project with uncertainty and asymmetric information.
That is why preparation can improve both the scientific discussion and the working relationship.
Send enough context that the meeting can start at the decision
Advisor time is used more effectively when the basic context is available before the conversation. A short agenda can list the decisions needed, the relevant deadline, and links to any draft, figure, table, or analysis that requires review. If the advisor needs to spend the first half of the meeting discovering what the problem is, less time remains to solve it.
Prioritize questions that are expensive to answer alone. Administrative details may belong with a program coordinator. A conceptual question about the research design, interpretation, scope, or next milestone is often a better use of advising time.
End with explicit next actions
Before the meeting ends, summarize what changed: which analysis will be run, what will be revised, who will contact another collaborator, and when the next checkpoint should occur. If a key instruction is ambiguous, restate it in concrete terms. A brief follow-up note can preserve decisions that would otherwise be reconstructed from memory weeks later.
