Clear expectations turn individual effort into coordinated results. Setting them, and keeping them aligned… is one of a leader’s most important responsibilities.
Over the years, working across programming, systems engineering, network operations, security, and management, I’ve come to appreciate how much of our success depends on setting and managing expectations.
People can work hard, have good intentions, and produce good results… and still disappoint one another.
One person expects a completed solution. Another believes they were asked to investigate options. A manager assumes a task is underway. An employee is waiting for clarification. A customer expects an update today, while the team plans to respond when the problem is resolved.
Each person has an understanding of what should happen. The trouble begins when those understandings don’t match.
By the time someone says, “That’s not what I expected,” the gap may have already cost time, created rework, or damaged trust.
That is why I consider setting and managing expectations one of the most important skills in management and business. It affects how we delegate, communicate, prioritize, deliver, and hold one another accountable.
And sometimes, the first opportunity to get it right is a simple email.
“I Saw Your Email” Doesn’t Tell Me What Happens Next
Here is a situation many of us will recognize.
You send an email requesting a task, a project update, or information needed to move something forward. Hours pass without a response. Eventually, you follow up.
The reply comes back, “I’m working on it.”
Or:
“I know. I saw your email. I’ll get to it soon.”
I’ll be honest, that frustrates me.
When I follow up after hearing nothing, I’m often trying to confirm that the request was received. Emails get buried. Messages get overlooked. Someone reads something between meetings, intends to return to it, and forgets.
We have all done it. I certainly have.
I would much rather hear, “I missed that, thank you for following up,” than receive a response suggesting I should have known the request was already being handled.
If you saw the email but never acknowledged it, that knowledge stayed with you. Everyone else was left guessing.
A brief response could have resolved the uncertainty…
- “Received. I’ll review this this afternoon and update you by the end of the day.”
- “I’m tied up today. Would tomorrow morning work?”
- “I have this, but I’m waiting on information from another team. I’ll follow up with them and update you tomorrow.”
Each response helps the sender understand what happens next. It also gives them an opportunity to explain if that timing won’t meet the business need.
Acknowledgment Is a Commitment to Communicate
Acknowledging a request does not obligate you to drop everything and complete it immediately.
You can acknowledge it while explaining that you have another priority, need more information, or cannot yet estimate completion.
What matters is giving the other person enough information to coordinate their own work.
“I’m working on it” can be a useful starting point, but it often needs a little more context. Are you investigating? Implementing? Testing? Waiting on someone else?
Likewise, “soon” means different things to different people. One person hears an hour. Another means sometime this week.
When you don’t know the completion date, commit to a next update:
“I need to investigate before I can give you a reliable estimate. I’ll update you tomorrow morning with what I find.”
That establishes something concrete without pretending to have an answer you don’t yet possess.
Remember… The Person Making the Request Has Responsibilities Too
Expectation management works in both directions.
As leaders, we need to examine the requests we send. Did we explain the outcome? Identify the owner? State the deadline? Explain why the timing matters?
“Please take care of this” may feel clear to the sender while leaving several unanswered questions for the recipient.
Does “take care of it” mean recommend a solution, implement a change, or coordinate with another department? Does it include testing and documentation? Is the deadline a firm business requirement or a preference?
A stronger request might say…
“Please review the options and send me your recommendation by Thursday afternoon. We need it for Friday’s planning meeting. If that timing conflicts with your current priorities, let me know today.”
The recipient now understands the deliverable, the reason for the deadline, and when to raise a concern.
We also need reasonable communication expectations. People require time to concentrate, attend meetings, and handle existing responsibilities. Every email cannot carry an expectation of immediate acknowledgment.
Teams should agree on appropriate response windows and escalation methods. An urgent incident needs a dependable channel. Routine work needs enough clarity that people can respond without constantly interrupting their concentration.
If It Matters, Put It in Writing
Some of the most important expectations are established in conversation: during a meeting, on a phone call, or in a quick exchange between other responsibilities.
Those conversations are valuable. But we should be careful about assuming that every detail was heard, understood, and remembered exactly as intended.
A person can hear the deadline and miss the dependency. They can remember the requested outcome but overlook a restriction. Two people can leave the same meeting with different understandings of who agreed to do what.
Details get lost in interpretation. Attention gets divided. Memory fills in gaps.
When something is critical, put it in writing.
That can be a short follow-up email, an updated project task, a ticket, or a summary in the agreed team channel. What matters is creating a clear reference that the people involved can review.
“Following our discussion, here is what we agreed… Alex will prepare the recommendation by Thursday. Implementation will wait for approval. We will review any outstanding questions Wednesday afternoon.”
A few sentences can capture the outcome, owner, deadline, dependencies, and approval requirements.
For significant commitments, ask the people involved to confirm the summary or correct anything you misunderstood. Written communication can contain ambiguity, too. Giving someone an opportunity to respond helps turn a record of your understanding into a shared agreement.
When circumstances change, update that same reference so people can identify the current commitment.
The greater the consequence of a misunderstanding, the more deliberate we should be about confirming the details. Important work deserves more than a hope that everyone heard the same thing.
A New Priority Requires a Conversation About Existing Work
One of the easiest ways to create unrealistic expectations is to keep adding work without revisiting earlier commitments.
A team member has several deliverables underway. Another urgent request arrives. Everyone agrees it matters, but nobody discusses what will move.
The original deadlines remain on the calendar, even though the capacity to meet them has changed.
Employees should feel comfortable saying…
“I can complete this today, but it will move the other deliverable to Friday. Which should take priority?”
Leaders need to welcome that information and make the decision. Then the affected commitments should be updated and communicated to anyone relying on them.
We cannot ask people to communicate honestly about capacity and then treat every raised conflict as a lack of commitment.
Ambitious goals still need a practical understanding of the work, dependencies, and resources involved. Otherwise, enthusiasm at the start becomes disappointment at the finish.
Always Confirm What “Done” Means
Expectation gaps also appear at the end of a task.
- A system has been configured. Has it been tested?
- A report has been generated. Has anyone verified the information?
- A change has been implemented. Have the affected users been informed?
Depending on the assignment, each of those may be part of completion, or a separate step owned by someone else. The important thing is agreeing before assumptions become obligations.
For technology teams, this distinction matters. Something can be technically functional while still requiring operational preparation.
The requester should define the expected outcome. The person doing the work should identify necessary steps that may have been overlooked. Together, they should establish how completion will be confirmed.
Closing the loop matters, too. If the work is finished but nobody knows, other people may continue waiting, following up, or delaying their next step.
A completion message should explain what was delivered and identify anything still outstanding. That gives the next person a reliable starting point.
Correct Misalignment as Soon as You See It
Once you recognize that someone’s expectations differ from yours, you have a responsibility to address the gap.
Perhaps they expect a finished implementation tomorrow, while you intended to deliver an assessment. Perhaps you believe they own the next step, while they are waiting for your approval.
Allowing that misunderstanding to continue makes the eventual conversation harder.
Address it directly…
- “Let me clarify what I’m committing to for tomorrow.”
- “I think we have different understandings of what completion includes.”
- “Before we proceed, let’s confirm who owns the next step.”
Then listen to their understanding. You may discover that your original message was incomplete, that circumstances changed, or that they have information you don’t.
Alignment requires both people to understand the agreement. Sending a message establishes that you communicated something; it doesn’t automatically establish that the other person understood it as intended.
Take the time to resolve the difference, confirm the revised agreement, and put the important details where everyone involved can find them.
Update the Commitment When Circumstances Change
Even well-defined expectations need maintenance.
An investigation uncovers additional work. A vendor misses a delivery. An incident redirects the team. A dependency takes longer than planned.
When you know a commitment is at risk, communicate early.
Explain what changed, what it affects, and what you can now reasonably commit to. Identify any decision or assistance needed to move forward.
If the situation remains uncertain, set the next checkpoint.
People may be disappointed by a delay, but early communication lets them adjust their plans. Silence leaves them relying on a commitment you already know is unlikely to hold.
Repeatedly moving a deadline also deserves attention. Updates help maintain visibility, but they should lead to an honest discussion about scope, capacity, or the underlying obstacle.
Accountability Starts With a Shared Understanding
Clear expectations make accountability fairer.
Before concluding that someone failed to deliver, ask whether the expected outcome was defined, understood, and supported by realistic priorities.
That does not remove individual responsibility. It gives responsibility a clear foundation.
Employees need to raise concerns, communicate progress, and follow through on commitments. Leaders need to provide direction, resolve competing priorities, and remain available for decisions.
Both need to speak up when the agreement no longer reflects reality.
Throughout my career, the tools and platforms have changed considerably. The need for clear communication has remained.
A brief acknowledgment can prevent unnecessary follow-ups. A realistic commitment can protect other people’s plans. A written summary can preserve details that would otherwise be lost. A timely clarification can keep an entire project moving toward the right outcome.
People should be able to plan around what we tell them.
Setting expectations gives them that starting point. Managing those expectations, and correcting the alignment whenever it slips… is how we keep their trust.
