“Please handle it.” “Do a better job.” “Keep me posted.” Leaders say those things every day, usually with good intentions. The problem is that none of them tells a person what success actually looks like.
When expectations stay in a leader’s head, employees have to guess. They may work hard, make a reasonable choice, and still miss the mark because the standard, deadline, or decision boundary was never made clear. Then the leader feels frustrated, the employee feels blindsided, and the next conversation gets harder than it needed to be.
Clear expectations are not a script for controlling people. They are a fair agreement about the work. They give a capable person room to use judgment while making sure everyone knows the result, the guardrails, and the next point of contact.
The Center for Creative Leadership’s guidance on setting expectations makes the same practical distinction: people need a shared understanding of the work, not a vague request they have to interpret alone. Use the five parts below to make that understanding visible before a small miss becomes a larger problem.
Why Good People Miss Vague Expectations
Most supervisors do not set out to be unclear. They are moving fast. They already know how the work should be done. They have said something similar before. From their side of the conversation, it can feel obvious.
But experience changes what you can see. A supervisor may hear “finish the client follow-up” and mean complete the calls, update the record, flag anything urgent, and leave the next shift a usable handoff. An employee may hear “make the calls.” Both people leave believing they agree until the deadline arrives and one of them discovers that their version of complete was different.
That is why clarity is an act of respect. It gives someone a real chance to succeed, raise a concern early, or ask for what they need. It also gives you something specific to return to later, which makes feedback fairer and less personal. The article Clear Is Kind is a useful companion when you need to say the hard part of an expectation without making someone small.
1. Name the Result, Not Just the Activity
Start with what needs to be true when the work is done. An activity is something a person does. A result is the condition the work is meant to create.
“Call the client” is an activity. “By 2:00, the client has a confirmed appointment, the record is updated, and the evening team can see any concern that needs follow-up” is a result. The second version makes the purpose, finish line, and impact much easier to see.
This does not mean every task needs a speech. It means you should add enough detail for the person closest to the work to make good decisions without coming back to you for every step. Try: “The goal is a clean handoff for the next shift. What do you think needs to be complete for that to happen?” Their answer will show you whether the expectation is usable or still too vague.
2. Make the Standard Visible
People cannot meet a standard they cannot picture. “Be professional,” “make it thorough,” and “use good judgment” may sound clear to the person saying them, but they can mean five different things to five different people.
Translate the standard into observable details. What has to be included? What is nonnegotiable? What does a good handoff look like? What is one example of work you want repeated? This is especially important with newer employees, changing processes, safety-sensitive work, and assignments that cross shifts or departments.
A supervisor might say, “A complete handoff includes the client status, what you tried, what still needs attention, and anything that could affect safety. If you are unsure whether something belongs in the note, put it in and ask me during the huddle.” That gives the employee a usable test instead of a vague warning to be careful.
The guide on showing what good looks like can help when words alone are not enough. A real example, a completed checklist, or a brief demonstration is often more useful than repeating the same instruction louder.
3. Be Clear About Ownership and Decision Boundaries
One of the fastest ways to create confusion is to assign a task without saying who owns the decision. Employees may wait for permission because they do not want to overstep. Leaders may assume someone will act because they thought the assignment was obvious. Then the work stalls in the gap.
Name the owner directly: “You are responsible for getting the schedule confirmed.” Then name the decisions they can make: “You can move the times within the available blocks. Bring me in if a client needs an exception or if there is no workable option.”
That balance matters. If you only give the task, people can feel exposed. If you tell them every move, you become the bottleneck. Strong expectations make the handoff clear and leave room for judgment inside the right boundaries.
Gallup’s manager development guidance connects clear expectations, ongoing coaching, and accountability. Those habits work together. A leader cannot expect ownership while holding every decision too tightly, and a person cannot responsibly own work without knowing where their authority begins and ends.
4. Ask What Support Will Make Success Realistic
A clear expectation is not a demand to make the impossible happen. If someone lacks information, time, access, training, or help from another team, the expectation may be perfectly clear and still not be realistic.
Ask one direct question before the work starts: “What could get in the way of this?” The answer may reveal a problem you can solve before it becomes an excuse after the fact. It also tells your team that raising a risk early is part of doing the work well, not a sign that they are failing.
Be specific about the support you are offering. “I will be available” is too loose. “Send me the draft by noon, and I will turn comments around before your 3:00 meeting” is support someone can plan around. “If the system is down for more than fifteen minutes, call me so we can decide how to document the work” gives a person a clear escalation path.
Holding a standard does not mean ignoring the conditions around the work. It means understanding them well enough to decide whether the person needs coaching, a resource, a process change, or a more direct response. The Fix the Process, Not the Person Dispatch is a useful check when the same miss keeps showing up across capable people.
5. Agree on the Follow-Up Before Anyone Walks Away
“Keep me posted” is not a follow-up plan. It leaves the employee guessing when to update you and leaves you guessing whether you are checking too early or too late. That uncertainty can feel like hovering to one person and abandonment to another.
Decide together when you will reconnect and what you will review. It may be a two-minute check at the end of a shift, a message after a client visit, a quick review of a completed work order, or a standing conversation each Friday. The format matters less than the agreement.
Match the follow-up to the work. A new employee, a safety concern, a hard deadline, or an unfamiliar task needs closer contact. A capable person doing familiar work usually needs more room. Consistency does not mean identical treatment. It means people understand why the check-in fits the work and know what will happen next.
The U.S. Office of Personnel Management’s performance-management guidance also treats planning, monitoring, and feedback as connected parts of the work. The same idea applies on a busy frontline team: an expectation is not finished when you say it. It stays alive through the next check-in.
When the Expectation Is Missed
Even a clear agreement can be missed. Do not begin by deciding that the employee did not care. Return to the work and get the information you need.
- Restate the agreement. “We agreed the client notes would be complete before the shift change.”
- Name the impact. “They were not complete, so the evening team had to reconstruct what happened.”
- Ask what got in the way. “Walk me through what made that difficult today.”
- Decide the repair. “Finish these two notes by 4:00, and tell me by 3:30 if you hit another barrier.”
- Set the next check-in. “We will look at the handoff process tomorrow and decide what needs to change.”
This conversation keeps the focus on the agreement, not the person’s identity. It also helps you sort the cause. A skill gap needs coaching. A resource problem needs support. A recurring process failure may need a better system. A repeated choice to ignore a clear expectation may need a firmer response. Those are not the same problem, and they should not receive the same leadership response.
For a single high-stakes conversation, use the hard conversation checklist to prepare the facts, the impact, and the next question before frustration takes over. For a broader approach to follow-through, Accountability in Leadership offers a practical framework for leaders who want to hold a fair standard without slipping into micromanagement.
How Muddy Boots Leadership Helps
Clear expectations sound simple until leaders have to use them in a busy week, across different personalities, changing priorities, and real consequences. That is where practice matters.
Muddy Boots Leadership helps frontline supervisors build a shared way to set expectations, coach through obstacles, address misses fairly, and follow through without becoming the bottleneck. Supervisor training programs give new and developing leaders a practical place to rehearse these moments. Leadership development consulting helps organizations turn the same habits into dependable team routines.
Try This Week
Choose one recurring assignment that has been producing too many follow-up questions, missed details, or last-minute surprises. Before the next handoff, say five things out loud: the result, the standard, the owner, the support available, and when you will reconnect.
Then ask the person to tell you what they heard. That one step will show you whether the expectation is truly clear or only clear in your own head.
Frequently Asked Questions
What should a manager include when setting expectations?
Cover the outcome, the quality or guardrails that matter, who owns the work, what support is available, and when you will reconnect. The employee should be able to describe the agreement in their own words before the conversation ends.
How do you set expectations without micromanaging?
Be clear about the result, boundaries, decision rights, and follow-up point, then leave room for the person to use judgment in the work. Micromanagement controls each step. A clear expectation gives people a destination and the support to reach it.
What do you do when an employee does not meet expectations?
Return to the original agreement, name the gap and its impact, ask what got in the way, and decide the repair and next check-in. Do not jump straight to a character judgment. You may find a skill, resource, process, or clarity problem that needs a different response.
How often should a supervisor review expectations?
Review them whenever work changes, a task carries meaningful risk, a new person is learning the role, or a pattern shows that the original agreement was not usable. For routine work, a brief check-in at the agreed time is usually enough.
