By Dr. Sheila Viesca
“Any questions?” Nobody speaks. The meeting ends with the reassuring appearance of agreement. Three days later, one employee submits a recommendation, another is still gathering comments, and a third is waiting for approval. The manager asks why a straightforward instruction produced three different responses. Each employee believed they were doing exactly what was expected.
I would examine the silence before judging the work. It may have concealed an incomplete brief, a reluctance to question authority, or both. A leader can leave a meeting feeling exceptionally clear while the team leaves with an assignment it must privately reconstruct. The cost appears later, attached to the names of the people who carried it out.
TalkShop’s management communication and leadership programs connect the way an instruction is delivered with the decisions another person must make afterward. I regard that connection as central to leadership: the message eventually becomes somebody else’s work.
The agreement nobody tested
People deserve a clear assignment before we judge how well they carried it out. That includes clarity about the judgment we expect them to exercise. An employee asked to “take ownership” may still need to know whether ownership includes choosing a supplier, changing a deadline, or challenging a request from a more senior colleague.
There is a second question beneath the instruction itself. Can the employee safely admit that the assignment is unclear? A manager can invite questions and still discourage them through an impatient expression, a sarcastic response, or a public reminder that the matter was already explained. People learn from those moments. The next time they are uncertain, they may decide that guessing is less uncomfortable than asking.
Harvard Business School scholar Amy Edmondson’s 1999 study of 51 work teams found an association between team psychological safety and learning behavior. Psychological safety concerns whether people believe they can take interpersonal risks, including admitting uncertainty. The finding gives leaders a reason to examine the social conditions surrounding questions, alongside the wording of their instructions. [1]
The difficulty is that agreement is socially convenient. The manager can move to the next item; the employee can avoid appearing unprepared. Nobody has to interrupt the meeting with a question whose answer may seem obvious to everyone else. I would be cautious about treating this convenience as evidence. A quick agreement may simply postpone the harder conversation until the deadline.
Imagine a supervisor asking a new employee to prepare the monthly performance report. The supervisor remembers the previous twelve reports and assumes that the format, recipients, and review sequence are familiar. The employee has seen only a spreadsheet. Both leave the conversation believing that the assignment is straightforward. Their confidence rests on different information. A useful check would uncover that difference while it is still inexpensive to correct.
This is why I would ask for the next step in the employee’s own words. What will you begin with? Where will the figures come from? Who needs to review the draft? These questions reveal the employee’s working picture of the task. They also expose missing access, outdated templates, or assumptions about somebody else’s availability. Listening to that picture gives the manager something more useful than a ritual acknowledgment.
What the assignment asks people to decide
Consider the instruction, ‘Please coordinate with the team and send this soon.’ It sounds reasonable until we ask what it actually requires. Coordinate with whom? Obtain approval or simply gather input? Send which version? How soon? Who can settle conflicting recommendations?
A more useful instruction would be: ‘Please gather Finance and Operations comments on the attached draft by Wednesday noon. Send me the consolidated version at 3 PM, with unresolved points highlighted. I will approve the final release.’ The additional detail gives the employee a basis for acting independently.
Return to the three employees after the meeting. Before discussing their diligence, put their outputs beside the original request. Which words established that a recommendation was required? Where was approval mentioned? If the answer depends on what the manager normally expects, the team was relying on an unwritten convention. Experienced employees may know it; newer colleagues may have no reasonable way to discover it.
Consider a hypothetical request to examine customer complaints. A summary of complaint categories, a recommendation for changing the process, and a response to individual customers are three distinct outputs. Each requires different information and authority. If the manager wants a recommendation, the employee needs to know whether they should compare alternatives, estimate resources, or simply identify the recurring issue. Those are design decisions about the assignment itself.
A clear brief can be short. It should identify the intended user of the output, the decision it will support, and the standard that makes it useful. Where a sample exists, show it and explain which features should be followed. Where the sample contains outdated information, say so. Otherwise, an employee may reproduce its weaknesses with considerable diligence and still disappoint the person who provided it.
There is also a responsibility on the receiving side. Saying, ‘To confirm, you need the recommendation rather than the full report by Friday,’ is a professional contribution. Teams should welcome that kind of clarification, especially when hierarchy makes questions uncomfortable.
Understanding an instruction does not establish that it can be completed under the proposed conditions. An employee may understand the deadline perfectly while knowing that a required approval normally takes longer. If the conversation allows only acknowledgment, the manager loses the chance to make a realistic decision. A feasibility discussion should therefore follow the clarity check, particularly when an assignment crosses teams or depends on information outside the employee’s control.
A useful response might be, “I can prepare the analysis by Thursday if Finance confirms the figures on Tuesday. If confirmation comes later, I can submit a provisional version with the missing items identified.” This is a practical contribution to planning. The manager can now decide whether to obtain the figures earlier, accept a provisional output, narrow the scope, or revise the deadline. The uncertainty becomes manageable because somebody has named it.
Employees also have responsibilities in this exchange. Raise the constraint while there is still time to act. Explain what has been checked and what remains an assumption. Avoid presenting every inconvenience as an impossibility. Managers, in turn, should resist treating every qualification as resistance. A team becomes more dependable when it can distinguish an obstacle that requires intervention from a preference that can be negotiated.
The person closest to the task may notice the constraint first.
The agreement needs a place to live
Before closing the next meeting, confirm four things with the person responsible:
·The output and the standard it must meet.
·The deadline and any earlier review point.
·The decisions they can make and those requiring approval.
·The dependencies or conflicting priorities that could prevent delivery.
Put the agreement in a brief written recap. Include the decisions still pending, because an unresolved question can quietly become an assumption once everyone returns to work.
A written recap has a particular value when authority is uneven. It allows a junior colleague to raise a discrepancy by pointing to the agreement rather than appearing to challenge a senior person’s memory. “The recap says Wednesday; has the deadline changed?” is a smaller interpersonal risk than “That is not what you told us.” The record gives clarification somewhere concrete to begin.
For an assignment involving several departments, record the owner of the consolidated output. Identify who supplies information, who reviews it, and who gives final approval. These responsibilities can belong to different people. When they remain implicit, several diligent employees may each assume that somebody else is coordinating the whole. The resulting delay can look like a lack of initiative even when the actual problem is an undefined responsibility.
A brief written record also protects continuity when somebody is absent. The colleague taking over should be able to see what was agreed, what has changed, and which decision is pending. This is particularly useful when teams work across locations or schedules. Information that exists only in one person’s memory becomes difficult to use at exactly the moment another person needs to continue the work.
What happens when the first agreement fails
I would begin the check with language that accepts some responsibility for the message: ‘Let us make sure I have given you enough to proceed.’ That small choice makes room for a useful answer. An employee can then explain that two departments have supplied different figures, or that the requested deadline conflicts with an earlier priority. The manager gains information that an automatic ‘Yes, understood’ would have concealed.
This needs to feel like a shared check on the assignment. If people experience it as a memory test, they may repeat your words while withholding the concern you most need to hear.
The repeated question can irritate a manager because it interrupts the story they have told themselves about the assignment: I explained; they understood; execution should follow. Yet work continues to introduce information after that moment. A changed request, a missing figure, or a competing instruction can make yesterday’s answer insufficient. The manager needs to discover which situation they are actually facing.
Suppose an employee asks again who should approve a client proposal. A dismissive response may end the exchange, but it will not resolve the fact that the commercial director requested one revision while the account manager requested another. A better response begins with, “What has changed since we last discussed it?” That question makes room for information before the manager decides whether the issue concerns understanding, judgment, or follow-through.
This does not require unlimited repetition without development. If the same question returns under unchanged conditions, review how the information was recorded and whether the employee can apply it to a comparable example. Provide feedback on the specific gap. The objective is to increase independence over time. Impatience may stop a question immediately while leaving the underlying dependence untouched.
When an assignment goes wrong, the first conversation should establish the sequence of events. What was requested? What did the employee understand? Which information was available at the time? Did the requirement change? A reconstruction of the facts gives both parties a basis for correction. Starting with a verdict encourages each person to defend their version before either has understood the other’s.
Suppose the recommendation is late because the employee waited for comments from a director. The manager had expected the draft to proceed without them. Two responsibilities now need examining. The manager did not state which comments were essential; the employee did not escalate the delay. Treating either person as the sole cause would leave part of the problem available to recur.
End the repair conversation with a usable change. Revise the template, identify the decision owner, or establish a review point before the final submission. “Communicate better” is too broad to guide the next assignment. “Send the assumptions for confirmation before completing the calculations” creates an action somebody can perform. The repair should leave the team better equipped for a similar task.
Give people enough clarity to act without you
Clarity also requires restraint. A manager who specifies every movement can leave an experienced employee with responsibility but no discretion. Define the output, the quality standard, and the boundaries of authority. Then distinguish what must remain fixed from what the employee can decide. For example, a regulatory deadline may be fixed while the method for gathering internal comments remains flexible. Knowing that distinction helps people exercise judgment without repeatedly seeking permission.
A manager can clarify the current assignment while also helping an employee make better decisions on the next one. Ask how the employee distinguished essential information from supporting detail. Discuss why a particular uncertainty required escalation. Invite them to propose the review point they would use for a comparable task. These questions connect the immediate output with the reasoning that will make future work more independent.
For a new employee, the discussion may require a concrete example and a closer review sequence. For an experienced colleague, it may be enough to establish the outcome and explain the limits of authority. Giving everyone the same amount of instruction can waste expertise in one case and conceal a learning need in another. The degree of guidance should reflect the task and the person’s demonstrated capability.
There is also a temptation to reward the employee who always rescues an unclear brief. Their resourcefulness may be valuable, but the rescue can conceal a fragile process. Ask what they had to infer and whom they had to contact privately. The goal is to preserve their judgment while making essential information available to colleagues who do not share their history or access.
For one week, keep a private record of assignments that return for rework. Look for the point at which expectations diverged. Was the brief incomplete? Was the required skill missing? Did a dependency fail? Did someone disregard a clear agreement? The answers lead to different management actions. Training, process correction, and a performance conversation each have a place; their usefulness depends on diagnosing the problem accurately.
I would compare the manager’s first request with the last revision, rather than counting clarifications as failures. Some questions improve the assignment. Others reveal missing preparation. Still others arise because a decision changed halfway through the work. Without that distinction, a team may learn to reduce its visible questions while continuing to make the same expensive assumptions in private.
Do not assume that every successful assignment had a good brief. Experienced employees sometimes compensate for unclear instructions through private knowledge and extra effort. Ask what they had to reconstruct. Equally, do not assume that every difficult assignment reflects poor communication. Missing resources, changing priorities, or a genuine skill gap may explain the result. The review is useful when it makes these differences visible.
The danger is turning this review into another ritual of control. A manager can require so many confirmations that an experienced employee spends more time proving understanding than doing the work. Retain checks that expose consequential uncertainty. Remove those that merely reassure the manager. A useful agreement should give people more room to act responsibly, with a clear point at which to return.
A question for the manager is whether the employee could continue responsibly if the manager became unavailable for a day. The answer can reveal where the agreement still depends on private knowledge, an unstated approval, or access that somebody has not arranged.
At the next meeting you lead, leave time for the person responsible to describe the assignment as they understand it. Listen especially for the decision they believe they can make without you. If their account differs from yours, the conversation has already produced something valuable: a misunderstanding discovered while it can still be repaired.
“I thought you meant” is an expensive sentence when it arrives after the work. Before the work begins, the difference it reveals is information a leader should want. What you do with that first clarification will influence whether anyone risks offering the next one.
Explore related TalkShop programs
TalkShop customizes management communication and leadership training around the conversations, decisions, and responsibilities of your team. Explore the program or discuss your organization’s requirements.
Explore the relevant TalkShop offering
Posted by 
