Habit, Not Hack: Make Group Meetings Matter (Mentor and Audience)
Every lab meeting is a free class in what no one teaches you.
The only question is whether anyone in the room knows they're enrolled.
Picture two lab meetings happening in the same building on the same afternoon.
In the first, a second-year student presents six months of data. Three senior members ask sharp questions. The PI gives detailed feedback. The junior students in the back row take occasional notes, check their phones, and leave without speaking. Nobody follows up afterward. The presenter goes home unsure whether the meeting went well or not.
In the second lab, the same kind of meeting happens — same data, same stage, same questions. But before the meeting, the PI sent a one-paragraph outline and asked everyone to come with a question. During the meeting, when a junior student asked something hesitant and half-formed, the PI said: "Actually, stay with that — I think you're onto something." Afterward, two lab members emailed the presenter with follow-up thoughts. The presenter went home knowing exactly what to do next.
Same hour. Completely different training.
Lab meetings aren't just routine updates. They're rehearsal spaces for scientific thinking, communication, and culture. But they only work when everyone in the room — presenters, listeners, and leaders — knows how to show up with purpose.
This post is for both sides of the bench.
The Habit For Graduate Students: Be Actively Present — Even When You're Not Presenting
Most students sit quietly through lab meetings, unsure of their role. If you're not presenting, it can feel like your job is just to show up and not disrupt.
It isn't. Lab meetings are a front-row seat to research culture — a recurring window into how experienced scientists think, where they get stuck, and what they actually value. Every exchange between your PI and a presenter is a data point about how science gets evaluated in your field. Every question from a senior lab member is a model of what scientific thinking sounds like out loud.
But you only benefit if you treat it that way.
Before the Meeting
Preparation doesn't have to be extensive. It has to be intentional.
If you can find a recent paper or abstract from the presenter, skim it. Ten minutes of context will make the next hour significantly more useful. You'll follow the logic faster, spot the tension earlier, and ask better questions.
Set one personal learning goal before you walk in. Not a vague one — a specific one. "I want to understand why they chose that statistical approach.""I want to pay attention to how the PI responds to uncertainty." Writing it down shifts your brain from passive to purposeful before the meeting has even started.
Prepare two questions — even if you never ask them. The act of formulating a question forces you to engage with the material at a level that passive listening never reaches. And you'll be surprised how often the question you prepared turns out to be exactly the right one to ask.
During the Meeting
Take notes as if you'll need to explain the work to someone else later — or apply it to your own project. This isn't transcription. It's active processing. It keeps you present in a way that passive listening rarely does.
Track what you don't understand. Write "??" next to unfamiliar terms, confusing figures, or logical leaps you can't follow. These aren't signs of ignorance. They're your research agenda for the week. The terms you don't know yet are the ones worth knowing.
Watch for patterns in how your PI engages. What earns genuine affirmation versus polite acknowledgment? What triggers a follow-up question versus a redirect? When does the room lean in and when does it go quiet? This is professional development in disguise — a real-time tutorial in how scientific thinking gets evaluated in your specific field and lab. Pay close attention to it.
When You Speak
You don't need to ask the most sophisticated question in the room. You need to ask a real one — something you genuinely want to know, framed specifically enough that the presenter can actually answer it.
"Can you walk us through why you chose that method over the alternative?"
"What's your plan B if this approach doesn't replicate?"
"I'm not sure I followed the logic between these two steps — could you say more about that?"
Questions like these do something that silence never does: they signal that you're thinking, engaged, and willing to push on the work respectfully. People remember consistent engagement. It builds more credibility over time than any single polished presentation.
After the Meeting
Don't close your laptop and move on.
Spend five minutes reviewing your notes while the meeting is still fresh. Identify the one thing that surprised you, the one thing you still don't understand, and the one thing that connects to your own work. Flag anything you want to follow up on — then actually follow up. Look up the term. Read the abstract. Send the email.
Consider starting a Lab Meeting Journal — just five to ten lines after each meeting. What was presented. What the key tension was. What the PI responded to. One thing you learned. One thing you still don't understand.
Over a semester this becomes something remarkable — a personal map of your lab's scientific thinking, a record of the questions that matter, and one of the most useful documents you'll have when it's time to write your own proposals or presentations. It takes almost no time to build and pays back far more than it costs.
The Habit For Supervisors and PIs: Make Participation the Norm — Not the Exception
Here's what most students won't tell you: they don't know what you want from them in lab meetings.
They don't know if they're supposed to ask questions or just listen. They don't know what a good question looks like to you. They don't know whether admitting confusion is a sign of engagement or a sign of weakness. So they default to the safest option — silence — and spend months watching a training opportunity they don't know how to access.
The culture of your lab meetings starts with you. Your tone, your structure, and the way you respond to the first tentative question from a junior member will teach everyone in the room what participation is supposed to look like here. Make sure what you're teaching is worth learning.
Before the Meeting
Send a brief agenda or outline twenty-four hours in advance — even a single paragraph. This gives every lab member, especially junior ones, a fighting chance to prepare. It signals that the meeting has a purpose and that preparation is expected.
Ask each person to come with one question or one takeaway from their own work that connects to what's being presented. Low stakes, but it shifts the meeting from a passive download to an active exchange before anyone has said a word.
Consider assigning rotating roles — discussion leader, notetaker, designated questioner for junior members. These aren't bureaucratic additions. They're permission structures. They give people who wouldn't naturally speak a reason and a role to do so. And they distribute the labor of the meeting in a way that develops skills across the whole lab rather than concentrating them in whoever is most confident.
During the Meeting
Model curiosity, not just critique. The questions you ask in lab meetings teach your lab what scientific thinking sounds like out loud. If your questions primarily demonstrate your own expertise, your lab will learn to perform expertise. If they demonstrate genuine curiosity — including uncertainty and confusion — your lab will learn that curiosity is safe here.
"What's something you're still unsure about in this data?"
"If you had to troubleshoot this result, where would you start?"
"Walk me through your reasoning — not the result, the thinking behind it."
Call out good thinking, not just good results. This is one of the most powerful habits a PI can build in lab meetings — and one of the rarest. When a student gives a careful, honest account of their uncertainty, name it as valuable: "That's exactly the right way to think about this." When someone asks a question that reveals a gap everyone else missed, say so: "That's a great catch — you're thinking like a reviewer." When a junior member offers a half-formed observation that points somewhere interesting, don't let it get talked over: "Stay with that — I think you're onto something."
What you praise is what your lab learns to value. Praise the thinking, not just the answer.
Invite contributions from people who haven't spoken. "Any thoughts from those who haven't weighed in yet?" This one sentence makes it normal to contribute, rather than exceptional. It protects the quiet members of your lab from disappearing into the background indefinitely.
After the Meeting
Acknowledge preparation and engagement — especially from quieter students. A brief "good question today" after the meeting costs you nothing and communicates everything about whether their participation was noticed and valued.
Follow up one-on-one with anyone who seemed confused or disengaged. Not to evaluate them — to understand what's in the way. Sometimes disengagement is about the meeting. Sometimes it's about something much bigger that the meeting surfaced.
Reflect on patterns. Are the same people always talking? Who never speaks? Is there a junior member who has been in the background for months? These patterns don't fix themselves. They require a deliberate choice to do something different.
Consider keeping your own Lab Meeting Journal. Five to ten lines after each meeting: what the key tension was, what question opened the most useful conversation, where a junior member surprised you, where the meeting lost energy and why. Over a semester this becomes a map of your lab's intellectual culture — where it's healthy, where it's stuck, and what it might need next.
Why This Habit Works for Everyone
Lab meetings aren't just about data. They're how a lab rehearses clarity, handles critique, and builds a culture of mutual learning — or doesn't.
Students learn faster when they observe and participate with intention rather than waiting for expertise they don't yet have. PIs mentor more effectively when they create space for reflection and curiosity rather than just reporting and evaluation. And both sides benefit when the meeting becomes a place where thinking out loud is normal, uncertainty is welcomed, and the quietest person in the room knows their question is worth asking.
The skills built in these meetings don't stay in these meetings. They travel — into seminars, conferences, postdocs, and leadership roles. Into the labs your trainees will run someday and the meetings they'll run inside them. Into every professional environment where the ability to ask a precise question, engage honestly with uncertainty, and make space for someone else's thinking turns out to matter more than anyone told you it would.
Which is almost all of them.
Your Weekly Reflection
For students — before your next lab meeting:
Do I know enough about what's being presented to follow along — and if not, what can I do in the next fifteen minutes?
What's one genuine question I want answered before I leave?
For students — after your next lab meeting:
What's the one thing I learned that I didn't know before?
Did I contribute something — or did I stay quiet when I had something worth saying?
Is there a pattern I noticed today about how my PI thinks or what they value?
For PIs — after your next lab meeting:
Did I model the kind of curiosity I want to see — including uncertainty and honest confusion?
Was there a junior member who stayed quiet that I should check in with?
Did I call out good thinking — or just good results?
What was the most useful exchange today — and do my students know that's what I valued?
For Everyone in Research Spaces
Lab meetings are already happening. The only question is whether they're already teaching what you want them to teach — and whether the people in the room know they're supposed to be learning.
Name it. Model it. Show up for it.
Turn the time-filler into the training ground. It's already there. It just needs someone to be intentional about it.
That's not a hack. That's a habit.
✨ Want to take this habit further? The GradLab Compass Habit Toolkit includes Communication, Boundaries & Professionalism resources to help 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.