Agreements vs. Expectations

An expectation is something you want. An agreement is something you both said yes to. Most accountability conversations are actually arguments about which one was in play.

WHAT IT IS

An expectation lives in your head. It may be completely reasonable, even obvious to you. But until it's been spoken and confirmed, it belongs to you alone. An agreement lives between two people. Both parties understand what's expected, and what happens if it isn't met.

Most accountability breakdowns aren't failures of follow-through. They're failures of agreement. The leader had an expectation. The other person had a different understanding. Neither had the conversation that would have surfaced that.

01 Assumed

02 Stated

03 Agreed

One sided. Never spoken. The leader believes it's obvious. The other person has no idea it exists.

"I thought everyone knew we don't miss Mondays."

Said out loud, once, without confirmation. The other person heard words. They may have understood something different.

"I told them it was a priority."

Both parties understand what's expected, what meeting it looks like, and what the consequence is if it isn't met. This is the only level that creates real accountability.

"We're aligned — first draft by Thursday, you'll flag me if anything shifts."

WHY LEADERS DEFAULT TO EXPECTATIONS

Agreements take time. They require a conversation, confirmation, and sometimes negotiation. Expectations feel more efficient: communicate it once and move on. The problem is that efficiency at the front end tends to create rework, conflict, and frustration at the back end.

Research on role clarity links ambiguity to lower performance and higher stress, findings that have held across decades of organizational research. Kahn and colleagues identified role ambiguity as a significant source of workplace stress as early as 1964. Most leaders are solving the problem at the wrong end.

WHAT IT COSTS

When accountability conversations happen without a prior agreement, they tend to feel unfair to the person being held accountable. And they are unfair. You can't hold someone accountable to a standard they didn't agree to. You can express disappointment. But accountability requires a prior commitment, and a commitment requires a conversation.

The repeated pattern of unspoken expectation, missed standard, and frustrating conversation tends to erode trust on both sides. The leader loses confidence in the person. The person loses confidence in the leader's fairness. The agreement was missing from the beginning.

ONE THING TO PRACTICE

Close the loop out loud.

At the end of any conversation where you're counting on someone to do something, ask: "What's your understanding of what we've agreed to?"

Not as a test but as a genuine check. What comes back will tell you whether you have a Level 3 agreement or a Level 2 statement. If the answer surprises you, you've just saved yourself a hard conversation down the road and you can have the clarifying one now, while it's still easy.

Common Questions

What's the difference between an expectation and an agreement at work?

An expectation is something you want from someone that you haven't actually said out loud or gotten their buy-in on. An agreement is something you've both talked through, both committed to, and both understand clearly. The reason this distinction matters is that people tend to keep agreements and resist expectations. Not because they're difficult, but because expectations put all the weight on one side. Both people had a say in it, so both people feel ownership over it.

Why do employees resist expectations but keep agreements?

Expectations feel like demands dropped from above. Even reasonable ones. When you tell someone what you expect of them, the implicit message is that your standards are the ones that matter, and their job is to meet them. Agreements flip that. Both people contribute to what the commitment looks like, which means the person on the receiving end isn't just complying, they're keeping their word. Built together, kept together. That's a completely different internal experience, and it shows up in the behavior. People honor commitments they made. They comply with, and often quietly resist, demands they received.

How do you turn an expectation into an agreement?

Say it out loud and ask if they can commit to it. That's most of it. "I need the weekly report by Thursday morning. Does that work for you, and is there anything you'd need from me to make that happen?" The key is that last part: asking what they need from you. An agreement is a two-way thing. If they can't meet the expectation as stated, now you find out why before it becomes a problem, not after. If they can, you have a real commitment instead of an assumed one.

What happens when expectations go unstated on a team?

They become invisible standards that people get judged against without knowing the game they're playing. The organizational psychologist William Schutz put it well: unexpressed expectations are premeditated resentments. The leader is disappointed. The employee is blindsided. And the conversation that follows, if it happens at all, starts with a deficit of trust on both sides because the employee had no idea the expectation existed. Most accountability problems I see on leadership teams aren't performance problems. They're clarity problems that nobody named.