A Colleague's Missed Deadlines: What to Do

It’s a common and awkward situation. A colleague you rely on starts missing deadlines, and their delay has a direct knock-on effect on your work, your team, and potentially your learners. Addressing it feels confrontational, but ignoring it can lead to bigger problems and resentment. Approaching the issue constructively is a vital professional skill that strengthens teams and protects quality.

Here is a practical framework for handling these sensitive conversations in a supportive and effective way.

Prepare for the Conversation

Before you say anything, take a moment to prepare. Going into the conversation with clarity and facts, rather than just frustration, is crucial for a positive outcome. A few minutes of preparation prevents the discussion from becoming personal or accusatory.

• Gather specific examples: Identify one or two recent, clear instances where a missed deadline impacted you. For example, 'I couldn't complete the course review report on Tuesday because I was waiting for the assessment data for unit 3'.
• Clarify the impact: Be clear in your own mind what the consequence was. Did it mean you had to work late? Did it delay feedback to learners? Did it cause an issue for an external stakeholder? Knowing the 'so what' makes the conversation purposeful.
• Check your assumptions: Is it possible the deadline was unclear or that an obstacle prevented them from meeting it? Approach the situation with curiosity, not certainty. Assume good intent until proven otherwise.
• Choose the right time and place: Find a private space where you will not be interrupted or overheard. Avoid raising the issue in a team meeting, over email, or when either of you is rushing to the next task.

Frame the Opening Carefully

How you start the conversation sets the tone for everything that follows. Your goal is to open a dialogue, not deliver a verdict. Lead with support and focus on a shared goal, such as ensuring learners get what they need or that a team project runs smoothly.

• Use a supportive opening: Start with a question like, “Is everything okay? I just wanted to check in about the deadline for the X task.” This shows concern for them as a person.
• Use 'I' statements: Centre the conversation on the impact on you and the process. For example, say “I had trouble finalising my part of the report because I was missing your figures,” instead of “You made me late with my report.”
• Stick to specifics: Avoid generalisations like “You always…” or “You never…” These phrases immediately put people on the defensive. Refer to the specific instance you prepared.

Focus on the Problem, Not the Person

Once you have raised the issue, the goal is to move quickly into collaborative problem-solving. This isn't about your colleague's personal failings; it's about a breakdown in a process that you both need to work. By working together, you can find a sustainable solution.

• Listen to their perspective: Ask open questions to understand their situation. Is their workload unmanageable? Is there a technical issue? Was there a miscommunication? Listen without interrupting.
• Brainstorm solutions together: Could the deadline be adjusted? Could the process be simplified? Is there a piece of information they are waiting for from someone else? Could a shared checklist or calendar help?
• Agree on a concrete next step: End the conversation with a clear, simple agreement. For example, “Okay, so for next week, you’ll send me the data by Tuesday lunchtime, and I’ll ping you a reminder on Monday. Does that work?”

Know When to Involve a Manager

A direct, supportive conversation between peers should always be the first step. In most cases, it’s all that is needed. However, if the issue persists and starts to pose a significant risk to quality or learner experience, you may need to escalate it.

• Give the agreed solution time to work: Don't rush to a manager after one conversation. See if the agreed change makes a difference.
• Frame it as a process issue: If you do need to speak to a manager, focus on the impact on the work and the risk to quality. For example, “I’m concerned about our ability to meet the reporting deadlines for learner progress. Can we look at the process to see where the bottleneck is?”
• Avoid personal complaints: The goal of escalation is to protect the quality of the provision and find a systemic solution, not to get a colleague into trouble. Keep your language professional and focused on outcomes.

Where this fits in QualityHero

Effective professional dialogue is the bedrock of a healthy quality culture. When colleagues can resolve process friction constructively, it ensures that the systems underpinning quality improvement run smoothly. Delays in data submission from one colleague can create bottlenecks that affect the accuracy and timeliness of information in course reviews, SARs, and QIPs. By addressing these issues early, teams protect the integrity of the data that feeds into modules like Leadership Reports, ensuring that leaders have a true and current picture of provider performance.