Chapter 28: Navigate Conflict, Feedback, Influence, and Politics

The rehearsal that failed

It is the first review of the hypercare rehearsal record at Meridian, and the room has two readings of the same failure. The escalation drill is the incident scenario from chapter 24: a clinician’s record goes missing mid-shift, and the site must fall back to paper without losing the patient’s story. It ran at clinic two in the first week of operation under hypercare, with the incident response team on site, as the steering committee’s condition required. Twelve stations ran the fallback. The continuity plan set a recovery time objective of thirty minutes: from the moment the record fails to the moment the clinician is back to work with the patient’s story intact, thirty minutes is the maximum the clinical governance standard will accept. Four of the twelve stations made it inside the objective. Five recovered between thirty and sixty minutes. Three exceeded the hour, and the slowest took ninety-seven minutes, forty of them spent searching for the paper kit, which the occupancy inspection had relocated from the treatment room to a store cupboard down the corridor.

Sam Otieno, the clinical lead, walks the room through the record the way he walked the floor after clinic one went live in chapter 11. He has the drill’s data, the station times, the observer notes, and the clusters. The four slowest stations all failed at the same moment, and the moment is a screen. When the platform session times out and auto-locks, which is exactly what happens when a clinician is deep in a record and the shift handover interrupts, the recovery screen presents a single prompt, “return to the workflow,” and nothing else. The fallback procedure, the steps the clinician must take to recover the story on paper, is not visible anywhere in the recovery path. The paper kit, relocated during the inspection, is not where the training put it. Sam’s reading is precise and he states it without heat: the staff did not fail the drill. The design failed the staff. The four stations did exactly what the screen invited them to do, they tried to return to a workflow that was gone, and the search time came from a location the drill had not updated. In his judgment, this is a product defect, a nonconformance against the acceptance criteria the project signed in chapter 21, and the fix is a design change to the recovery path, not another training session for nurses who were trained.

The vendor’s implementation lead reads the same record and reaches the opposite conclusion with the same precision. The platform telemetry is on the table: at all twelve stations, the failure event was logged, the recovery screen was displayed within nine seconds, and the platform behaved exactly to the specification that was signed, priced, and accepted. Eight of the twelve stations followed the first two steps of the trained procedure before diverging, which the vendor reads as evidence that the procedure was learned and that the divergence is adherence under pressure, not design. The paper kit relocation is an operational change the project made after the vendor’s last walkthrough, and the vendor was not informed. In the vendor’s reading, this is a training and environment issue: the fallback procedure needs reinforcement through scenario training, the kit locations need to be verified as part of the drill’s setup, and the recovery screen, which met its specification, should not be redesigned because a training gap was exposed. And the vendor says the sentence that makes the room go quiet: “If every drill that fails becomes a product defect, then the contract has no boundary, and we will be redesigning screens forever at our own cost.”

Both readings are locally rational. Sam is protecting the patient and his staff, and he has the cluster data and the chapter 11 history on his side, the trained nurses who revert to paper under workload pressure, the platform terminal waiting at the end of the corridor. The vendor is protecting its scope, its pricing, its reputation, and the truth that a contract without a boundary is not a contract at all, and it has the telemetry and the signed specification on its side. Neither is lying, and neither is stupid. The disagreement is real, consequential, and entirely predictable, and it is also, in the way that matters for this book, a gift: a project in its second wave of clinics is about to learn something about its recovery path that it would otherwise have discovered in a real incident, and the only question is whether the learning will cost the relationship or build it.

That is the argument of this chapter, and it is worth stating before the evidence: conflict is information before it is a problem. The disagreement in the room is the project’s recovery path speaking to the people who own it, and the leader who can diagnose what kind of conflict this is, task, process, relationship, status, or values, and respond to the kind it is rather than the kind it feels like, turns the room from a dispute into a design conversation. The instruments are four, and they are the chapter’s spine: the conflict diagnosis, which names the species before any response is chosen; the conversation planner, which designs the difficult conversation; the influence map, which finds the real decision right; and the escalation brief, which carries the conflict that cannot be resolved in the room to the authority that can decide it. The meeting system of chapter 27 built the room. This chapter is about what happens in the room when the people disagree, and the claim is that mastery here is not the absence of conflict, it is the ability to make the conflict produce learning instead of damage.

Conflict is information

Start with the economics, because the economics explain why the craft matters and why the avoidance feels rational and is not. Conflict is expensive in the currency the project cannot mint more of, attention, and the cost is not the meeting time, it is the deferred decision, the silent expert, the rework that the withheld evidence produces. An industry survey published in 2008 by the consultancy CPP, based on responses from several thousand employees across nine countries, estimated that respondents spent an average of about 2.8 hours a week in conflict-related activity, a figure the report extrapolated to roughly 359 billion dollars of paid time each year in the United States. The number is old, survey-based, and much-quoted, and its size has become folklore, but the direction of the finding has not been seriously contested: unresolved conflict consumes organizational attention at scale, and the consumption is mostly invisible, because it shows up not as argument but as silence, avoidance, and the corridor conversations that the meeting never hears.

The research on what conflict does to teams is sharper than the folklore, and it distinguishes the species the folklore lumps together. Frank de Wit, Lindred Greer, and Karen Jehn published a meta-analysis in the Journal of Applied Psychology in 2012 that pooled more than a hundred studies of intragroup conflict, and their findings, in my own words, are the following. Relationship conflict, conflict about the people themselves, who is trusted, who is valued, who slighted whom, showed a consistent negative association with both team performance and member satisfaction across the studies, and the association held in nearly every condition they examined. Process conflict, conflict about how the work should be done, who does what, when the review happens, whose approval gates whose delivery, also showed a negative association with performance, and this is worth pausing on, because process conflict feels productive, it is about the work, but the meta-analysis found it reliably costly, in part because process questions are where responsibility and status live, and arguments about process easily become arguments about who is trusted with what. Task conflict, conflict about the work itself, what the right answer is, whether the recovery screen should expose the procedure, whether the estimate is honest, showed a small and mixed association: mildly negative under some conditions, mildly positive under others, and the balance tipped positive in the settings where the team was psychologically safe, moderately interdependent, and able to separate the argument about the work from the argument about the people.

That last finding carries the chapter’s whole argument: task conflict can sharpen judgment, but only in a climate where people can argue about the work without fearing that the argument will be taken as an attack on the person. In a team without safety, task conflict converts into relationship conflict, because the safest reading of a challenge is an attack, and the challenge is answered with a counter-attack, and the evidence gets buried under the attribution. In a team with safety, the same challenge is an input, and the evidence gets examined. The project leader’s job, then, is not to reduce conflict, it is to keep task conflict task-shaped, and that requires naming the species, which is the first instrument.

The five species

Five kinds of disagreement deserve names, and each has a tell and a fitting response, and the discipline is to diagnose before you respond, because the response that fits one species inflames another.

Task conflict is disagreement about the work: whether the recovery screen should expose the fallback, whether the estimate should be 40 or 52 weeks, whether the segmentation of the rollout should be staged or all at once. Its tell is that both sides are pointing at evidence, even when the evidence is thin, and both sides can usually state the other’s argument back. Its fitting response is deliberation: evidence, criteria, the acceptance matrix, the decision method, a date. Task conflict is the reading the opening scene invites, and the temptation is to stop at that reading — the mistake the layers section later corrects.

Process conflict is disagreement about how the work will be done: who owns the drill’s setup, whether the vendor must be informed of kit relocations, whose gate the rehearsal record clears, who reviews the record before it reaches the steering committee. Its tell is the sentence “that is not our process,” or the newer form, “that is not how we work.” Its fitting response is explicit process design: the responsibility matrix, the interface agreement, the decision rights, written down and agreed, because most process conflict is not a conflict about values, it is a conflict about ownership that nobody ever settled. The failure is to treat process conflict as personality conflict, because the person who is “difficult about the drill setup” is usually a person who was never told who owns the drill setup.

Relationship conflict is disagreement about the people: trust, respect, reliability, history. Its tell is attribution, the sentence “he did not train them,” “she does not care about the schedule,” the reading of the other’s motive as bad. Its fitting response is not more evidence, because evidence does not settle a trust question, it is repair work: the conversation about the history, the apology where an apology is owed, the small reliable act that rebuilds the ledger of chapter 26, and, where the history is too damaged, the boundary that contains the relationship while the work proceeds. The failure is to feed relationship conflict with task tools, to schedule a “data review” for a trust wound, because the data review will confirm each side’s worst reading of the other and deepen the wound.

Status conflict is disagreement about standing: whose expertise counts, who gets to interpret the record, whose call is final. Its tell is the escalation of the pronoun, the argument that shifts from “the recovery screen” to “my team,” “my contract,” “my license,” and the audience, the conversation that is really about the people watching, the steering committee, the ward, the vendor’s leadership. Its fitting response is status work: recognition, respect rituals, the invitation that gives each side its domain, the evidence session where each side’s expertise is asked for rather than challenged. The failure is to ignore status, because status conflict is the species that turns task conflict into a fight, and the leader who answers a status question with a technical answer has escalated the fight.

Values conflict is disagreement about what matters: safety versus schedule, privacy versus convenience, profit versus access. Its tell is the unshakeable phrase, “we do not do that here,” “this is about patients, not metrics,” and the refusal of trade, because values are not traded, they are held. Its fitting response is not resolution, because some values conflicts cannot be resolved, it is containment and decision: the value named explicitly, the decision right identified, the decision made on the record with the value conflict recorded, the dissent noted, the review date set. The failure is the values conflict that goes underground, because the person who cannot say “this violates our standard” will say it in the incident report.

The diagnostic rule that covers all five is simple to state and hard to hold: name the species before you choose the response, and expect the species to shift, because a conflict that starts as task, the drill failed, becomes process, who owns the setup, becomes relationship, the vendor does not care, becomes status, whose expertise counts, and sometimes approaches values, the patient’s safety versus the contract’s boundary, in a single meeting. The scene in this chapter’s opening is exactly that ladder in miniature, and the leader who responds to the ladder’s top rung as though it were the bottom, who answers a status conflict with a technical briefing, is the leader who will read the same record twice more before the escalation lands on a desk that has no time for it.

The diagnostic before the response

Once the species is named, the response must be chosen, and the response map is a two-axis space with a long pedigree and a short description. On one axis sits assertiveness, the weight given to your own interests and the decision you need; on the other sits cooperativeness, the weight given to the other side’s interests and the relationship. Between the two axes sit five familiar modes, usually associated in the practitioner literature with the conflict instrument developed by Kenneth Thomas and Ralph Kilmann in the 1970s, and I describe them in my own words because the instrument’s own materials are proprietary. Avoiding is low on both axes: the issue is set aside, the meeting not held, the email unanswered. It is right when the stakes are tiny, the timing is wrong, the temperature is too high to think, or the decision belongs elsewhere; it is wrong as a default, because avoided conflict does not disappear, it accumulates interest. Accommodating is low assertiveness and high cooperativeness: you give the other side what it wants. It is right when the relationship is worth more than the issue, when you are wrong, or when the other side’s position is a genuine nonnegotiable; it is wrong as a default, because chronic accommodation teaches the room that your interests do not matter. Competing is high assertiveness and low cooperativeness: you press for your position, through evidence, authority, or persistence. It is right when the decision is urgent, the stakes are high, the criteria are clear, or someone must protect a line, a safety floor, a compliance obligation, a budget; it is wrong as a default, because the win is Pyrrhic when the other side must implement the decision. Compromising is the middle: each side yields something. It is right when time is short, the issue is genuinely divisible, and the relationship needs a gesture; it is dangerous when the issue is not divisible, because splitting a safety requirement or a quality standard in half is not a compromise, it is a failure with a budget. Collaborating is high on both axes: the problem is treated as a joint problem, the interests explored, the options invented, the solution built that neither side would have reached alone. It is the most expensive mode and the most powerful, and it is right when the stakes are high, the interests are compatible beneath the positions, and the time exists to do the work.

The choice among the modes is the decision tree that this chapter’s visual would draw, and the tree branches on four questions, which is why the visual has four trunks. First, the stakes: what is the consequence of getting this wrong, for the patient, the budget, the schedule, the reputation, the obligation? If the stakes are high, the modes narrow to collaborating or competing, because avoiding and accommodating would pay the consequence later. Second, the time: how long until the decision must be made, the wet-season window, the gate date, the hypercare review? If the time is short, competing or compromising become the honest modes, because collaboration has a schedule and the schedule has already been spent. Third, the relationship: will the people in this room need to work together after this decision, for how long, and on what? If the relationship is durable and the work is interdependent, collaborating is the investment that pays; if the relationship is disposable, the vendor contract ending, the consultant leaving, the modes can afford to be harder. Fourth, the authority: who holds the decision right, and what are the guardrails around it? If you hold it, the modes describe how you will exercise it; if someone else holds it, the modes describe what you will do with your influence, which the later section builds.

The tree’s most important teaching is not the branches, it is the order of the questions, because the order is what the room usually gets wrong. The room that asks “what is the relationship worth” first will accommodate its way into a safety failure, because the relationship felt more urgent than the consequence. The room that asks “who has the authority” first will compete its way into a trust collapse, because the authority question was answered before the stakes were understood. Stakes, time, relationship, authority: the order is the discipline, and the discipline is why the scene in this chapter’s opening is diagnosable. The stakes at Meridian are high, a recovery path that failed four of twelve stations, a gate condition that depends on the rehearsal record, patients whose records could go missing; the time is bounded, the first review is the gate evidence and wave three planning is running inside the grant window; the relationship is durable, the vendor and the project will build three more clinics together; and the authority is layered, the classification sits with the acceptance criteria and the clinical governance review, the decision on the fix sits with the steering committee, and the funding sits with the grant. The tree says: collaborate, with the evidence as the joint problem — the collaboration the rest of the chapter builds.

The response map has three characteristic failures, and each deserves a name because each is a character in every project. The first is the reflex competitor, who answers every conflict with force, who treats the room as a contest, and whose tell is the raised voice, the deadline weapon, the “this is nonnegotiable” that is not. The reflex competitor wins the small battles and loses the war, because the room learns to hide the evidence the competitor would have used to win the right way. The second is the reflex avoider, who answers every conflict with delay, who schedules the follow-up that never comes, and whose tell is the phrase “let me take that away and think about it,” spoken by the person who will never return to it. The reflex avoider keeps the peace and pays the interest, and the interest compounds in the silence tax of chapter 27, the withheld evidence, the corridor discovery, the incident report. The third is the single-mode leader, who has one response for everything, usually the mode that matched their temperament once and their context never again, the accommodator who cannot hold a line, the competitor who cannot build a coalition, the compromiser who splits what should not be split. The single-mode leader is the most common of the three, because most leaders have never been taught the map, and the fix is not temperament, it is diagnosis: name the species, ask the four questions in order, choose the mode, and check the choice against the person you are about to be in that room.

The three layers under the argument

The response map assumes the conflict is what it appears to be, an argument about the recovery screen, and the discipline of the chapter is that the argument is never only the argument. Under every position sit three layers, and the leader who cannot see the layers will keep responding to the surface while the conflict deepens underneath.

The first layer is interests. Roger Fisher and William Ury built the modern negotiation field on this distinction in their 1981 book “Getting to Yes,” and the idea, in my own words, is that a position is what someone says they want, a fixed screen change, a training program, a boundary on the contract, while an interest is why they want it, and the positions may clash while the interests underneath them overlap or even align. Sam’s position is a product defect; his interests are patient safety, his staff’s dignity, and a recovery path that works when the workload is real. The vendor’s position is a training gap; its interests are scope integrity, pricing, reputation, and the truth that an unbounded defect clause would price its next proposal out of the market. The interests are not identical, but they are not opposites either: both sides want a recovery path that works, and neither side wants the clinics to open on a broken drill. The work of the difficult conversation is to move the discussion from the positions, where they clash, to the interests, where they can be combined, and the move requires the second layer.

The second layer is identity, the story each person is telling about who they are in this work. The social psychologists Edward Jones and Richard Nisbett observed in 1972, in a classic chapter on the actor-observer distinction, that people tend to explain their own behavior by the situation and other people’s behavior by the person’s character: when I fail the drill, I was under pressure and the design failed me; when you fail the drill, you were not trained and you did not follow the procedure. Lee Ross named the pattern’s sharpest form, the fundamental attribution error, in a 1977 review of the attribution literature: the tendency to over-explain other people’s behavior in terms of their dispositions and to under-weight the situation they are in. The rehearsal record at Meridian is a case study in both: Sam sees staff trapped by a bad screen, the vendor sees staff who did not follow the procedure, and each is reading the same behavior through the other’s disposition because each is in a different situation. The identity layer is why the attribution matters: Sam’s identity includes “I protect my staff,” and the vendor’s includes “I deliver to spec,” and a disagreement about a screen is also a disagreement about whether each person is good at what they claim to be.

The third layer is face, and it deserves the name the sociologist Erving Goffman gave it in his 1955 essay on face-work. Face, in Goffman’s terms, is the positive social value a person effectively claims for themselves in the course of an interaction, the standing that lets them keep talking, and face-work is everything a person does to keep their actions consistent with that claim. Face is not vanity, and it is not weakness: it is the condition of staying in the conversation. A person who loses face in a room cannot hear the evidence in that room, because the evidence has become a verdict on them, and the conversation after that is about the face, not the work. Sam’s face is tied to the clinical evidence and the chapter 11 history of training that did not hold; the vendor’s face is tied to the spec, the price, and the clause that must mean something. The leader who wants the evidence to settle the substance must first arrange the room so that no one has to lose face to accept it.

The escalation spiral is what happens when the layers are ignored. The argument about the screen becomes an argument about who is competent, because the screen question was answered with attribution, “your staff were not trained,” “your product invites the error,” and the attribution is an identity attack, and the identity attack is answered with a counter-attack, and the counter-attack recruits witnesses, the steering committee, the ward, the vendor’s leadership, because status conflict needs an audience, and the audience polarizes, and the conflict that started as a drill record ends as a relationship scar that will outlive the clinics. The spiral is the most expensive failure in this chapter, and its field signal is the shift of pronoun, the sentence that stops being about the work and starts being about the people, the “we” and “they” that replace “the screen” and “the drill.”

The de-escalation moves are the mirror of the spiral, and they are four. Slow down: the spiral accelerates because the responses are fast, and the fastest responses are the oldest ones, so the leader who can slow the room, take the meeting offline, ask for the record in writing, give the temperature an hour to fall, has already broken the spiral’s rhythm. Name the stakes: state out loud what each side is actually risking, the gate condition, the contract boundary, the patient’s record, and let the room see that the stakes are shared, because the spiral survives on the illusion that only one side is risking anything. Separate the people from the problem, in Fisher and Ury’s phrase, which the conversation planner later in this chapter makes mechanical: treat the people as partners in examining a problem that belongs to neither of them. And protect face deliberately: arrange the evidence so that each side can change its reading without losing its standing, the vendor can accept a defect correction as a design improvement within the spirit of the spec, Sam can accept training reinforcement as the joint work of the fix, and both can walk out of the room with the identity they walked in with, plus a better system.

The difficult conversation is a design problem

The conversation is the instrument the whole craft runs through, and the discipline is to treat it as a design problem, the way chapter 27 treated the meeting, because the conversation that is left to instinct is the conversation that the instincts run, and the instincts were built for the savannah, not for the steering committee. Feedback and difficult conversations are the same act at different temperatures: feedback is the regular form, the observation about the work that lets a person or a team adjust before the consequence arrives; the difficult conversation is the feedback whose stakes are high enough that the room goes quiet, the classification dispute, the performance problem, the broken commitment, the politics. Both deserve the same design, and the design has a spine of four moves that this chapter’s mastery drill will ask the reader to script: observation, impact, inquiry, and request.

The observation is the hardest move to get right, because the observation is data, and the human mind does not naturally report data, it reports interpretation wearing the costume of data. “Your team did not follow the procedure” is not an observation, it is an attribution; the observation is “four of the twelve stations did not reach the paper kit within the recovery time objective, and the observer notes record them searching for the kit for a combined fifty-five minutes.” “You are not committed to the schedule” is an attribution; the observation is “the migration window decision has been deferred twice, on 3 and 10 August, and the vendor’s change window closes on 21 August.” The discipline of the observation is the discipline of the evidence hierarchy this book has used since chapter 2: name what happened, with dates and numbers where they exist, and mark the interpretation as interpretation, “in my reading,” “as I see it,” so that the interpretation can be examined instead of defended. The ladder of inference that chapter 12 used for stakeholder communication applies at the level of the sentence: the data, the selection, the meaning, the assumption, the conclusion, the belief, and the action climb the ladder in a single breath, and the observation is the move that refuses the climb.

The impact is the second move, and it answers the question the observation leaves open: why does this matter, and to whom? The impact is stated in terms of consequences, not character: “when the drill exceeds the recovery time objective, the gate condition at the first review is not met, and the record that the steering committee will read does not yet demonstrate that a patient whose record fails can be protected.” The impact is what converts the observation from a report into a reason to change, and it does it without a verdict on the person, because the consequence is attached to the behavior, not to the character. The impact is also where the leader must be honest about whose impact it is: the impact on the work, the patient, the gate, the budget, the team, stated plainly, not inflated, because the inflated impact, the drama version, is manipulation, and the room can feel the inflation.

The inquiry is the third move, and it is the move that most leaders skip, because it is the move that gives the other person the floor at the moment the leader most wants to hold it. The inquiry is the question that invites the other side’s view, their intent, their context, the pressure they were under, the constraint they were carrying: “what do you see in this record that I am not seeing?” “what was the situation when the kit was relocated?” “what would your team need to make the recovery path work?” The inquiry is not rhetorical and not a trap; it is the genuine request for the evidence that only the other person has, and it is the move that de-escalates, because it signals that the conversation is an exchange of views, not a verdict. The inquiry is also where the attribution error gets corrected, because the other person’s situation, which the observer cannot see, comes out of the room and onto the table, and the room that hears “we relocated the kits during the occupancy inspection, and the drill setup was not informed” has learned something the observation alone could not teach.

The request is the fourth move, and it closes the loop with a specific, owned, behavioral ask: “will the integration team add the fallback procedure to the recovery screen and confirm the kit locations with the clinic before each drill?” “will you bring the migration decision to the meeting on Thursday with a recommendation?” The request is what separates feedback that changes the work from feedback that changes the mood. It is specific, so that both sides know what was asked; it is owned, so that the asker is in it too, the support, the access, the time; and it is behavioral, so that the follow-up can verify it. The request is also where the commitment language of chapter 12 returns, the owner, the verb, the date, because a request without a date is a wish, and the follow-up is the meeting that opens with the previous record.

The four moves are the skeleton, and the craft is in the muscles, and the craft has three named conditions. The first is the care that the radical candor tradition names: Kim Scott’s 2017 book “Radical Candor” argues, in its own vocabulary, that effective feedback sits at the intersection of caring personally and challenging directly, and that the two common failures are ruinous empathy, the praise that avoids the challenge and lets the problem grow, and obnoxious aggression, the challenge that skips the care and wounds the person. The translation for this book: the challenge is the respect, and the respect is the challenge, and the conversation that says “your work matters to me, and this gap is in the way of what we both want” is the conversation that can be heard. The second is the receiver’s reality, which Sheila Heen and Douglas Stone map in their 2014 book “Thanks for the Feedback”: a person receiving feedback filters it through three triggers, in my own words, the truth trigger, is this accurate, the relationship trigger, is this the right person to be saying this to me, and the identity trigger, what does this say about who I am. The leader who has given the observation with data has addressed the truth trigger; the leader who has built the relationship through the ledger of chapter 26 has addressed the relationship trigger; and the identity trigger is addressed by the face-work of the previous section, the framing that separates the behavior from the person, “the drill fell short of the objective” rather than “you failed.” The third condition is the praise, because feedback does not survive on critique alone: the specific, evidence-based recognition of chapter 26, the acknowledgment that names the outcome rather than the hours, is what makes the critique possible, because a person who has been seen for what they did well can hear what they did less well. Praise that names the evidence, “the observer notes show eight stations found the procedure within the first two steps,” is the soil the difficult conversation grows in.

The minimum viable instrument is the conversation planner, one page, five fields, and it is the chapter’s second field output: the design the reader is asked to produce before the conversation happens. The first field is the diagnosis: the species, the stakes, the time, the relationship, the authority, the answer to the four questions of the decision tree. The second field is the outcome: what the conversation should change, the decision, the behavior, the commitment, stated as an object, not a feeling. The third field is the opening, scripted: the observation, the impact, the inquiry, the request, in the four-part form, written out, rehearsed, because the opening is the whole conversation, and the conversation that opens well rarely needs the rescue that the conversation that opens badly requires. The fourth field is the likely turns: the objection, the counter-attribution, the silence, the emotion, and the planned response to each, the inquiry that meets the counter-attribution, the pause that meets the silence, the acknowledgment that meets the emotion. The fifth field is the follow-up: the owner, the verb, the date, the review, and the record, because the conversation is not over when the room disperses, it is over when the follow-up verifies the request.

The planner is the design, and the delivery is the craft, and the craft has three practical rules. Choose the place and the time as design decisions: private, unhurried, the attention of both people, not the corridor, not the meeting’s edge, not the day before the gate. Choose the medium by the stakes: the consequential feedback, the classification dispute, the broken commitment deserve the live conversation, because the live conversation carries the face-work and the repair, while the small correction travels fine as a written observation, and the written difficult conversation is the one that gets misread at the exact moment the stakes are highest. And choose the opening to be first-person and evidence-based, in the four-part form, with the one sentence that is never said: the “you always” that is not an observation but a verdict, and the verdict is where the spiral starts.

Influence without the right to command

The project leader’s structural condition is the subject of this section: responsibility without authority. The project leader is accountable for the outcome, chapter 1 said, and the people who must act to produce it, the vendor, the peers, the executives, the operations staff, the other teams, mostly do not report to the project leader, which means the project leader must get people to act who do not have to, which is the definition of influence. The chapter 9 stakeholder system mapped who the people are and what they care about; chapter 12 built the communication and the negotiation; this section builds the influence, the craft of the ask, and it rests on a claim that is worth stating as a claim: influence is not a personality trait, it is a system of levers, and the system can be designed.

The levers, in the order a project leader should inventory them. Legitimacy is the weakest lever and the most common default: the mandate, the charter, the authority someone else delegated. It moves the people who care about the mandate, and it fails against the people who care about something else, which is most people. Expertise is the lever of the evidence: the person who has done the analysis, seen the failure mode, read the record, and can show the work. It moves the people who respect evidence, and it fails against the people who do not share the frame, which is why the next levers matter. Relationships are the lever of the ledger: the trust built in chapter 26, reliability plus honesty plus repair, the kept commitments, the honest bad news, the repaired mistakes. It is the lever that makes all the others work, because the person who trusts you will hear your evidence, and the person who does not will not. Reciprocity is the lever of the exchange: the favor bank, the help given before the help needed, the information shared before the information requested. It moves the people who keep ledgers, most people in a working relationship, and the research popularized in Adam Grant’s 2013 book “Give and Take” finds that the people who give without keeping score build the networks that let them call in help, with the caveat that the giver who cannot set boundaries becomes the taker’s resource. Reputation is the lever of the future: the track record of the person who delivers what they promised and reports what is true, the credibility that travels ahead of the introduction. It compounds, because the reputation of the person who hides bad news is the reputation that makes everyone re-verify. Information is the lever of the picture: the access, the early warning, the synthesis, the person who knows what is changing before it is public. It must be used with the ethics of chapter 4, because information held for advantage is manipulation, while information shared for the work is influence. Timing is the lever of the moment: the ask made when the decision is open, the evidence presented when the listener can absorb it, the alliance formed before the crisis. Influence that works arrives early; influence that arrives during the crisis arrives too late to build, only to direct. Coalitions are the lever of the network: the allies who carry the same evidence into different rooms, the trusted intermediaries of chapter 9, the federation leader, the respected clinician, the sponsor’s peer. The person who hears the same message from three directions hears it differently than from one.

The minimum viable instrument is the influence map, and it is the chapter’s third field output, one page, five questions. Who decides: the name, the decision right, the person whose signature or silence actually settles the question, and the discipline is to find the real decision right, which is usually not the loudest voice and not always the highest title. Who advises: the people whose view the decision maker will actually weigh, the trusted analyst, the peer, the confidant the decision maker actually consults, and the discipline is to find the advice channels, because the decision maker hears through the people they trust. Who blocks: the people who can stop the decision without making it, the veto holder, the compliance gate, the person whose silent refusal becomes a delay, and the discipline is to include the blockers in the influence design before the decision is made, because the blocker discovered after the decision is the blocker who has won. Who implements: the people who must act for the decision to mean anything, the nurses, the integration team, the operations staff, and the discipline is to treat implementation as the influence problem it is, because the decision that the implementers do not own is the decision that the implementers will quietly re-decide. And what does each one need to be able to say yes: the question that the whole map reduces to, the incentive, the risk, the constraint, the information, the face, the cover, the credit, and the discipline is to ask it literally, in the conversation, “what would you need to be able to say yes to this,” because the answer is usually a reasonable thing that the asker never asked for.

The influence map turns the ask into a design with a sequence. Start with the advisers and the blockers, who shape the decision before the decision maker sees it: give them the evidence early, ask their counsel, incorporate their constraint. Then the decision maker, with the evidence, the options, the recommendation, and the record, in their frame, their language, their success measures, because the influence that works answers the decision maker’s question, not the asker’s. Then the implementers, with the request, the ownership, the support, and the recognition, because implementation is where the decision becomes real. And throughout, the currency of the exchange, the help given, the information shared, the credit passed, because the map is not a one-time transaction, it is a ledger the next map will draw on.

The ethical line deserves its own paragraph, because it is the line that separates the craft from its corruption, and the book’s position is firm. Influence is the design of a request that preserves the other person’s agency: they could say no, they have the evidence to say no, and the request is honest about what it asks and what it offers. Manipulation is the design of a request that removes the agency: the lie, the withheld evidence, the manufactured urgency, the appeal to a false authority, the promise that will not be kept. The test is the one this book has used since chapter 4: would the person still say yes if they knew everything you know, and would the decision survive the record being made public? The influence that fails the test is not influence, it is a debt that will be collected, in the relationship, in the reputation, in the incident report, and the collection date is always sooner than the manipulator expects. The chapter 9 ethical boundary and the chapter 4 ethical decision record apply here without modification: the project leader influences, and does not deceive.

Politics: the informal system that decides

Politics is the word for the informal system that decides, and the first discipline is to say the word out loud, because the refusal to say it is the first move of the naive character this section will name. Every organization of more than one person runs two systems at once. The formal system is the one the org chart draws: the roles, the authority, the process, the governance, the decision rights of chapter 8. The informal system is the one the org chart does not draw: the relationships, the histories, the debts, the loyalties, the access, the trust, the timing, the unspoken rules about who is heard and who is not. The projects that run only on the formal system are the projects whose decisions stall at the informal gates the formal map does not show; the projects that pretend the informal system does not exist are the projects where the informal system runs them. Jeffrey Pfeffer, whose “Managing with Power” (1992) and “Power” (2010) argued the case over two decades, put it in terms that have aged well: power is not a dirty word, it is the capacity to get things done in an organization, and the refusal to build it is a choice with consequences, because the work still needs to get done, and the work will be done by the people who did build it.

The practices of the trustworthy politician, in the order a project leader should take them. Read the real decision flow: the org chart says the steering committee decides, and the real flow says the decision was settled in the corridor the day before, by the two people the committee trusts. For every decision you need, ask not who is on the committee but who the committee hears, because the committee hears through its trusted channels, and the trusted channels are the informal system. Map the stakes honestly: for every person who touches the decision, what do they win, what do they risk, what do they lose? Resist the caricature: the executive who delays the decision is not the villain, they are the person whose bonus, whose reputation, whose mandate is on the line. The stakes map is the chapter 9 stakeholder map with the incentives made explicit. Know the currencies: every organization trades in things other than money, recognition, access, information, credit, cover, time, and the exchange that works is the exchange of the currency the other person values, not the currency you value. Build the alliances before they are needed: the relationship built when there is nothing to ask for is the relationship that can carry the ask when it comes, and the discipline is the chapter 26 ledger, the small kept commitments, the honest bad news, the credit passed, the help given before the help needed.

Choose the battles: not every hill is worth the climb, and the discipline is the decision tree of the earlier section applied to the political field, the stakes, the time, the relationship, the authority, and the battle that fails the stakes test is the battle that spends the political capital the next battle needs. Choose the timing: the request made when the decision is open, the evidence presented when the listener can absorb it, the bad news delivered early enough to be a gift rather than late enough to be a betrayal, and the chapter 25 lesson holds, the corridor promise is the fastest currency of credibility lost, and the early bad news is the slowest. Present in their frame: the recommendation that answers the decision maker’s question, in their language, against their success measures, because the influence that works is the influence the listener can take into their own room and repeat without embarrassment, and the discipline is to test every recommendation against the question, “can the person I am asking repeat this to their own boss and look good?” And protect your credibility: the reputation of the person who delivers what they promised and reports what is true, because the credibility is the political capital, and the capital is spent by the promise that cannot be kept and the report that cannot be verified.

The three failure characters deserve names, because each is a recognizable person in every project, and each is a caution about what the trustworthy politician is not. The naive treat the org chart as the power map: they build the evidence, submit it to the formal process, and wait, and the decision stalls at the informal gate they did not see, and they conclude the organization is irrational, which is the naive’s defining move, the attribution of the informal system’s existence to other people’s irrationality rather than to the structure of power. The cynical treat every colleague as a rival: they read every conversation for the angle, every offer for the trap, and they are right often enough to confirm the reading, and the reading becomes self-fulfilling, because the colleagues they treat as rivals become rivals, and the alliances they never built are the alliances the trustworthy built instead. The manipulative trade on secrets and pressure: they withhold, they exaggerate, they manufacture urgency, they use the vulnerability they learned in confidence, and they win the short game and lose the long one, because the people they manipulated keep the record, and the record is the reputation, and the reputation is the future influence. The trustworthy politician is none of the three: they see the informal system, they work it openly, they build the alliances and the credit and the timing, and they do it without deception, because the openness is not a limitation, it is the strategy, and the reputation for openness is the lever that makes the other levers work.

The boundary case is where the discipline is tested: the conflict of interest and the hidden agenda. The conflict of interest is the situation where the person’s incentives point away from the work, the vendor’s account manager whose bonus depends on containing the defect scope, the executive whose legacy is tied to the date, the peer whose project competes for the same budget, and the discipline is not to pretend the conflict does not exist, it is to name it, to bring it into the open where it can be examined, and to design the governance that contains it, the decision on the record, the external reviewer, the escalation path. The hidden agenda is the name for the interest that has not been disclosed, and the discipline is the same in reverse: the person whose “yes” comes with a condition they have not stated, and the only way to surface the hidden agenda is the question that the influence map ends with, “what would you need to be able to say yes,” asked early, asked often, asked in the room, because the agenda that is surfaced is an agenda that can be negotiated, and the agenda that is hidden is a bomb with a fuse.

Safety and standards, held together

The conflict craft depends on a climate, and the climate has a name that the research gave it and a shape that the practice must hold. Psychological safety, in the sense Amy Edmondson gave the term in her 1999 study of learning behavior in work teams, published in the Administrative Science Quarterly, is the shared belief that a team is safe for interpersonal risk-taking, that a person can speak up, ask the question, admit the error, challenge the plan, without being punished or humiliated. The evidence for its power is strong: Edmondson’s own studies of hospital teams found that the teams with the most psychological safety reported the most errors, not because they made more, but because they could say them, and the teams that could say their errors were the teams that learned from them, while the silent teams were the ones whose errors surfaced in the incident report. The chapter 26 version of this finding, the four rooms of comfort, anxiety, apathy, and the learning room, and the Google research that found safety the most important of the five team dynamics, is the team-level statement; this section is the conflict-level statement, because the conflict craft is impossible in a room where the disagreement is priced as a risk.

The shape is the two axes, and it is the correction to the most common misreading of psychological safety, which is the misreading that safety means comfort. Edmondson’s own framing, developed in her 2018 book “The Fearless Organization,” is two-dimensional, in my own words: psychological safety on one axis, the freedom to speak, and performance standards on the other, the expectation of excellence, and the two axes make four zones. High safety and low standards is the comfort zone, the team that is warm and undemanding, where the feedback is soft, the challenge is rare, and the mediocrity is protected by politeness. Low safety and low standards is the apathy zone, the team that neither cares nor speaks, where the work is done with the least engagement that will pass. Low safety and high standards is the anxiety zone, the team that is demanding and afraid, where the pressure is high and the silence is total, where the errors are hidden and the blame is sharp, where the conflict goes underground and the corridor runs the project. And high safety and high standards is the learning zone, the team where the bar is high and the voice is free, where the task conflict is welcome because it is safe, where the person who says “the drill record is wrong” is thanked, and where the accountability holds because the safety makes it bearable.

The leader’s moves are the moves that hold the two axes together, and they are five, and each has a failure mode that must be named. Model vulnerability: the leader who says “I misread the record,” “I changed the schedule without checking the clinics,” “I was wrong about the migration window,” demonstrates that error is discussable, and the failure mode is the leader who confesses the small error and conceals the large one, because the room reads the pattern, and the pattern teaches that confession is theater. Invite dissent explicitly: the chapter 27 re-ask, the designated dissenter, the second-chance question, “before we record this, who holds a doubt that has not been spoken,” and the failure mode is the invitation that is not sincere, the leader who asks for dissent and punishes it, because the insincere invitation is worse than none, it teaches the room that the ask was a test. Respond with curiosity: the challenge answered with “say more,” “what do you see,” “walk me through the record,” instead of with defense, and the failure mode is the leader whose curiosity is a delay tactic, the question asked to buy time until the defense arrives, because the room reads the difference between the question that seeks the evidence and the question that postpones the verdict. Price silence: the leader who names the cost of the unspoken, “the silence in this room is a risk on the register,” who thanks the person who spoke the uncomfortable truth, who records the dissent that was overruled, and the failure mode is the leader who prices silence in words and rewards it in action, because the team watches the action.

And separate accountability from blame, which is the move that makes the safety sustainable, because the room that is safe for errors is the room where the errors still have owners and the owners still have consequences, and the distinction is the difference between the question “who is responsible for the recovery path” and the question “whose fault is the failed drill,” the first an accountability, the second a verdict, and the leader who asks the first while refusing the second is the leader who can hold the high standards without killing the safety.

The balance is the chapter’s answer to the two most common objections, and both objections are half right. The objection that psychological safety is softness meets the answer of the anxiety zone: the demanding team that is afraid is not a high-performing team, it is a team whose failure is invisible, and the high standards without safety are the standards that produce the silent incident. The objection that accountability is blame meets the answer of the comfort zone: the warm team without consequences is not a safe team, it is a team whose failure is protected, and the safety without standards is the safety that produces the polite disaster. The learning zone is the both, the high bar and the free voice, and it is the climate that this chapter’s whole craft requires, because the difficult conversation can only be held in a room where the difficult conversation is known to be safe, and the influence can only be built in a system where the candor is known to be priced.

When the leader must carry the conflict

The craft so far assumes the leader can hold the conversation, and most of the time the leader can, because most conflicts are the two people in the room with the record on the table. But three situations take the craft beyond the conversation, and the leader must recognize each one, because each has a different instrument and a different exit. The first is the conflict that the parties cannot resolve themselves, because the emotions are too hot, the history too long, or the positions too public. The second is the conflict whose resolution is outside the room, because the authority, the budget, or the obligation belongs to someone else. The third is the conflict that is genuinely irreconcilable, because the values at stake will not trade. The instruments for the three are mediation, escalation, and containment, and the failure to distinguish them is the failure that turns a resolvable dispute into a wound.

Mediation is what the leader does when the parties are stuck and the leader is not a party, and the discipline is that the leader who is a party cannot mediate — the rule chapter 27’s facilitation section stated for the retrospective, restated here for conflict: the person whose own interests are in the room cannot hold the process, because the process will serve the interest, invisibly and honestly, and the room will feel it. The leader who is a party has two options: hand the mediation to a colleague who is not, the sponsor, the PMO lead, the trusted peer, or separate the roles explicitly, “I am the decision owner and I will hold the process, and I will ask you both to hold me to it,” which is harder and sometimes necessary. The mediation itself has a sequence, and the sequence protects the face of both parties before it touches the substance. Meet separately first, and the separate session is the collection of the two views, the two evidence sets, the two face needs, and the two red lines, and the discipline is to ask, in the separate session, the three questions that the joint session cannot ask safely: “what do you need to be able to work with the other side on this,” “what would make this acceptable to you,” “what must not happen in the joint session.” The separate sessions are also where the leader learns whether the conflict is resolvable at all, because the red lines heard in private are the red lines that the joint session will confirm. Then the joint session, and the joint session is a designed room, not a free-for-all. The ground rules are stated at the opening, the leader holds the process, the airtime, the order, the record; the people are separated from the problem in the framing, “we are here to fix the recovery path, and both of you own parts of it”; the interests are invited before the positions, “what do you each need to be able to say the clinic is safe to keep running.” The frame is future-facing, the request and the commitment rather than the attribution and the history, because the past is where the blame lives and the future is where the fix lives. And the close restates the agreement, owns the actions, sets the dates, confirms the record, and names the review date. The mediation fails in two characteristic ways, and both are visible in advance. The joint session held too early, before the separate sessions have collected the face needs, is the session that explodes, because the face needs were never heard. And the joint session that ends with a handshake and no record is the session that will be re-litigated, because the handshake does not survive the corridor, and the record does.

Escalation is what the leader does when the resolution is outside the room, and the instrument is the escalation brief, the chapter’s fourth field output, and it deserves a full description because it is the difference between the conflict that travels as a problem and the conflict that travels as a decision. The escalation brief is one page, and it carries the issue, the parties, the attempts, the interests, the options, and the recommendation, with the decision right and the date attached. The issue is the conflict named in one sentence, with the evidence, the drill record, the four slowest stations, the recovery time objective, the classification dispute. The parties are the two sides, named, with their positions and their legitimate interests, because the brief that names one side as the problem is not an escalation, it is a weapon. The attempts are what the project has already done, the separate sessions, the joint session, the evidence review, the offers, the refusals, because the escalation that arrives without the attempts is the escalation that arrives as someone else’s problem, and the attempts are what makes it the authority’s decision. The options are the real alternatives, with the consequence and the cost of each, the design change, the training, the condition, the re-drill, the cost, the schedule, the risk, because the authority cannot decide without options, and the options are what the decision tree of the earlier section produces. And the recommendation is the leader’s judgment, stated plainly, with the confidence and the uncertainty named, because the brief that asks the authority to decide without a recommendation has abdicated the judgment the authority delegated. The escalation brief is the chapter 4 ethical decision record’s operational cousin: the record covers the decision made under pressure, the brief covers the decision that must not be made in the room, and both carry the same discipline, the evidence, the options, the recommendation, the decision right, the date.

Containment is what the leader does when the conflict is genuinely irreconcilable, and the discipline is the hardest of the three, because it requires the leader to accept that some disagreements do not resolve. The values conflict is the usual case: the clinical director who will not compromise the safety standard, the community leader who will not accept the relocation, the regulator who will not move the date, and the values do not trade, and the consensus that the room reaches by pressure is not a resolution, it is a postponement of the dissent into the implementation. The containment has five moves, and each is a decision on the record. Name the conflict openly, “we disagree about whether the gate can hold, and the disagreement is about values, not competence,” because the unnamed values conflict goes underground and sabotages from below. Identify the decision right, the person or forum whose authority the decision belongs to, the steering committee, the sponsor, the regulator, and state it at the opening, “this decision belongs to the committee, and the committee will make it on the record.” Make the decision on the record, with the evidence, the options, the rationale, and the dissent noted, because the decision that records the dissent is the decision that the dissenter can live with, and the decision that erases the dissent is the decision that will be fought later. Set the review date, because the values conflict may not be resolvable today and may become resolvable when the evidence changes, and the review date is the promise that the dissent was heard, not overruled into silence. And then proceed, with the decision, because the project cannot wait for the values to align, and the leader who postpones the irreconcilable decision is the leader who has made the delay the decision, which is a decision the leader was not authorized to make. The containment is not a failure of the craft, and the chapter says this plainly because the craft literature rarely does: some conflicts are not meant to be resolved, they are meant to be decided, and the mastery is in knowing which is which, and the test is the one the separate session collects, whether the red lines have a path to move, and the values conflict whose red lines are absolute is the conflict that containment fits.

The three instruments share a rule, and the rule is the chapter’s operational heart: the conflict that is resolvable in the room belongs in the room, the conflict that is not resolvable in the room belongs on the record, and the conflict that is not resolvable at all belongs in the decision right, and the failure pattern that covers all three is the leader who holds a conflict that belongs elsewhere, who mediates what the authority should decide, who escalates what the room should resolve, who contains what could have been negotiated, because the holding pattern is the most comfortable of the failures, it feels like responsibility, and it is the responsibility that is actually procrastination wearing a title.

The record of the rehearsal

The worked application runs the instruments in order, and it starts where the chapter started, with the room that has two readings of the same record. Dana Okafor, the project leader, does not start with the evidence, because the evidence is what both sides already have, and the evidence is the problem, not the solution, until the layers underneath it are handled. She starts with the diagnosis, and the diagnosis takes a walk, not a meeting. She walks to Sam’s clinic floor first, because Sam’s face and Sam’s history are the ones she can read without armor, and she asks him the separate-session question: “what do you need to be able to work with the vendor on this?” Sam answers with the chapter 11 history, the nurses who were trained and reverted to paper, the terminal at the end of the corridor, the dashboard that showed 95 percent trained and 35 percent adopted, and he says the sentence that names his real interest: “my staff did not fail this drill, and I will not let the record say they did.” The interest underneath the defect position is the dignity of his staff and the truth of the record, and Dana records it. Then she walks to the vendor’s implementation lead, in the integration room, and asks the same question, and the vendor lead answers with the contract: “we delivered to spec, we priced to spec, and if the spec moves after the fact, the next spec will be priced with that risk inside it.” The interest underneath the training position is the integrity of the contract and the viability of the vendor’s own business, and the interest is as legitimate as Sam’s, which is the diagnostic finding Dana needed: the species is not values, it is a task conflict with process, relationship, and status layers, and the interests are compatible beneath the positions, because both sides want a recovery path that works and a record that tells the truth.

The diagnosis done, Dana designs the joint session, and the design is the chapter’s craft in sequence. The session is private, neutral, unhurried, an hour and a half, no steering committee in the room, because the status layer needs an audience, and the audience would escalate the status conflict. The opening is the ground rules and the frame, and Dana speaks the frame out loud: “we are here to fix the recovery path, and the record is the evidence we share, and the classification, defect or training, will be decided by the acceptance criteria and the clinical governance review, not by this room’s persuasion.” The frame is the face protection: neither side is asked to concede, the criteria will decide, and the criteria are outside the room’s politics. Then the evidence, and here Dana runs the observation, impact, inquiry, request form herself, as the chapter’s model: the observation is the drill record, the four slowest stations, the cluster at the recovery screen, the fifty-five minutes of kit search, the telemetry, the nine-second display, the eight of twelve first steps; the impact is the gate condition and the patient, the first review, the wave three planning, the record that the steering committee will read; the inquiry is the move that changes the room, because Dana asks each side, “what do you see in this record that the other does not,” and the vendor lead answers with the relocation, “the kit was moved by the occupancy inspection, and our walkthrough was before the move,” and Sam answers with the screen, “the recovery path asks the clinician to return to a workflow that is gone, and the procedure is not visible anywhere in the path.” Both statements are true, and the room hears the two truths side by side, which is the moment the attribution spiral dies, because each side has been given the other’s situation, and the situation is what the attribution could not see.

The classification is the joint session’s substance, and the instrument is the acceptance matrix of chapter 21, which is the agreement both sides actually signed, and which neither side can accuse the other of moving. The matrix row for the escalation capability names the acceptance criterion, in the words the project and the vendor agreed: a clinician can recover a patient’s record within the recovery time objective using the documented fallback, without external assistance, under a simulated interruption. The rehearsal is the verification evidence for that criterion, and the record is the evidence. Dana puts the row on the table, and the question becomes narrow and technical: does a recovery path that presents “return to the workflow” and no fallback procedure, with the kit in an unverified location, satisfy the criterion “using the documented fallback, without external assistance”? The vendor lead reads the row, and the room watches the reading, and the vendor lead says the sentence that the face protection made possible: “under the criterion as written, the recovery path does not demonstrate the fallback is documented at the point of recovery, and I will take that to our defect handling as a nonconformance, on the condition that the training reinforcement is part of the fix, because the drill also shows the procedure was learned and then not followed under pressure, and the fix should not pretend the training is irrelevant.” The vendor’s position moves, and it moves because the criterion is the reference, not because the vendor lost a contest, and the move costs no face, because the criterion, not the vendor, made the call, and the vendor gets the training point in return. Sam accepts the training reinforcement for the same reason, because the fix is the joint design, and the criterion is the judge.

The politics arrives in the week after the session, and the chapter teaches it because the chapter teaches the informal system, and the informal system does not stop because the joint session succeeded. Dana learns, through the corridor, that the vendor’s account manager has briefed the finance director privately — the week before the classification reached the steering committee — that the “defect” framing is the project’s way of buying an enhancement on the vendor’s budget. The finance director, carrying the grant window and the wave three schedule, has started to lean toward the training-only reading. The briefing is not deception, it is politics, the account manager protecting the vendor’s interests through the informal system, and the finance director is a reasonable person with a reasonable interest, the schedule. Dana’s move is the move this chapter teaches: she does not outflank the account manager, and she does not retaliate, because the retaliation would make the account manager an enemy and the finance director a party, and both would be right to feel it. She invites the account manager and the finance director into the evidence review, the acceptance matrix row, the drill record, the joint session’s record, and the classification recommendation, with the decision left to the steering committee on the record, where it belongs. The account manager, seeing the criterion and the data, and seeing that the decision will be made on the record with the external reviewer present, does what the evidence review makes possible: he withdraws the private framing, publicly, in the review, and the finance director drops the training-only reading, and the classification travels to the steering committee as a joint recommendation rather than a dispute. The chapter’s lesson is stated in the telling: the informal system will run whether the leader acknowledges it or not, and the leader who brings the informal briefing into the open evidence, without humiliation, has used the politics instead of being used by it.

The steering committee decides on the record: the recovery screen is a nonconformance against the accepted criterion, corrected by the vendor under its defect handling, with the change to the recovery path, the fallback procedure visible at the point of recovery, and the kit locations verified and documented at every clinic as part of the drill setup; the training reinforcement is co-delivered, the vendor’s trainers and Sam’s super-users, scenario-based, in the first two weeks; the second rehearsal runs at clinic two in week three, with the same twelve stations, the same incident, the same recovery time objective, and the record of the second drill becomes the gate evidence at the first review, which chapter 24’s condition requires; and the fix, the screen change and the kit verification, propagates to clinic one and the wave three clinics before their own rehearsals, because the record review found the same recovery-path gap in the clinic one materials, the paper kit that had been relocated and never re-verified. The second rehearsal passes: all twelve stations recover within the recovery time objective, the slowest at twenty-six minutes, and Sam’s reading and the vendor’s reading meet in the outcome that neither reading alone would have produced, the design fix that the vendor owned and the training that Sam’s team co-delivered, and the record shows the two owners side by side, which is the record the trust is built from.

The worked application closes with the caution that closes every worked application in this book: the instruments are the instruments, and the instruments are only as alive as the people who hold them. The acceptance matrix settles the classification because both sides signed it, and the matrix that is not kept current is the matrix that will fail the next dispute; the joint session changed the room because the face protection preceded the evidence, and the leader who skips the separate sessions to save time has spent the time that the joint session will need; the politics moved because the informal briefing was brought into the open evidence without humiliation, and the leader who retaliates against the informal system has declared war on a system that cannot be defeated, only navigated. And the deepest caution is the one the chapter has been building toward: the resolution worked because the conflict was diagnosable as task with layers, and the interests were compatible beneath the positions, and the leader who applies the same craft to a genuine values conflict, the regulator’s standard, the community’s red line, has misread the species, and the mediation that works on the screen dispute will fail on the values dispute, which is why the containment discipline belongs beside the conversation craft, in the same kit, for the same leader.

What the machine can hold

The conflict craft is document-heavy at its edges and human-heavy at its center, and the boundary is worth drawing precisely: the machine is genuinely useful at the edges and genuinely dangerous at the center, and a chapter that did not draw the line would teach its readers to automate the face-work, the one thing that cannot be automated. The machine can draft the diagnosis checklist from the project’s records: the species prompts, the four questions of the decision tree, the stakes, the time, the relationship, the authority, the fields of the conflict diagnosis, prefilled from the schedule, the gate dates, the contract, the stakeholder register, and the draft is a starting point, and the diagnosis itself, the reading of what kind of conflict this is and who holds the red lines, is the leader’s, because the machine cannot see the history in the corridor. The machine can draft the conversation planner skeleton: the observation field, with the candidate observations extracted from the record, the dates, the numbers, the events, and the discipline is the one this chapter taught, the machine can assemble the data and the human must mark the interpretation, because the machine cannot reliably distinguish the observation from the attribution, and the sentence “your team did not follow the procedure” is grammatically identical to “four stations did not reach the kit,” while the first is a verdict and the second is a fact. The machine can draft the influence map from the stakeholder register and the decision log: the who decides, who advises, who blocks, who implements, the names and the roles, and the map is a hypothesis, because the real decision flow, the corridor, the trusted channels, the currencies, is the knowledge the machine does not have, and the leader who trusts the drafted map over the walked floor has confused the register with the system. The machine can draft the escalation brief from the issue log, the attempts, the options, the dates, and the brief is the efficient form, and the recommendation, the judgment, the confidence, the choice among the options, is the leader’s, because the recommendation is the accountability, and the accountability does not delegate.

The machine’s most useful role in this chapter is the one it can do honestly: flag the attribution language in the project’s own records, the minutes, the issue log, the status report, the sentences that say “the team failed to,” “the vendor refused to,” “the contractor delayed,” and mark them for review against the observation standard, because the flag is a mechanical pattern and the review is the human craft; the machine that flags “your staff were not trained” in the draft minutes has done the room a service, and the rewrite into “the drill exceeded the objective” is the craft, and the craft is the leader’s. The data boundary is the boundary this book has held since the personnel chapters, and it holds absolutely here, because this chapter’s material is the most sensitive in the book: the difficult conversation, the performance feedback, the mediation, the politics, the names, the face, the personnel records, the negotiations, belong inside the approved boundary, and no draft, no summary, no transcript, enters an unapproved system, whatever the tool promises, because the person whose difficult conversation was summarized into a database has been given a reason to stop having difficult conversations, and the silence is the cost. And the center stays human, and the center is the whole point: the conversation itself, the observation spoken with the care that the receiver can hear, the inquiry that invites the other’s situation, the face protected in the room, the read of whether the red line moves, the judgment of who must be in the room and who must not, the decision to mediate, escalate, or contain, all of it is the human system, and the human system is the subject of this part of the book, and the machine that is asked to hold the difficult conversation has been asked the one question it cannot answer, what is happening between these two people, and the answer is the leader’s, held with the attention that the people in the room have entrusted.

Practice

One. A quick check: name the species. For each scene, name the primary species of conflict, task, process, relationship, status, or values, and the response that fits it. (a) At BlueLine, the civils director and the contractor’s project manager disagree about whether the flood-plain certification evidence supports the resequence, and both sides bring drawings and test records. (b) At KijaniPay, the compliance team and the delivery team have spent three meetings arguing about whose approval gates the merchant onboarding flow, and neither team can say who owns the interface. (c) At Meridian, Sam Otieno has stopped trusting the vendor’s implementation lead since the rehearsal, and he now routes every vendor communication through Dana instead of resolving it directly. (d) At Northstar, the field logistics lead and the headquarters operations lead are arguing in front of the coordination meeting about whose forecast was wrong, and the audience is the other field teams. (e) At Meridian, a clinical governance lead states that connecting a clinic before the accessibility remediation is complete violates the organization’s standard, and the finance director answers that the grant window cannot wait, and neither position moves.

(a) is task conflict: the evidence is on the table, and the fitting response is the evidence review, the criteria, the acceptance matrix, a decision method, and a date. (b) is process conflict: the ownership was never settled, and the fitting response is the interface agreement and the decision rights, written down, because the argument about the process is an argument about a missing decision, not a difficult person. (c) is relationship conflict: the trust ledger is damaged, and the fitting response is the repair conversation, the history named, the small reliable acts, and the boundary that keeps the work moving; a data review would confirm each side’s worst reading of the other. (d) is status conflict: the audience is the tell, and the fitting response is the status work and the private room, because status conflict escalates when it is performed and de-escalates when it is private. (e) is values conflict: the standard will not trade for the window, and the fitting response is containment and decision, the value named, the decision right identified, the decision on the record, the dissent noted, and the review date. The trap is grading the scenes by the heat of the argument rather than the species: heat is the symptom, the species is the diagnosis, and the response that fits the species is the response that reduces the heat.

Two. A field drill: the conversation planner for a real conflict. Take a conflict that is live on the project you lead or know best, and produce the planner before the conversation happens. (a) Diagnose: name the species, and run the four questions, the stakes, the time, the relationship, the authority, and choose the response mode, avoiding, accommodating, competing, compromising, collaborating, with the reason. (b) Name the outcome: what the conversation must change, the decision, the behavior, the commitment, stated as an object. (c) Script the opening in the four-part form: the observation, the data, with the interpretation marked as interpretation; the impact, the consequence, attached to the behavior, not the character; the inquiry, the genuine request for the other side’s view, intent, and context; and the request, specific, owned, behavioral, with the date. (d) Plan the turns: the likely objection, the counter-attribution, the silence, the emotion, and the response to each. (e) Write the follow-up: the owner, the verb, the date, the review, and the record.

The drill passes when the opening can be read aloud and the observation field contains no attribution, no “you always,” no verdict disguised as data, and the inquiry is a question the other person can answer without losing face. The three failures and their repairs: the observation written as interpretation, “he is not committed to the schedule,” repaired by the data, “the migration decision has been deferred twice, on 3 and 10 August, and the vendor’s change window closes on 21 August,” because the data is examinable and the interpretation is not; the inquiry written as a rhetorical trap, “you do see the problem, right,” repaired by the open question, “what do you see in this that I am not seeing”; and the request without the date or the ownership, repaired by the commitment form of chapter 12, the owner, the verb, the date, because the request without a date is a wish, and the follow-up is where the conversation is verified.

Three. A field drill: the influence map for a decision you need. Take a decision that is waiting on people who do not report to you, and draw the map. (a) Who decides: the name and the decision right, the real right, not the loudest voice. (b) Who advises: the people the decision maker hears, and the advice channels. (c) Who blocks: the veto holders, the silent delays, the compliance gates. (d) Who implements: the people whose action makes the decision real. (e) What each one needs to be able to say yes: the incentive, the risk, the constraint, the information, the face, the cover, the credit, and the discipline is to ask the question literally, in the conversation, “what would you need to be able to say yes to this.” (f) Design the sequence: the advisers and the blockers first, the decision maker second, the implementers third, and the exchange, the help given, the information shared, the credit passed.

The drill succeeds when the map changes the plan, when the who-advises column changes the sequence of the asks, and when the what-do-they-need column contains at least one answer the reader did not know. The three failures and their repairs: the map that stops at the org chart, repaired by the walked floor, the question asked in the corridor, “who actually settles this,” because the informal system is the map and the org chart is the decoration; the who-blocks column left empty, repaired by the question “who can stop this without deciding it,” asked until it yields a name; and the sequence that skips the advisers and the blockers, the evidence taken straight to the decision maker, repaired by the ordering of the section, because the decision arrives at the decision maker already shaped, and the shaping is the influence.

Four. A decision room: the classification dispute at Meridian. It is the week after the failed rehearsal at clinic two, and the options on the table for the first review are: (a) accept the vendor’s reading, a training and environment issue, and schedule scenario retraining plus a kit-verification pass, with the recovery screen unchanged; (b) accept Sam’s reading, a product defect, and require the vendor to redesign the recovery path under the defect clause before the next drill, with no training reinforcement; (c) run the joint evidence review, the acceptance matrix row on the table, the drill record, the telemetry, the relocation, and take the classification to the steering committee on the record, with the design change as a defect correction and the training reinforcement co-delivered; (d) postpone the classification to the wave three planning, run the second rehearsal as scheduled in week three, and let the record of the second drill settle the question. Decide the move, the order of the rooms, the record, and what the escalation brief must carry if the steering committee is needed.

The defensible answer is (c), and the reasoning is the chapter’s sequence: the classification belongs to the criteria and the decision right, not to the persuasion of either party, and the acceptance matrix is the reference both sides signed, which makes the move principled rather than political. (a) protects the schedule and the vendor’s scope but leaves the four slowest stations’ failure unexplained, and the chapter 11 history, the trained nurses who reverted to paper, is the evidence that training alone has already failed once; (b) forces the design change but buys it with a fight, the vendor reads the defect classification as scope creep, the account manager briefs the finance director, and the status conflict escalates with an audience; (d) is the postponement machine of chapter 27 wearing the evidence costume, the second drill run on an unresolved defect. The order of the rooms: the separate sessions first, Sam’s floor, the vendor’s integration room, the face needs and the red lines collected; then the joint session, the matrix row, the record, the telemetry, the relocation, the observation, impact, inquiry, request; then the steering committee on the record, with the external reviewer, the classification, the design change as a defect correction, the training co-delivered, the second drill in week three, the fix propagated to clinic one and wave three, and the review date. The escalation brief must carry the issue, the parties with their legitimate interests, the attempts, the options with costs, and the recommendation, because the steering committee decides on the record, and the brief is what the decision is made from. Credit belongs to any answer that lets the criteria decide and protects the face of both parties; the unsafe answer is (b) in a public forum, because the public defect verdict with no face protection converts a resolvable task conflict into a relationship scar.

Five. A decision room: the retrospective that must hold the senior engineer. It is KijaniPay, and the retrospective has reached the settlement-exception spike, the January incident where the exception queue peaked at 640 items and the settlement engineer’s fix sat waiting for a signature for four days, and the room is blaming the engineer, a senior specialist who has delivered the platform’s core settlement logic for three years. The options: (a) name the engineer’s delay as the root cause, with the dates, and set the expectation that the next exception is escalated immediately; (b) let the retrospective focus on the system, the approval workflow, the queue policy, the signature requirement, and address the engineer’s delay privately, outside the room; (c) run the full chapter: the observation with the dates, the impact on the merchants and the queue, the inquiry into the four days, what the engineer was waiting for, and the request, an owned change to the exception escalation; (d) skip the individual question entirely and treat the spike as pure system design. Decide the move, and say what the record must carry.

The defensible answer is (c) in the room, with the private follow-up, and the reasoning is the learning zone’s two axes: the high standard, the four days are a real gap and the engineer owns a real part of it, and the high safety, the gap is examined with the inquiry, not the verdict. (a) is the attribution error weaponized, the blame assigned in front of the room, the identity threat, the senior specialist’s face spent as the price of the lesson, and the chapter 26 consequence follows, the silence, the withheld evidence. (d) is the comfort zone, the system absolved of the person, and the chapter 21 lesson applies, the root cause is the person and the system together, and the fix that excludes the person’s behavior is the fix that repeats. (b) is half right, the system focus is the learning zone’s frame, but the engineer’s delay is the observation that belongs on the table, because the retrospective that censors the individual gap teaches the room that the gap is unspeakable. The record must carry: the observation, the four days, the impact, the queue peak, the merchant harm; the inquiry’s finding, what the engineer was waiting for, the signature, the unclear ownership; the request, the owned change, the exception escalation path, the engineer’s commitment and the system’s commitment side by side; and the follow-up date, because the record is the contract, and the contract is verified at the next retrospective. The unsafe answer is (a), because the public blame spends the safety, and the safety is the climate the whole conflict craft depends on.

Six. The mastery drill: script the opening of the difficult conversation. Take the Meridian scene, or a conflict of your own, and script the first ninety seconds of the conversation in the four-part form. Write the observation, the data, with dates and numbers where they exist, and no attribution; write the impact, the consequence, attached to the behavior and the work, not the character; write the inquiry, the genuine open question that invites the other side’s view, intent, and context; and write the request, specific, owned, behavioral, with the date. Then read the script aloud, and check it against the three triggers: would a reasonable person hear the truth trigger answered, the observation as accurate data; the relationship trigger answered, the care and the history present; the identity trigger answered, the behavior separated from the person, the face protected.

The drill passes when the script can be spoken without the sentence “you always,” without the verdict disguised as data, and without the rhetorical inquiry, and when the person hearing it could repeat it back without embarrassment. The Meridian model, in the voice this chapter taught: “The rehearsal record shows eight of twelve stations outside the recovery time objective; the four slowest clustered at the recovery screen, and the observer notes record them searching for the paper kit for a combined fifty-five minutes, with the slowest at ninety-seven minutes, forty of them spent searching. As I read it, the gap is in the recovery path, and the impact is the gate condition at the first review and the patient whose record fails before the fix. What do you see in this record that I am not seeing? Will the integration team add the fallback procedure to the recovery screen and verify the kit locations with the clinic before the next drill, by the end of this week, and will you join me in the joint review on Thursday to walk the matrix row together?” The check against the triggers: the truth trigger is answered by the data, the record, the eight of twelve, the fifty-five minutes, the ninety-seven; the relationship trigger by the care, the shared problem, the Thursday walk-through, the invitation; the identity trigger by the frame, the gap is in the path, not in the person, and the fix is the joint work. The failures and their repairs: the observation that climbs the ladder of inference, “the vendor did not train the staff,” repaired by the data, the drill record, the telemetry, the dates; the request that is a wish, “we should fix the recovery path,” repaired by the owned, dated request, “will you own the screen change by the end of this week”; and the script that protects the asker’s comfort, the inquiry asked as a formality, the request softened to avoid the risk, repaired by the honesty of the chapter’s frame, the care and the challenge together, because the conversation that protects only the asker has spent the other person’s face without buying the fix.

Seven. The transfer question. On the project you lead, who are you avoiding, and what is the conflict costing, the deferred decision, the silent expert, the rework, the corridor conversation? What species is it, and what does the decision tree say, the stakes, the time, the relationship, the authority, and what mode does the tree name? What are the positions, and what are the interests underneath, and where do the interests overlap, because the overlap is where the fix lives? Who holds the identity in the room, and whose face is at stake, and what is the arrangement that lets them change their reading without losing their standing? Who decides the decision you need, who advises them, who blocks, who implements, and what does each one need to be able to say yes? What is the informal briefing that will run whether you acknowledge it or not, and what is the open evidence that could hold it? And when the conflict is over, what will the record carry, the decision, the dissent, the owners, the dates, the review date, the sentence that says the two owners fixed it together? The durable principle: conflict is information before it is a problem, and the leader’s first move is diagnosis, because the species determines the response, and the response that fits a task conflict inflames a relationship conflict, and the craft that lets the evidence settle the substance is the craft that protects the face while the work advances. The most common next failure is the one this chapter’s worked application named: the conflict resolved and the climate unchanged, the matrix filed, the joint session forgotten, the informal system left to run, the silence priced in words and rewarded in action, because the craft is not a sequence of meetings, it is a climate, and the climate is held by the leader’s own behavior, the vulnerability modeled, the dissent invited, the curiosity kept, the accountability held, the face protected. And the climate has a next seam this part has been building toward: the conflict craft, the feedback, the influence, and the politics are the work of the rooms, and the rooms only matter if the work moves, which is the argument of the next part of the book, the mobilization and execution that turns alignment into delivery, and the next chapter opens where every project’s promise is tested, in the first thirty days of a credible start.

Notes

• The composite cases remain author-created illustrative material. The Meridian rehearsal scene, the hypercare escalation drill at clinic two with twelve stations and a recovery time objective of thirty minutes, four stations within the objective, five between thirty and sixty minutes, three beyond the hour, the slowest at ninety-seven minutes with forty minutes of kit search, the platform telemetry displaying the recovery screen within nine seconds at all stations, eight of twelve following the first two steps of the trained procedure, the auto-lock recovery screen presenting “return to the workflow” and nothing else, the paper kit relocated by the occupancy inspection, the acceptance matrix row for the escalation capability naming the recovery criterion, the vendor’s acceptance of the nonconformance with the training reinforcement as the condition, the account manager’s private briefing of the finance director, the second rehearsal passing all twelve stations with the slowest at twenty-six minutes, and the fix propagated to clinic one and the wave three clinics, are all teaching constructions consistent with the facts established in earlier chapters: the six-clinic program, the shared platform, the grant window at month thirty-six, and the sponsor Elena Marchetti from chapters 1, 5, and 8; the wave structure with clinic one live and clinics two and three as wave two, the hypercare, the escalation rehearsal running in the first week of operation with Sam Otieno as the owner and the record judged at the first review, the sub-processor amendment, the continuity drill, the recovery time objective and the recovery point objective, the conditional release conditions, and the external reviewer from chapters 23 and 24; the acceptance matrix with its verification and validation evidence and the acceptance criteria as preconditions from chapter 21; the trained-but-not-adopted gap, the 95-percent-trained and 35-percent-adopted numbers, the paper record, the terminal placed where the paper was, Sam Otieno, Thelma, and Nora Kariuki’s dashboard from chapter 11; the vendor’s implementation lead, the life-cycle conversation, and the refusal of the false binary from chapter 13; the training capacity conflict, the floor leads, and the clinic one visit from chapter 25; and the KijaniPay settlement-exception spike, the 640-item queue peak, the four-day signature wait, and the design-not-people finding from chapter 26’s subject matter. The teaching numbers are introduced here and fully reproducible: 12 stations, a 30-minute recovery time objective, 4 within the objective, 5 between 30 and 60 minutes, 3 beyond 60, 4 plus 5 plus 3 equals 12, the slowest at 97 minutes with 40 minutes of searching, 55 minutes of combined kit search across the four slowest stations, the telemetry display at 9 seconds at all 12 stations, 8 of 12 following the first two steps, and the second rehearsal at 26 minutes for the slowest station, all stated with their assumptions as teaching judgments rather than measurements.
• The evidence cited in this chapter is described in my own words and, where the source is a specific published work, attributed: the de Wit, Greer, and Jehn meta-analysis of intragroup conflict, “The paradox of intragroup conflict: A meta-analysis,” Journal of Applied Psychology, volume 97, 2012, pooled more than a hundred studies and found relationship conflict negatively associated with team performance and satisfaction, process conflict negatively associated with performance, and task conflict’s association small and mixed, turning positive under conditions of safety and moderate interdependence, and I have stated its findings qualitatively rather than reproducing its statistics; the CPP Global Human Capital Report of 2008, an industry survey of employees across nine countries, reported an average of about 2.8 hours per week in conflict-related activity and an extrapolation to roughly 359 billion dollars of paid time per year in the United States, and I have labeled it an old, survey-based estimate whose direction, not whose precision, is the point; the actor-observer asymmetry is from Jones and Nisbett’s chapter in the 1972 volume “Attribution: Perceiving the Causes of Behavior”; the fundamental attribution error is from Ross’s 1977 review in “Advances in Experimental Social Psychology,” volume 10; the face and face-work concepts are from Goffman’s 1955 essay “On Face-Work,” in Psychiatry; the psychological safety definition and the two-axis learning-zone framing are from Edmondson’s 1999 Administrative Science Quarterly article “Psychological Safety and Learning Behavior in Work Teams” and her 2018 book “The Fearless Organization”; the positions-and-interests and separate-the-people-from-the-problem concepts are from Fisher and Ury’s 1981 book “Getting to Yes,” the three-conversations framing of difficult conversations is from Stone, Patton, and Heen’s 1999 book “Difficult Conversations,” the feedback triggers are from Heen and Stone’s 2014 book “Thanks for the Feedback,” the radical candor framing is from Kim Scott’s 2017 book “Radical Candor,” the influence principles and the reciprocity research are discussed through Cialdini’s “Influence” (first published 1984) and Grant’s 2013 book “Give and Take,” the organizational power argument is from Pfeffer’s “Managing with Power” (1992) and “Power” (2010), the conflict-response modes are the two-axis assertiveness-and-cooperativeness map popularized by the Thomas-Kilmann conflict instrument of 1974, whose proprietary materials I have not reproduced, and the ladder of inference is the communication concept associated with Chris Argyris used in chapter 12. None of these sources is cited as a guarantee of success; each is cited for the concept described in my own words, and readers should consult the current editions of the sources for their own use.