Habit, Not Hack: Managing Expectations Before They Manage You (Mentor)
Clarity is kindness — and when you're the one in charge, it's also your responsibility.
The first time Dr. Reyes welcomed a new student into her lab, she thought she did everything right.
Warm smile. Onboarding folder — lab protocols, safety forms, a reading list, a calendar invite for their first one-on-one. A genuinely encouraging "Welcome aboard. Let me know if you have any questions."
She thought she was being approachable. Giving the student room to settle in without overwhelming them on day one.
What she found out weeks later, through a casual comment from another lab member, was that the student had left that meeting confused, a little deflated, and quietly unsure whether they actually belonged there. They had waited for someone to tell them what to do next. Nobody did. So they had spent two weeks reading papers they weren't sure were relevant, unsure whether to interrupt anyone to ask.
Dr. Reyes hadn't meant to be vague. She hadn't meant to send any message at all.
But that's exactly the problem.
Silence Isn't Neutrality. It's a Vacuum.
And in graduate advising, vacuums fill with anxiety.
When a new student doesn't know how their advisor works — how they prefer to give feedback, what independence actually means in this lab, whether bringing a rough idea is welcome or premature — they don't sit comfortably in that uncertainty. They fill it. With assumptions, worst-case interpretations, and the quiet conviction that everyone else already knows something they don't.
Most advisor-student tension doesn't come from a lack of care. It comes from mismatched assumptions — and the tricky part is that neither side usually knows the mismatch exists until it has already strained the relationship.
The student who disappears for two months wasn't being avoidant. They were being independent — the way they understood independence to mean. The student who checks in constantly wasn't being needy. They were doing what they thought was expected. The student who handed in a draft that went in entirely the wrong direction wasn't being careless. They were working from a map nobody gave them.
What It Actually Costs
Dr. Reyes started paying attention to what the silence was costing her lab.
The student who spent a semester on a direction nobody had explicitly approved. The postdoc who didn't flag a problem early because they weren't sure if bringing problems was welcome. The talented PhD candidate who became quieter and more cautious over time — not because they were losing interest in the science, but because they had learned, through a hundred small signals, that uncertainty was something to hide rather than share.
None of these were dramatic failures. They were quiet ones. The kind that accumulate slowly and are almost impossible to trace back to a single cause — because the cause wasn't a bad moment. It was the absence of a conversation that never happened.
The most expensive thing in mentorship isn't a mistake. It's a mismatch that goes unnamed long enough to become a pattern.
The Shift Dr. Reyes Made
She stopped assuming her students knew how she operated.
Not because they were incapable of figuring it out — but because making them figure it out silently was an unnecessary tax on their energy and her relationship with them. They were spending cognitive resources decoding her when they could have been doing science.
So she started surfacing expectations from both sides — early, explicitly, and without making it a formal performance. Just a conversation. The kind that should have been happening from day one.
She started asking:
"What do you need from me to get started — and what would feel like too much or too little support?"
"How do you like to receive feedback — written comments you can sit with, or live conversation where we can think through it together?"
"What's your working style when you're drafting or stuck? Do you want to talk it through early, or work through it first and then come to me?"
"What would make this milestone feel successful to you — not just to me?"
And she started sharing how she worked — because she realized her students had no way of knowing unless she told them:
"I tend to give brief feedback unless you ask for more detail. If you want line edits, tell me."
"I like updates every two weeks. Even a two-line email saying 'no progress yet, here's why' is more useful to me than silence."
"You can bring rough ideas. You don't have to impress me before you show up. That's what the early meetings are for."
"If something isn't working — the project, the dynamic, anything — I want to know early. Not because I'll have a perfect answer, but because I can't help with something I don't know exists."
Why This Feels Hard — And Why It's Worth It
It can feel awkward at first. Like you're overexplaining, or micromanaging, or stating things that should be obvious.
But here's what Dr. Reyes found: nothing she said was actually obvious to her students. What felt like common sense to her — because she had been in academia for fifteen years — was completely opaque to someone who had never had a PI before. The things she assumed everyone knew were precisely the things nobody had ever told her students.
Naming your working style isn't micromanagement. It's modeling. You're not just teaching research — you're showing your students what it looks like to work with someone clearly, honestly, and without making them guess.
And the students who experience that? They carry it forward. They set expectations with their own collaborators. They ask clarifying questions without apologizing for them. They build working relationships that don't run on silent assumptions.
The expectation-setting culture you create in your lab doesn't stay in your lab.
The Habit: Make Expectations Explicit — Early and Often
This isn't a one-time conversation. It's a practice — revisited at the start of new projects, after major transitions, and any time you sense the relationship has drifted into assumption territory.
1. Have the working-style conversation in the first two weeks. Don't wait for a problem to surface it. Before the first major project begins, sit down and name how you work — and ask how they work. Not as a performance review, but as a genuine alignment conversation. "Here's what helps me be a good advisor to you. What helps you do your best work?"
2. Ask about their expectations, not just your own. It's easy to tell students what you expect. It's rarer — and more powerful — to ask what they're expecting from you. "What were you hoping this relationship would look like? What kind of mentorship has worked well for you before?" Their answers will tell you more than any onboarding checklist.
3. Start meetings with alignment, not just agenda."Before we dive in — what's most useful for us to cover today?" That one question prevents twenty minutes of the wrong conversation. It also signals that you see the meeting as a collaboration, not a report.
4. Revisit expectations after transitions. New project. New year. Post-submission slump. Conference season. These are moments when the implicit rules of the relationship often shift without anyone naming it. Check in: "I want to make sure we're still aligned on what support looks like right now. Has anything changed for you?"
5. Make it safe to flag misalignment. The goal of all of this is to create an environment where a student can say "I think I misunderstood what you were asking for" without it feeling like a confession of failure. That safety doesn't happen automatically. You have to build it — by responding well the first few times it's tested.
What Good Advising Actually Is
Good advising isn't intuitive. It's iterative.
The best mentorship isn't about reacting to problems — it's about designing relationships that prevent them. And the foundation of that design is simple: stop assuming, start aligning.
When Dr. Reyes stopped expecting her students to decode her and started making herself legible to them, something shifted. Her students came to meetings more prepared. They flagged problems earlier. They brought rougher, braver ideas — because they knew rough and brave were welcome.
And she grew too. Because staying in the habit of asking "what do you need from me right now?" kept her from calcifying into the kind of mentor who gives the same guidance to every student regardless of who they actually are.
The Long Game
The students who come through your lab will mentor their own students someday. They will set expectations — or fail to — based in part on what they experienced with you.
The one who learned that clarity is normal will name their working style on day one with their own trainees. The one who learned that checking in is welcome will build labs where silence isn't the default. The one who heard "you can bring rough ideas" will say it to someone else — and mean it.
Every expectation conversation you have is a small act of culture change. Not just for this student, in this lab, right now. But for every lab they'll ever be part of.
Your Weekly Reflection
After each one-on-one this week, ask yourself:
Did I assume my student knew something I never actually told them?
Is there a working-style preference I have that I've never made explicit?
Did I ask what they needed from me — or only tell them what I needed from them?
Is there a student who seems confused, disengaged, or overly cautious that might just need a clearer map?
When did I last check in on whether our expectations are still aligned?
For PIs and Research Advisors
Your students are not mind readers. Neither are you.
The relationship that works isn't the one where everyone magically understands each other — it's the one where both sides have committed to making the invisible visible before it becomes a problem.
Make clarity a habit. Make alignment a ritual. Make it safe to say "I think I misunderstood" — because that sentence, spoken early, saves months.
That's not a hack. That's a habit.
✨ Want to take this habit further? The GradLab Compass Habit Toolkit includes Skills, Growth & Competence tools alongside Communication, Boundaries & Professionalism resources to help understand abilities with honesty, communicate expectations clearly, and make meetings more focused, manageable, and productive.
Stories are fictionalized or composite narratives, created to illustrate common challenges and patterns in research life. They are intended for educational and reflective purposes and do not represent any specific individual or institution.