What Happened
Businesses are paying closer attention to how managers communicate expectations to their teams. The conversation centers on a familiar problem: employees underperform not because they lack skill, but because nobody told them clearly what "good" looks like. The gap between what leaders think they communicated and what employees actually heard is costing companies real money and real morale.
The Communication Angle
Here is the question worth asking: If your employee missed the mark, did they fail, or did you?
Most managers believe they set clear expectations. They held the meeting. They sent the email. They explained the project. And yet the work comes back wrong, the deadline gets missed, or the behavior continues. The problem is not effort. The problem is that "clear" is not a feeling you have when you speak. It is a condition that exists only when the other person can repeat back exactly what you meant.
This is where managers make the fatal mistake. They confuse talking with communicating. Talking is output. Communicating is a two-way transfer where something actually lands. When you tell someone "I need this done well and on time," you have talked. You have not communicated. "Done well" means seventeen different things to seventeen different people.
The fix is specific and it is not complicated. You anchor expectations to observable behaviors and concrete outcomes. Not "be professional in client meetings." Instead: "In client meetings, you speak only after the client finishes, you offer one solution per problem raised, and you follow up with a written summary within 24 hours." Now there is no room for interpretation. The employee knows exactly what success looks like before they walk into that room.
There is a second layer that most managers skip entirely: the confirmation loop. After you set the expectation, you ask the employee to tell you what they heard. Not "do you understand?" because every human being on earth will say yes to that question whether they understood or not. You ask: "Walk me through how you would handle this." That response tells you everything. If they get it right, you are aligned. If they get it wrong, you just saved yourself a missed deadline and a difficult follow-up conversation.
This is exactly the kind of scenario I break down in Say It Right Every Time. The chapter on precision language gives you a framework for stripping vague instructions down to their concrete core, so that what you say and what gets done are finally the same thing. The tools in that chapter work whether you are setting expectations with a new hire or resetting them with someone who has been doing the job for years.
Never Be Lost
for Words Again
Get word‑for‑word scripts for the conversations that shape your life, from job interviews and negotiations to difficult talks with family and partners, so you always know exactly what to say and how to say it.
Never Be Lost
for Words Again
Get word‑for‑word scripts for the conversations that shape your life, from job interviews and negotiations to difficult talks with family and partners, so you always know exactly what to say and how to say it.
Key Takeaway
Before your next assignment conversation, write down three things on paper: the specific outcome you need, the deadline that is not negotiable, and one example of what failure looks like. Then, after you deliver those expectations to your employee, ask them to summarize the assignment back to you in their own words. If their summary matches your paper, you are done. If it does not, you just found the exact gap you need to close before the work starts.
