To set clear expectations, explain what result is needed, what good looks like, when it is due, which decisions the employee owns, and what support is available. Then ask them to talk through their understanding. Send a short recap and agree when to check in.
“Take more ownership” is not enough on its own. One person may hear “decide independently”; another may hear “send me more updates.” The conversation needs to make that difference visible before work begins.
Prepare five things before the handoff
- Outcome: What should exist or change? “A decision-ready supplier comparison” is clearer than “research suppliers.”
- Standard: What must it include? Show a useful example, name required checks, and distinguish essentials from preferences.
- Timing: When is the output needed, and why? Include any review time rather than treating the first draft as the final deadline.
- Authority: Which choices can the employee make? Which need approval? Who else has a say?
- Support: What access, context, training or help will you provide? What other work may need to move?
The University of Iowa’s performance guidance recommends checking that expectations were clear and that tools, training and resources were available before treating a performance gap as an employee problem. That is a useful preparation check for a new assignment too.
A complete expectations conversation
This fictional example is a manager assigning a vendor comparison to a team member. The numbers and deadlines illustrate the conversation; they are not recommended targets for every team.
Manager: “We need to choose a support platform at Monday’s planning meeting. Could you prepare a two-page comparison by Thursday at 3? It needs cost, integration limits and one recommendation. I’ll review Friday. You can choose the comparison format; I’ll make the spending decision.”
Employee: “Does that include a security review? I can compare features by Thursday, but Security needs more time.”
Manager: “Good catch. Mark security approval as pending; we won’t sign a contract before it’s complete. I’ll contact Security today. Does the rest fit with your onboarding project?”
Employee: “Only if I move the onboarding draft to next Tuesday.”
Manager: “I’ll confirm that change with the project owner. Talk me through what you’ll deliver Thursday so we can check we mean the same thing.”
Notice the manager did not ask “All clear?” and treat a yes as proof. Asking for the plan exposed two dependencies and a competing priority. It also gave the employee room to influence how the work would be done.
Check understanding without turning it into a test
“Repeat that back to me” can sound like an exam. Explain that you are checking the brief, including your own communication:
I want to make sure I explained this clearly. How are you thinking about the result and the first step? What have I left ambiguous?If their plan differs from yours, find the point of difference. Do not silently wait for the final result and then reveal the standard you had in mind.
For an experienced employee, you can invite a proposed standard: “What would a good handoff look like from your perspective?” For someone new to the task, supply more examples and context. Independence does not require withholding information.
If they say the expectation is unrealistic
Ask which constraint is driving the concern. Is it time, an unfamiliar skill, access to an input, or a conflict with another commitment?
Employee: “I can’t deliver all of that by Thursday.”
Manager: “Which part is the constraint? Let’s work out what can fit without skipping the required checks.”
A fair agreement may mean less scope, a different date, a different owner or additional support that is genuinely available. It may also mean explaining why a requirement is fixed and making another priority decision. Do not relabel an impossible workload as a confidence problem.
See deadline pushback examples for the employee’s side of this conversation.
Send a recap both people can use
Outcome: a two-page supplier comparison for Monday’s decision.
Includes: cost, integration limits, recommendation; security status clearly marked.
Owner: Alex. Format and research approach: Alex’s decision.
Timing: draft Thursday at 3; manager review Friday.
Support: I’ll request the security review and confirm the onboarding date change today.
Check-in: Wednesday, 15 minutes on open questions and risks.
If an input slips: flag it when you know, with the effect on the plan.Ask them to correct anything you missed. A recap is a shared working agreement, not a way to manufacture consent where there is still a disagreement. Acas guidance on objectives recommends reasonable, achievable objectives that reflect workload, regular conversations and shared written records. Its employment-law context is UK-specific; use your own organization’s policies for formal performance processes.
Common mistakes and your next step
- Using a personality label: Replace “be proactive” with the action you need, such as flagging a blocked dependency before the handoff.
- Changing the standard quietly: If requirements change, update scope and timing together.
- Delegating a result but retaining every decision: Specify decision rights. See delegating without micromanaging.
- Treating a check-in as an inspection: Ask what needs a decision or support, not only what is finished.
Before your next handoff, write the five points above. Circle the one you have been assuming rather than saying. That is the question to resolve together.
In TalkCraft, Leadership Conversations → Set Expectations Early and Clearly offers related written decision practice. The examples in this article are original teaching examples, not an exact transcript of an app scenario.
