Name the behavior the employee could observe, apologize for it without qualification, then offer a choice about when or how to return to the work issue. Do not begin by asking why the employee went quiet. Silence does not reveal its cause, and the work may still need a decision, owner, and timeline.
What should the manager do first?
Name the behavior the employee could observe, apologize for it without qualification, then offer a choice about when or how to return to the work issue. Do not begin by asking why the employee went quiet. For example: ‘I raised my voice and interrupted you. I’m sorry. I’d like to hear your view on the handoff. Would you rather continue now, send thoughts later, or meet tomorrow?’ This illustration should fit what the manager actually did.
The manager can describe their conduct, but silence does not reveal its cause. Asking for an explanation first can make the employee responsible for naming the harm and restarting the exchange. In ‘Forced versus Voluntary Apologies: Trust Repair as a Matter of Perceived Values,’ participants considered a coworker who failed to complete an important assignment. Participants who waited and received an apology reported higher trust than those who demanded one. This offers a reason to take initiative; it does not prove a script will repair this exchange.
The Government of Canada job aid ‘Tips for Having Constructive Performance Conversations’ advises patience when an employee withdraws, allowing silence, and considering a later meeting. Applied here, acknowledge the manager’s tone, leave room, and invite a return without pressing for reassurance. Keep repair separate from the work decision: an apology addresses how the conversation was handled, while the task may still need an owner, input, and timing. The employee need not explain their feelings before the manager takes responsibility.
Sources: Forced versus Voluntary Apologies: Trust Repair as a Matter of Perceived Values; Tips for Having Constructive Performance Conversations (COR1-J03)
Why should the manager take the first repair step?
The manager should begin the repair because the manager can name what they did: raised their voice, cut the employee off, or let irritation take over the exchange. The employee should not have to make a case for why that conduct deserves acknowledgment before the manager responds to it. That is especially relevant across a reporting relationship. The manager controls more of the conversation’s conditions, including when it resumes and how the work is judged. Asking the employee to first explain the silence can add a second demand: account for a reaction whose cause the manager does not yet know. A direct apology lets the manager take responsibility for their own contribution without asking the employee to disclose what they felt.
A workplace experiment gives limited support to taking that initiative. In “Forced versus Voluntary Apologies: Trust Repair as a Matter of Perceived Values,” full-time employees encountered a video vignette in which a coworker failed to complete an important assignment. The two-part study had 156 matched participants; several days after the scenario, participants could demand an apology or wait to see what happened, and were assigned to an apology or no-response condition. Among participants who received an apology, those who waited reported higher post-repair trust than those who demanded one: the reported means were 2.46 and 2.02, respectively, with a statistically significant difference in the analysis. This is evidence about a staged coworker competence failure and participants’ ratings, not a test of a manager who showed frustration. It cannot tell us how a particular employee will respond. Its narrower lesson is useful: when the person who caused a rupture volunteers accountability, the other person does not have to initiate that step.
The hierarchy here makes transfer from that study uncertain, not irrelevant. A manager who waits for the employee to raise the issue may leave the lower-authority person carrying both the original discomfort and the work of prompting a repair. The manager can avoid that burden without demanding forgiveness: “I got frustrated and interrupted you. I’m sorry. I should have let you finish.” Then stop. A question such as “Are we okay?” or “Can you forgive me?” changes the task; now the employee may feel asked to reassure the person who has authority over their work. An explanation like “I was under pressure” can also sound like a request to treat the behavior as unavoidable. The manager can explain the work context later if it matters, while keeping responsibility for delivery clear.
“Trust Repair,” a review of research on broken trust, separates short-term responses such as apologies from longer-term responses such as changes in arrangements or monitoring. That distinction cautions against treating the apology as the whole repair. Words can mark responsibility and reopen contact; what follows must show whether the manager’s conduct changes. The employee may remain quiet or may not accept the apology. The manager’s first step is still worthwhile because it is theirs to take. A concise, unqualified apology asks for no verdict on the relationship.
Sources: Forced versus Voluntary Apologies: Trust Repair as a Matter of Perceived Values; Trust Repair
Why silence cannot tell you what the employee thinks
Silence tells the manager that the exchange has stopped moving. It does not reveal why. The employee may be thinking, disagreeing, choosing not to answer in the moment, or attending to something outside the conversation. Those possibilities are not diagnoses; they are reasons to avoid turning a pause into a verdict. A manager who treats quiet as consent may close a decision the employee has not accepted. One who labels it defiance may turn an uncertain moment into a confrontation. Research on psychological safety helps explain why speaking up can carry weight at work, but it cannot decode one person’s silence. In “Psychological Safety and Learning Behavior in Work Teams,” psychological safety means a shared belief among team members that it is safe to take interpersonal risks. The study tested a model in a multimethod field study of 51 manufacturing teams. Team psychological safety was associated with learning behavior; learning behavior, in turn, mediated its association with team performance. This is evidence about patterns among teams, not a finding about what any employee meant by going quiet after a manager showed frustration. It supports taking the conditions for speaking seriously, while leaving the cause of this particular pause unknown. The distinction matters because a team climate and an individual moment are different things. A team may generally make questions and mistakes easier to raise, while a person still chooses to pause in one conversation. Or a generally difficult climate may make a response feel more consequential. A manager’s authority can add weight to the exchange because the manager may influence work assignments, evaluation, or access to support. That possibility does not establish that fear caused this employee’s silence. It does mean that the manager should be careful about asking the employee to account for it as though the reason were already known. The Government of Canada’s “Tips for Having Constructive Performance Conversations” advises managers to allow silence, listen, and, when an employee appears withdrawn, consider pausing and meeting again. The job aid also suggests asking what the employee understood or what may be affecting participation. Those prompts can help once the manager has acknowledged their own visible frustration and made space for a response. Asked too early, “Why did you go quiet?” can sound like a demand to explain a reaction the manager has already interpreted. The employee may choose to discuss the exchange; they may instead want to address the work, or to return later. The CIPD’s manager guide notes that conflict can include subtle conduct such as talking over someone or failing to value their views, and recommends early attention to workplace conflict. That guidance makes the manager’s own behavior relevant without proving that one pause signals a wider problem. Start with what can be checked: “I interrupted you and raised my voice.” Then invite, rather than assign, meaning: “Would you like to continue now, send your view later, or set another time?” If the employee corrects the manager’s account, listen. If they decline to explain, keep the work conversation open and do not call the silence agreement. The manager can name conduct and offer a route back; only the employee can say what the pause meant to them.
Sources: Psychological Safety and Learning Behavior in Work Teams; Tips for Having Constructive Performance Conversations (COR1-J03); Dealing with bullying and workplace conflict: Guide for managers
What an apology can repair—and what it cannot settle
A useful apology names what the manager did and takes responsibility for it. It does not decide whether the employee’s work position was right, erase the effect of the exchange, or require the employee to forgive quickly. The manager can acknowledge a raised voice, interruption, or dismissive response while still needing to resolve the original disagreement. Keeping them separate makes the apology clearer: it addresses the manager’s way of handling the conversation, not the merits of every point raised in it. The 2017 systematic review and meta-analysis “The trust repair effect of apology” combined 18 papers, 36 effect sizes, and 4,731 participants. Across those studies, apology had a positive average association with trust repair (d = 0.44, p < 0.001). But the effect varied with the kind of trust violation and the comparison condition; apologies worked better on competence-based than integrity-based violations, and the effect was larger against silence than denial. A pooled average across different situations cannot tell a manager how one employee will respond to frustration from someone with authority over their work. It supports trying a direct acknowledgment, not promising reconciliation. The review “Trust Repair” by Lewicki and Brinsfield distinguishes short-term responses, including apologies, from longer-term responses such as changes to the relationship’s structure or monitoring. The distinction matters because a sentence can open repair without completing it. If the manager apologizes for interrupting and then repeatedly cuts the employee off, later conduct gives the employee more information than the first sentence did. In some situations, repair may need a change in how decisions are discussed or followed up, not another expression of regret. The review surveys trust-repair research broadly; it does not prescribe a script for this incident. A practical apology can stay observable and modest: “I raised my voice and interrupted you. That was my responsibility, and I’m sorry. I’ll let you finish when we pick this up.” The first sentence identifies conduct the manager can verify. The next accepts responsibility without adding “but I was under pressure” or asking the employee to say it is all right. The final sentence names a change the manager can control. This is a usable structure for the situation, not a validated checklist or a guarantee of trust repair. Avoid telling the employee what they felt or demanding an account of the silence as part of accepting the apology. One objection is that the manager should not apologize if the employee’s position on the work is mistaken. That confuses delivery with substance. A manager can maintain a performance concern, explain the evidence for it, and set a clear expectation after taking responsibility for expressing frustration poorly. The voluntary-apology study, “Forced versus Voluntary Apologies: Trust Repair as a Matter of Perceived Values,” offers a limited parallel: in a two-part workplace vignette about a coworker who failed to complete an important assignment, participants who waited and received a voluntary apology reported higher trust than those who demanded one. It did not study a manager’s tone or test this sequence, so its result cannot settle the present case. It does caution against making the employee request the acknowledgment first. A concise apology can coexist with a firm work discussion; the concern should be reopened after the manager has owned the way it was delivered.
Sources: The trust repair effect of apology; Trust Repair; Forced versus Voluntary Apologies: Trust Repair as a Matter of Perceived Values
How can the manager give the pause room before asking for an account?
Once the manager has apologized, the next move is to stop talking long enough for the apology to land. A pause is not a test of whether the employee accepts it. It gives them room to decide whether they want to respond now, return to the work later, or use another channel. The manager can make that choice real by offering a couple of workable options rather than asking, “Why have you gone quiet?” That question asks the employee to explain behavior whose meaning the manager does not know. The Government of Canada’s “Tips for Having Constructive Performance Conversations” advises managers to allow a moment of silence when an employee appears unresponsive or withdrawn, to be patient, and to consider meeting again to work through the issue. As a job aid rather than a controlled test, it cannot show which response restores trust; it does support letting silence stand and pausing without abandoning the matter. Because the manager’s frustration preceded the silence, the pause should follow acknowledgment of that conduct; otherwise, “take your time” could sound like a demand to move on without repair. The format of a return should fit the work. If the matter is small and the employee seems ready, the manager can invite a response in the moment: “I’m sorry I cut you off and sounded frustrated. We can pause. Would you like to continue now, or come back to the handoff later?” If the issue needs thought, a later meeting may be better. The Fair Work Ombudsman’s “A manager’s guide to difficult conversations in the workplace” recommends allowing time to digest difficult information and offering a break before meeting later; it also advises managers to choose a time when the conversation will not be rushed or interrupted. That guidance supports offering time as an option, not prescribing a fixed waiting period. Written input can also be useful when the work question is easier to organize outside a live exchange. For example, the manager might ask whether the employee would prefer to send their view before a short follow-up. Neither guide establishes that writing is more comfortable or effective for a particular employee. The subject may also matter. A brief clarification about a handoff can be handled differently from a disputed performance concern that needs a careful, supported conversation. The manager should offer a route that fits the decision and let the employee say if another format would work better. An illustrative exchange might be: “I raised my voice and interrupted you. I’m sorry. You don’t have to explain your reaction right now. I do want to hear your view on the deadline question. Would you rather continue now, send me your thoughts, or meet tomorrow?” The apology names conduct the manager can verify; the invitation asks about the work, not for reassurance or a description of the employee’s feelings. The employee may answer, ask for more time, or decline to discuss the interaction. None of those responses tells the manager exactly why the employee went quiet. If the employee does not choose an option, the manager can leave the invitation open once and set a practical point for checking back, especially if the work cannot wait indefinitely. The Fair Work Ombudsman guide emphasizes agreeing on next steps and when to revisit an issue. Applied here, that means making the work follow-up clear while keeping the emotional conversation voluntary: “I’ll send the handoff details today; let’s check the decision tomorrow, and you can tell me if another format is easier.” The employee can re-enter the work without first providing an account of their silence.
Sources: Tips for Having Constructive Performance Conversations (COR1-J03); A manager’s guide to difficult conversations in the workplace
Keep the work decision clear while leaving room to respond
An apology can address how the manager spoke; it does not answer the work question behind the exchange. Once the manager has owned the frustration, name that question plainly: what needs deciding, who owns the decision, and what information is still needed. For example, the issue may be whether a handoff can be completed with the current plan. The employee’s quiet does not settle it. The manager should leave room for the employee’s view while remaining accountable for moving the work forward.
Separate time for a respectful conversation from the time the work allows. A pause may give both people space to collect their thoughts; a deadline may be needed because another person or task depends on the decision. Explain the deadline and its practical reason without using it to demand an immediate emotional response. If there is no real deadline, do not manufacture urgency. If there is one, say what must be decided by when, and ask what input the employee can provide before then. This keeps a choice about response format or timing meaningful without leaving the work indefinitely open.
The Fair Work Ombudsman’s *A manager’s guide to difficult conversations in the workplace* recommends closing with agreed actions, who will take them, and when, then setting a time to revisit the issue. It also advises confirming agreements in writing where appropriate and following through. Applied here, a short note can record the decision still needed, each person’s next step, any input the employee agreed to provide, and the date to resume. It should describe the work agreement, not turn silence into a performance judgment or a record of presumed motives.
The Government of Canada job aid *Tips for Having Constructive Performance Conversations* recommends allowing a moment of silence when an employee withdraws and proposing another meeting to determine together what may resolve the issue. That supports a pause with a return point, rather than pressing for an answer on the spot or letting the matter drift. A manager might say: ‘We still need to decide how the handoff will work. I’d like your view before I decide. Would you prefer to send it in writing by tomorrow, or talk again Thursday? I’ll confirm the decision by Friday because the next project step depends on it.’ This is an illustrative option, not a tested script; dates and format should fit the work.
If the employee does not choose a format immediately, the manager can restate the open question and next check-in, then explain how the employee can contribute before the decision. The manager remains responsible for making a timely, transparent call when it is theirs to make. Closing the issue because the employee stopped speaking risks treating quiet as consent; postponing every decision risks hiding ownership. A clear next step holds both needs together: space to respond and a visible route to resolve the work.
Sources: A manager’s guide to difficult conversations in the workplace; Tips for Having Constructive Performance Conversations (COR1-J03)
When one repair conversation is not enough
A single lapse in tone can usually be addressed with the repair already described: name the behavior, apologize, then make a clear invitation back to the work. The relevant question is what happened, whether it has happened before, and whether the matter now involves a concern that needs a formal route. The CIPD’s *Dealing with bullying and workplace conflict: Guide for managers* describes a wide range of conflict behaviors, from overt intimidation to subtler acts such as talking over someone or ignoring them. It notes that behavior may occur once or repeatedly, and that less visible conduct can contribute to disputes over time. This guidance does not establish that one frustrated response is bullying. It does give a manager reason to look beyond the dramatic incident: repeated interruptions, personal remarks, public humiliation, or persistent unreasonable pressure call for attention to the conduct itself, not another attempt to get the employee to talk more openly. The same guide recommends early attention to developing conflict and clear expectations for respectful conduct. It also distinguishes informal resolution from formal procedures: where an issue is sufficiently serious, including alleged discrimination, harassment, or a fundamental breach of the employment relationship, it advises seeking support and following company procedures. Those categories are examples from UK professional guidance, not a universal legal test. a manager should consult the applicable workplace policy and internal support rather than decide alone that a concern is too minor to record or too serious for ordinary channels. Acas’s *Challenging conversations and how to manage them* makes the process distinction concrete. It says internal policies should guide action on matters such as grievances or discipline, and that where a manager has evidence of a policy breach, they should consider the seriousness of the conversation and get management support. That is different from returning privately to apologize for an isolated lapse. If an employee raises a formal complaint, describes retaliation, or indicates that a private meeting would feel pressuring, repeated invitations to talk one-to-one may make the manager’s preferred repair the employee’s new burden. Follow the designated process, ask an appropriate manager or HR contact for guidance, and respect any safeguards the process sets. A manager can still take responsibility for their own observable conduct, but should not use an apology to bypass a complaint, discourage documentation, or seek reassurance that the matter is settled. When a formal concern exists, the appropriate next step may involve another person, a documented process, or a pause in direct contact. What happens depends on the policy and circumstances; the employee’s silence alone does not supply that answer. The manager should also avoid promising confidentiality beyond what the process permits, or implying that raising a concern will affect assignments, evaluations, or access to support. For an ordinary one-off lapse, return to the conversation when the employee has a reasonable chance to respond, and keep the work question distinct from any personal account they choose not to give. For repeated or serious conduct, address the behavior through the route designed to examine it. Escalation depends on the conduct and its pattern, not on how much the employee speaks in the moment.
Sources: Dealing with bullying and workplace conflict: Guide for managers; Challenging conversations and how to manage them
The short sequence that reopens the work
The practical sequence is to own the behavior the employee could observe, apologize without qualification, pause, offer a choice for returning, and make the work decision and follow-up explicit. Keep three kinds of statement separate. “I raised my voice and interrupted you” describes the manager’s conduct. “You felt unsafe” assigns an inner state the employee has not confirmed. “We still need to decide the handoff” names an outstanding work question. A repair begins with the first; it does not require the manager to guess the second before they can address the third.
An illustrative reopening might sound like this: “I raised my voice and interrupted you earlier. That was not appropriate, and I’m sorry. I should have let you finish.” Then stop. The pause gives the apology room without asking the employee to accept it, explain their silence, or reassure the manager. The manager can continue: “We still need to settle who owns the handoff. Would you rather talk now, send me your view in writing, or meet later today?” Those options should be genuine. If there is a real deadline, name it plainly and identify what input is needed by when; do not turn urgency into pressure for an immediate emotional response.
This is a practical synthesis, not a script tested in this exact situation. In Forced versus Voluntary Apologies, a two-part workplace vignette experiment involved 156 full-time workers responding to a coworker who failed to complete an important assignment. Participants who waited and then received an apology reported higher trust than those who demanded one and then received it. The scenario concerned a competence failure between coworkers, so it cannot show that these words will restore trust after a manager shows frustration. It does support the manager taking initiative rather than making the employee request acknowledgment. Trust Repair, a review of repair research, also distinguishes short-term words such as apologies from longer-term responses. The manager’s next conduct therefore matters after the exchange, too.
The Fair Work Ombudsman’s A Manager’s Guide to Difficult Conversations recommends confirming next steps, who will act, and when, then arranging a follow-up; it also cautions managers against relying on assumptions about what an employee thinks. Applied here, record the work agreement when useful, not an interpretation of the employee’s silence. If the employee declines to discuss the interaction, accept that answer without repeated requests for an account or forgiveness. Keep the necessary work channel open: clarify the task, deadline, and a reasonable way to provide input. If no immediate decision is required, agree on a time to revisit it rather than filling the silence with repeated messages. If a decision cannot wait, explain what must be decided, what input is still welcome, and who will make the call. The manager can show respect in subsequent conversations by listening without interruption and keeping their tone measured. A reopened work discussion is a useful next step; the employee’s immediate disclosure or reassurance is not proof that the apology worked.
Sources: Forced versus Voluntary Apologies: Trust Repair as a Matter of Perceived Values; A manager’s guide to difficult conversations in the workplace; Trust Repair
Choose one behavior to practice next
After the conversation, choose one part of your own response to practice in the next disagreement. Perhaps irritation showed up in your voice before you noticed it; perhaps you interrupted or answered before the employee had finished. Name the behavior plainly, then choose a small alternative: pause, lower your volume, or let the other person finish before you reply. This is a practice target, not a verdict about your character. Later conversations show whether you follow through.
A brief private note can keep the reflection concrete: what happened just before frustration rose, what you did that the employee could observe, and what you want to try next time. Keep the employee’s reaction out of the scorecard. They may not offer reassurance or explain the pause. Your responsibility is to make your own conduct more deliberate and keep necessary work conversations clear.
The private 32-item Emotional Skills Profile offers a structured way to reflect on recent emotional habits and judgments about authored scenarios. Those reflections remain distinct; the profile cannot explain this employee’s silence or certify that your account is correct. Explore the profile at /assessment for a development prompt. Then return to the practical test: can you notice frustration early enough to let the other person finish?
Questions readers ask
What should a manager say when an employee goes quiet after the manager shows frustration?
Name the observable behavior, apologize without qualification, then offer a choice about when or how to return to the work issue. Avoid asking the employee to explain their silence before taking responsibility.
Does an employee’s silence mean they agree?
No. Silence shows that the exchange has paused; it does not establish agreement or explain why the employee stopped speaking.
Should the manager apologize even if the employee was wrong about the work?
The manager can apologize for how they handled the conversation and still address a work concern. Delivery and the merits of the work issue are separate.
When is a private repair conversation not enough?
Repeated or serious conduct, a formal concern, or circumstances where private contact could pressure the employee may call for the applicable workplace process and support.
Sources
- Forced versus Voluntary Apologies: Trust Repair as a Matter of Perceived Values
Supports a limited comparison of voluntary and demanded apologies in a coworker competence-failure vignette, not this manager-employee incident.
- Tips for Having Constructive Performance Conversations (COR1-J03)
Supports allowing silence, listening patiently, and considering a later meeting when an employee appears withdrawn.
- Trust Repair
Supports distinguishing short-term verbal trust-repair responses such as apologies from longer-term responses.
- Psychological Safety and Learning Behavior in Work Teams
Supports the team-level relationship between psychological safety and learning behavior in a field study of 51 manufacturing teams.
- Dealing with bullying and workplace conflict: Guide for managers
Supports attention to workplace conflict, conduct patterns, and clear expectations; it does not establish the cause of one pause.
- The trust repair effect of apology
Reports a positive average apology effect on trust repair across 18 papers, 36 effect sizes, and 4,731 participants, with variation by context.
- A manager’s guide to difficult conversations in the workplace
Supports managing tone, avoiding assumptions, allowing time, and recording agreed next steps where appropriate.
- Challenging conversations and how to manage them
Supports following applicable workplace policies and seeking management support for serious or complex concerns.
Apply it to the real situation
Choose one response to practice in your next difficult conversation
From this guide: The manager can reflect on their own emotional habits and scenario judgments, but the profile cannot explain the employee’s silence or verify the manager’s account.
After the conversation, you can reflect on what you noticed, how frustration affected your response, and what behavior you want to practice next time. The private 32-item Emotional Skills Profile separates recent-behavior summaries from judgments on authored scenarios. It is a development aid, not a way to infer what an employee felt or certify that a repair worked.
