Habit, Not Hack: The First Year Looks Different From the Other Side of the Desk (Mentor)
The students arriving now are not entry-level. Mentoring them like they are, is the first mistake.
Dr. Okonkwo prided herself on knowing how to read people.
After three years running her own lab, she had developed what she thought of as a reliable instinct for graduate students — who needed space, who needed structure, who would ask for help and who would quietly struggle until something broke.
She thought she was good at it.
Then she lost Leila.
The Pattern She Hadn't Named
Leila had joined the lab in year one. She was sharp, technically skilled, and worked without complaint. She showed up early and stayed late. She did not ask for much.
Dr. Okonkwo had read this as independence. Self-direction. The qualities she had valued in herself as a graduate student and had, without fully articulating it, been mentoring toward ever since.
What she had not read — what she had not thought to look for — was what Leila's silence was actually costing her.
Leila left at the end of her second year. She said, carefully, that it was a better fit elsewhere. Dr. Okonkwo spent a month being certain that was true and another month understanding it wasn't — not entirely.
A colleague, another PI who had been running her lab for fifteen years, said the thing that stayed with her:
"The students who never ask for anything are not the ones who need nothing. They're the ones who decided asking wasn't safe."
Dr. Okonkwo sat with that for a long time.
What She Changed
The next rotation student who came in was Soren — a first-year with four years of undergraduate research, a fellowship, and the specific alertness of someone trying very hard not to look like they were trying very hard.
Dr. Okonkwo recognized it immediately. She had looked exactly the same way, twelve years ago, in her own first rotation.
This time, she did not assume the recognition was enough.
At their first meeting, she tried something she had been reluctant to try because it felt too simple to be useful:
She asked Soren what they actually needed.
Not what the lab needed. Not what the project needed. What Soren needed, specifically, from her, in order to do their best work in these four months.
Soren had a list. They had clearly been waiting to be asked.
"I realized," Dr. Okonkwo said later, "that I had been mentoring people the way I wished someone had mentored me. But they weren't me. They had different gaps, different strengths, different fears. My job was never to give them what I needed. It was to figure out what they needed — and those are not the same thing."
That moment sparked a shift.
She stopped running her mentorship on assumption and started running it on information.
The Habit: Mentor the Person in Front of You, Not the Version of Yourself You Remember
The first year asks a great deal of graduate students. It also asks a great deal of the PIs who supervise them — most of whom were never trained for the job, learned it by receiving it with varying degrees of success, and are doing their best with the model they inherited.
That model is often insufficient. The habit that changes it is specificity: knowing what this particular person, right now, actually needs.
Before the Rotation Begins: Ask, Don't Assume
Before the first meeting, send your rotation student six questions. Not the standard onboarding document — the safety procedures and equipment access, that's for the lab manager. This is different.
Ask:
What kind of feedback do you find most useful, and what kind tends to land badly even when well-intentioned?
Do you prefer regular check-ins or space to go deep and report back?
What do you most want to develop this rotation that has nothing to do with experimental technique?
Under what circumstances do you find it hardest to ask for help?
Is there anything about how the lab runs that you want to flag early — even if it's just a question?
What do you want me to know about you that I probably wouldn't learn from watching you work?
You will learn more from the answers to these questions than from a month of observation.
During the Rotation: Read What Isn't Being Said
First-year students who are struggling do not always look like they are struggling. The ones who arrived already competent — with research experience, with skills, with a record of getting things done — are often the most likely to absorb difficulty quietly, because asking for help has never felt like part of the job description.
Watch for:
Coming in early and staying late without visible output. This is not diligence. It is often the specific stillness of someone working hard without knowing if they are working in the right direction.
"It's fine" answers to direct questions. Fine is not a state. It is a deflection. When someone says fine, ask: what's the part that isn't fine?
Never asking clarifying questions in meetings. In a healthy lab, people ask questions. Silence in the presence of complexity is not understanding — it is often self-protection.
Energy shifts when the PI enters the room. If your lab is different when you're there, that difference is information about what you've built — not what you intended to build.
Start every one-on-one with: "What's the thing you most need clarity on right now?" Not results. Not updates. What they need. The answer will tell you where they actually are.
When They're Teaching: Acknowledge the Invisible Work
Most first-year graduate students are also TAs. The TA assignment generates enormous invisible work — emails, grade disputes, students who need more than a recitation section can give — and supervisors rarely ask about it because it is not technically their domain.
Ask about it anyway.
At your next one-on-one:
How is the TA assignment actually going — not officially, but actually?
Is it taking more time than it should? If yes: have you told the course coordinator?
Is there a student you're spending significant emotional energy on? If yes: have you connected them with student services, or just mentioned it?
When you ask these questions, you signal that the invisible parts of the first year are visible to you. That signal changes what a trainee believes they are allowed to say.
When Reviewing the Proposal: Coach the Thinking, Not the Formatting
The research proposal is where first-year students most often reveal the gap between how they were trained to write and how scientists actually argue.
Most first-year proposals are too comprehensive. They try to prove knowledge instead of arguing a position. The introduction reads like a textbook because the student is demonstrating that they belong here, rather than making a case for what they want to do.
When you give feedback on a draft, ask these questions before you mark anything up:
What is the central question of this proposal? Can I state it in one sentence?
Is the introduction built around that question, or around demonstrating field knowledge?
Where is this student's actual thinking — and is it visible, or buried under citation?
Then give feedback that surfaces the thinking, not feedback that adds comprehensiveness.
"This doesn't sound like you thinking. This sounds like you proving you've read."
That sentence, said with care, is the most useful thing you can say to a first-year whose proposal reads like a literature review.
When They Choose Another Lab: Receive It Honestly
Not every rotation ends in a match. This is correct and expected.
What is less expected — and more important — is what you do with the information that a student chose not to stay.
Ask yourself, honestly:
Did they have enough information to make a real choice, or did they only see the version of the lab I presented?
Was there anything about how I ran the rotation that made asking questions feel risky?
If I could do it again, what would I do differently?
You do not have to share this reflection with anyone. But not doing it means the next rotation student inherits the same conditions.
The students who don't stay are not failures. They are often the most accurate readers of what your lab is actually like — more accurate than the ones who stay because leaving feels too complicated.
Your Habit-Forming Reflection After Each Rotation
Ask yourself:
Did I ask what this person needed, or did I assume I knew?
Was there anything they seemed to be carrying that I didn't ask about?
Did I name clearly, at least once, what success in this rotation looked like — and when something was done well?
Would the person who rotated here describe this lab the same way I would?
And for your current graduate students and postdocs — not just rotation students:
When did I last ask what they need from me, specifically, this week?
Is anyone in the lab the same person when I'm in the room as when I'm not?
Am I mentoring toward who they are trying to become, or toward who I was?
The PI role is not an extension of the scientist role. The skills that made you good at research — depth, persistence, independent problem-solving — are useful here, but they are not sufficient.
Mentorship requires a different kind of attention: to the particular person in front of you, to what they are not saying, to the gap between what they need and what you needed at their stage.
The students arriving now have bachelor's degrees and research experience and, frequently, a clearer accounting of what the academic environment costs them than the generation that trained them. They are not entry-level in any meaningful sense. They are professionals at a transition point, learning a new mode.
Your job is not to remind them of what they don't know yet.
It is to create the conditions in which what they already know can grow into something neither of you has fully imagined.
That's not a hack. That's a habit.
✨ A successful first year isn't just about individual effort—it's about shared clarity. Use the Skill Gap Analysis, Individual Development Plan, Mentorship Relationship Map, and Lab Onboarding Checklist to align expectations, identify development opportunities, and build stronger trainee-supervisor partnerships from the start.
