# How Professionals Turn Workplace Disagreements Into Better Decisions - Published: 2026-10-26 - Author: [Terkel](https://pursuethepassion.com/author/brett.md) - Topics: [Expert Roundups](https://pursuethepassion.com/topics/expert-roundups.md) - Source: https://pursuethepassion.com/how-professionals-turn-workplace-disagreements-into-better-decisions/ - Publisher: Pursue The Passion ## How Professionals Turn Workplace Disagreements Into Better Decisions Workplace disagreements can lead to stronger decisions when teams focus on evidence, shared goals, and practical tests. Experts in the field share proven ways to turn conflict into useful action, from comparing data to testing competing ideas. These strategies help teams address concerns, reduce ego, and choose solutions with greater confidence. - Have Managers State Each Other’s Cases - Empower Critics to Run Pilots - Let Traffic Select the Stronger Design - Use Pre-Mortems to Forge Hybrid Solutions - Compare Twin Unit Budget Figures - Invite Colleagues to Explain Concerns - Check Codes on Joint Site Visits - Acknowledge Expertise Through User Research - Inspect Homeowner Priorities Onsite - Prioritize Adolescent Welfare Above Ego - Anchor Family Conflict in Brand Stewardship - Convert Deadlocks Into Time-Bound Experiments - Validate Invoice Logic Through Sandbox Checks - Demonstrate Process With Concrete Tasks - Match Security Deployment to Incident Logs - Address Disputes Privately With Practical Options - Chart Canine Triggers for Flexible Progression - Base Audio Layouts on Guest Coverage - Define Common Goals and Ethical Costs - Review Service Notes for Reliable Comfort - Ask Which Clue Alters Advice - Elevate Patient Evidence Over Clinical Pride - Separate Egos From Investment Choices - Serve Client Needs, Then Commit - Restate Views, Then Measure Outcomes ### Have Managers State Each Other’s Cases Good leadership is not about winning arguments. It's about making sound decisions while maintaining people's trust in you. Last month I was faced with mediating between two of our regional managers who were in heated disagreement over a potential restructure in relation to our staffing complement across our campuses. Before I allowed either of them to table their case, I asked them to first write up the case as perceived by the other. Only then were they able to present their own argument. It's awkward at first but I found that the managers appreciated one another's points of view and it took the heat out of the situation. By writing out their colleague's argument they had to delve deeper into the other's perspective and it made the discussion less personal. We were able to focus on our common goals and use objective data to make a decision regarding the restructure. Afterwards the two managers sat down together and had a good laugh over lunch. Despite disagreeing strongly about rosters, their relationship is intact. --- ### Empower Critics to Run Pilots I give the person who disagrees with me control of the test. When we replaced a shared support inbox with a proper helpdesk, the strongest objection came from the colleague who had run that inbox for years and knew every workaround. Arguing would have won the meeting and lost the rollout. So he got the pilot: two weeks, his queue only, his rules for routing, and the right to call it off. He did not call it off. The system did the sorting he had been doing by hand, and when he said "this is better" to the team, I never had to sell it again. The disagreement turned into a better outcome because it stopped being a debate and became an experiment, with the skeptic holding the controls. People resist change they cannot influence. Give the most credible critic authority over the trial and you get an honest test and a spokesperson you could never have hired. --- ### Let Traffic Select the Stronger Design We disagree about what the best version of a law firm's website intake page is, my co-founder and I each build our version, and we test both with live traffic. We let the data make the decision. After 3 weeks my co-founder's version won out with 22% more form submissions. At our next team meeting I let the team know that my co-founder's version won the test, and I lost the argument. After 15 years in legal marketing, I can tell you that losing in front of the team didn't cost me a thing. My co-founder is just as engaged as ever and brings disagreements to me sooner, not later. It's all about maintaining a positive working relationship. --- ### Use Pre-Mortems to Forge Hybrid Solutions When arguments get stuck, I go back to the numbers. What actually keeps uptime higher? What do users click more? We fought for weeks over a predictive ads rollout. Neither side would budge. So we ran a pre-mortem, imagining how each approach could fail. That killed the either-or framing and got us to a hybrid that outperformed both originals. Data cuts through the noise. --- ### Compare Twin Unit Budget Figures When we couldn't agree on renovation budgets, I suggested testing both approaches on two similar units side by side. The market answered for us. Hard to keep arguing when you have actual rent rolls to compare. After that, budget calls got way easier because we both trusted what the numbers said over our own hunches. --- ### Invite Colleagues to Explain Concerns When I disagree about a clinical protocol or training method, I ask my colleague to walk me through their thinking. I reflect back what I heard, especially their 'what ifs' about patient safety, then add my take. Once this turned a heated debate into an actual fix for our safety curriculum. Curiosity over certainty, every time. --- ### Check Codes on Joint Site Visits When a contractor and I disagreed on a standpipe flow test, I asked them to walk the site with me and check our findings against the actual NFPA and local code. Not a debate. Just two people looking at the same thing at the same time. Safety stays the priority, and this way neither of us is guessing. Beats arguing over email. --- ### Acknowledge Expertise Through User Research I've learned that when a colleague has clinical expertise I don't, saying that upfront changes the whole conversation. We were stuck on a feature decision recently, and I suggested we just test both approaches with a small user group. Turns out neither option won outright. We ended up combining elements from both. Small tests like that take the pressure off disagreements and give you actual data to work with. --- ### Inspect Homeowner Priorities Onsite When we disagree on a big call like upgrading a furnace, I'll pull everyone on-site for a quick walk-through. We talk through what the homeowner actually wants, compare safety, efficiency, and cost, and hash it out before we decide. Focusing on specifics instead of the argument usually gets us to a better answer than any of us started with. --- ### Prioritize Adolescent Welfare Above Ego When a colleague and I can't agree on a treatment plan, I bring the focus back to the adolescent's goals. I ask each of us to explain our assessment and the risks we're concerned about. Usually we find a combined approach that's safer for the kid. Putting their safety over being right has kept working relationships going and led to better outcomes. --- ### Anchor Family Conflict in Brand Stewardship In a family business you can't win an argument and walk away, because the person you disagreed with is at the next holiday dinner, so I've learned to argue about the decision and never about the person. The approach that helps most is agreeing first on what we're both protecting, which for us is usually the customer who has trusted the brand since my father started it, and then letting the disagreement be about how to protect it. Once we're arguing about the same goal, the better idea usually wins on its own, and nobody has to lose face for it to happen. After more than 20 years in our family's company, I'd say a working relationship survives disagreements that are about the work and breaks on the ones that turn personal. --- ### Convert Deadlocks Into Time-Bound Experiments I treat disagreement as a design problem: clarify the shared goal, separate opinions from facts, then choose a time-bound experiment to test the better idea. I start by restating the other person's view to ensure I've understood it, surface the assumptions behind both positions, and agree on success metrics we can measure quickly. On several product and marketing decisions at Cyber Techwear this method let us move from gridlock to a small pilot, learn fast, and decide with data rather than ego, preserving trust and improving the outcome. --- ### Validate Invoice Logic Through Sandbox Checks The worst approach when it comes to handling any conflict in the workplace is treating it like a battle of confidence. As the creator of Fleeter.ai, I have understood how important it is to divert the conversation from confidence into evidence that may help in reaching a conclusion. A case in point would be a conflict around the shipment of the invoicing update. In this case, the developer thought that the code was fine while I was concerned about how the updates on wait time, gratuity, and the driver payout could impact real-life bookings. We created the same workflow in staging, cross-checked the totals and discovered one edge case which we were able to fix prior to release. The most valuable lesson I learned, was that I did not feel the need to win the battle to save the company anymore. Instead, I began trying to find a test that would convince both parties involved in the dispute. --- ### Demonstrate Process With Concrete Tasks I try to understand the cost my colleague is pointing out before defending my design. A disagreement often becomes more useful when we walk through one actual task instead of debating the process in the abstract. In an engineering discussion at Market Brew, a colleague questioned whether a deployment QA workflow was too opinionated for small development tests. I explained the developer-testing path: the developer could name themselves as the tester, keep the work tracked and avoid routing that small check through someone else's testing queue. The colleague said the workflow made more sense once the intended end result was clear. The useful outcome was a shared understanding of the path and its purpose. I would not describe that conversation as proof of faster delivery or universal adoption. It showed that an objection to unnecessary handoffs could coexist with the need to track what changed. My takeaway is to treat the objection as information about the workflow. Show the smallest concrete example, clarify what must remain true, and leave room to change the design. People can challenge a process without having their competence or motives put on trial. --- ### Match Security Deployment to Incident Logs As the Operations Manager at Elite Security in Las Vegas, I regularly coordinate assignments alongside experienced law-enforcement professionals where operational viewpoints can clash. When disagreements arise, I steer the focus away from personal preferences and back to objective risk assessments, like access points and site traffic patterns. For instance, when team members disagree on whether a client needs a static post or mobile patrol sweeps, we evaluate real-time data from our digital incident logs and field tablets. Looking at verifiable activity helps us structure coverage objectively instead of debating assumptions. Reframing the discussion around practical post orders and real-world conditions keeps working relationships intact. It turns a potential conflict into a collaborative effort that delivers a safer, more reliable deployment. --- ### Address Disputes Privately With Practical Options Over 25 years of managing more than a billion dollars in critical hospital construction, I've seen that high-stakes disagreements are inevitable. Protecting the relationship starts by pulling the conversation into a private, closed-door one-on-one rather than debating in front of the wider team. I treat that space as a two-way dialogue where their read on the issue matters just as much as mine. Naming the hard point as an investment in the shared outcome rather than a personal critique prevents defensiveness and keeps trust intact. From there, we focus on accountability without blame, putting two or three practical options on the table to evaluate together. Disagreements turn into better results the moment both people focus on solving the project's problem instead of trying to be the hero who wins the argument. --- ### Chart Canine Triggers for Flexible Progression In running Free Reign K9 with my partner Damian, we often differ on the exact starting point for a dog with reactivity or fear issues. Our shared evaluation process forces us to lay out the dog's specific temperament and past responses before choosing tools like prong collars or slip leads. One case involved a German shepherd where I favored extra decompression weeks and Damian wanted to introduce corrections sooner. We each pulled from our separate hands-on cases to map the dog's triggers step by step. Combining the two views produced a clearer progression that kept the owner involved from the first session onward. The dog reached reliable off-leash control on trails faster because the plan stayed adaptable instead of locked to one method. --- ### Base Audio Layouts on Guest Coverage Running Blue Ridge Sound requires aligning teams around venue layouts, power access, and run-of-show needs for every wedding or event we staff. When a colleague and I differ on system placement, we anchor the talk in the confirmed guest count and coverage zones rather than preferences. This keeps the focus on execution. One time a question about subwoofer array spacing led us to map audience geometry first, which produced cleaner transitions between ceremony and reception. The same habit carries into STANDBY Local when we automate workflows. Disagreements become tests against actual client timelines, and the stronger process usually emerges from that check. --- ### Define Common Goals and Ethical Costs As CFO at Cool Masters Services, I'm often in decisions where customer trust, cash flow, rebates, financing, and operational reality all collide. My rule is: name the shared goal first, then debate the path. If I disagree with someone, I try to say, "Here's what I think you're protecting, and here's what I'm protecting." That keeps it from becoming personal and turns it into a tradeoff discussion. One example: we've had conversations about promoting energy rebates up to $14,000. I pushed for making sure rebates never became a pressure tactic, so the better outcome was messaging that still highlights savings but stays grounded in honest system evaluations. Another useful question is: "If we're wrong, who pays the price?" In HVAC and plumbing, the answer is usually the homeowner, so that question quickly moves the room away from egos and toward the most ethical decision. --- ### Review Service Notes for Reliable Comfort With over 30 years in HVAC and running my own company for more than 15 years, I make daily calls with technicians on repairs, installations, and plumbing upgrades across Middle Tennessee homes. When views split on a service approach, such as pushing a whole-home dehumidifier versus addressing just the AC coils for a sticky-house complaint, I have each tech walk through the exact homeowner outcome using our past service notes. This keeps the talk on the shared priority of reliable comfort and the 12-hour response promise instead of personal angles. The result is usually a clearer plan that cuts repeat calls and strengthens how the crew works together on the next job. --- ### Ask Which Clue Alters Advice As a board-certified foot and ankle surgeon and practice owner, I make decisions where disagreement can mean imaging vs injection vs surgery. My rule is: argue the mechanism, not the person--what tissue is involved, what evidence do we have, and what risk are we accepting if we're wrong? When a cortisone shot doesn't resolve heel pain, clinicians may split on repeating it or changing course. I slow it down by asking what the failed treatment taught us: if inflammation isn't the main driver anymore, we may need to address chronic tissue degeneration instead of just "more anti-inflammatory." With surgical decisions, I welcome a second opinion rather than treating it as a challenge. One toe surgery patient did that, the independent surgeon agreed with the plan, and it actually strengthened trust instead of weakening it. The practical phrase that helps most is: "What finding would make you change your recommendation?" That turns disagreement from a status contest into a shared search for the next useful piece of information. --- ### Elevate Patient Evidence Over Clinical Pride Thirty years of running my own practices taught me that most workplace disagreements aren't really about the decision on the table -- they're about whose clinical judgment gets trusted. I learned early that if I made the disagreement about me versus them, I'd win the argument and lose the relationship. The shift that worked for me was making the patient the third voice in the room. When a colleague and I clashed over how to sequence a complex case -- whether to address gut inflammation or hormonal disruption first -- I'd bring the actual clinical picture back to center. "Here's what the patient's data is telling us. What does this change for your thinking?" That reframe moves it from competing opinions to shared problem-solving. One case that stuck with me: I had a strong disagreement with a colleague about whether a patient was ready to progress in their protocol. I thought yes, she thought no. Instead of pushing, I asked her to walk me through what she was seeing that I wasn't. She surfaced a pattern in the assessments I'd underweighted. She was right. I changed my position publicly, and that moment built more trust between us than any agreement ever had. The willingness to be wrong out loud is underrated in clinical settings. It's the fastest way to signal that you care more about the outcome than the credit -- and that's what keeps a working relationship intact when the next disagreement comes around. --- ### Separate Egos From Investment Choices Running property management means I'm constantly making joint calls with contractors, vendors, and co-owners on things that directly affect someone's investment. The stakes are real, so I learned fast that letting ego drive a disagreement is the most expensive mistake you can make. When I hit a real impasse -- say, a renovation scope dispute with a contractor on whether to gut a kitchen or do a surface refresh -- I redirect the conversation to the owner's actual goal. Is this a flip, a long-term hold, a rental reset? Once we anchor to that, the "right" answer usually surfaces on its own without either side needing to win. The move that's saved me the most relationships is separating the decision from the person. I'll say "here's what the tenant feedback and the unit's condition are telling us" rather than "you're wrong." That keeps the other person's judgment intact while we both look at the same evidence. The best outcomes I've seen came from disagreements where both sides stayed in the room long enough. A colleague pushing back on my renovation timeline once forced us to restructure our vendor sequencing -- the project actually finished cleaner and faster than my original plan would have. --- ### Serve Client Needs, Then Commit Trial law taught me something fast: if you can't disagree with your co-counsel without blowing up the case, you'll lose. I've worked alongside some of the most aggressive, opinionated attorneys in Michigan -- Geoffrey Fieger, Ven Johnson -- and you learn quickly that the loudest voice in the room isn't always right. When I disagree with a colleague on strategy, I lead with the client's outcome, not my ego. On a catastrophic injury case, my co-counsel and I once split hard on whether to push for trial or accept a significant settlement. I made my case, he made his, and we both kept asking the same question: what does this client actually need? That framing kept it from becoming personal. The thing that actually protects the relationship is being willing to lose the argument and own it fully once the decision is made. If the team moves a direction I disagreed with, I commit to it completely -- half-hearted execution is worse than the wrong strategy executed well. Disagreements in high-stakes environments are inevitable. The goal isn't to eliminate them. It's to make sure they sharpen the outcome instead of fracturing the team. --- ### Restate Views, Then Measure Outcomes As CMO at J Sterling's, I've had to make decisions that affect six locations, licensed therapists, and a customer experience reflected in 12k+ reviews. My rule is: disagree hard on the issue, but protect the person. When I disagree with a colleague, I try to restate their position better than they stated it before I argue mine. It lowers defensiveness and often reveals the real concern, like staffing capacity, service quality, or customer expectations. One example is marketing promotions. A campaign may look great from a demand standpoint, but an operations colleague may push back because the spa team could get overloaded; the better outcome is usually a smaller test, clearer booking limits, and messaging that protects the guest experience. The approach that helps most is turning opinions into a shared test. Instead of "my idea vs. your idea," I ask, "What would we need to see to know this worked?" That keeps the relationship intact because the decision belongs to the data and the customer, not someone's ego. --- ## Related - [Values and Ethics in Business Decisions: Choose Growth Without Compromise](https://pursuethepassion.com/values-and-ethics-in-business-decisions-choose-growth-without-compromise.md) - [Say “No” Without Regret in Client Work With Values-First Decisions](https://pursuethepassion.com/say-no-without-regret-in-client-work-with-values-first-decisions.md) - [Choosing Which Client Feedback to Act On for Better Project Outcomes](https://pursuethepassion.com/choosing-which-client-feedback-to-act-on-for-better-project-outcomes.md) - [How Professionals Protect Focused Work From Constant Interruptions](https://pursuethepassion.com/how-professionals-protect-focused-work-from-constant-interruptions.md)