Conflict Management
Conflict Management
What is conflict management?
- Handling conflict constructively, not suppressing it
- Conflict is the seed of better decisions
- Collaboration (win-win) is generally ideal
Once conflict management takes hold, the language of meetings changes first. Talk about people ('Why do you work like that?') shifts to talk about conditions ('Under what conditions is that schedule feasible?'). It doesn’t reduce the total amount of conflict. It changes the channels it flows through. A team whose unspoken words used to leak out in smoking breaks and group chats, much like overtime for conversation, becomes a team that raises an issue on the spot and closes it on the spot. Decisions that end in one round and don’t get reversed behind the scenes are the first change people notice.
In practice, the starting point is to split conflict into two kinds. Task conflict, where people clash over schedules, design or priorities, raises the quality of the conclusion. Relationship conflict, once it slides into 'that's just how he is,' erodes performance. Telling them apart is surprisingly easy: check whether the subject of the sentences being traded is 'the proposal' or 'the person.' The five Thomas-Kilmann modes are also a matter of conditions, not rank. For irreversible issues such as safety incidents or legal violations, firm competing is right, and during the 30 minutes when emotions are running hot, avoiding (a cooling-off period) is actually the correct answer. Collaboration is not the best mode but the most expensive one, so you reach for it only when time and the size of the issue can support it.
Conflict management is not the same as a leader acting as judge and deciding who is right. The moment a leader issues a verdict, the losing side hides issues from then on, and the organization goes underground again. What a leader should hold is process, not judgment: decide in advance who speaks, by when, on what grounds, and how far up to escalate if there is no resolution. Teams with an escalation rule such as 'if the parties can't resolve it within three days, the team lead sets up a 30-minute joint meeting, and if that fails, the division head decides' don't let conflicts fester.
The most common misstep in the field is setting 'harmony' as the goal. When a leader calls the two sides in separately and soothes them with 'just bear with it this time,' that day's meeting goes quiet, but both people conclude the leader is not on their side. A patched-up conflict comes back weeks later attached to a bigger issue, disguised as a missed deadline or a sudden exit interview. The opposite is risky too: a team that champions 'healthy clashes' and puts every issue through an all-out debate. A debate with no designated decision-maker only makes meetings longer. Managing conflict means attaching a conclusion and a deadline to it.
Yeonmi SongSpecialist instructor and coach in relationship management, resilience, and self-leadership
John KimInstructor John Kim, CEO of Nanum Consulting and author of “B2B Marketing Design”It was formalized in models such as the Thomas-Kilmann conflict mode instrument (1970s).
Consider a hypothetical case: Company A, an industrial software firm with 240 employees and KRW 62 billion (≈ US$46,386,400) in annual revenue. Over six months, the development division missed 11 delivery dates that the sales division had promised at the bid stage. The two division heads had stopped speaking to each other in the weekly meeting. The CEO said, 'Figure out whose fault this is,' but the company turned to a six-week conflict mediation program instead.
- When the HR manager interviewed nine practitioners from both sides separately, sales said, 'Development just says no,' and development said, 'Sales sells features that aren't in the quote.' The issue was not people but an information gap at the quoting stage.
- At the joint workshop in week two, an external facilitator first had everyone vent for 30 minutes, then had each side estimate the other division's monthly overtime hours and write them on the board. The development division's actual overtime was double the sales team's estimate.
- When the head of development declared, 'From now on, we set the delivery dates,' the CEO asked about conditions instead of ruling. 'What information, arriving when, would let you give us an answer within three days?' That is how the 48-hour technical review before quoting rule was born.
- For deals with a win probability above 50%, the sales lead must request a pre-review from the development lead, and development must answer within 48 hours with one of three verdicts: feasible, conditional, or not feasible. This was put in writing. Only the CEO can approve exceptions.
- Six months later, late deliveries fell from 11 to 2, and the gap between quoted and actual effort dropped from 38% to 12%. The bigger change was that the two division heads began requesting data from each other first in the weekly meeting.