# How Teams Turn Workplace Disagreement Into Better Decisions - Published: 2026-10-26 - Author: [Economist Zone](https://economistzone.com/author/economistzone-com.md) - Topics: [Q&A](https://economistzone.com/qa.md) - Source: https://economistzone.com/qa/how-teams-turn-workplace-disagreement-into-better-decisions/ - Publisher: Economist Zone ### Surface Risks, Then Assign Authority Rick Elmore, CEO, Simply Noted. With experienced people, disagreements are rarely about facts. They are usually about different risks each person is trying to avoid. What I do: ask each person to state what they are worried will happen if their option is not chosen. That moves the conversation from "my plan versus yours" to "what are we protecting," and often a third option shows up that covers both concerns. Then I set a decision rule before debating further: who decides, by when, and what data would change the answer. If it is a reversible call, we pick one and run it as a small test with a clear review date. If it is hard to reverse, I take more time but still name the decision owner. Trust is preserved when everyone knows they were heard and knows how the decision was made, even when they disagree with the result. I have seen teams recover from a lost argument far faster than from an unclear one. --- ### Run a Private Reversal Exercise Before deciding, we use a written reversal test where each person privately answers what evidence would change their mind and what would not. This helps prevent people from defending their public positions simply because they have already stated them firmly. The goal is not to make everyone agree. Instead, it shows that every viewpoint should have clear standards for being challenged. When we compare responses, we can see whether new information could resolve the disagreement or whether it reflects different judgments. If judgment is the issue, we make the decision and record our reasoning. We also set a time to review it. People are more likely to accept an outcome they dislike when the process makes their thinking visible and allows fair reconsideration. --- ### Resolve Gridlock Through a 30-Day Pilot A difficult disagreement becomes manageable once the team separates a decision from an identity statement. Leaders often treat one choice as proof of who was right, which invites defensiveness. In business, the better question is whether a decision can be designed to teach quickly without creating damage the organization cannot absorb. I helped resolve a stalemate by replacing a launch debate with a 30-day experiment. The team agreed on audience, ceiling, threshold, and shutdown trigger before work began. Both sides saw their concern represented in the design. A reversible test gave people permission to support a path they would not have chosen, because learning rather than victory became the shared objective. --- ### Clarify Duties, Then Close Deliberation When experienced colleagues disagree, I recommend asking each person to define the responsibility behind their position before debating solutions. In behavioral health, two sound recommendations can reflect different duties: protecting client experience, supporting clinical judgment, maintaining workable operations, or managing immediate risk. Naming those responsibilities changes the discussion because it shows what each colleague is trying to protect without reducing the issue to personality or authority. Then identify which responsibilities are nonnegotiable, which tradeoffs are acceptable, and who has the appropriate role to make the final decision. The decision-maker should close the discussion by stating the choice, the concerns incorporated into it, the safeguards required, and whether and when the decision should be reviewed. Continuing to debate after the decision can weaken accountability, while closing without acknowledging substantive concerns can weaken trust. One practice I recommend is giving each colleague a final risk statement before the decision is closed. Each person names the consequence they are most concerned about and one practical safeguard that could reduce it. The decision-maker does not have to adopt every safeguard, but should respond to each material concern and explain what will be incorporated. This helps preserve trust because disagreement was considered on its merits, not treated as resistance. It also gives the team specific protections to monitor during implementation instead of leaving concerns unresolved. --- ### Weight Criteria Via Neutral Facilitation I recommend starting by agreeing on the result the decision must produce, then turning that result into three or four job-related criteria. Before anyone argues for an option, the group should decide how those criteria will be weighted. Each proposal is then evaluated against the same standard, with evidence separated from preference and any material uncertainty stated plainly. This prevents the discussion from becoming a contest over confidence, tenure, or presentation style. If no option clearly leads, identify the criterion creating the tie and gather only the information needed to resolve it. Set a deadline, name the person responsible for the final call, and explain the choice against the agreed criteria. That gives everyone a clear account of how the decision was reached and how their substantive concerns were considered. One practice that has helped is using a neutral facilitator for the final decision meeting. The facilitator should not be responsible for advocating either proposal and should manage equal speaking time, keep comments tied to the agreed criteria, and pause the discussion if it becomes personal or repetitive. That person should not choose the winner. Their role is to protect the quality of the conversation while the designated decision-maker weighs the substance. This separates process authority from decision authority, allowing disagreement to remain direct without becoming a judgment about either colleague. --- ### State Regrets and Argue Both Sides I make everyone state the decision they'd regret most, not the one they prefer. Preference arguments go in circles because two smart people can both be right about what they've seen. Regret forces specifics. One person says they'd regret burning six weeks of runway on a channel nobody can measure. Another says they'd regret losing the window entirely. Now we're arguing about actual risks instead of taste. Then I ask what would have to be true for the other person's view to be the correct one. The people in my masterminds who have been running companies for a decade usually answer that honestly, and most of the time they find the condition is testable. If the test is cheap, we run it. If it isn't, somebody owns the call and the rest of us back it in public. In the masterminds I run, that second question does most of the heavy lifting. Arguing for someone else's position for two minutes makes it hard to keep treating them as the obstacle. Trust survives because nobody had to be wrong. The conditions changed, or we learned something, or one person had the authority and used it. What kills trust is a decision that gets made quietly after the meeting, where the person who lost finds out secondhand and never got to say what they feared. --- ### Let Metrics Settle the Dispute The practice that turns competing opinions into a decision is agreeing first on what we are measuring, then letting the numbers argue instead of the people. When I ran my NBN telecom company, my most experienced people regularly disagreed on how to approach a hard area, such as whether to send a full civil crew first or start with jointing. Both sides were usually right about something. So before anyone defended a plan, we agreed on the outcome that mattered, which was work signed off with no rework and the crews paid, and then each person laid out how their approach hit it. That shifted the conversation from who was right to which plan was most likely to get the work approved. When it was still close, I made the call, explained it, and committed to reviewing the result after a set period, so whoever disagreed knew their view would be tested rather than dismissed. I never asked anyone to do something I would not do myself, which kept trust intact even when I overruled them. Agree on the scoreboard, give each view a fair test, and have one person own the decision. --- ### Draft the Buyer's First Experience When my team splits on something important, I stop the debate and make us write the customer's experience first. One paragraph, present tense, describing what the person opening the box sees and does. Nobody gets to argue their position until that paragraph is agreed on. The reason is that most senior disagreements on my team aren't really about the decision. They're about two different pictures of who we're serving. Operations is picturing a repeat buyer who knows the routine, and marketing is picturing someone nervous about doing this at home for the first time. Both people are right about their own customer and talking past each other. Once the paragraph is written, the options sort themselves out, because one of them serves the person we just described and the others don't. The argument moves off who is smarter and onto whether we described the customer correctly, which is a question anyone can be wrong about without losing face. I have whoever disagreed most strongly write the first draft of that paragraph, since they've thought hardest about the risk. If their version of the customer survives scrutiny, we go their way. If it doesn't, they've talked themselves out of it in their own words, and nobody had to overrule anyone. --- Deleted by user --- ### Use a Weighted Impact Matrix To achieve a constructive way to move forward from the discussion among different views, it is necessary to eliminate ego from the discussion by focusing on agreed performance indicators. While carrying out workflow reformations, I often come across the problem of opposition coming from senior executives where one of the parties is considered as a representative of system security and vice versa. When both parties are arguing with an intention of performing the best job possible but due to the differences in their goals, all discussions eventually remain fruitless. It is a common practice for me to suggest stopping the discussions and defining one or two common indicators of success of a project. For instance, if we are seeking to automate the process of processing large amounts of documents for banks, I suggest having the rate of documents done within one hour of the delivery as the common indicator. From that moment on, it becomes possible to evaluate each idea against that indicator instead of arguing among each other. One of the practices that keeps trust in the teams under my guidance in spite of the challenging decision-making process, is the application of Impact-Weighting Matrix. When it comes to making a decision that implies a risk, we start from identifying the objectives we have, say, compliance with regulations, avoiding churn, and high speed of implementation, having assigned numeric weights to the objectives based on the overall strategy of the company. Once we reach the peak of disagreement, we score each of the suggestions based on the previously defined weights. Thus, the whole process turns from the struggle about possession of the truth into having collaborative efforts to model the data, as now a person whose opinion was ignored realizes that their opinion has not been dismissed, it was just following the rules of the business model. --- ### Align Choices Around Customer Needs "As a founder, operator, and startup advisor, I've learned that experienced people usually don't disagree because one person is right and the other is wrong. They disagree because they're solving for different risks, timelines, customers, or constraints. In building Steven Mitts Services and advising early-stage founders, I've seen this show up most often when a team is deciding what to build next, which customer to prioritize, or how quickly to push a product into market. When disagreements arise, I try to slow the conversation down before pushing toward a decision. The framework I come back to is this: let every serious viewpoint be heard, then move the discussion back to three questions — what are we trying to protect, what are we trying to learn, and what does the customer need from us right now? That shift moves the room from personal opinions to shared decision criteria. It also preserves trust. People can support a decision they did not originally agree with when they believe the process was fair, the tradeoffs were made visible, and their concerns were taken seriously. This matters in entrepreneurial work because speed is important, but false alignment is expensive. A founder can force a decision and get temporary momentum, but if the team leaves the room unclear or unheard, execution usually suffers later. Healthy disagreement is not a threat to progress; it is often the raw material for a better strategy. The leader's job is to turn that disagreement into clarity: name the risks, choose the clearest path forward, explain why, and keep learning from the market. That is how teams move from debate to execution without losing trust." — Steven Mitts, Founder & CEO, Steven Mitts Services --- ### Solicit Silent Written Views A useful practice is silent writing before group discussions. Everyone takes time to note their recommendation, the evidence supporting it, and what might change their mind. This prevents the first speaker from shaping the discussion and gives quieter, thoughtful people room to contribute. It also allows everyone to form an opinion before hearing others. The notes are then read before anyone defends a position. The group identifies common ground first, then examines the assumptions that cause disagreement. Discussions become less personal when people question written assumptions instead of challenging a colleague's judgment. Each meeting ends with a clear owner, a decision date, and a shared explanation, building trust through consistency even under pressure. --- ### Prioritize Client Facts I try to move the discussion from what each person believes to what clients actually need. Experienced people usually have good reasons for their opinions, and those reasons deserve a real hearing. But when the conversation comes back to the people we serve, the right path often becomes much clearer. Moving to a free model during COVID was a big decision, and there were different perspectives on changing a model that had worked for us. Charging up front had always been part of how we operated. But when we looked at what clients were facing, the situation became clearer. Events were canceled, budgets were uncertain, and many groups didn't have $499 to put down before trying an online auction. Other platforms had already started offering free services, which added to the case for making the change. Looking at these realities helped us agree on a direction, and it has worked out really well. The practice I'd recommend is bringing real client evidence into the room and letting it carry weight. It keeps the discussion focused on solving the problem rather than defending individual opinions. --- ### Convert Dissent Into Safeguards I have seen trust strengthen when leaders make room for principled dissent without allowing disagreement to become permanent gridlock. The key is to show that challenge is valuable before the decision, while commitment is essential after it. Both expectations must be explicit. One practice that made this possible was a closing round called "what would make this work." After a decision, every participant named one action, safeguard, or communication step that would improve the chosen path. Critics often contributed the most useful protections because they had examined the weaknesses closely. Their concerns became part of execution rather than evidence of opposition. That approach preserved candor, gave the decision practical support, and reminded the team that trust is built through follow-through. --- ### Shrink Commitments and Keep Records We look for the smallest decision hidden within the largest argument. Senior teams often debate broad questions about pursuing a new direction when the immediate choice is whether to test demand first. Breaking the issue into a smaller commitment reduces defensiveness and provides useful information. This helps us move beyond opinions and make better decisions. We end disagreements with a decision log that records the choice, the owner, the assumptions, and the review date. This practice is not bureaucracy but a way to protect trust. When outcomes are known, memory can become selective, so we review past assumptions instead of blaming individuals. This builds a culture where thoughtful risks are welcome and decisions can be revised without fear. --- ### Expose Your Proposal's Weakness When experienced colleagues disagree, I first narrow the discussion to the precise point that remains unresolved. A conflict may involve disputed facts, a difference in priorities, or concern about implementation. Those are different problems and should not be handled as one broad disagreement. Disputed facts call for better information. Competing priorities require a clear decision about the tradeoff the organization is prepared to make. Implementation concerns require defined safeguards, responsibilities, and checkpoints. I ask each colleague to state which type of disagreement is driving their position and what specific information or condition could change their recommendation. That keeps the conversation focused on the decision rather than the people advocating for each option. Once the remaining issue is clear, the group can document the choice, the rationale, and the conditions that would justify revisiting it. One practice I've found helpful is asking each colleague to identify the strongest weakness in their own recommendation before responding to anyone else. This can make intellectual honesty reciprocal. It also gives people permission to examine risk without treating questions as personal criticism. The discussion becomes more balanced because each position is presented with its limitations, not merely its advantages. Trust can be preserved when colleagues can see that their concerns were examined seriously, even if the final decision differs from the outcome they preferred. --- ### Frame Trade-Offs in Small Groups As CEO, when experienced colleagues disagree I begin by clearly framing the rationale and the decision criteria, then hold scheduled small-group conversations after that initial framing to surface questions and concerns. Those small groups let people explain assumptions, identify gaps, and turn competing opinions into specific trade-offs we can evaluate. We document remaining unknowns and the criteria we will use to decide so the path forward is explicit. This practice preserved trust by giving people a respectful forum to be heard and by showing how decisions would be made. --- ### Gather Anonymous Pre-Reads Trust is usually damaged before the meeting, when colleagues arrive having built private constituencies around a preferred answer. That is common in organizations with specialist leaders, because each function sees a different portion of the workflow. The remedy is to surface reasoning early enough that people can challenge it without performing for an audience. One practice was a written pre-read with anonymous comments before the decision meeting. I watched quieter experts raise dependencies missed in live debate, especially handoffs and approval delays. The meeting focused on unresolved facts, not speaking confidence. A named owner recorded why alternatives were declined. That record prevented relitigation and showed contributors their input affected the outcome. --- ### Assign One Owner Up Front When experienced people disagree, I try to get the argument out of the meeting and onto the brief. Most disagreements I see in production are between people who are each right about something. On one multi-city project, one city's crew captured how a product fails in the field and how the team fixes it, while another city shot a clean, polished script. Same brand. Review turned into a debate over which story was allowed to ship. Nobody was wrong. We just had no agreed standard for what proof the piece needed to carry. So the first move is to write down the question we're actually deciding and what the decision has to protect: the claim legal will accept, the customer we're trying to convince, the delivery date. Once that's on paper, opinions turn into tradeoffs people can compare. The practice that does the most to keep trust intact is naming one decision owner in writing before the work starts. A department doesn't count, and neither does a group thread. When that line is blank, you end up with three owners in three channels around the second round of revisions, and none of them can close it. When the name is there, everyone still gets heard, and people know who makes the call. In my experience, senior people accept a decision they argued against much more easily when the process was clear before anyone had a stake in the outcome. I also try to separate the person from the position. If someone pushed hard for the other option, I want them to see that their concern made it into the plan, even if their option didn't. --- ### Pressure-Test Assumptions and Mirror Positions When experienced colleagues disagree, I move the conversation away from defending complete proposals and toward testing the assumptions beneath them. I ask each person to name the facts their recommendation depends on, what remains uncertain, and what outcome would show that the choice was wrong. Then I separate reversible decisions from choices that would be difficult to undo. When the decision is appropriate for a limited test, a defined pilot with a clear endpoint can replace speculation with evidence while established safety, clinical and compliance procedures remain in place. If it is not, the group should spend more time pressure-testing assumptions and planning safeguards. The path forward is either the smallest appropriate test or, for an irreversible choice, the option whose downside can be managed within established procedures. This gives disagreement a useful role without making consensus a prerequisite, and colleagues can support implementation without pretending their original judgment changed. One practice I recommend is requiring each colleague to summarize the other position until the other person confirms that the summary is accurate before responding. The summary should include the proposal, the concern behind it, and the tradeoff the colleague is willing to accept. This is not an exercise in agreement. It confirms that the disagreement is understood accurately and can expose assumptions that were implicit. Once both summaries are accepted, discussion focuses on the actual difference rather than correcting mischaracterizations. Trust is preserved because each person sees that their reasoning received serious consideration. --- ### Write Independently for Better Debate Verbal debates often reward speed and status, which can distort decisions when experienced colleagues are involved. We ask everyone to write their answers to the same question before anyone speaks. This simple practice gives each person time to think without being influenced by others. It also helps reveal whether disagreements concern the goal, expected results, or acceptable risks. During a difficult planning discussion, we found that everyone agreed on the desired outcome but had different levels of confidence in the timing. This made the solution clear, as staged checkpoints were more suitable than a single commitment. Trust remained strong because nobody had to abandon a carefully presented argument. We realized the group had been debating different factors rather than the same issue. --- ### Map Organizational Effects When experienced colleagues disagree, I move the conversation to an Impact Mapping exercise that answers Who, What, When, and Why. We place roles and system overlaps on an org-chart view so opinions are tied to concrete impacts and ownership. That shifts debate into trade-offs with named owners and clarifies how messages must be relayed, which preserves respect for each perspective. In my experience, using Impact Mapping reduced surprises, increased adoption through trust, and created a clear path forward. --- ### Anchor Rebrand Plans to Common Outcomes When experienced colleagues disagree, I return to the shared outcome rather than ask whose proposal has more support. Each person explains how their preferred option advances that outcome, which constraints it respects, and what tradeoff it requires. I identify agreed points that can become decision criteria. In web design, those criteria might include the intended user experience, technical feasibility, timing, and the client's stated goals. The person responsible for the decision should weigh each option against those criteria, make the call, and explain why. Clarity matters, but so does preserving each colleague's ownership of implementation. A decision should not turn one person into the winner and another into the obstacle. Experienced people can disagree strongly and still contribute their best work when the reasoning is clear and their expertise is considered. One practice I used during DIGITECH Web Design's rebranding effort was putting the shared outcome in writing before evaluating competing ideas. We gathered the team to define what the rebrand needed to accomplish, so everyone was working from the same reference point rather than defending individual preferences. When opinions differed, we evaluated each alternative against those agreed goals in the room. The final decision did not necessarily match every person's preference, but each colleague could see how their input was considered and why the chosen direction best fit the agreed criteria. That helped preserve trust while still allowing a clear decision to be made. --- ### Validate Workflows Against Real Tasks I move the discussion toward the conditions the decision must satisfy. Experienced colleagues can both be right about different failure modes: one wants visibility and accountability, while another wants to avoid unnecessary interruptions. We had that tension in a Market Brew engineering discussion about deployment QA. A colleague challenged how much process a small development check needed. I walked through the intended developer-testing mode: name yourself as the tester, keep the change tracked and avoid putting the task into another person's testing flow. The colleague said that made more sense once the end result was explained. The practice is to test the process against a real task. Can the developer complete the check without an unnecessary handoff? Can the team still see who owns the change and what was tested? Those questions give competing opinions something concrete to evaluate. I think trust is easier to preserve when the discussion produces a clearer decision instead of a winner. Keep the legitimate constraint behind each objection, make the chosen path explicit and identify what evidence would justify revisiting it. --- ### Ask What Evidence Changes Minds Before the argument goes any further, I ask each person what they would need to see to change their mind. That moves the conversation from defending positions to naming evidence, and quite often both sides discover they're waiting on the same missing fact, which someone can go and find. If nothing could change either view, it's a judgment call, so we agree who makes it and by when, and the person whose view didn't win can put their objection on record without having to pretend they agreed. ## Related - [How Leaders Resolve Competing Project Priorities](https://economistzone.com/qa/how-leaders-resolve-competing-project-priorities.md) - [Hybrid Work Leaders Share Practical Rules That Improved Office Days](https://economistzone.com/qa/hybrid-work-leaders-share-practical-rules-that-improved-office-days.md) - [Hybrid Work Norms That Cut Meetings and Boost Focus](https://economistzone.com/qa/hybrid-work-norms-that-cut-meetings-and-boost-focus.md) - [How to Get Delayed Cross-Functional Projects Back on Track](https://economistzone.com/qa/how-to-get-delayed-cross-functional-projects-back-on-track.md)