Honest Conversations at Work: Feedback, Disagreement, and Repair

The Version You Keep Rehearsing

Something happened in Tuesday's meeting. You have replayed it several times since — once while making dinner, twice while pretending to read a document. You know you should probably say something. And you know this is not a stranger you can walk away from: the two of you will be in the same meeting on Thursday, sharing a project, a deadline, and probably a spreadsheet.

That is what changes the conversation. A difficult conversation at work is really two questions at once: what needs to be said, and what happens after you say it. Handling one well means addressing something honestly while staying attentive to what is actually yours to address, what power each person holds, what consequences are possible, and what the working relationship needs afterwards — because it usually continues the next morning.

This article is about those workplace conditions, not about the general mechanics of hard conversations. Those mechanics — how to open without accusation, how to listen, how to pause and repair mid-conversation — have their own guide in this library, How to Have Difficult Conversations, and this one links to it rather than repeating it. What follows is everything the workplace adds on top: hierarchy, reputation, privacy, documentation, and the plain fact that you cannot simply leave.

Why an Honest Conversation at Work Is Different

Most conversation advice assumes two people who chose each other and can un-choose each other. Work removes both assumptions. You did not select your colleagues, you cannot walk away from them, and the relationship carries a formal structure that a friendship never does: roles, reporting lines, evaluations, and consequences that outlast any single conversation.

Three things follow. First, the stakes are professional as well as personal — a mishandled conversation at work can change what people think of your judgment, not just your company. Second, the audience is rarely just the two of you: colleagues watch how disagreement is handled and update their own behaviour accordingly. Third, the relationship has to keep functioning regardless of outcome. You do not need to resolve the relationship. You need the two of you to be able to share a meeting on Thursday.

This is also why connection at work is worth the effort in the first place — the argument of the series cornerstone, Why Connection at Work Matters. A team where nothing real can be said is not harmonious; it is merely quiet, and the problems are still there, travelling by other routes.

First Decide What Kind of Problem You Have

Before any wording, there is a sorting step most people skip. What follows is a Fika Pause editorial sorting — practical guidance, not a validated scientific model — and its purpose is to stop every problem being treated as the same problem.

• A misunderstanding. Two people working from different facts. These usually dissolve with a question, not a conversation.
• A difference of preference. They like meetings; you like messages. No one is wrong, and the fix is usually a negotiated arrangement rather than anyone being corrected.
• Behaviour affecting shared work. Something specific and observable — missed handoffs, meetings that start without the decision-maker, work redone without consultation. This is the natural territory of a direct conversation.
• A disagreement about a decision. You think the plan is wrong. This is not a complaint to be smoothed over; it is a professional contribution to be made clearly, once, in the right forum.
• A repeated pattern. The same issue, already raised, still happening. This is no longer a misunderstanding, and treating it as one wastes everyone's patience.
• A role or process problem. Unclear ownership, impossible handoffs, incentives that pull against each other. No conversation between two people fixes a structure.
• An issue requiring a formal channel. Conduct that organisational processes exist for. This is not interpersonal friction and should not be handled as though it were.

The sorting matters because each type has a different right response, and the most common workplace-conversation failure is using the response for one type on a problem of another.

Not Every Problem Needs a Conversation

There is a genre of advice that treats every workplace irritation as an unhad conversation. This is proportionality failure, and it makes people dread honesty. Sometimes the right response is to let a minor irritation go — genuinely let it go, not store it. Sometimes it is to ask a factual question, clarify a process, adjust a workflow you control, or request guidance from the person whose job it is to decide.

Sometimes the right response is to write down what happened and keep it. Documentation is not aggression; it is memory that does not degrade, and it is what separates a pattern from a mood if you ever need to show one. And sometimes the right response is to use an established process from the start. A conversation is one instrument among several, and reaching for it every time is not courage — it is habit.

Choose the Setting Before Choosing the Words

People rehearse sentences and neglect logistics, and the logistics do more damage. A few principles hold up well.

Private beats public. Feedback delivered in front of an audience changes what the conversation is: now it is also about face, and the other person is managing the room as well as the issue. Almost nothing about shared work requires witnesses.

Surprises should be small. An ambush produces defensiveness in people who would have engaged willingly with ten minutes' notice. Naming the subject in advance — could we find fifteen minutes about the handoff process — is not weakening your position. It is giving the conversation a chance to be one.

Writing and speaking do different jobs. Speaking gives you tone and the ability to adjust in real time; writing gives precision and a record. Written messages also amplify misunderstanding, because a careful reader can parse one sentence for an hour. A workable default is to say it first and write it down second, when it needs to be remembered or tracked. On distributed teams, where a corridor does not exist, choosing the channel is most of the setting — the conditions around that choice are covered in Connection on Remote and Hybrid Teams.

None of this is a law. There are situations where a public correction is the honest minimum and situations where putting something in writing immediately is exactly right. The point is to choose deliberately rather than discover the setting by accident.

Feedback Between Peers

Most feedback guidance quietly assumes a manager speaking downward. The harder and more common case is raising something with a colleague when you have no authority at all — and it needs its own shape.

The shape is a request about shared work, not an evaluation. Describe the specific behaviour and what it does to the work you share, then make a concrete ask. When the draft goes out before I've seen it, I spend the next day correcting my own section — could I get a look before it leaves? is a request a colleague can say yes to. It describes the observable issue, the effect on shared work, and the change wanted, without rating anyone.

What makes peer feedback curdle is borrowed managerial language. Words like expectations, performance, and going forward imply an authority the speaker does not hold, and the listener hears a performance review conducted by someone unqualified to give one. This is not a nicety. Kluger and DeNisi's meta-analysis of feedback research — hundreds of effect sizes across tens of thousands of observations — found that feedback improved performance on average, but in over a third of cases it reduced it, and the failures clustered where feedback drew attention to the person rather than the task. Feedback aimed at someone's work is a contribution. Feedback aimed at someone's self is a provocation, whatever the intent.

Finally, hold the possibility that you are missing context. The colleague may be working to instructions you have not seen. Asking before asserting is not weakness; it is how a request stays accurate. The ordinary craft of talking with colleagues day to day is the subject of How to Talk to Coworkers; this section is only about what changes when the talk carries a request.

Disagreeing With Someone Above You

Disagreement with a manager is not the same activity as disagreement with a peer, and advice that pretends otherwise is not advice. Research on employee voice — reviewed by Morrison — shows that people weigh the costs and benefits of speaking before they open their mouths, and that silence is common, patterned, and responsive to consequences. In interviews with employees across industries, Milliken, Morrison and Hewlin found people withheld concerns from those above them most often because they expected to be seen negatively — as a complainer, as not a team player — and because they feared damaging a relationship they depended on. These are not irrational reactions. They are readings of incentives.

Two honest principles follow. The first is that you are not obligated to speak. Just be brave is not guidance; the risk of disagreement is real, unevenly distributed, and best judged by the person carrying it. Declining to raise something can be a reasonable decision, and it should be made deliberately rather than by default.

The second is that when you do disagree, form does real work. Questions before challenges, because some disagreements dissolve when you hear the constraint you were missing. Disagreement with the idea, kept separate from any verdict on the person. A private setting rather than a meeting with an audience. And a single clear statement rather than a campaign — a disagreement made well once is a contribution; the same disagreement made weekly becomes a reputation.

When You Are the Person With More Power

Managers and senior colleagues alter a conversation simply by being in it, and no amount of informality switches this off. The asymmetry belongs to the role, not the personality.

The practical consequence is that an invitation to disagree is not evidence that disagreement feels safe. Detert and Burris examined which leader behaviours were associated with employees actually voicing ideas and concerns, across two field studies, and found that people spoke up more to leaders seen as genuinely approachable — general openness signals on their own were not what predicted voice. My door is always open is an invitation. What happens after someone walks through it is the evidence, and the team keeps a careful record of the difference.

This places more responsibility on the person with more power, and it is worth stating plainly: how the first piece of honest disagreement is received teaches the whole team more than any stated value. Ridicule, visible irritation, or a quiet penalty that arrives three weeks later will be remembered long after the open-door policy is forgotten. Retaliation does not need to be dramatic to be instructive.

There is also a limit to what any individual manager can fix by being personally gracious. Whether an entire team believes honesty is survivable — the shared, team-level condition Edmondson's research describes — is a larger subject than one conversation, and this series gives it its own article. What one person with power can always control is the next response they give. Belonging and trust under exactly these conditions are covered in Belonging and Trust at Work.

One more case deserves naming: power is not only formal. The colleague who has been there ten years, the one who trained everyone, the one whose opinion the manager repeats — none of them hold authority on a chart, and all of them can make disagreement expensive for someone newer. If that description fits you, some of this section is yours even though your job title says otherwise.

Intent and Impact at Work

You have heard the slogan: intent doesn't matter, impact does. It is a correction that became a distortion. Both matter, and at work they do different jobs.

Impact is what requires attention. If a comment landed as a slight or a decision cut someone out of information they needed, that effect exists regardless of what was meant, and pretending otherwise because the intent was good is how small injuries become standing grievances. Intent is what explains. It tells the other person what actually happened and whether it is likely to happen again, and ignoring it entirely teaches people that nothing they mean is ever relevant — which makes honesty expensive.

Stone, Patton and Heen's framework — a practitioner model, not a scientific one — separates these conversations usefully: what happened, what it meant to each person, and what each person contributed. The general mechanics of navigating that territory belong to How to Have Difficult Conversations. The workplace-specific point is smaller: in a continuing professional relationship, a repair that acknowledges the impact while taking the intent seriously is the one that lets both people return to normal.

Listen for the Part You Might Be Missing

One short discipline, because the listening skills themselves live elsewhere. Workplace disputes are unusually rich in missing information, for structural reasons: people occupy different roles, see different parts of the same process, receive different instructions, and are rewarded for different priorities. The colleague whose behaviour looks careless may be responding rationally to a constraint you have never been shown.

Before concluding anything about a person, check what their position lets them see that yours does not. The craft of doing that — listening so someone feels heard, and asking questions that surface what you are missing — is covered in How to Listen So People Feel Heard and How to Ask Better Questions. Here it is enough to keep one question in reserve for every difficult conversation: what would have to be true for their version of this to make sense?

Repair Is Different When You Still Work Together

Most advice about difficult conversations ends at the conversation. At work, the conversation is the middle. What makes workplace repair distinctive is that it has to produce a functioning arrangement between two people who will keep meeting — in calendars, in documents, in decisions — whether or not warmth ever returns.

Repair, in this setting, is mostly behavioural. Acknowledging what happened rather than letting it become unspeakable. Correcting the misunderstanding where it needs correcting. Making one specific change and following through on it, visibly, because follow-through is the only part anyone else can verify. Checking later whether the working arrangement actually improved, briefly and without ceremony. Then allowing normal professional interaction to resume — the same meetings, the same small questions — without demanding emotional closeness as the price of peace.

This is a place where trust theory earns its keep without being retaught: trust between colleagues is rebuilt through repeated small predictions confirmed, not through a single sincere conversation. The fuller account is How Trust Is Built. The workplace version is simply that the weeks after the conversation are the conversation, read by everyone involved.

When the Conversation Doesn't Fix It

A conversation is not magic, and honesty about its limits is part of handling it well. Some situations do not yield to one: behaviour that continues after it has been clearly raised, requests that are acknowledged and quietly ignored, problems created by incentives or structures neither of you controls, and power differences too large for a direct conversation to bridge safely.

There is also a category of conduct that should never have been routed to a private conversation in the first place. Some workplace problems need a process, not another heart-to-heart, and treating them as interpersonal misunderstandings protects no one — least of all the person being harmed. If an issue involves harassment, discrimination, retaliation, threats, or your safety, the appropriate next step is the channel your organisation maintains for exactly this, or qualified outside support. This article is educational; it cannot assess any specific situation, and it is deliberately not legal or HR advice.

Process matters in the less dramatic cases too. Colquitt's validation research on organisational justice confirmed that employees judge fairness along distinct lines — the outcome, the procedure that produced it, and how they were treated and informed along the way. People can accept an outcome they dislike when the process was straight and they were treated with respect. They rarely accept the reverse. Whatever route a problem takes, how it is handled is itself part of what gets judged.

A Fika Pause Framework for Honest Conversations at Work

Everything above in six moves. This is a Fika Pause editorial framework — a practical sequence, not a validated scientific model — and it is meant to be run through slowly, not recited.

1. Notice. What actually happened, in observable terms — separated from the story you have been rehearsing about it.
2. Place. Is a direct conversation the right instrument at all, or does this belong to a question, a process change, documentation, or a formal channel?
3. Power. What does each person's role change about how the same words will land — including your own role, which you are the worst placed to see?
4. Say. Address the specific thing clearly, as a request about shared work rather than a verdict about a person.
5. Hear. What might their position let them see that yours does not? Leave room for the answer to change your mind.
6. Repair. What happens after — the change made, the follow-through, the return to ordinary professional contact.

If a step reveals that a conversation is not the right instrument, the framework has already done its work. Noticing that early is most of the skill.

Practising This Week

Do not practise on your hardest unresolved conflict. Choose something small — a minor friction you would normally let pass — and run it through the thinking, not necessarily the conversation.

Where This Fits in the Workplace Connection Series

This series has been building one argument in stages. Why Connection at Work Matters made the case; Belonging and Trust at Work covered what those words mean under hierarchy; How to Talk to Coworkers, Making People Feel Welcome at Work, and Workplace Rituals That Last handled the ordinary conditions; Connection on Remote and Hybrid Teams took the same questions across distance. This article is about what happens when something real is at stake between people who still have to work together.

One article remains between here and the capstone. The next steps up from the individual conversation to the team-level condition that decides whether honesty is survivable at all — psychological safety, which this article touched and deliberately did not teach — and the final article turns to anyone shaping a whole workplace rather than a single relationship. The series page lists everything in reading order, the Fika Pause Learning Path shows where this sits in the wider library, and for the conversational mechanics underneath all of it, the Conversation Skills capstone is How to Have Better Conversations.

Knowledge Check

Frequently Asked Questions

The questions below are the ones most often asked about honest conversations between colleagues. Where the full answer belongs to another guide — the general mechanics of difficult conversations, listening, questions, or trust — the answer here stays short and points to the article that owns it. Nothing here is legal or HR advice.