Your dispatcher and your lead tech had the same argument in June. They had it again in July. Now it is September, and the wording has barely changed. Somebody's job notes were thin, somebody got rerouted at 2 p.m., and both of them came to you separately to explain why the other one is the problem. You talked to each of them. Things got quiet for two weeks. Then it came back.
That loop is the most common people problem in HVAC, plumbing, and electrical shops between $1M and $10M. It is rarely about attitude. It is two capable people who give and receive information in completely different ways, working under real pressure, with nothing written down about how they will handle each other. Using DISC for conflict resolution in the workplace gives you a practical way to break that cycle: prepare with what you know about each person, run one clear conversation, then write down what changes.
In this guide, you'll discover how to prep for that conversation using each person's behavioral style. You will learn to keep both people describing actions instead of trading character judgments. Then you will turn what they agree on into a one-page working agreement with names and deadlines. A full illustrative example runs from a dispatcher and lead tech through to the day-30 review.
Why the Same Conflict Keeps Returning Between Good Employees
Recurring team conflict survives because the last conversation ended in feelings, not in a decision. Nobody wrote down who does what, so the old habits came back the first busy Monday.
Most owners solve conflict the way they solve a warranty call: talk to both parties, calm everyone down, move on. That works for a one-time misunderstanding. It does nothing for a pattern, because the pattern is built into how the two people work, not into what happened Tuesday.
The other reason it returns is that you are handling it as two separate conversations. Each person gets your ear, agrees with you, and leaves with a slightly different version of the fix. Nothing shared exists between them.
Separate Behavioral Differences From Character Judgments
The first move is to stop diagnosing character. When your service manager says the lead tech "doesn't respect the schedule," what he means is the tech makes his own call in the field and reports later. That is a behavioral difference around authority and autonomy, not a respect problem.
Behavioral styles shape how people push, pause, question, and go quiet. One person hears a direct correction as normal business. Another hears the same words as a threat to a relationship they value. Neither read is wrong, and neither is a flaw.
Once you name the friction as a difference in behavior, both people can talk about it without defending who they are. That single shift is what makes the conversation in the next section possible.
Spot the Operational Cost of Unresolved Friction
Interpersonal conflict in a trades business shows up on the profit and loss statement before it shows up in a complaint. Managers lose a striking share of their week to handling workplace conflicts big and small, and in a shop that hour count usually belongs to the owner.
Here is where the money leaks when two key people stop cooperating cleanly:
- Extra truck rolls because job details were withheld or half-passed
- Techs sitting on hold instead of calling the person they are avoiding
- Callbacks from work done off an incomplete scope
- Overtime spent fixing a routing decision nobody confirmed
- Your own hours absorbed as the go-between for two adults
None of that lands in a single line item, so it feels like normal chaos. It is not normal. It is the price of an unwritten relationship between two people whose work depends on each other, and it compounds quietly while everyone treats it as the cost of a busy season.
Recognize Avoiding, Escalation, and Other Destructive Responses
Under stress, people fall into predictable conflict behaviors. Learn the four you will see most, because each one hides the real issue in a different way.
- Avoiding: the dispatcher stops calling the tech directly and routes everything through you
- Escalating: voices rise on the radio, then the story arrives at your desk pre-argued
- Over-documenting: one person starts building a paper trail to win later
- Silent compliance: someone agrees in the room and changes nothing in the field
Avoiding is the most expensive because it looks like peace. Nothing is loud, so you assume it resolved. Meanwhile two departments have quietly stopped talking, and the work routes around the gap.
Once you can name which response each person defaults to, you can plan the conversation instead of reacting to it. That planning starts with what their behavioral profile tells you about pressure.
Using DISC for Conflict Resolution in the Workplace Starts With Prep
Preparation is where DISC earns its keep. Before you put two people in a room, you should already know how each one gives information, takes correction, and behaves when the day goes sideways.
The DISC model sorts behavior into four styles: Dominance, Influence, Steadiness, and Conscientiousness. Most people show a blend, with one or two styles leading. You do not need to teach the model to your team to use it, and this article assumes you have basic profiles in hand.
That is the whole role DISC plays here. Using DISC for conflict resolution in the workplace means using it as preparation, not as a diagnosis, and it never gets said out loud in the room. Nobody in that meeting should hear a letter assigned to them.
What a DISC Profile Reveals About Pressure and Correction
A DISC assessment tells you three practical things for a conflict conversation. How the person delivers information (fast and short, or complete and sequenced). How they receive correction (as data, or as a signal about the relationship). And what they do when pressure rises.
That third one matters most for planning. Pressure is when the friction happens. A D-style tends to push harder and decide faster. An S-style often withdraws to keep the peace. A C-style usually stops moving until the information is complete. These are tendencies to check against the actual person, not fixed rules, but they give you a starting read.
Self-awareness is the payoff. When both people can name their own pressure response out loud, the conversation stops being a negotiation over who is difficult.
Prepare for a D-Style or High-Dominance Employee
With a high-D employee, lead with the problem and the decision you need. Skip the warm-up. Give them the headline in the first 20 seconds, or they will assume you are avoiding something.
Bring one specific example, not five. D-styles argue the pattern and concede the incident, so anchor on a job number and a date. Then ask them directly what they want changed, because they respond better to authorship than to instruction.
Expect interruption and do not treat it as disrespect. Set one rule up front: each person finishes before the other responds.
Prepare for an I-Style Employee Who Needs to Be Heard
An I-style needs to talk before they can commit. Give them room early in the conversation, then be firm about landing a specific action, because enthusiasm is not the same as follow-through.
Their communication preference is verbal and relational, which means details go missing in handoffs. That is often the actual mechanism behind the friction: a call happened, the information was warm, and nothing got written into the job.
For an I-style, the written agreement is the fix. They will honor it when they helped word it and when someone checks in on it.
Prepare for an S-Style Employee Who Avoids Tension
An S-style will often agree in the room and stay unhappy afterward. Treat that as a tendency to watch for rather than a certainty, and confirm it against the person in front of you. Where it holds, plan for it: ask directly what part of the plan will not work on a busy Friday, and wait through the silence for a real answer.
Give them the topic before the meeting. Steadiness styles need processing time; sprung on them cold, they default to whatever keeps the peace. A one-line heads-up the day before changes the quality of what you get.
Watch for the quiet withdrawal after the conversation. If your dispatcher stops calling one tech and starts calling you, the agreement did not take.
Prepare for a C-Style Employee Focused on Facts and Standards
A C-style will bring evidence, and you should bring some too. Vague statements about "communication" get dismissed. Come with dates, job numbers, and the exact standard being missed.
C-styles read a correction as a question about their competence, so separate the standard from the person clearly. Tell them what the process should produce, then ask what is stopping it.
Their instinct toward precision is useful in the agreement stage. Let them draft the wording on what "complete job notes" means, because they will make it specific enough to hold.
You now know how each person handles pressure. Next is putting them in the same room without it turning into another round of the same argument.
How to Run a DISC-Based Conflict Conversation
Run the conversation in one sitting, with both people present, and with a written outcome as the stated goal. Two separate conversations produce two separate versions of the truth, which is how you got here.
You are not a neutral mediator in this room. Your obligation runs to the business, so guide toward an operating decision instead of a peace treaty.
Set a Shared Goal Before Discussing the Friction
Open with what both people want. Fewer callbacks. Fewer 4 p.m. surprises. Jobs that go out complete the first time. Name the shared outcome before anyone describes the problem.
This gives you something to return to when the discussion drifts into history. "We agreed the goal is complete job details before the truck leaves. Does that step get us there?"
Keep the framing on the business need in positive terms. That single move keeps both people problem-solving instead of defending.
Describe Actions and Impact Instead of Assigning Motives
Set one ground rule and enforce it: describe what happened and what it cost, not why you think the other person did it. Motive is the fastest route back to a character fight.
Give them the sentence shape:
- The action: "The work order on Job 4412 had no model number."
- The impact: "I made two trips and lost 90 minutes."
- The request: "I need the model number in the notes before dispatch."
Compare that to "he doesn't care whether I have what I need." Same frustration, but one version can be solved this week.
When someone slips into motive, redirect once and move on. Two redirections and both people learn the rule holds.
Give Each Person Time to Explain What Is Not Working
Each person gets uninterrupted time. Ask open-ended questions and then say very little; listening closely and talking less is what surfaces the real mechanism.
You are listening for the process failure hiding under the complaint. A dispatcher who "changes jobs constantly" may be absorbing same-day emergency calls with no rule for what gets bumped. That is a routing gap, not a personality clash.
Ask each person for one thing they would change about their own habit. High-D and high-C people will do this if you ask directly.
Move From Compromise to a Clear Resolution Approach
Compromise splits the difference. A resolution approach names the new standard. You want the second one, because a split difference decays as soon as the schedule gets tight.
Aim for a SMART solution: specific about who does what and by when, measurable so you can tell it happened, and realistic for a July week rather than a slow February one.
Test each proposed step against your worst day. If the plan only works when the board is light, it is not a plan.
Close With a Decision, Owner, and Deadline
End with three things spoken out loud: the decision, the person who owns it, and the date it starts. Have someone repeat them back.
Then write them down before anyone leaves the room. Putting the solution in writing keeps everyone's memory in line with what was agreed, which is the difference between a good meeting and a change in behavior.
Verbal agreements between two people who already misread each other do not survive a busy week. The document does the holding.
Turn the Conversation Into a Written Working Agreement
A working agreement is one page that says who gives what information, who confirms it, by when, and what happens when it breaks. It is not a warning or an HR file. It is an operating standard between two roles.
Write it in their words during the meeting. Both people sign or initial it; you keep a copy, and each of them keeps one. This is how you build shared language between two people who describe the same event differently.
Define Who Gives Information, Who Confirms It, and by When
Most recurring friction between an office role and a field role is an unowned handoff. Assign the handoff explicitly.
State three things per handoff: who supplies the information, who confirms receipt, and the deadline. "Dispatch enters equipment model and access notes by 4 p.m. the day before. Lead tech confirms in the app by 7 a.m." Confirmation is the piece owners skip, and it is what stops the "I sent it" argument.
Cover the exceptions too. Same-day emergency calls need their own rule, because that is where every standard gets tested.
Agree on How Each Person Will Raise a Problem Early
Healthy conflict needs a channel. Decide now how each person flags a problem while it is still small, and make the method match how they operate.
- Text or app note for a specific job issue that needs a record
- A direct call when a decision is needed in the next 30 minutes
- A standing five-minute end-of-day check for pattern problems
- A named escalation path for anything neither person can decide
Put a time limit on stewing. "If it is still bothering you at end of day, it gets said at the 4:45 check." That gives your S-style permission to speak and gives your D-style a place to put it besides the radio.
Document Escalation Rules Before the Next Busy Day
Write the escalation rule while everyone is calm, because nobody negotiates fairly at 3 p.m. on a 100-degree Thursday. Name which decisions each person makes alone, which ones need the other's input, and which come to you.
Be specific about the last category. If everything can come to you, everything will, and you are back to being the switchboard between two people. Most shops find only two or three decision types genuinely belong at the owner level.
Add a tiebreaker. When the two of them cannot agree in the moment, the customer commitment wins, and the disagreement gets reviewed later.
Build a Follow-Up Rhythm That Prevents Old Habits From Returning
Agreements decay in about two weeks without a check. Put the follow-up on the calendar in the same meeting.
Use a simple rhythm: a 10-minute check at day 14, another at day 30, then fold it into whatever regular one-on-one you already run. Ask two questions. Did the agreement hold? What made it hard? Keep the coaching on the process, not the personalities.
Put the day-14 and day-30 checks in your calendar before you leave the meeting, not afterward. Owners who want the same discipline across their whole leadership layer build it into their broader leadership development for service teams, so the rhythm outlasts one fixed relationship.
Seeing the sequence run start to finish makes it easier to copy. Here is the whole thing on one real conflict.
Worked Example: Dispatcher and Lead Tech Move From Friction to Follow-Through
This example is a composite, drawn from how these conflicts typically run rather than a single client file, so read the outcomes as what the process is built to produce, not as a logged result. Picture a plumbing company around $4M with a dispatcher and a lead tech who have argued monthly for a year. She says he ignores the board. He says she sends him out blind. Both are partly right.
The owner has handled it three times with separate conversations. It quiets down, then returns every busy stretch.
Name the Real Issue: Incomplete Job Details and Last-Minute Changes
The complaint was "attitude." The mechanism was two specific failures. Job notes went out without fixture type or access details, and jobs got reassigned after 1 p.m. with no heads-up to the tech already en route.
Two failures, two owners, two fixable steps. That reframe took the conversation from character to process in the first ten minutes.
The owner brought three job numbers as evidence. Specifics kept both people from arguing about the general.
Use DISC Insights to Keep the Conversation Productive
Her DISC profile read high C with S. She wanted complete information and hated being blamed for a system gap. His read was high D with I. He decided fast in the field and reported after.
So the owner opened with the problem statement in one sentence for the lead tech, and sent the dispatcher the agenda the night before. She came in with notes. He came in ready to decide.
Ground rule stated up front: describe the action and the cost, no motives. He said two trips, 90 minutes lost. She said four calls chasing details he could have entered in the app.
Both statements were factual. Neither required anyone to be the villain.
Create a Written Agreement for Job Notes, Parts, and Escalations
They drafted one page in twelve minutes. She wrote the standard for notes because precision is her strength. He wrote the escalation rule because speed is his.
- Job notes include fixture type, age, access, and prior visits, entered by 4 p.m. the prior day
- Lead tech confirms notes in the app by 7 a.m. or calls dispatch by 7:15
- No reassignment after 1 p.m. without a direct call to the tech en route
- Scope changes over $500 go to the service manager, not the dispatcher
- Anything unresolved between them goes to the 4:45 end-of-day check
Both initialed it. The owner kept a copy, and the two of them posted theirs.
Review the Agreement After Two Weeks and Adjust It. On day 14, the owner asked the two questions. It held on notes and broke on the 1 p.m. rule twice, both times during same-day emergency calls.
So they adjusted one line: emergency reassignments are allowed after 1 p.m., with a text plus a call attempt. That amendment is what makes the agreement survivable in real conditions.
By day 30, when the process works, the monthly argument does not come back, callbacks on that tech's jobs fall, and the owner stops fielding side complaints from either one. The agreement, not the meeting, is what produces that. Your own results will depend on following the check-in rhythm rather than on the meeting alone.
One agreement fixes one relationship. Doing this across a whole crew takes something more durable.
Build a Team That Solves Problems Without Making Them Personal
Single working agreements repair a specific relationship. Building a team that handles friction on its own takes shared language and a habit of separating behavior from character, applied across everyone.
A team-wide behavioral assessment does that work. It maps each person's destructive conflict responses and gives them wording to use in the moment. Teams that go through one together stop treating disagreement as a threat, which is where real problem-solving starts.
Emotional intelligence gets built the same way skills do: repetition plus feedback. That is why coaching sits alongside the assessment instead of replacing it.
- Individual DISC debriefs so each person knows their own pressure response
- Cheat sheets for adapting to the three styles they work with least
- Role-based workshops so dispatch, install, and service practice on real scenarios
- Pulse surveys to catch friction before it becomes a pattern
Run that sequence over about four weeks, and the change holds, because each piece reinforces the last. Owners building alignment further up the org pair it with one standard across departments, so dispatch, install, and service are not each running their own version of what "raising it early" means.
Where This Leaves You Monday Morning
The recurring argument between your dispatcher and your lead tech is a missing operating standard, not a personality problem you have to referee forever. Prepare with what DISC tells you about how each person gives information and handles pressure. Run one conversation with both people present. Then write down who does what, by when, and check it at day 14.
You are refereeing because nobody else in the building has the standing to. That changes when the standard is written rather than held in your head, and when your supervisors are trained to run the conversation themselves. Training your supervisors to hold one of these conversations is what takes you out of the middle permanently, and it is worth understanding why alignment comes first before you try it across a whole crew.
It also gets easier when you have other owners to compare notes with. Comparing notes with owners who have run the same conversation is often faster than working it out alone.
If the same two people keep landing on your desk with the same complaint, that is worth one conversation. Talk with Dale at Jackson Advisory Group about whether DISC debriefs and written working agreements are a fit for your crew.
Frequently Asked Questions
How Can DISC Help Resolve Conflict Between a Dispatcher and Technician?
DISC tells you how each person gives information and reacts to correction, which lets you prepare the conversation instead of winging it. A high-C dispatcher needs complete details and advance notice; a high-D tech needs the problem stated in one sentence. You still have to run the conversation and write down the agreement, but you go in knowing what will land.
What Are the Four DISC Conflict Styles?
Dominance pushes for a fast decision and can steamroll input. Influence talks it out and may agree without committing to specifics. Steadiness avoids tension and goes quiet, while Conscientiousness stops and demands facts before moving. Most people blend two of these, and the blend is what you plan around.
Should Managers Use DISC Profiles to Mediate Workplace Disagreements?
Yes, as preparation, not as a label to hand someone in the middle of an argument. Use the profile to choose your wording, your pacing, and how much advance notice each person gets. Announcing "you're just a high D" during a disagreement gives people a way to dismiss the conversation.
What Should a Written Working Agreement Include?
Name each handoff, who supplies the information, who confirms it, and the deadline. Add how each person raises a problem early, which decisions each makes alone, what escalates to you, and the review date. One page is enough if it is specific enough that neither person can honestly claim confusion.
How Do You Keep a Conflict Agreement From Falling Apart After a Few Weeks?
Schedule the check-in during the same meeting where you write the agreement: 10 minutes on day 14 and again on day 30. Ask whether it held and what made it hard, then amend the line that broke instead of scrapping the whole thing. Agreements fail from neglect far more often than from bad terms.
