Habit, Not Hack: Deciding What Enough Looks Like (Trainee)

In research, the hardest question isn’t “how do I do more?” It’s “how do I know when I’m done?”

The problem wasn't that Sam didn't know how to work hard.

The problem was that there was no clear stopping point.

Every figure could be cleaner. Every control could be expanded. Every analysis could be rerun just one more time. The work was never bad — it just never felt finished. And when Sam asked whether it was enough, the answers were always vague.

"Let's see how it looks." "Maybe add one more." "We'll know when we get there."

So Sam kept going.

The Moving Goalpost

Weeks turned into months.

The goalposts shifted quietly — one extra experiment here, a small revision there. None of it unreasonable on its own. All of it exhausting together. The kind of exhaustion that doesn't announce itself because each individual ask is perfectly defensible.

What made it worse was watching others stop sooner.

Someone submitted a paper with fewer controls. Another defended with a smaller dataset. Sam assumed they were cutting corners or missing something obvious. The kind of quiet judgment that research culture quietly encourages — the idea that more is always more rigorous, that stopping earlier is always a compromise.

Until a postdoc said something that changed everything.

"They didn't do less," she said. "They decided earlier what 'enough' meant."

The Question Nobody Asks Before Starting

That night, Sam rewrote their project plan.

Not to add tasks. To define an endpoint.

Not "what else could I add?" — that question has no natural bottom. But "what would make this complete?" That question does.

For one figure, the answer looked like this:

— Reproducible trend across three independent replicates — One orthogonal validation method — Limitation stated clearly in the discussion

Anything beyond that was improvement, not requirement. Valuable, maybe. But optional — and therefore a conscious choice, not an obligation.

The distinction matters more than it sounds. When improvement is optional, you can decide whether to pursue it. When everything is a requirement, you can't stop at all.

What Happened When Sam Named It Out Loud

At the next meeting, Sam tried something new.

"This meets the criteria we discussed," they said. "If we want to go further, we should decide why."

The room went quiet.

Then the PI nodded.

"This is enough. Let's move on."

Sam felt something unfamiliar.

Relief. Not because the work was perfect — but because it was complete on purpose. There's a difference between finishing because you ran out of time and finishing because you reached the line you drew. Only one of them feels like a decision.

The Habit: Define "Enough" Before Perfectionism Takes Over

Perfectionism in research isn't always a personality trait. Sometimes it's a systems failure — nobody defined what done looks like, so done never arrives.

This habit closes that gap. Before starting any significant piece of work, write a completion criterion:

This will be enough when...

Be specific. Not "when it's good" — that's not a criterion, it's a feeling. But "when I have three replicates showing a consistent trend and one independent validation" — that's a line you can actually reach.

The criteria don't have to be perfect. They just have to exist. You can revise them with your advisor. You can negotiate them upward if new questions emerge. But you need a starting point that isn't "we'll know when we get there" — because that answer means you never will.

A Note on What This Isn't

This is not a habit about doing less.

Some projects genuinely require more. Some figures need another replicate. Some datasets aren't ready. This habit doesn't tell you to stop early — it tells you to decide early what stopping looks like, so that when you do add more, it's a choice with a reason, not an anxiety response to an undefined standard.

The researchers who finish things aren't always the ones who care less. They're often the ones who care enough to be precise about what they're aiming for.

For Supervisors and Mentors

When you say "let's see how it looks" or "we'll know when we get there," you are not being vague on purpose. You're being appropriately flexible about emerging science.

But your trainee may be hearing something different: there is no finish line.

The most useful thing you can do at the start of any project phase is name the criteria out loud. Not a perfect rubric — just the minimum viable completion point. What does this figure need to show before we move on? What would make this section of the thesis ready?

When your trainee says "this meets the criteria we discussed" and you can say "yes, it does" — that's not just a productive meeting. That's a trainee learning what done feels like. And that habit will follow them for the rest of their career.

Perfectionism doesn't feel like a problem when it's happening. It feels like rigor. It feels like caring. It feels like not cutting corners.

But there's a version of rigor that protects the work — and a version that just extends it indefinitely. Learning to tell the difference is one of the most important skills research training rarely teaches directly.

Define the line. Reach it. Then move.

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.