The Sequence Map for Workplace Conflict: A Coaching Tool

Every organizational conflict runs on a predictable sequence of behaviors that the participants repeat until the pattern itself becomes the problem. Treat the workplace as a system of interlocking moves rather than a collection of personalities. When you are called into a corporate environment to settle a dispute between two executives, your first task is to set aside the psychological explanations they offer for their conduct and attend to the chronological order of their interactions.

Jay Haley insisted that the unit of observation is the social situation. The useful question is never why a person is angry. It is what happens right before they express the anger and what happens immediately after. That focus on sequence lets you map the conflict with technical precision, and the map is the whole instrument. Once you have built it, you locate the single move that holds the pattern together and you change that move.

Filming the conflict instead of accepting the adjective

Begin by asking for the most recent incident. When a client tells you their colleague is aggressive, do not accept the adjective as a fact. Ask for the specific behavior that occurred at ten o’clock on Tuesday morning.

I once worked with a senior director who claimed his manager was sabotaging his career. I asked him to describe the sabotage in a way I could film with a camera. The manager, he said, would wait until the end of a board meeting to ask a technical question he could not answer. That was the first step. The director would stammer and look at his notes, the second step. The manager would sigh and glance at the chief executive, the third step. By the time the meeting closed, the director was ready to fire off a defensive email, the fourth step.

That email did not end anything. It became the trigger for the manager to exclude him from the next agenda-setting session, which confirmed the director’s belief that he was being sabotaged, which led him to withhold information from the manager. This is a maintaining loop, and your job is to locate the point where the loop starts to repeat. Skip the mapping and you fall into the same trap as the participants, listening to hours of complaint about personality while the behavior that sustains the conflict runs on unnoticed.

How a provocation becomes a failed solution

The opening move is usually a small act that violates a local rule of the hierarchy. Healthy systems let late emails and sharp comments pass. A conflicted system reads the same provocation as the signal of a larger threat, so the participants turn hypervigilant and watch for the first move. A project manager once felt her lead developer was eroding her authority. She monitored the group chat for any message he sent that did not include her name, and the instant a message appeared without her name on it, the sequence began.

The second move is the intervention that fails. A manager tries to settle things with logic or a direct command and believes they are ending the conflict, when in fact they are supplying the next beat in the dance. A supervisor calls a meeting to clear the air, which sounds like a professional remedy. If the sequence involves a subordinate who already feels micromanaged, that meeting reads as more micromanagement. The subordinate answers with passive resistance, step three. The supervisor raises the pressure, step four. The remedy feeds the disorder.

Common sense is often the engine of the conflict. When a person tries harder at what has already failed, the sequence accelerates. Two engineers I worked with were feuding over technical standards. One would write a long document setting out his position. The other would respond by flagging a minor error in the first paragraph. The first engineer would rewrite the whole document to make it longer and more detailed. Each attempt to clarify only sharpened the irritation. You will find this in almost every workplace dispute, so watch for the moment the participants reach for a common-sense fix.

Steps three through six: how the loop hardens

The middle steps recruit other people and other machinery. Watch for triangulation, the recruitment of allies. When two people cannot resolve a power struggle, they pull in a third to tip the scales, often an HR professional, a boss, or a sympathetic colleague, and the aim is to get that third party to agree the other side is the problem. The move expands the sequence and makes it harder to resolve, because the participants are now performing for an audience. Identify who is being recruited and what role they play in keeping the thing alive. As the coach, take care not to become that third person yourself.

Next comes formalization. The conflict leaves the realm of interpersonal tension and enters official documentation. An employee files a complaint, or a manager issues a performance improvement plan. The move is meant to stop the behavior, and it usually locks the behavior in place. The documented party now has a legitimate grievance to be hostile about, the documenting party now has a paper trail to defend, and the conflict is no longer between two people. It runs between two people and the organization. Past this stage the participants stop talking to each other and start talking to files.

The last step is deadlock. The sequence has run so many times that both parties feel exhausted and stuck. They have tried everything they know, nothing has worked, and this is usually the moment you are called in. The participants want a miracle, or they want you to order the other person to change. You are not there to change personalities. You are there to change the sequence, and you do it by introducing a maneuver that makes the old sequence impossible to complete.

Prescribing the conflict so it cannot function as rebellion

Milton Erickson often turned a client’s own resistance into the lever. A client determined to argue was given a specific time and place where arguing was required. Carry this into the corporate setting. If two employees bicker in every meeting, direct them to hold a scheduled ten-minute disagreement each morning before the meeting starts. Once the behavior is a requirement, its function changes, because a required behavior can no longer serve as a rebellion.

This shifts the locus of control. The conflict is no longer something that happens to the employees. It is something they perform on your command, and that creates a strategic bind. Follow the instruction and have the ten-minute argument, and they are cooperating by disagreeing. Refuse the argument, and they have stopped the conflict to spite your authority. Either way the original circular sequence breaks. We call this a therapeutic double bind, and notice that you have not asked anyone to change their personality or their values. You have only changed the rules of the game they are playing.

I once applied this to two executives locked in a perpetual struggle over office resources, whose every meeting collapsed into an unresolved debate about budget allocations. For the next three weeks I prohibited them from reaching agreement. Their disagreement, I told them, was so vital to the checks and balances of the company that any sign of compromise would be read as a lapse in professional judgment. By the second week the requirement to disagree had grown so tiresome that they were finding quiet, unofficial ways to settle their differences, purely to escape the burden of the scheduled conflict.

Correcting the incongruent hierarchy

Every workplace has a formal structure, and the conflict often exposes an informal one that contradicts it. A subordinate may hold more power over a superior than the org chart admits. A middle manager hesitates to discipline an underperforming clerk because the clerk is friends with the CEO, and the sequence turns muddy. You cannot settle the dispute between manager and clerk until you address the hierarchy underneath it.

A director I worked with was being bullied by his own assistant. The assistant would forget to schedule important calls, and the director would spend his evenings repairing the damage. His remedy was to be more helpful and understanding, which only told the assistant the behavior carried no consequence. This is a symmetrical relationship where a complementary one belongs. I instructed the director to stop fixing the mistakes and instead to ask the assistant for a daily two-hour training session on the scheduling software. The director played the incompetent student, the assistant played the expert teacher, and the sabotage became impossible to sustain because the assistant was now answerable for the director’s performance. No lecture on management corrected the hierarchy. A task did, by making the assistant’s position untenable.

Refusing to be the third corner of the triangle

When you are the HR professional, you are frequently the third person in the triangle, and the pull to mediate is strong. Resist it in the traditional sense. Mediation tends to validate the idea that the conflict is a legitimate debate rather than a sequence of behaviors. Change the sequence instead, by removing yourself or by making your involvement a burden.

I once consulted for a tech company where two lead developers refused to speak and communicated only through their department head, who was spending four hours a day as a human relay station for their technical disputes. I told the department head to stop translating. He was to inform both developers that he had developed a temporary inability to understand technical language, so any dispute they wanted him to settle had to be written up as a detailed technical manual. The developers found the requirement so irritating that they bypassed him and started talking to each other again, just to avoid the extra work. The goal is not to be liked. The goal is to be effective.

Building an ordeal the organization will allow

The ordeal is a cornerstone of the work. Erickson used it to make the symptom harder to keep than to give up. In a workplace the ordeal has to be professionally defensible. You cannot ask an employee to scrub a floor with a toothbrush, and you can ask them to document the conflict in an exhaustive, time-consuming way.

When a team complains of poor communication, do not propose a retreat. Instruct them to meet every morning at seven o’clock for a mandatory thirty-minute briefing where no one is allowed to sit down, and tell them it continues until every member signs a statement that they are fully informed. Most teams watch their communication problems vanish within three days, because the solution costs more than the original problem. You are hunting for the point of least leverage, the small change that disrupts the whole system. You do not need to change the company. You need to change the sequence of one specific interaction.

A junior employee once felt ignored by his supervisor. His sequence was to work late, wait to be noticed, and turn resentful when the supervisor left at five. I told him to start leaving at four fifty-five each day, but to leave a handwritten note on the supervisor’s desk detailing one thing he had learned that day. The passive wait for recognition became an active assertion of presence. The supervisor, who had ignored him before, began to look forward to the notes, and the resentment loop broke because the employee was no longer a hostage to someone else’s schedule.

When the client says they did not do it

Be ready for the client who returns and reports that they skipped the task. This is not a failure. It is a clinical datum. If the client refuses the task, wonder whether you made it too easy. A resistant client often needs a harder ordeal or a more indirect route. You might tell them you now see the conflict is far more complex than you first thought, and they are probably not ready to resolve it yet. Their resistance then works against the problem. Tell a person they are not ready to change and you often provoke them into proving you wrong by changing at once, because the surest way to get someone moving is to stand in their way. You use your authority to restrain change, and the restraint forces the client to own the improvement.

This is why the follow-up meeting matters. Your attention is not on whether they enjoyed the task. It is on what specifically happened in the sequence once the task entered it. Listen for any deviation from the old pattern. Even a small shift in the timing of a dispute means the system is cracking. Listen, too, for the moment the participants stop blaming each other and start complaining about the absurdity of your instructions. When they unite against you, they are no longer united against each other.

Stay detached throughout. If you become emotionally invested in the outcome, the clients will use your investment as another piece in their game and fail simply to show you that you cannot control them. Present your tasks with a measure of indifference. You are a consultant offering a technical solution. You are not a savior. If a task fails, the sequence has not been fully mapped yet, so you return to observation and look for the move you missed.

Often the missed move is someone higher up. I once worked with a team that refused every intervention, until I discovered the CEO was feeding the team leader contradictory advice in private. The real sequence ran between the team leader and the CEO, not among the team members. I instructed the team leader to ask the CEO for still more contradictory advice, specifically a new set of impossible goals every Tuesday, which forced the CEO to confront the absurdity of his own management style. Do not hunt for the bad guy in these situations. Find the person most stuck in a repetitive loop, change the loop, and the people change as a consequence.

Keeping the client in the present

Stay on the present interaction. The history of a conflict matters only if it is being reenacted in the room right now. When two coworkers say they have hated each other for ten years, look at how they express that hatred today. Do they avoid eye contact? Do they copy the manager on every email? That is the sequence. You intervene in the email habit and leave the ten-year history alone.

One client spent forty minutes of every session rehearsing a grievance from five years back. I told him that for every minute he spent on the past, he had to spend two minutes standing on one leg. This was not punishment. It made the past more physically demanding than the present, and he quickly found he had nothing more to say about the old grievance. Physical and logistical constraints like this force the client into the here and now and teach them, by experience, that the old ways of interacting cost too much. When the cost of the conflict outweighs the benefit of the status quo, the behavior changes. That is the basic rule of human systems, true in the warehouse and the boardroom alike.

Reversing roles to break a polarized pattern

Silence can be the move that runs a sequence. You will sometimes see one person talk incessantly while the other holds a stony silence, and the silence is not the absence of behavior. It is a tactic that provokes the talker into more extreme statements. There the silence is the problem, and you have to break it.

A partnership I worked with had one partner who went quiet for days whenever he was angry. I told him his silence was so valuable that he was only allowed thirty minutes of it a day, scheduled on his calendar, and that at all other times he had to speak at least one sentence every five minutes, even if only to remark on the weather. His tactical silence became a logistical chore. The other partner, who normally begged him to speak, was told to ignore him whenever he did. The talker became the silent one and the silent one became the talker, and the sequence shattered.

This role-reversal task works well when a conflict has polarized into two extreme positions. You simply switch the positions, telling the cautious person to be reckless and the reckless one to be cautious, and you hold the switch only long enough to break the habit. This is the technical application of Erickson’s observation that people will do almost anything if you frame it correctly. You are not asking anyone to change their nature. You are asking them to perform a role for a limited stretch, and the performance creates a new experience, which is what leads to change. You direct the performance, watch the cues, and rewrite the script as the play runs. Once the pattern breaks, the employees find their own way of interacting that leaves the old conflict behind, because human beings adapt. Take away the old adaptation and they build a new one. Your job is to make sure the new one works better.

Reading the end state as a boring routine

You know the work is finished when a boring routine has replaced the drama of the loop. Do not seek an apology between the parties. Do not wait for a statement of mutual respect. Watch for the moment the participants stop talking about each other and start talking about the technical requirements of their jobs.

Two engineers once spent six months filing formal grievances against each other over shared lab equipment. My intervention required them to submit a joint written report every Friday detailing the exact number of minutes each had used the equipment. After four weeks the report became a chore, and they dropped the grievances because the grievance process was now less irritating than the reporting requirement. That is a professional outcome. The sequence was disrupted by making the conflict more labor-intensive than the work itself.

Re-establish the formal hierarchy before you exit the system. If a supervisor has been bypassed by a subordinate, the loop returns the moment you walk out. Instruct the manager to issue a direct, simple order that has nothing to do with the conflict, such as telling a department head to order a subordinate to reorganize the filing system by a set date. The point is not the files. The point is the subordinate following a direct command, because once they comply with a mundane order the pattern of defiance is broken.

I recently advised a chief executive who was being undermined by a founding partner. I told the chief executive to move the weekly executive meeting fifteen minutes earlier without consulting the partner. When the partner arrived at the new time and sat down, the hierarchy was reset and he had acknowledged the chief executive’s right to set the schedule.

Predicting the relapse and holding the ordeal

As you near the end of a case, predict a relapse. Tell the clients they will probably have a major blowout within the next thirty days, and explain that this is a necessary test of whether they remember how to use the new sequence. The prediction puts them in a double bind. If they fight, they are following your instructions and proving your expertise. If they do not fight, they are proving they have changed. You stay the director of the sequence either way, and a minor setback is kept from spiraling back into the original loop.

To a pair of feuding project managers you might say: I expect you to disagree about the budget next Tuesday. When it happens, I want you to notice exactly who starts it and how long it lasts before one of you walks away. By turning the fight into a matter of observation rather than an emotional event, you strip it of its power to disrupt the office.

Keep the weight of the ordeal in place until the new behavior is automatic. Lift the consequence too early and the old sequence reasserts itself, so be prepared to be the difficult person in the room. We do not work to be liked. We work to be effective.

I once required a marketing team to meet in a cold warehouse every morning at six o’clock to discuss their communication failures, and told them the meetings would continue until they could show three consecutive days without a missed deadline. They hated the warehouse more than they hated each other, and they began to cooperate to escape it. Hold the ordeal until the cost of the conflict outweighs the benefit of the grievance. When the team complains about the early hour, simply state that the schedule is a consequence of their own inability to manage their time.

Exiting cleanly

Make your exit abrupt. Long endings invite the clients to find new problems to discuss. State plainly that the work is finished because the target sequence has been achieved. Do not ask how they feel about the ending. Summarize the behavioral changes and leave the room. If they try to pull you back with a fresh crisis, treat it as a technical matter rather than a return to coaching, and say something like: that sounds like a management issue for your supervisor to handle. The line reinforces the hierarchy and closes the door on your involvement.

A client once called me three weeks after our final session to report a new argument. I told him to consult the manual we had created and to call his boss if the manual did not cover it. I offered no new session and asked for no details. The refusal to engage prevented him from rebuilding the triangulation loop with me as the third party.

The whole approach rests on your ability to remain a detached observer of behavior. People do not change their personalities, and they do change their moves when the game grows too expensive to play, and you are the architect of that expense. You provide the structure that makes the old habits impossible to sustain. I once watched a long-running conflict between a surgeon and a head nurse resolve only after the hospital administrator was forced to enforce a strict protocol for equipment requests. The surgeon could no longer yell for what he wanted. He had to fill out a form, and the form was the intervention, because it forced a new sequence that bypassed his temperament. The most effective interventions are frequently the most mechanical ones. A stable hierarchy is the primary prevention against the next circular loop, and the intervention has succeeded when you are no longer needed to keep the peace. You observe behavior, you interrupt loops, and you exit.