Habit, Not Hack: Asking Questions (Trainee)
The difference between a bold question and an awkward one is intent, clarity, and respect — and knowing when to be assertive.
Some grad students take notes during seminars. Some stare at the slides and nod politely. And some — like Maria — rehearse a question in their head for fifteen minutes and still say nothing.
The Story: "I had a question… but I didn't ask."
Maria was in her second year of grad school when she attended a seminar by a visiting speaker — an expert on stress signaling in plants. One part of the talk sparked something: a translational stalling mechanism that mirrored what she'd been observing in yeast.
She had a question. She also wondered: Could I ask for their plasmid or protocol?
But instead of speaking up, she hesitated. She worried she wasn't senior enough to make that kind of request. That her email would seem presumptuous. That she hadn't earned the right to ask.
So she said nothing.
Later, she reflected: "I realized I wasn't just afraid of asking — I wasn't clear on what I wanted from the answer, or how to ask respectfully."
That moment sparked a shift.
Maria began journaling after talks:
What was my actual question?
Was I trying to learn, collaborate, or request something?
What would a respectful, professional version of that question look like?
She didn't just want to ask questions. She wanted to ask them well — in seminars, in labs, and in emails.
The Habit: Ask with Purpose, Ask with Grace
Whether you're asking a clarifying question during a talk, requesting materials from a PI halfway across the world, or asking a workmate for help — clarity, intention, and tone matter every time.
Before Asking: Know What You Want
Ask yourself:
Am I trying to understand something more deeply?
Do I want to connect their work to mine?
Am I seeking access to a resource, dataset, method, or mentorship?
When you know your why, you'll ask with confidence and professionalism — and you'll be far more likely to get what you need.
During Seminars: Frame It Thoughtfully
Good seminar questions are specific, respectful of time, and grounded in the speaker's actual content. Try:
"Thank you for the talk. I'm curious — on slide 9, you mentioned [specific result]..."
"I'm working on something related and was wondering if you've considered [adjacent mechanism]..."
"Would you be open to sharing more about that assay design?"
You don't need to be senior to ask a good question. You need to be prepared and specific.
When Requesting Research Materials
Whether you're reaching out to a published PI, a collaborator, or a shared facility — a well-crafted request goes a long way. Include:
A brief introduction (2–3 lines about you and your research)
A clear statement of what you're requesting and why
A reference to their work and how you'll give credit
An offer to handle logistics (MTA, shipping, etc.)
Example:
Dear Dr. Smith, I enjoyed your recent paper on X. I'm a graduate student working on [brief topic] and was especially interested in your use of [construct/method]. Would you be willing to share the [plasmid/protocol]? We'd be happy to arrange an MTA and will cite your work appropriately.
This is how connections and collaborations begin.
When Asking Workmates or Lab Staff
It's easy to treat internal requests casually — but this is where good lab culture lives or dies. Mind your tone, timing, and transparency:
Don't demand. Ask. ➤ "Hey, would you be open to walking me through the settings you used for the FPLC yesterday?"
Don't downplay real needs. ➤ "I'm at a standstill until I can use the centrifuge — can I book a slot this afternoon and coordinate with you?"
Don't apologize for needing help. ➤ "Would you be open to walking me through this column setup? I want to make sure I'm doing it correctly."
Give context. ➤ "I'm planning a long thermocycler run — would that interfere with anything you've got lined up?"
Don't assume they'll read your mind. ➤ "I've been waiting a while for the shared antibody — can we come up with a schedule that works for both of us?"
Acknowledge effort. ➤ "Thanks for letting me borrow that last week — saved me a lot of time."
When to Be Assertive, Not Just Polite
Sometimes, asking politely isn't enough. You'll need to move from asking to advocating — especially when:
You're being delayed by someone's lack of follow-through
You need access to something necessary for your experiments
You're navigating authorship, data sharing, or workload boundaries
In those moments:
Stick to facts: "I sent the request two weeks ago and haven't heard back."
Be specific about what you need and why
Offer solutions or next steps
Stay calm, professional, and firm
Assertiveness is not aggression. It's clarity with boundaries.
Supervisors — this applies to you too. When a trainee is waiting on feedback, unclear on expectations, or approaching a deadline, modeling assertive and timely communication sets the tone for the entire lab. The culture you want starts with how you show up in these moments.
Respect isn't reserved for titles. It's for your peers, your staff, and the people you mentor. And respectful requests still have room for assertiveness — especially when timelines, fairness, or data are involved.
Your Habit-Forming Reflection After Any Exchange
Ask yourself:
What did I really need to know or receive?
Did I ask clearly, professionally, and early enough?
Did I show appreciation and acknowledge others' time?
If I didn't get a reply — or got a no — did I follow up respectfully or redirect my approach?
Asking for what you need — whether it's knowledge, feedback, or a reagent — isn't overstepping. It's stepping into your role as a real scientist.
It takes more than answers to move your research forward. It takes questions — asked clearly, kindly, and without shame.
That's not a hack. That's a habit.
✨ Want to take this habit further? The GradLab Compass Habit Toolkit includes Communication, Boundaries & Professionalism tools designed to help you ask defining questions and navigate difficult conversations with clarity.
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.