When leaders assume they’ve been clear, misunderstandings can quietly turn into frustration, resentment, and performance problems.
I’ve had conversations with employees where I walked away believing we were completely aligned on what needed to happen. I explained the assignment, discussed what I thought were the important details, and left feeling confident they understood what I expected. Then the work came back, and it wasn’t what I had envisioned. My first reaction was usually frustration because I couldn’t understand how we had ended up with such different ideas of what success looked like. It took me some time to recognize that just because something was clear in my mind didn’t mean I had made it clear to someone else.
Unspoken expectations at work can create problems long before anyone realizes a misunderstanding exists. Leaders often assume that because they’ve assigned responsibility, they’ve also established clarity. Employees may leave the same conversation with an entirely different understanding of the priorities, deadlines, or quality of work expected. Both people believe they know what needs to happen, and neither recognizes the gap until the result disappoints someone. What begins as a simple misunderstanding can eventually become frustration, resentment, and even a performance issue that might have been avoided.
How Unspoken Expectations at Work Become Performance Problems
One of the challenges of leadership is that our experience can work against us when we’re communicating expectations. The more familiar we become with a task or responsibility, the easier it is to forget how much information we’re carrying around in our heads. We know which details matter, what problems to anticipate, and what a successful result should look like because we’ve been through the process before. But someone who hasn’t had those experiences may not have the same understanding, even when they genuinely want to do a good job.
Think about a manager who asks an employee to prepare a proposal by Friday. The manager expects a complete recommendation with supporting information, accurate numbers, and enough detail to make a decision. The employee understands the assignment as preparing an initial draft for discussion. Friday arrives, and the manager is frustrated because the proposal isn’t ready to present, while the employee is confused because they delivered what they believed was requested. Neither person necessarily failed to put in the effort, but they were working toward two different outcomes.
These misunderstandings happen in smaller ways every day. A leader says something is a priority without explaining how it compares to the other work already assigned. A deadline is established without clarifying whether it means the beginning or end of the day. Someone is given ownership of a project without understanding which decisions they can make independently and which require approval. Each assumption may seem insignificant on its own, but together they create uncertainty that eventually affects performance.
When those gaps continue, the consequences extend beyond a missed deadline or an incomplete assignment. Employees begin feeling that expectations keep changing or that they’re being evaluated against standards they never understood. Leaders become frustrated because they believe they’re repeatedly explaining the same things. Trust begins to weaken as both sides develop their own interpretation of what’s happening. What started as a communication problem can slowly become a relationship problem.
Assigning Responsibility Isn’t the Same as Creating Understanding
I’ve learned that giving someone responsibility for something is only part of the conversation. We can delegate a task, establish a deadline, and identify who’s accountable for the result without ever confirming that we share the same understanding of what success looks like. We may believe we’ve communicated everything necessary because the person nodded, agreed, or said they understood. But agreement in the moment doesn’t always mean alignment on the outcome.
Creating shared understanding requires us to move beyond simply telling someone what needs to happen. We need to explain why the work matters, what the finished result should accomplish, and where the person has the freedom to make decisions. We also need to understand how they interpret the assignment, what obstacles they anticipate, and whether they believe the expectations are realistic. That conversation takes more time initially, but it can prevent considerably more time being spent correcting misunderstandings later.
I also think leaders sometimes confuse clarity with giving people detailed instructions for every step. Those aren’t necessarily the same thing. We can be clear about the outcome, the standards, and the boundaries while still allowing someone to determine how they’ll accomplish the work. In fact, when people understand what success looks like and why it matters, they’re often better positioned to make decisions and take ownership without needing constant direction.
This is one reason I’ve come to appreciate leading with curiosity before offering advice. When we ask someone how they plan to approach an assignment, what they believe the priorities are, or what support they might need, we learn something about their understanding that we wouldn’t discover by continuing to explain our own. We also give them an opportunity to identify concerns or offer a better approach. Clarity becomes something we develop together rather than something we assume we’ve delivered.
Why Leaders Need to Examine Their Assumptions Before Judging Performance
One of the more difficult lessons I’ve learned is how quickly frustration can influence the way we judge someone else’s performance. When an employee doesn’t deliver what we expected, our minds naturally begin searching for an explanation. We may assume they weren’t paying attention, didn’t take the assignment seriously, or simply failed to follow through. Sometimes those explanations are accurate, but I’ve also experienced situations where my initial judgment turned out to be based on an expectation I had never clearly communicated.
The Stoics understood how much our judgments influence our reactions to events. Epictetus taught that we are disturbed not simply by events themselves, but by the opinions we form about them. I’ve found that idea particularly useful in leadership because our first interpretation of a situation often feels like the truth, especially when we’re frustrated. If I believe someone ignored my instructions, I’m likely to approach the conversation differently than if I recognize the possibility that we misunderstood each other.
That doesn’t mean we should avoid holding people accountable or assume every missed expectation is a communication failure. Employees have a responsibility to ask questions, communicate obstacles, and follow through on the commitments they’ve accepted. There are times when expectations were clear, the necessary support was available, and someone simply didn’t deliver. Those situations require direct conversations about performance and accountability. But I believe we make better decisions when we understand what actually happened before deciding why it happened.
I’ve found it helpful to separate the observable facts from the assumptions I’m making about them. If a report was due at noon and wasn’t delivered, that’s something we can establish. Whether the person was careless, overwhelmed, confused, or dealing with an unexpected obstacle requires a conversation. Approaching that conversation with curiosity doesn’t weaken accountability. It gives us a better chance of addressing the actual problem instead of reacting to the explanation we’ve already created in our minds.
This is also where the difference between blame and accountability becomes important. Blame often focuses on identifying who’s at fault, while accountability requires understanding what happened, accepting responsibility, and determining what needs to change. Sometimes the employee needs to improve their follow-through, and sometimes the leader needs to communicate more clearly. There may also be situations where both have something to own. The goal should be to understand the failure well enough to prevent it from becoming a recurring problem.
How to Set Clear Expectations Without Micromanaging
When I think about improving communication, I don’t believe the answer is creating longer instructions or adding more oversight to everything we delegate. Most people don’t need someone constantly telling them how to do their jobs. They need enough clarity to make good decisions, understand the standards they’re expected to meet, and recognize when something requires additional communication. The challenge for leaders is learning to provide that clarity without taking away the ownership we’re trying to develop.
One practice I’ve found useful is spending more time discussing the outcome rather than simply describing the task. Instead of telling someone to prepare a proposal, I can explain what decision the proposal needs to support, what information should be included, and how the finished work will be evaluated. We can discuss the deadline, any important milestones, and which decisions they have the authority to make. These conversations help establish expectations while still leaving room for the person to determine the best way to accomplish the work.
I also try to make room for the other person’s perspective before the conversation ends. Asking how they understand the assignment or what they see as the biggest challenge can reveal differences that weren’t obvious when I was doing all the talking. Sometimes they identify a problem I hadn’t considered or explain why the timeline may be unrealistic. Other times, their response confirms that we’re aligned and gives both of us greater confidence moving forward. The purpose isn’t to test whether someone was listening, but to make sure we’re working from the same understanding.
Follow-up is another part of establishing clarity that leaders sometimes overlook. Expectations aren’t always something we can communicate once and assume will remain unchanged. Priorities shift, new information becomes available, and unexpected challenges arise. A brief conversation during the work can help identify those changes before they create larger problems. When follow-up is approached as an opportunity to provide support and maintain alignment rather than simply check on progress, it can strengthen ownership instead of undermining it.
Of course, clarity also requires consistency after the work is completed. If we establish expectations but fail to address missed commitments, those expectations gradually lose their meaning. People need to know that agreements matter and that accountability will follow when commitments aren’t met. At the same time, leaders have to be willing to acknowledge when their own communication contributed to the problem. We can’t reasonably expect people to take ownership of their responsibilities if we’re unwilling to do the same.
Better Communication Begins With Better Awareness
I don’t think leaders intentionally leave expectations unspoken. Most of the time, we genuinely believe we’ve communicated what someone needs to know. The problem is that we’re often unaware of how much we’re assuming the other person already understands. Our experience, familiarity, and perspective make certain things seem obvious to us, even when they may not be obvious to anyone else.
The longer I lead people, the more I recognize that effective communication requires more than explaining what I want. It requires understanding what someone else heard, what they believe success looks like, and whether we’ve established an agreement we can both reasonably expect to be honored. That doesn’t eliminate misunderstandings or guarantee that everyone will meet their commitments, but it creates a stronger foundation for both performance and accountability.
The next time someone doesn’t meet an expectation, I want to be willing to examine my own assumptions before reaching a conclusion about their performance. I can still address the missed commitment, ask difficult questions, and hold people accountable for the results. But I also need to consider whether I gave them the clarity they needed to succeed. Sometimes the most useful improvement we can make as leaders begins with recognizing what we thought we communicated but never actually said.