Habit, Not Hack: Helping Trainees Decide What Enough Looks Like (Mentor)
The most rigorous labs aren't the ones that always do more. They're the ones that know exactly why.
Dr. Nguyen prided herself on rigor.
Her lab was known for thoroughness — strong controls, careful interpretation, clean data. It was a reputation she had earned and protected. When people described her work, thorough was the word they used. She took it as a compliment.
But over time, she started noticing something she hadn't expected.
Projects were stalling.
Not failing. Not collapsing. Just expanding — quietly, incrementally, without a clear reason why.
The Pattern She Hadn't Named
When trainees brought updates, conversations drifted in a familiar direction.
Another replicate. Another condition. Another angle. Each suggestion made sense in isolation. None of them were wrong. But collectively, they created a lab culture where done was a horizon that moved every time someone got close to it.
Trainees were working hard. They were also working indefinitely.
Then a student asked a question Dr. Nguyen wasn't prepared for.
"How will we know when this is done?"
She didn't have a good answer. Not because she hadn't thought about it — but because she realized she had never actually said it out loud. She had been mentoring toward quality. She had not been mentoring toward completion. And for her trainees, those two things had become impossible to tell apart.
What She Changed
At the next lab meeting, Dr. Nguyen tried something new.
"For every project going forward," she said, "we're going to define three things up front."
What specific question are we answering?
What evidence is sufficient to answer it?
What would be genuinely useful but is not required?
The third question was the most important one. Not because aspirational experiments are bad — some of the best science starts there. But because when everything is required, nothing is actually prioritized. And the trainee who can't tell the difference between a must-have and a nice-to-have doesn't know when they're allowed to stop.
The shift was noticeable. Discussions became sharper. Revisions became intentional. Trainees stopped doing the quiet guessing game of which extra experiment will finally earn approval — a game that, Dr. Nguyen realized, she had inadvertently created by never answering that question directly.
The Habit: Specify The Finish Line Before The Race Begins
Dr. Nguyen also changed the way she gave feedback.
Instead of "let's add one more" — which sounds harmless and is often well-intentioned — she started asking a different question:
"What decision will this data help us make?"
If there was a clear answer, the experiment belonged in the project. If there wasn't, it went on a list of future directions, not the current milestone. The science didn't suffer. If anything, it improved — because the work that remained was tighter, more purposeful, and easier to defend.
She also started doing something that felt simple but turned out to be more powerful than she expected: she said out loud when something was complete.
Not "this looks good, let's move on" — which is a positive signal but not a declaration. But "this answers the question we set out to answer. This is done."
For trainees who had spent months not knowing if they were close or far from finished, hearing that sentence landed differently than she anticipated. Several of them told her later it was the first time they had felt that way in years.
What This Habit Asks of You
This is not a habit about lowering standards. Dr. Nguyen's lab did not become less rigorous. The papers were still thorough. The controls were still strong. The difference was that rigor became purposeful rather than reflexive — a choice made for a reason, not a default that expanded to fill whatever time was available.
Before the next project phase begins, consider naming three things explicitly with your trainee:
— What is the minimum viable result that answers the central question? — What would constitute sufficient evidence to move forward? — What experiments or analyses are aspirational rather than required?
You don't have to get this perfectly right on the first try. You can revise it as the science develops. But having the conversation at all changes the dynamic — because now your trainee knows there is a line, you both know approximately where it is, and when they reach it, they can say so without guessing whether you'll move it again.
A Note on What This Isn't
This is not a habit about rushing. Some projects genuinely need more. Some data genuinely isn't ready. The habit doesn't tell you to accept incomplete work — it tells you to define complete work, so that when something falls short, both you and your trainee can name exactly what's missing rather than gesturing vaguely toward more.
The trainees who learn to define done become the scientists who can scope a project, meet a deadline, and communicate clearly about what their data does and doesn't show. Those are not small skills. They are the skills that make the difference between a researcher who produces and one who perpetually prepares to produce.
Clarity about enough doesn't lower standards.
It protects them.
That's not a hack. That's a habit.
✨ Research often comes with vague goals and invisible expectations. The Team Retrospective Guide, One-on-One Meeting Form, and Collaboration Agreement help make the implicit explicit—creating space to define what's enough, align priorities, and build healthier, more productive collaborations. Click on each tool to explore.
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.