Habit, Not Hack: Estimating Time Honestly (Mentor)

The timelines in your lab are only as honest as the culture you've built around them.

Dr. Singh noticed the pattern early.

Deadlines were missed — not dramatically, not with any single catastrophic failure, but consistently. Timelines slipped by days, then weeks. Projects that were almost done stayed almost done for longer than almost done should last. Everyone sounded busy. No one sounded surprised.

She sat with that last part for a while. If nobody was surprised, the slippage wasn't unexpected. Which meant everyone had known, at some level, that the timeline wasn't real — and had said it anyway.

The System She Had Built Without Meaning To

Dr. Singh's first instinct was to address the trainees. Better planning. More realistic commitments. More accountability around deadlines.

But the more she looked at it, the more she recognized something uncomfortable.

Her trainees weren't bad at time management. They were bad at estimating — and she had spent months inadvertently teaching them to be.

The evidence was in her own meeting notes. When a trainee gave a short timeline, the conversation moved forward. When a trainee gave a longer one, she asked questions. Is that really how long it will take? What's the rate-limiting step? Can we tighten that up? Not aggressively — she wasn't demanding the impossible. But the questions themselves carried a signal: shorter is better, longer requires justification, confidence means committing to something fast.

Her trainees were smart. They learned quickly.

So they gave short timelines. And then they missed them. And the cycle repeated, and Dr. Singh had been diagnosing it as an execution problem when it was actually a culture problem — one she had created.

The Habit: Ask for Honest Estimates, Not Comfortable Ones

Dr. Singh stopped asking the question that had been generating the wrong answers.

She had been asking: "When will this be done?"

That question, in the culture she had built, produced an estimate designed to satisfy rather than inform. It invited the trainee to say whatever sounded acceptable rather than whatever was accurate. So she replaced it with questions that couldn't be answered optimistically by reflex:

"What assumptions does that timeline rely on?"

"What usually goes wrong with this kind of experiment — and have you built time for that?"

"What's your range? What's the fastest realistic scenario, and what's the more likely one?"

These questions did something the original question couldn't: they made the assumptions visible. And once assumptions were visible, they could be examined — by the trainee, by Dr. Singh, together — rather than buried inside a number that sounded confident but wasn't grounded in anything.

Making Room for Uncertainty

Dr. Singh also changed the language she modeled.

She started saying, in meetings where she was asked about her own timelines for grant submissions, paper revisions, feedback turnarounds: "My best estimate is X, but that assumes Y. If Y doesn't hold, add another week."

She said out loud, more than once: "It's okay to say you don't know yet. That's more useful than a number you're not confident in."

She introduced range estimates as the standard format. Not "three weeks" but "two to four weeks, depending on whether the first run works." Not a single date but a window with an explicit condition attached.

The lab initially found this mildly uncomfortable — ranges felt less decisive than single dates, and there was a residual sense that uncertainty was something to be hidden rather than named. That discomfort faded quickly. What replaced it was something that felt better: a shared understanding that the estimates meant something, because they were trying to be accurate rather than acceptable.

What Shifted

The first thing that changed was the quality of the information in meetings.

Instead of a series of dates that everyone knew might slip, Dr. Singh had ranges with conditions. She could plan around them. She could identify in advance which projects were most likely to need more time and why, and she could make decisions about resources and sequencing accordingly. The planning became real rather than aspirational.

The second thing that changed was the relationship between trainees and accountability.

When a trainee gave a range and hit the longer end of it, that wasn't a failure — it was accuracy. When they hit the shorter end, it was a genuine win. The goalposts were honest, which meant performance against them was legible in a way it hadn't been before.

Fewer surprises. Better planning. Less of the quiet, low-grade panic of a lab where everyone knows the timelines are fiction but no one says so.

"I've noticed our planning has gotten more reliable," one postdoc told her. "I think it's because I actually believe the timelines now."

What This Habit Asks of You

You don't have to redesign your entire meeting structure. You need to change two things: the questions you ask, and what you praise.

Change the question. Replace "when will this be done?" with "what does that timeline assume?" and "what's your range?" These questions signal that you want accurate information, not reassuring information. Over time, your trainees will start generating accurate information by default, because that's what the environment rewards.

Change what you praise. When a trainee gives you a conservative estimate that turns out to be right, name it explicitly. "You said four weeks, it took four weeks — that's exactly the kind of planning I want to see." When a trainee says "I don't know yet, I need another week to assess" rather than inventing a number, acknowledge that as the professional behavior it is. The culture in your lab is built from what you respond to, not just what you say.

Model it yourself. When you are asked for timelines — by collaborators, department chairs, your trainees — give ranges with stated assumptions. Demonstrate that uncertainty named out loud is not weakness. It is precision.

A Note on What This Isn't

This is not a habit about accepting slow timelines or removing accountability from your lab. Dr. Singh's lab did not become a place where any estimate was acceptable as long as it was wide enough. Deadlines still mattered. Commitments still meant something.

What changed was that the commitments were real — grounded in actual conditions rather than in what the trainee calculated you wanted to hear. A deadline that has been honestly estimated and then missed is a problem worth investigating. A deadline that was never honest to begin with is just a different kind of fiction, and holding people accountable to fiction is not the same as holding them to a standard.

Trust isn't built by finishing early. It's built by finishing when you said you would — and that only happens when the original estimate was true.

The timelines your trainees give you are shaped by what they believe you want to hear. If you have been rewarding optimism and questioning conservatism, you have built a lab where honest estimation feels risky. That is worth knowing — because it's also entirely within your power to change.

Ask better questions. Praise accuracy. Model uncertainty.

The reliable information will follow.

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

✨ Sustainable productivity starts with being honest about available time. The Invisible Work Planner, Weekly Capacity Planner, help uncover hidden demands, assess real capacity, and create plans that reflect actual working conditions—not idealized ones. Click on each tool to explore.