A deadline passes. Then another. You mentioned it once, assumed it was understood, and moved on to the dozen other things competing for your attention. Yet you find yourself increasingly frustrated… 

There may not be a hard due date for this manuscript, but you want it out sooner rather than later. 

Or, your graduate student needs to submit their dissertation by a specific date, and you can see how your time to review their chapters is getting more and more compressed because drafts are not making their way to you. 

Or, you are thinking four steps ahead on a key project, and your postdoc doesn’t seem to see the same urgency in making progress. You thought this experiment or analysis would be done by now. 

Why can’t they just stick to the timeline you gave? 

Missed deadlines and the attending frustrations are a common challenge PIs face. It’s easy to default to “the student just doesn’t care enough” or “maybe this person is lazy”. Yet, there are many different reasons that deadlines come and go without progress (for proof, check your own work: how often do you shift self-imposed deadlines or delay others’ requests that seem either more flexible or less important than your other tasks?). Let’s inspect how shifts in leadership approaches can make a difference here.  

Challenge 1: The Missed Deadline

Before addressing a missed deadline, it helps to get curious about what caused it. The reason can inform your response.

Sometimes the task was underestimated: by you, by the trainee, or both. Sometimes competing priorities pulled attention elsewhere, and nothing was communicated. Sometimes the trainee got stuck, didn’t know how to ask for help, and hoped the delay might go unnoticed. And sometimes the deadline itself was never really firm to begin with: a date mentioned in passing during a group meeting, a soft “let’s aim for” that was never written down or justified. Trainees take their cues from how leaders talk about time, and if “soon” and “by next week” are used interchangeably, it becomes hard to tell which dates actually matter.

A conversation that starts with “Walk me through what happened” uncovers more than one that starts with “This was due Friday.” The first invites an honest account. The second invites a defense.

The goal isn’t to excuse missed deadlines. Reliability matters, and trainees need to build it. The goal is to diagnose accurately before you respond, so that the actual underlying problem gets resolved. A trainee who underestimated the task needs help scoping. One who got stuck and needs an easier and/or safer way to flag trouble early. One who didn’t take the deadline seriously needs a clearer conversation about expectations and consequences. 

And if you find the deadline was never really concrete in the first place, the fix starts with you. Explain why the deadline exists, because sometimes, to them, it can just feel arbitrary. Maybe they don’t realize that the piece of data you’re waiting on is crucial to your next grant proposal or that meeting with a collaborator.  Note the deadline somewhere (e.g., your project management system, or have them email it to you), confirm with the trainee that it is realistic, and check in proactively. Note, this does not mean to “micromanage” the task. Instead, it opens the opportunity to identify obstacles early, when they might still be overcome without negatively impacting the outcome.

Challenge 2: Work That Meets the Deadline but Not the Bar

Sometimes a team member might complete the task on time, yet the product doesn’t meet the expectation. For example, an analysis is technically complete but misses the point of the question. The draft includes all of the required sections but reads like a first pass, not a final one. This is a different problem than a missed deadline, but PIs sometimes respond to it the same way, with a vague “this needs more work,” which leaves the trainee no clearer on what “more” means.

Unmet expectations often trace back to one of a few sources: the group member doesn’t yet have a clear picture of what “good” or “acceptable” looks like for this particular task; they ran out of time and submitted something incomplete or rushed rather than miss the deadline or they genuinely believe the work meets the bar and the gap is one of standards, not effort.

Specific feedback closes that gap faster than general feedback. “The methods section is missing the control comparison we discussed, and the discussion doesn’t yet address the alternative explanation,” gives a trainee something to act on. “This isn’t there yet” doesn’t. Where possible, showing an example of work that does meet the bar, an old figure, a well-scoped abstract, teaches faster than describing the bar in the abstract. 

Whether it comes to writing, experiments, or analyses, consider working side-by-side with them and explaining both your process and how you know you’ve reached the desired outcome. If you think you have sufficiently explained and they’re still not “getting it,” use your curiosity again: “I’ve demonstrated my process and what success looks like, and we still need to get closer to that outcome. What do you think might be causing the misalignment here?”

Challenge 3: The Trainee Who Resists Feedback

Some group members will take feedback well and adjust accordingly. Others meet every comment with an explanation for why the current situation is fine, or they just stick with their original approach after appearing to agree with you in the moment.

This is often mistaken for stubbornness, but it’s frequently something else: someone who has invested a great deal in an approach can experience feedback on it as a threat rather than as help, especially early in a project when their confidence in their own judgment is still forming. Defensiveness could be a symptom of that anxiety, not evidence that the person is uncoachable.

Separating the critique from the person helps here, as does asking questions before offering the fix: “What was the thinking behind this approach?” could reveal a piece of context you were missing, or show a gap in understanding you can address directly. It’s also worth distinguishing between a trainee who wants to understand the reasoning behind feedback and one who is negotiating to avoid changing anything. The first deserves the full explanation. The second needs a clearer statement of what has to change and why it isn’t optional. 

What can be challenging for PIs, especially early in building your own career, is that sometimes the best step is to allow the trainee to experience the natural consequences of their choices. Getting tough reviewer critiques, missing that conference submission deadline, or running into dead ends with their projects can be powerful lessons that shape their future choices. Yet, for the PI, this means accepting some risks or losses; after all, your name is likely also on the author line, or your resources are going down the drain with the delays or failed analyses. Try to find opportunities for natural consequences that minimize impacts on yourself or others on your team.

Challenge 4: Uneven Effort Among Trainees

In any group, some trainees consistently go above and beyond, and others do the minimum required to get by. Left unaddressed, this dynamic tends to resolve itself in the worst possible direction: your most reliable people absorb the slack, resentment builds, and eventually the strongest performers start wondering why they bother.

PIs often hesitate to address this head-on because it can feel like comparing people, which is uncomfortable, or like criticizing effort, which is hard to quantify. But the cost of staying silent is higher than the cost of the conversation. A trainee coasting through a project rarely realizes how visible that is, or how much it’s affecting the people around them.

How to approach this? Start from expectation rather than comparison. Saying, “Here’s what I’d expect from someone at this stage on a project like this,” sets a standard without bringing in anyone else’s performance. That comparison can be further demotivating or even set up interpersonal conflicts. 

And it’s worth checking, before assuming laziness, whether the trainee understands what’s expected, has the bandwidth to deliver it, or is disengaged for other reasons, such as a personal circumstance or a loss of autonomy, confidence, or progress that is demotivating them. 

The Remaining Challenge: Your Own Patterns

As with most recurring leadership issues, it’s worth turning the lens back on yourself before assuming the problem sits entirely with your trainees.

A few questions worth revisiting periodically:

• Are my deadlines and expectations realistic, or am I operating from my own pace and processes rather than theirs?
• How have I confirmed that my team member and I have communicated effectively around the timeline and expectations?
• Do I consistently follow up on deadlines and on feedback, or only when something has already gone wrong?
• Have I made it easy for someone to tell me they’re behind or struggling before it becomes visible in their work?
• Am I addressing a pattern, whether it’s a missed date, uneven effort, or feedback that isn’t addressed the first time I notice it, or waiting until it’s happened three or four times?
• Do I constantly set deadlines and move them, making it seem like the deadlines aren’t real?

Building the Habits

Handling these challenges well is less about any single conversation and more about the habits built around them.

1. Make expectations explicit and shared. Deadlines, quality standards, and what “good” looks like should be demonstrated to the trainee, written down, confirmed with the trainee through both communication and observation, and revisited before they matter, not just after.
2. Build in regular, low-stakes checkpoints. Frequent small check-ins surface scoping problems, quality gaps, and disengagement earlier than infrequent large ones, and they don’t require heavy oversight to work.
3. Diagnose before you respond. A missed deadline, below-expectation work, defensiveness, or coasting can each stem from different causes, capacity, clarity, confidence, or motivation, and each calls for a different fix. Don’t reach for the same response every time. Also, what helps one trainee might not help another.

The Bigger Picture

Much like yourself, your team members won’t meet every deadline. Yet, most of us feel a sense of accomplishment when we make even small amounts of progress, and setting deadlines can help us make regular progress. How we communicate the deadline, its importance, and flexibility matters. How we respond when progress stalls or deadlines pass unmet also matters. The good news is that these are skills we can practice and refine so that we become adept at spotting the underlying issues and adjusting before those issues grow. As with many leadership qualities, communication and modeling are important ways to help our team members understand expectations and adapt their behaviors to meet them.

For more on building a group culture where these conversations come easily, see How Successful PIs Build (and Repair) Research Group Culture and Tackling the Tough Conversations: Guidance for PIs Who Keep Putting Them Off.