A Conversation About Missed Expectations

You have probably felt it before: a deadline slips, a deliverable comes in below standard, or a teammate's contribution falls short of what was agreed. In a sma

Level: Manager
Setting: Small team
Core skill: Repairing a gap
Common pitfall: Avoiding it until it's big
Practice to try: A fact-first opening

What this looks like in real work

You have probably felt it before: a deadline slips, a deliverable comes in below standard, or a teammate's contribution falls short of what was agreed. In a small team, these gaps are visible and felt quickly. The conversation about missed expectations is the moment you sit down with the person and address the gap directly. It is not about blame; it is about repair. The goal is to understand what happened, agree on what needs to change, and restore trust. In practice, this might look like a project manager who promised a report by Friday but delivered it the following Wednesday without warning. Or a designer who was supposed to collaborate with a colleague but instead worked in isolation, causing rework. These are not catastrophic failures, but they are gaps between what was expected and what occurred. Left unaddressed, they can fester. A conversation about missed expectations is a chance to reset. It is a normal part of managing people, not a sign of failure. In a small team, where everyone relies on each other, these conversations are especially important because the ripple effects of a missed expectation are felt by everyone. The earlier you have them, the easier they are.

Why it trips people up

Many managers avoid these conversations because they fear conflict, worry about damaging relationships, or hope the issue will resolve itself. In a small team, the closeness can make it even harder: you might be friends with the person, or you might worry that bringing up a missed expectation will make you seem petty or overly demanding. There is also the fear of being wrong. What if the expectation was unclear? What if circumstances beyond their control caused the gap? These are valid concerns, but they are reasons to approach the conversation carefully, not to avoid it. Another trip-up is the tendency to wait until the gap is so large that it demands attention. By then, frustration has built up, and the conversation is likely to be more emotional and less productive. The longer you wait, the more you might read into the situation, and the more the other person might feel ambushed. In a small team, avoidance can also create a culture where expectations are vague and accountability is low. People start to guess what is acceptable, and performance drifts. The conversation itself is not the problem; the problem is the buildup of unspoken disappointment.

The mistake that quietly hurts

The most common mistake is avoiding the conversation until the gap becomes too big to ignore. This quiet avoidance might feel like keeping the peace, but it actually erodes trust and performance. When you wait, small misses accumulate. The person may not even realize they are missing expectations because no one has told them clearly. Meanwhile, you might become resentful, and other team members might notice the inconsistency. In a small team, this can lead to a culture of silence where people are unsure where they stand. The damage is not just to the individual; it affects the whole team's ability to rely on each other. Another version of this mistake is addressing the gap indirectly, through hints or sarcasm, which leaves the person confused and defensive. Or you might bring it up in a group setting, which can feel like public shaming. The quiet hurt comes from the gap between what you expect and what you communicate. If you never clearly state the expectation, you cannot fairly hold someone to it. And if you wait until you are frustrated, your delivery may be sharper than intended, making repair harder. The cost of avoidance is often much higher than the cost of a timely, respectful conversation.

A practice you can repeat

One concrete practice to make these conversations easier is the fact-first opening. This means you start the conversation by stating the observable facts, without interpretation or judgment. For example, instead of saying, "You seem disengaged and you're letting the team down," you say, "I noticed that the report was due on Friday, and it was submitted on Wednesday. Can you help me understand what happened?" The fact-first opening does three things: it grounds the conversation in shared reality, it reduces defensiveness, and it invites the other person to explain. To use this practice, prepare by writing down the specific facts: what was expected, what was observed, and when. Avoid words like "always," "never," or "unprofessional." Stick to what a camera would have recorded. Then, open the conversation with those facts and a genuine question. After the person responds, you can move to impact and next steps. This practice is repeatable because it works for any missed expectation, big or small. It also helps you stay calm and curious rather than frustrated. Over time, using a fact-first opening becomes a habit that builds a culture of clarity and early repair. It signals that you are interested in solving the problem, not attacking the person.

What to say and do

When you sit down for the conversation, choose a private setting and a time when neither of you is rushed. Start with a fact-first opening, then pause and listen. Here are a few phrases you can adapt: "I noticed that the client proposal was due on Tuesday, and it was sent on Thursday. What got in the way?" "The expectation was that you would review the code before merging, but I saw it went in without review. Can you walk me through what happened?" "I want to make sure we're on the same page. The deadline for the draft was last Friday, and it came in on Monday. What support do you need to meet the next one?" After you hear their perspective, acknowledge any valid points. Then, restate the expectation clearly and ask what they will do differently. For example: "So going forward, the expectation is that you'll flag any delays as soon as you see them. Does that sound workable?" Agree on a follow-up check-in. Throughout, keep your tone neutral and your body language open. Avoid interrupting or jumping to solutions before they have finished. If the gap was due to unclear expectations on your part, own that. Repair is a two-way street. End by confirming the next step and expressing confidence in their ability to meet it. This turns a difficult moment into a constructive one.

When the stakes get higher

Sometimes a missed expectation is not a one-time slip but a pattern, or it has significant consequences for the team or the work. In those cases, the conversation needs to be more structured and may need to include a clear improvement plan. You might say, "This is the third time this month that the weekly update has been late. I need to understand what's going on, because the team relies on it." At this level, you should document the conversation and the agreed actions. Set specific, measurable expectations and a timeline for review. If the person is defensive or dismissive, you may need to be more direct about the impact: "When the update is late, the rest of the team can't plan their work, and it creates a bottleneck." In a small team, high stakes can also mean that the person's role is critical, and the gap is affecting others' ability to do their jobs. You may need to involve others or adjust responsibilities temporarily. However, even in high-stakes situations, the principles remain: be factual, be clear, and be fair. Avoid making threats or ultimatums in the moment. If the gap continues, you may need to escalate to formal performance management, but that is a separate process. The goal of this conversation is still repair, but with firmer boundaries and closer follow-up. Remember that your role is to support the person in meeting expectations, not just to punish them.

Questions new leaders ask

Q: What if the person gets emotional or cries? A: Stay calm and give them a moment. Acknowledge their feelings without letting the conversation derail. You can say, "I can see this is upsetting. Take a minute. We can work through this together." Then return to the facts and the path forward. Q: How do I know if the expectation was clear enough? A: If you never explicitly stated the expectation, or if it was vague, then it's on you to clarify. In the conversation, ask, "On a scale of one to ten, how clear was the expectation?" and adjust accordingly. Q: What if the person disagrees with my facts? A: Listen to their perspective. If there's a genuine disagreement about what happened, focus on what you can both agree on and what needs to happen next. You might say, "We see this differently. Let's focus on how to prevent it going forward." Q: Should I wait until the next scheduled one-on-one? A: If the gap is small, you can wait, but if it's affecting work or trust, address it sooner. A quick, informal conversation can prevent a bigger issue. Q: What if I'm the one who missed an expectation? A: Own it. A simple "I said I would do X, and I didn't. I'm sorry. Here's how I'll fix it" models accountability for your team.