Introduction
“Be more proactive.” “Own the project.” “Take more initiative.” These phrases sound like expectations, but they’re really feelings — vague enough that two different people could interpret them two different ways, and specific enough to sound like clear direction. Most performance problems that get labeled as attitude or skill issues are actually expectation-setting problems in disguise.
The Three Components of an Expectation That Actually Works
- A specific, observable outcome. Not a trait or attitude, but something someone could point to and confirm did or didn’t happen. “Send the weekly client update by Friday at noon” is observable. “Communicate better with clients” is not.
- A timeframe. An expectation without a deadline is a wish, not a commitment — and wishes don’t create accountability.
- The reasoning behind it. People follow expectations they understand far more consistently and durably than ones handed down without context. A brief explanation of why something matters dramatically improves follow-through.
The Simple Test for Whether an Expectation Is Clear Enough
Imagine two different people on your team receiving the same instruction. Would they interpret it the same way and produce comparably similar results? If not, the expectation needs to be more specific — not because your team lacks judgment, but because ambiguous instructions force people to guess, and different people guess differently.
Common Mistakes in Setting Expectations
- Confusing your own mental clarity with communicated clarity. An expectation can feel completely clear to the manager who’s been thinking about it for days and still land ambiguously for someone hearing it for the first time.
- Setting the expectation once and assuming it will stick. Especially for new or unusual expectations, a single mention often isn’t enough — reinforcing it in the following 1:1 or check-in meaningfully improves follow-through.
- Skipping the “why.” Managers under time pressure often skip the reasoning to save time, which actually costs more time later when the expectation is misunderstood or under-prioritized.
- Setting expectations only around outcomes, never around standards. Two people can hit the same outcome through very different levels of quality or thoroughness — if that matters, it needs to be part of the expectation.
A Practical Framework for Setting Any Expectation
- State the specific, observable outcome you need
- Attach a clear timeframe
- Explain briefly why it matters
- Ask the person to restate it in their own words — this single step catches most misunderstandings before they become problems
- Follow up at a natural checkpoint, not just at the deadline
Frequently Asked Questions
Won’t overly specific expectations feel like micromanagement?
Specificity about the outcome and the reasoning is different from specifying exactly how the work gets done — the latter is what tends to feel like micromanagement. Clear expectations about what and why , paired with real autonomy over how , are generally well received.
How do I set expectations for ambiguous or creative work that doesn’t have a clear observable outcome?
Even ambiguous work benefits from defining what “done well” would look like as specifically as possible, along with a clear checkpoint for feedback partway through — this reduces the risk of significant misalignment being discovered only at the end.
What if someone consistently doesn’t meet a clearly stated expectation?
At that point, the issue has usually moved from clarity to either a skill gap or a genuine performance or accountability conversation — worth revisiting after confirming the expectation itself was actually clear and understood.
Related Learning Path
Management Foundations
Three courses that build the mindset, expectations, and operating discipline required to lead people well.
View This Learning Path →