Habit, Not Hack: Design work around energy (Mentor)

Hours are easy to count. Energy is what actually runs the lab.

The meeting was at 10 a.m. on a Tuesday.

Dr. Reyes had put it there deliberately — midmorning, not too early, plenty of time before lunch. A reasonable slot. A considerate one, even.

What they hadn't thought about was that their most prolific writer in the lab — the one who had been quietly producing the best chapter drafts anyone had seen in years — wrote every morning from eight to eleven without interruption. Without fail. And now didn't.

The draft that week was halting. The one after that, thin. Dr. Reyes assumed it was a rough patch. It wasn't. It was a Tuesday at 10 am.

The Assumption Running Most Labs

There is a version of lab management that treats time as a neutral container.

You have hours. Your trainees have hours. You fill those hours with tasks, meetings, experiments, and expectations. The calendar is a logistics problem, not a science problem.

This assumption is understandable. Labs are complex. Schedules are tight. Equipment slots open when they open. Core hours exist for a reason. You can't build an entire operation around one person's preference for silence in the morning.

But there's a difference between can't always accommodate and never thought to ask.

Most supervisors are in the second camp — not because they don't care about their trainees' working conditions, but because they were never trained to think of cognitive timing as a real variable. They were trained to think about productivity in hours. And hours feel equivalent in a way that, neurologically, they are not.

What Dr. Reyes Started Noticing

After the writing slump stretched into a month, Dr. Reyes stopped assuming and started paying attention.

Not in a formal way. Just noticing. Who was sharp at which meetings? Who sent their most cogent emails at what time of day? Who looked blank-faced during afternoon check-ins that should have been simple? Who sent a Slack message at 8:47 am. with a fully formed solution to a problem that had been discussed, unresolved, the day before?

The patterns were not subtle once they were visible.

One postdoc did her best experimental troubleshooting in the first two hours of the day. A PhD student took longer to warm up — slow to start, but reliably hitting their stride from noon to three, when others were fading. Another trainee — the quiet one everyone underestimated — produced nothing of consequence when interrupted and extraordinary work when left alone.

None of this had been designed for. None of it had been asked about. The lab calendar had been built around equipment availability, meeting conventions, and Dr. Reyes's own schedule — without a single conversation about when each person actually functioned best.

The Negotiable and the Non-Negotiable

Before anything else, a clarification: this is not a habit about pretending constraints don't exist.

Department seminars happen when they happen. Dissertation committee meetings, core facility booking windows, institutional deadlines, and required training sessions don't move because someone's cognitive peak is at 9 am. Those are fixed points — and everyone, trainees included, understands that. Accommodating them is part of working within a larger institution, and no energy management framework changes that reality.

What this habit is about is everything else. The recurring lab meeting that defaulted to Wednesday at 10 am because that's when it was first scheduled three years ago. The one-on-one check-in placed mid-morning out of habit rather than intention. The Slack message sent at 9 am. that could have waited until noon. The open-door culture that means a trainee's best window gets quietly consumed by whoever stops by first.

These are the negotiable hours — and most labs have more of them than anyone realizes.

The Habit: Schedule Meetings Around Cognitive Load, Not Just Convenience

Dr. Reyes made one structural change: lab meetings moved to Thursday afternoons.

Not because Thursday afternoons were ideal for everyone. But because they were consistently low-value time — the cognitive trough before the week's end, when no one was doing their best independent work anyway. Moving the meeting there didn't cost anyone a high-output window. It just occupied hours that had largely been occupied by distraction and fatigue.

The morning slots that had been fragmented — a 10 am here, an 11 am check-in there — were largely cleared. Trainees who needed uninterrupted mornings got them. Those who needed the structure of an early touchpoint could schedule one. Nothing was mandated. A few things were protected.

What Supervisors Actually Control

PIs often feel like they have less control over their lab's schedule than they do.

You control when recurring meetings happen. You control whether you send a quick-question Slack at 9 am that costs someone their flow for forty minutes. You control whether your check-ins are scheduled or reactive, predictable or random. You control whether "my door is always open" functions as support or interruption. You control the cultural norms that determine whether leaving at a reasonable hour feels safe, or whether presence is still quietly read as productivity.

These are not small things. They accumulate into an environment — one that either supports concentrated work or one that slowly erodes it without anyone quite intending that outcome.

The Conversation Most Supervisors Haven't Had

There is a question worth asking every trainee, once, early:

When do you do your best thinking — and is anything in your current schedule working against that?

Some trainees have thought about this carefully and can answer immediately. Most haven't been asked and need a moment. A few will give you information that changes how you structure the next six months.

This conversation does not require you to accommodate every preference. Research doesn't run on individual circadian preference alone, and you don't need to pretend otherwise. Department meetings still happen at 2 pm on Mondays. The instrument still books out by 8 am. The constraints are real, and naming them alongside the question is part of having it honestly. But within what can't move, there is almost always more flexibility than a lab's default calendar suggests — and the act of asking signals something important: that output matters more to you than optics, that you understand cognitive work has conditions, and that you are paying attention to the person, not just the deliverable.

That signal, reliably, changes things.

A Note on What This Isn't

This is not a habit about lowering expectations.

Dr. Reyes's trainees did not produce less. They produced more — more cleanly, with less friction, with fewer weeks of grinding that yielded nothing. The standard didn't change. The conditions improved.

This habit also doesn't require a calendar overhaul or a lab-wide policy on protected time. It requires two things: noticing that cognitive timing is real, and making at least a few deliberate choices that reflect that reality.

Some of those choices are structural — where the moveable meetings land, when interruptions are normalized. Some are conversational — asking, once, a question that most people have never been invited to answer. Some are just habitual — pausing before scheduling a 10 am meeting and asking whether this could be an email, a Thursday, or a five-minute conversation that doesn't cost anyone their morning.

You did not get to where you are by treating all hours as equal. You have rhythms, too — windows where you write, windows where you think, windows where you manage and respond and show up.

You learned, probably through accumulated exhaustion, to protect some of those windows.

Your trainees are trying to learn the same thing. The fastest version of that education is a supervisor who already understands it — and builds a lab that doesn't require everyone to figure it out the hard way.

That's not a hack. That's a habit.

✨ Understand the energy level, not just the workload. The GradLab Compass Weekly Capacity Tracker helps one identify peak productivity windows, while the Burnout Early Warning Tracker helps catch early warning signs before burnout takes hold.Check them out here.

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.