The public terrain.

POLL: Be honest. When your last big negotiation went sideways, where did it actually die? ○ At the table, with the supplier ○ In your own building, before the meeting ○ In a clause nobody read ○ It didn’t go sideways (respect) I’ve been asking rooms this for 25 years. Almost nobody votes for option one. And yet option one is what nearly all negotiation training is about. That gap is the entire reason I’m publishing my doctrine this month. Vote, then tell me the story in the comments. The option-two stories are always the best ones.

You weren’t hired to negotiate contracts. You were hired to decide what your company is committed to, for years, in writing, at a price. Those are not the same job. One of them is administration. The other is stewardship of every dollar the enterprise has promised to somebody else. Look at what actually passes through your hands: which suppliers survive, which capabilities exist in three years, what happens to the plant when the next shortage lands, and how much regret gets baked into a contract that outlives everyone who signed it. Now look at how the role gets described internally. “Can you push them down another two percent.” The gap between those two descriptions is where an entire profession lost its confidence. I’m spending the next 30 days closing it. Procurement doesn’t happen to you. It happens through you.

CASE FILE 001: Why did a supplier we’d worked with for nine years suddenly turn aggressive? Same company. Same product. Same account manager. Nothing about the deal had changed. And in the space of one quarter, a partner became a shark: hard deadlines, escalations over our heads, a 12% increase presented as non-negotiable. The buying team’s theory: they’d finally shown their true colors. The actual answer: their parent group had been acquired four months earlier, and the account manager had been handed a margin target he had no chance of hitting through volume. He wasn’t attacking us. He was drowning, and we happened to be the nearest solid object. You could not have found that in a pricing model. You find it by asking who is standing behind the person in front of you, and what they are asking of him. Once the team knew, the deal took a different shape: a longer term, a mix shift toward the products that actually carried margin, and a number that let him go home with something. Nobody “won.” Something better happened. The pressure got solved instead of absorbed. People don’t negotiate positions. They negotiate pressures. Every difficult counterpart you have ever met was protecting something. The only question is whether you found out what, or just took it personally.

Nobody bypasses procurement because they enjoy paperwork violations. They bypass you because, in the moment they made the decision, going around you was the rational choice. That sentence is unpleasant. It’s also the only useful place to start. Put yourself inside the head of the VP who signed “just this once”: He had a deadline that was real to him. He believed involving procurement meant six weeks, four templates, and a conversation about a two percent discount he did not care about. He assumed you would slow him down and not protect him from anything he was actually afraid of. He wasn’t evil. He was doing a cost-benefit analysis. And your function lost it. Here is the uncomfortable part: mandates don’t change that math. Policy doesn’t change that math. Escalation doesn’t change that math. They just raise the cost of getting caught, which produces better-hidden bypasses, not fewer of them. What changes the math is being genuinely useful to the thing he is protecting. Speed, if he’s protecting a launch date. Air cover, if he’s protecting his own neck. Continuity, if he’s protecting a plant that can’t stop. Procurement gets bypassed when it is seen as a tollbooth. It gets routed through when it is seen as an advantage. You cannot legislate your way into that. You can only be worth the detour. Which of your stakeholders is currently doing that math about you?

CASE FILE 002: How did a 4% saving turn into an eight-figure problem? The negotiation was, by every internal measure, a triumph. A hard-fought 4% reduction on a large components contract. Announced at the quarterly review. The buyer was named in the CEO’s note. Eighteen months later the same company was air-freighting parts across a continent to keep a line running. Here is the chain nobody drew at the time. The 4% came out of a supplier who was already thin. To fund it, they cut a shift. With one less shift, their tolerances drifted. With drifting tolerances, our reject rate crept up. With a creeping reject rate, our buffer stock got thin. And when a bad month arrived, there was no buffer left, and the only thing standing between us and a stopped line was an aircraft. Nobody in that chain did anything irrational. Each person optimized the number in front of them. The saving was real. It just moved. Out of the price column, where it was visible and celebrated, and into expedites, scrap and firefighting, where it was invisible and nobody’s fault. That is Commercial Myopia, and it is not stupidity. It is a structure that pays people for this quarter’s visible number and charges next year’s invisible one to nobody in particular. The question that prevents it takes four seconds: if this supplier says yes to our number, what do they have to cut to afford it? If nobody at your table can answer that, you are not negotiating. You are transferring risk onto your own future.

Procurement should be the most respected function in the company. It controls more of the P&L than sales influences. It decides which suppliers exist. It is the last line of defense before a bad commitment becomes a five-year liability with a signature on it. So why isn’t it? I’ll say the unpopular half out loud, as someone who loves this profession enough to be honest with it. Partly it’s org design: the function gets measured on one number, so it gets treated like one number. But partly it’s us. We describe ourselves as the last to know. We say “they’ll just go around us anyway” in the tone people use for weather. We accept the savings-report definition of our value and then feel wounded when the business accepts it too. A function that describes itself as powerless will be believed. The way out isn’t a rebrand or a seat at a table nobody is offering. It’s evidence. Prevented disasters, documented. Suppliers kept healthy on purpose. Deals that didn’t blow up in year three, and a paper trail showing exactly who made sure of it. Respect follows demonstrated judgement. It has never once followed a job title. Start the file. One paragraph per deal: what future problem did we just prevent, and what would it have cost? In a year you will not need to argue about respect. You will just hand them the file.

CASE FILE 003: Why did the stakeholder say yes on Tuesday and no on Thursday? Nothing about the proposal changed. The numbers were the same. He had been enthusiastic, on the record, in front of witnesses. Two days later he was cool, evasive, and suddenly full of concerns about implementation risk. The team assumed he was being political. He was. That is not an insult, it’s a diagnosis, and it comes with a treatment. What happened on Wednesday: his own boss had presented a competing initiative to the exec committee, and our project now sat awkwardly across it. Saying yes on Thursday meant publicly backing the wrong horse in a race his career was already entered in. The proposal was never the problem. The proposal had become evidence in a different argument. Here is what most procurement teams do next: re-send the business case. Add a slide. Sharpen the ROI. You are polishing a document that nobody is reading, in an argument nobody told you about. What actually worked: a fifteen-minute conversation that started with “what does this need to look like for it to help you on Wednesday, not hurt you?” The answer reshaped the sequencing, not the substance, and let both initiatives land as complements. He said yes again the following week, and this time it held, because it was no longer costing him anything to say it. When a yes reverses without a reason, the reason exists. It is just in a room you weren’t in. Map that room before you rewrite the deck.

POLL: Of your ten largest contracts, how many renewed last year without a real negotiation? ○ None, we work every one ○ One to three ○ Four to six ○ Most of them, if I’m honest There’s no wrong answer here, and I promise the distribution will not be flattering, including for teams I’ve trained. Every auto-renewed contract is a negotiation that never happened. And “the negotiation that never happened” is the quietest place in the enterprise for money to disappear, because nobody has to explain a decision they never consciously made. Vote, then tell me: what stops the renewal from being worked? Time, or the fear of poking something that currently works?

Why is everything urgent? Not rhetorically. Mechanically. Because the answer explains most of your week. Urgency is almost never created at the moment you feel it. It is created weeks earlier, by someone who deferred a decision, and it travels downhill until it reaches the last function that cannot say no. That function is you. Watch the physics of it. Engineering delays a spec because the requirements aren’t settled. Sales promises a date to close a quarter. Finance holds the budget until the forecast firms. Each of those is an individually reasonable act of self-protection, and each one takes time out of the process without taking any out of the deadline. By the time the request reaches procurement, all the slack has been spent by other people, and what’s left is an emergency with your name on it. Then, magnificently, the organization concludes that procurement is slow. Here is the part that matters. An urgent request is not a workload problem. It is a diagnostic. It tells you precisely where in your enterprise decisions go to be avoided, and it is the most accurate map of organizational dysfunction you will ever be handed for free. So stop absorbing them silently. Start logging them: what was urgent, when the underlying decision was actually made, and how many weeks vanished in between. Six months of that log is not a complaint. It is evidence, and it is the single most powerful document a Head of Procurement can carry into a conversation about resourcing. The most expensive word in procurement is “urgent.” It is also the most informative.

CASE FILE 004: Why do Finance and Procurement fight, when they want the same thing? They don’t want the same thing. That’s the whole answer, and almost nobody says it out loud. Finance is accountable for a number in a period. Procurement is accountable for a commitment across years. Those two mandates are not aligned, they are structurally in tension, and the tension is designed into the org chart. So when Finance hands you a savings target that everyone quietly knows will damage a supplier you cannot afford to lose, they are not being reckless. They are protecting the thing they are measured on, exactly as you are protecting the thing you are measured on. I watched a team spend four months fighting that target, escalating, building decks, losing. Then someone tried a different move. They went to the CFO’s team before the target was set, not after, and asked one question: “What number do you need to defend, and to whom?” The answer was oddly specific. It wasn’t a percentage. It was a cash-timing problem in a single quarter. That is tradeable. Payment terms, phasing, a deferred step-up, none of which require squeezing a supplier who was already at the edge. Finance got the quarter it needed to defend. The supplier stayed healthy. The deal nobody would have had to apologize for in eighteen months. Cost: one twenty-minute conversation, held before the fight instead of during it. Most internal wars are not disagreements. They are two people defending different scoreboards, at maximum volume, in a language neither has bothered to translate. Ask what they’re protecting. Then ask who they have to protect it in front of.

Companies spend millions teaching people how to negotiate. Almost nobody teaches them how to SEE a negotiation. That difference is expensive, and I want to be precise about what it costs. Negotiation training gives you tactics: anchoring, concession patterns, BATNA, silence. All real. All useful. And all of it operates inside a frame that somebody else already built, usually before you were invited. Seeing is different. Seeing is knowing that the supplier’s aggression started when their parent group was acquired. That your stakeholder’s objection is about a rival initiative, not your deal. That the “non-negotiable” increase is protecting a margin a middleman is eating. That the urgent request in your inbox is a decision somebody avoided in April. None of that is on the certificate. Here is what I’ve watched for 25 years: when the tactics are equal, and at senior levels they usually are, the deal goes to whoever saw more of the board. Which is why the best procurement teams I work with are not obsessed with tactics. They are obsessed with diagnosis. They are strangely calm in rooms where everyone else is escalating, because they can see what the other people are reacting to. If your team is constantly firefighting, being bypassed, and inheriting supplier problems it didn’t create, I’d gently suggest the following: You don’t have a negotiation problem. You have a visibility problem. And you cannot train your way out of a visibility problem with more tactics. You need a system for seeing. What’s the biggest negotiation your team walks into in the next 90 days? And can anyone on it tell you, today, what every person on the other side is protecting?

POLL: Have you ever been overruled on a deal you turned out to be right about? ○ Yes, and I said nothing ○ Yes, and I put my concerns in writing ○ Yes, and I was later blamed for the outcome ○ No Option three is the one I want to talk about, because it is the most common answer I get in private and the rarest one I hear in public. The blame rotation is real: the team that flagged the risk is often the team that wears it when the risk arrives, because by then everyone has forgotten who flagged it. Memory in large organizations is not neutral. It reorganizes itself around whoever is available to hold the bag. Which is why written positions matter. Not as ammunition. As a record that a calmer version of you saw this coming. Vote honestly. And if you picked three, you are in significant company.

The calmest person in the room is running the room. They just aren’t announcing it. I’ve watched this for 25 years, in rooms with a lot of money on the table, and I have never once seen the loudest person control the outcome. Here is what calm actually is, because it gets mistaken for temperament, and it isn’t temperament. It’s inventory. Calm is knowing your walk-away because you wrote it down last week, when nobody was watching and your judgement was clean. Calm is having already named the tactics they might run, so when one arrives, you feel recognition instead of adrenaline. Calm is understanding what every person at that table is protecting, so nothing anyone does is a surprise, and surprise is the parent of every bad concession ever made. Calm is not caring less. It is having done the work early enough that you don’t have to think fast under pressure, which is fortunate, because nobody thinks well under pressure. Not you, not me, not the person across the table who is currently performing certainty. Anxiety in a negotiation is almost always information. It is telling you about a piece of preparation you skipped. Which means composure is not a personality trait you were or weren’t born with. It is a Tuesday afternoon and a blank sheet of paper. Be the calmest person in the room. Then use it, quietly, to do the most good.

Four hours after posting the Pre-Brief, one question keeps coming back: “What’s the catch?” There isn’t one. No gate, no email wall, no call booked under false pretenses. It’s nine questions on one page, and it’s free because a doctrine about stewardship that hoarded its own instruments would be a contradiction in terms. But I’ll tell you the real reason, since we’re being honest. The people this actually helps will use it, and it will catch something, and some of them will come back and tell me what it caught. That’s the whole business model. It doesn’t require a gate. It requires the thing to work. It’s in the comments of this morning’s post. Give it 45 honest minutes before your next big negotiation. Then come back and tell me what it caught. That’s the only payment.

You don’t need more leverage to negotiate better deals. I know. Let me make the case, because I think leverage has become the profession’s favorite excuse. “Sure, I’d negotiate like that too, if I had their buying power.” No. Some of the best outcomes I have ever witnessed came from teams with no leverage at all. What they had instead was sight, and the willingness to change the shape of the problem instead of pushing harder on it. Three from my files. Instead of hiring consultants to repair a broken supplier relationship, we had the Head of Procurement quietly attend the meeting and stand behind her stakeholder. The supplier’s behavior changed within minutes. A negotiation that had been stalled for weeks moved that afternoon, because the actual problem was never commercial. It was an ego that needed witnessing. Instead of accepting a finance target everyone knew would damage a critical supplier, we changed the internal conversation before we changed the external one. Cost: a twenty-minute pre-brief. Result: a deal nobody had to apologize for a year later. Instead of trying to win another price argument with a monopoly supplier, we mapped what every single person involved was actually protecting. Cost: a whiteboard. Result: millions protected, and a supplier who wanted to keep working with us. None of that required buying power. It required seeing the game differently. So give me the monopolistic supplier. Give me the impossible stakeholder. Give me the unrealistic finance target. We are going to find the bigger pie anyway, because leverage is what you use when you cannot see another way through, and there is almost always another way through. “You can never solve a problem on the level on which it was created.” That was Einstein, and he was not talking about procurement, but he might as well have been. What’s the move that changes the game, instead of fighting harder inside it?

CASE FILE 005: Why did the supplier relationship collapse three months after we won the negotiation? That word, “won,” is doing a great deal of work in that sentence. The deal was a triumph on paper. Every concession went one direction. The supplier signed at a number their own team had called impossible eight weeks earlier, and the buying team went for a celebratory dinner. Then, quietly, service degraded. The good account manager was moved to another client. Our orders started arriving at the back of the queue. Small requests that used to take a phone call now took a change order. Nothing you could point to. Nothing that breached the contract. They didn’t retaliate. That’s the part people get wrong. They simply reallocated their best people, their flexibility and their goodwill to the customers who hadn’t taken those things from them. Because here is what a negotiation actually is: it is the first meeting of a relationship, conducted in a language both sides remember for years. A supplier who is beaten will comply with the contract. A supplier who is stewarded will call you when a shortage is coming, three weeks before it hits your competitors. That call is worth more than every concession in the file. And it cannot be bought, contracted, or won. It can only be earned, in the room, on the day you had the power and chose to use it well. The next time you are about to extract the last four percent from someone who cannot afford it, ask what you are buying with it, and what you are quietly selling. Every negotiation has a price. Not all of them are on the invoice.

Why does procurement accept being the scapegoat? I’ve been turning this over for years, because the pattern is too consistent to be an accident. A contract goes wrong. The team that raised the risk in month two is the team that answers for it in month twenty. And here is the strange part: they mostly take it. Quietly. Professionally. Without a fight. I think there are three reasons, and only one of them is the organization’s fault. First, the evidence is unwritten. The concern was raised in a meeting, in a corridor, in a “just so you’re aware.” When the reckoning comes, there is nothing to point at, and a memory is no match for a signature. Second, the function is trained to be helpful. Procurement people are, as a population, unusually conscientious. Conscientious people absorb blame in order to keep things moving, and every time they do it, they teach the building that the blame fits. Third, and this is the hard one: being the scapegoat is oddly safe. It is a known role. It comes with the comfort of low expectations and the moral high ground of the misunderstood. Fighting it means claiming authority, and claiming authority means being genuinely accountable for outcomes, and that is a colder place to stand. I say this with real affection for this profession: some of us have made peace with being wronged because it is easier than being responsible. The way out is not indignation. It is documentation, and then judgement, and then a track record nobody can rewrite after the fact. Write the concern down. Send it. Keep it. Not to win an argument in two years, but so that the version of you who saw it coming still exists when everyone else has rearranged their memories. Prevented regret only counts if someone can prove who prevented it.

CASE FILE 006: How does a company outsource its way into a crisis, one entirely reasonable decision at a time? This one is on the public record, so let’s use it. Boeing’s 787 program. The strategy, simplified: push more of the design and build out to a global supplier network, and let those partners carry the development cost. On paper it was elegant. Lower capital exposure, faster scale, a leaner core. What followed is well documented: years of delay, an aircraft that had to be substantially reworked, and a company that ended up buying suppliers and bringing work back in-house to regain control it had traded away. I’m not interested in blame. I’m interested in the mechanism, because the mechanism is in your building too. Every individual sourcing decision was defensible. Each one moved a cost off the balance sheet. What nobody was accountable for was the aggregate: the slow transfer of capability, judgement and integration knowledge out of the enterprise, in exchange for numbers that looked excellent quarter by quarter. Nobody makes that trade on purpose. It gets made in pieces, by people who are each optimizing what they can see. That is Commercial Myopia at industrial scale, and it is why I keep insisting procurement is not a cost function. Procurement is the only function positioned to see the aggregate. What capability are we quietly giving away? Who will own the knowledge in five years? What can we no longer do ourselves? If nobody in your enterprise is asking those questions, it isn’t because the answer is comfortable. It is because the question has no owner. It should have one. It should be you.

Your title does not determine your influence. Your judgement does. I want to be careful here, because that sentence can be said in a way that is simply false, and cruel to people stuck under bad management. So let me say the precise version. A title gets you into the room. It does not determine what happens once you are in it. I have watched a category manager three levels down quietly redirect a negotiation that a room full of VPs had been circling for weeks, and she did it without raising her voice or invoking a single ounce of authority. She did it because she was the only person present who knew what everybody in that room was protecting. She had written it down the night before, on two sheets of paper, while everyone senior to her was preparing to argue. Authority is granted. It can be withheld, revoked, or handed to someone less capable for reasons that have nothing to do with you. Judgement is accumulated. Nobody can take it, and after enough deals, nobody can ignore it either, because the pattern becomes too expensive to overrule. This is the quietest promotion mechanism I know. Not visibility. Not politics. Not being liked. Just being, deal after deal, the person in the room who turns out to have been right, and who has the paperwork to show they were right in advance rather than in hindsight. That reputation takes about two years to build and roughly forever to lose. Start this quarter. Pick the hardest deal on your desk and out-prepare everyone senior to you on it. Not to win. To be useful. Influence is what accumulates when people notice you are worth listening to.

CASE FILE 007: Why did a deal that everyone agreed on die in Legal? Both parties had shaken hands. Commercial terms settled, relationship warm, everyone pleased. Then it went to contract, and four months later it was dead, and the two business teams were barely speaking. The autopsy is instructive, because nobody involved did anything wrong. Legal on our side had been burned two years earlier on an indemnity clause, and had since adopted a position on liability caps that was, in their world, non-negotiable. Legal on their side had a mirror-image scar and a mirror-image position. Two departments, each protecting their organization from a wound the other had never heard of, negotiating a clause neither business team understood or cared about. Nobody escalated it, because from the inside it looked like a technicality. Technicalities do not get escalated. They get ground on, for months, until the commercial energy that made the deal possible has fully dissipated and someone quietly moves on. That is the systems game, the fourth of the four games, and it is where more deals die than anyone counts. Not commercial. Not human. Not even political. Just process, precedent and institutional scar tissue, doing what it was designed to do. The move that would have saved it costs one hour: bring both legal teams into the room while the commercial energy is still high, and ask each of them, out loud, what they are protecting and why. Scars, spoken aloud, become tradeable. Scars that stay buried in redlines become the reason a good deal quietly dies. If a deal is stuck in a clause, the clause is almost never the argument. Find out who got hurt, and when.

POLL: In your organization, when a supplier deal goes badly, who ends up wearing it? ○ Procurement ○ The business stakeholder who chose the supplier ○ Nobody, we move on ○ The supplier I ask because the answer tells you almost everything about how your function is actually valued, regardless of what the org chart says. If the answer is procurement, and procurement did not make the decision, then you are carrying accountability without authority. That is not a personality problem or a communication problem. It is a structural one, and it will not be fixed by working harder. If the answer is “nobody, we move on,” then your organization has no learning loop, which means it will buy the same regret again in about three years. Vote. And if the third option is yours, I’d genuinely like to hear how that goes.

People constantly mistake pressure for leverage. They are close to opposites. Leverage is a structural fact. You have alternatives, or you don’t. You can walk, or you can’t. It exists whether or not anyone in the room is behaving loudly. Pressure is a performance. It is what people apply when they are worried their leverage will not hold up under examination. Watch what happens when you learn to tell them apart. The counterpart who raises their voice is not demonstrating strength. They are telling you the argument is not working on its own. The counterpart with genuine leverage rarely needs to raise anything, because the facts are doing the work, and they know it. The vendor who imposes an arbitrary deadline is not exercising power. They are trying to prevent you from using time, which is the resource that would reveal how weak the deadline is. The executive who escalates over your head is not asserting authority. They are avoiding a conversation they expect to lose on the merits. Aggression is a tell. It is what pressure looks like when it is pretending to be leverage. This is why the calm negotiator has such an unfair advantage. They are not reacting to the volume. They are reading it as data, and the data usually says: this person is more worried than I am. So the next time somebody gets loud in a negotiation, before you brace, ask yourself the quiet question. What are they afraid I’ll notice if they let this go quiet?

There is a cost that appears in no savings calculation I have ever been shown, and it is usually the largest one. Start with what the savings number contains. A price, before. A price, after. A volume assumption. A percentage that goes on a slide and, in a good year, into somebody’s bonus. Now here is what it does not contain. The expedite freight when the cheaper supplier misses a window. The engineering hours spent requalifying a part that was fine before you switched. The quality escape that reaches a customer eighteen months later. The premium you pay in the next shortage because the supplier you squeezed now allocates their scarce capacity to somebody who treated them better. The negotiation you will not be able to win in three years because you spent all your credibility winning this one. None of that is fraud. Every one of those costs lands in a different budget, in a different quarter, under a different name, owned by a different person who has no idea it started in your negotiation. The savings number is not a lie. It is just a photograph of one moment, presented as if it were a film. So here is the discipline I’d ask of any team I work with. Before you report a saving, answer one question in writing: Where did this cost go? If the honest answer is “it left the enterprise,” that is a real saving, and you should be proud of it and paid for it. If the honest answer is “somewhere else in the building, and probably later,” you have not saved anything. You have moved it somewhere it will be harder to see, and charged the future for the privilege. Cost never disappears. It only changes location.

CASE FILE 008: Why did the supplier everyone squeezed become the supplier nobody could replace? It starts as good news. A supplier accepts terms that make your team look excellent. Then accepts them again the following year, because by now they need the volume. Their margin thins. Their investment stops. Their best engineers leave for a competitor who pays them. Two years on, they are the only one left who makes the part, because everybody else exited a category that stopped being worth serving. And now they are weak, indispensable, and quietly furious. That is the worst position a procurement function can engineer for itself, and the terrible irony is that it was engineered by winning. Every individual negotiation was a success. The aggregate was a trap. Toyota is the standard counter-example, and it is worth understanding precisely why. The famous thing about their supplier model is not that they are generous. It is that they treat supplier capability as part of their own production system, something to be invested in and protected, because a supplier who cannot invest is a supplier who cannot improve, and a supplier who cannot improve becomes a ceiling on you. That is not sentiment. It is self-interest with a longer time horizon. So the question to ask before your next aggressive win is not “can they accept this?” It is: “if they accept this, what will they no longer be able to do for me, and when will I need it?” Sometimes stewardship means spending more. Paying to keep a capable supplier healthy is not weakness, and it is certainly not charity. It is the cheapest insurance policy in the enterprise, and it is the one nobody gets credit for buying.

Procurement deserves better heroes. Right now the profession’s folk stories are all about extraction. The buyer who broke a supplier. The record-breaking savings number. The hard case who made someone cry in a negotiation and got promoted for it. We tell those stories because they are legible. They have a number and a villain and a winner. Nobody has to explain them. But look at who I actually want to celebrate. The category manager who spotted an auto-renewal on page 40 and saved her company thirty-four months of silence. The buyer who refused a savings target because he knew what it would do to the supplier keeping his plant running, and who took the political damage for it. The VP who walked into a monopoly negotiation with no leverage whatsoever and came out with a price below half of what was demanded, without a raised voice in the room. The person who wrote the risk down, in writing, and was ignored, and was right, and stayed anyway. Those stories have no number on the front and no villain in the middle, which is exactly why they never get told. A disaster that did not happen leaves no evidence, and this profession has built its entire mythology on the evidence it can photograph. I’d like to change what we tell each other about what excellence looks like here, because the stories a profession tells determine the people it attracts and the behavior it rewards. So: tell me about the best procurement person you have ever worked with. Not the toughest. The best. What did they do that nobody else in the building noticed? I will read every single one of these.

A month ago I taught you to interrogate every deadline you are handed. Today I have one, so interrogate mine. “What specifically changes, internally, after the date?” My honest answer: a print run starts, pre-work goes out, and a roster locks at 24. That’s all. No price rise, no reopening, nothing dramatic. If that answer had been vague, you would have been right to ignore it. That standard applies to me too, and it should. Hold every deadline to it. Including mine. Especially mine.

In October 1962, two governments had every incentive to escalate, and one of them found a way not to. I teach the Cuban Missile Crisis in workshops, and procurement people always look faintly insulted for the first ninety seconds, until they recognize their own week in it. Here is what happened, in the terms of our doctrine. Two contradictory messages arrived from Moscow: one conciliatory, one hard. The obvious move was to answer the hard one, because the hard one was the threat. Instead, Kennedy’s team answered the conciliatory one and behaved as though the aggressive message had never been sent. That is a Knight’s Move. They did not fight harder inside the frame they were handed. They chose which frame to stand in. Second: they worked out what Khrushchev actually needed, which was not victory. It was the ability to go home without humiliation, in front of his own hardliners. So the missiles came out of Cuba publicly, and the American missiles came out of Turkey quietly, months later, unannounced. Both men got what they were protecting. Only one of them had to say so out loud. Third, and the part that stays with me: the pressure in that room to look strong was enormous, and looking strong would have killed everyone. The discipline was to keep asking what the other side needed to survive politically, while the entire building screamed for a response. Every serious negotiation contains a smaller version of this. A counterpart who cannot be seen to concede. A stakeholder who needs a win to take back to their boss. A supplier who will accept your number, but only if it is not called a defeat. Give people a way to say yes that they can survive. Diplomacy is not softness. It is the most rigorous form of seeing there is, and the stakes are only ever a matter of degree.

CASE FILE 009, the last one: I have spent 25 years collecting procurement disasters. They all have the same shape. Not similar. The same. Every one of them, without exception, contains these four things. One: somebody knew. There is always a person, usually mid-level, who raised the concern early and was overruled, ignored, or thanked and forgotten. The information was in the building. It just had nowhere to go. Two: the decision was made under manufactured time pressure. Not real pressure, manufactured. A deadline that, examined afterwards, turned out to have no internal cause at all on either side. Three: nobody had mapped what the other party was protecting, so the deal was built on stated positions rather than actual drivers, and stated positions are where negotiations go to be wrong together. Four: the cost arrived later, in a different budget, under a different name, and by then the causal chain was invisible and the people responsible had been promoted. That is it. That is the anatomy of essentially every procurement horror story I have ever taken a statement about. Which means, and I want to be exact about this, that these disasters are not bad luck. They are a repeatable process, and anything repeatable can be interrupted. Interrupt one: make it safe to raise a concern and impossible to lose it. Write it down. Interrupt two: interrogate every deadline before you inherit it. Interrupt three: map what everyone is protecting before you open your mouth about price. Interrupt four: ask where the cost went, not whether the number got smaller. Four interruptions. That is the entire doctrine, and none of them require budget, authority, or leverage. They require somebody in the room who is willing to see. For thirty days, I have been trying to make that somebody you.

The last thing I want to say this month is about why this job is so hard to be proud of. Prevention is invisible. Structurally, permanently invisible. When you stop a disaster, nothing happens. That is the entire point, and it is also the problem, because “nothing happened” is indistinguishable from “there was never anything to worry about,” and the second interpretation is always available to anyone who wants it. So the person who prevented the crisis and the person who never saw it coming look identical from the outside. One of them will be told they were being difficult about a clause. Meanwhile the person who creates a crisis and then heroically resolves it is standing in a room full of applause. Firefighting is visible. It has drama, a timeline, and a photograph. This asymmetry is not unique to procurement. Ask anyone in safety, in security, in public health, in maintenance. It is the tax paid by every profession whose finest work is an absence. I don’t have a way to make prevention visible to the world. But I have one for you. Keep the file. Every deal, one paragraph: what future problem did we just prevent, and what would it have cost. Write it the week it happens, while the counterfactual is still vivid, because in six months even you will have forgotten how close it came. Do it for the quarterly report, yes. But mostly do it for the harder thing, which is knowing what you are worth on the days when nobody says it. Procurement exists to prevent regret. Most of that work will never be applauded, and it is still the most consequential thing happening in your building. I see it. That is what the last thirty days were for.

Three hours left on Cohort 001, and then the roster locks and I stop mentioning it. No countdown graphic. No last-chance theater. Just the plain facts, one final time: 24 seats. Three days, September 8 to 10. Every mission run on a real deal from your own desk. $1,000. Passports print tomorrow morning. If it’s a yes, the link is in the first comment. If it isn’t, that is genuinely fine, and I mean that. The Pre-Brief stays free forever, the Dispatch goes back to weekly on Sunday, and everything I taught this month is still yours. Thank you for the best thirty days I have had on this platform. Go and prevent something.

Procurement folks, what’s the most creative fake deadline a vendor ever handed you? Mine (from a client file): “Our pricing system updates Friday and we literally cannot stop it.” The system, it turned out, was a spreadsheet. I’ve started asking one question whenever a deadline shows up: “What specifically changes for you, internally, after that date?” Real deadlines have boring, specific answers: quarter close, board dates, capacity windows. Fake ones get vague fast. What’s the best (worst) one you’ve collected? And did it survive a direct question?

POLL: Think about the last negotiation that went sideways on your team. Which layer did it actually die in? ○ Commercial, price, terms, the deal itself ○ Human, ego, fear, trust between the people ○ Political, stakeholders, status, someone’s career ○ Systems, precedent, process, “how it’s always done” I’ve asked rooms of procurement professionals this for 25 years. The votes almost never land on “commercial”, and yet commercial tactics are nearly all the profession gets trained in. Curious what this group’s distribution looks like. Explain your vote in the comments if you’re willing; the stories behind “political” votes are always the best ones.

Honest question for this group: what actually works against the executive bypass? The pattern: your team builds a sourcing position for six weeks. Then a senior stakeholder signs something “just this once” (golf relationship, conference handshake, urgent-ish deadline), and your leverage evaporates retroactively. I’ve seen four responses in the wild: 1. Escalate and fight it (usually loses, always costs) 2. Absorb it quietly (trains everyone that bypassing works) 3. Policy/mandate hardening (works until the next exception) 4. Getting procurement into the stakeholder’s planning BEFORE the deal exists (works, but requires a seat nobody offers you) Number 4 is the only one I’ve watched actually end the pattern, but getting there is its own negotiation, and it’s political, not commercial. What’s worked in your building? Real answers preferred over policy-manual answers.

A question that’s been bothering me (asked as someone who delivers training for a living, so, bias declared): Think about the last negotiation training your team took. Can you name ONE documented outcome from it? A story with a number in it that someone still tells? Not a satisfaction score. Not “people liked it.” An outcome. I ask because the industry default, mine included, years ago, is measuring training by attendance and smiles. But a training that doesn’t change a live deal within 90 days mostly just redecorated people’s vocabulary for a quarter. If your answer is yes: what made it stick? If no: what would training have to look like for a real outcome to survive contact with your actual workload? (Collecting perspectives, will share the pattern if the thread gets going.)

Scenario for the group, real case from my files, anonymized. You’re the VP: Your sole-sourced supplier (no short-term alternative, tooling and quals all with them) informs you they’re closing the production site. They offer to relocate production to another country, if you accept DOUBLE the current price. You have: real switching costs, a plant that can’t stop, and a counterpart who knows both. What’s your first move? Not your eventual strategy, your literal first move, this week. I’ll share what the actual team did (and the outcome, which surprised their own leadership) once there are a few answers in. No tricks. There’s no single right answer, but there IS a move most people skip.

How do you report a disaster that didn’t happen? Serious question. Procurement’s most valuable work is preventive: the clause you caught, the vendor you walked away from, the “urgent” deal you slowed down until it stopped being a trap. None of it shows up anywhere, because a crisis that never occurred has no line item. So the function gets measured on the one thing that IS visible: the savings number. And then we wonder why procurement gets treated as a cost center. Some teams I know have started writing one-paragraph “prevented regret” logs after major deals (what future problem did we stop, what would it have cost), and sending a digest up quarterly. Does your team do anything like this? If you’ve found a way to make prevention visible to finance, I want the mechanics. This might be the profession’s biggest unsolved reporting problem.

[Checked with the moderators before posting.] I released a free one-page negotiation preparation instrument this week, the HIPPO Diplomatic Pre-Brief. No email gate, no upsell page, just the PDF. Sharing here because several members asked for it after the fake-deadline thread. It’s nine questions to answer before any major negotiation. The three that people tell me change their deals most: • What enterprise interest are we actually protecting? (Never “best price”, the real one.) • For every stakeholder, including internal ones: what are they protecting, versus what are they asking for? • What regret is this deal capable of creating, and how specifically do we prevent it? 45 minutes with these before a big negotiation will change what you notice in the room. Link in the comments (or DM me if links aren’t allowed here and I’ll send it directly). If you use it on a live deal, come back and tell the group what it caught, that’s the only payment.

A category manager wrote something after a workshop that I can’t stop thinking about: “Many of us realized we also negotiate with ourselves.” You know the meeting she means. It happens at your desk at 11 PM, before the real one. “They’ll never accept it.” “I don’t want to seem difficult.” “We need this deal more than they do.” And a concession gets made, alone, in advance, for free, before the counterpart says a word. The uncomfortable part: the inner voice uses the exact same tactics we’re trained to spot in vendors. False urgency. Manufactured scarcity (“we have no alternatives”). Status pressure (“who am I to push back on a VP”). Question for the group, and answer as honestly as a public forum allows: what does YOUR inner negotiator concede most often, price, timeline, or scope? And has anyone found a reliable way to catch it before the meeting instead of after?

POLL: Before your last significant negotiation, did you have a WRITTEN walk-away position? Not a number in your head, written down, before the meeting. ○ Yes, always do ○ Had one in my head ○ Honestly, no ○ “Walk-away” isn’t realistic in my category No judgment, the “in my head” option exists because that’s where mine lived for years too. But here’s why I ask: under pressure, the number in your head is negotiable. You’ll renegotiate it with yourself mid-meeting and call it flexibility. The one on paper, written by a calmer you on a quieter day, holds. Every large save I’ve documented in 25 years, including a $3.7M one that took seven rounds, traces back to a position that was written down before round one. Vote, and if you picked option 4, tell me your category. Sole-source and monopoly situations have their own version of a walk-away, and that’s a thread worth having.

Auto-renewal horror stories. Let’s hear them. I’ll start, from a client file: a three-year SaaS agreement with an auto-renewal on page 40, and a 180-day notice window. Miss the window (everyone missed the window) and year three silently becomes year four at list price. It was caught 48 hours before signature. The regret it prevented wouldn’t have surfaced for 34 months. The auto-renewal is Commercial Myopia’s favorite instrument: it converts “a negotiation that should happen” into “paperwork that already happened.” Every auto-renewed premium is a meeting nobody held. Two questions for the group: 1. What’s the worst renewal clause you’ve caught (or missed)? 2. Does anyone run a systematic renewal-teardown, actually re-negotiating the top N renewals each cycle instead of rubber-stamping? What did it surface?

A three-word experiment for your next stuck negotiation: swap “what do they want?” for “what are they protecting?” The first question gets you a position, a number, a demand, a no. The second gets you a driver, a margin target someone’s boss set, a factory that needs predictable mix, a career that can’t absorb another failed project. Positions are granite. Drivers are tradeable. Case from my files: a “non-negotiable” 20% increase turned out to be protecting a supplier’s margin against a middleman nobody had mentioned. The buyer restructured to direct business, supplier got more volume, buyer saved ~€200K/year. The 20% demand was never the real thing. Try the swap this week on the counterpart who frustrates you most (vendor or internal, it works disturbingly well on internal stakeholders). Then report back: what were they actually protecting? I have a theory that 80% of the answers land in one of three buckets, and I’m curious whether this group proves it.

Five sentences. Which have you said out loud this year? 1. “We’re always the last to know.” 2. “We spend all day firefighting.” 3. “They’ll just go around us anyway.” 4. “They only care about the savings number.” 5. “We clean up messes we didn’t make.” I’ve heard these from some of the most technically brilliant procurement people I’ve worked with in 25 years, said casually, like weather reports. Here’s what I’ve come to believe, and push back if you disagree: these aren’t observations. They’re a learned identity, installed by years of bad org design and reinforced every time we repeat them. And identities, unlike weather, can be replaced. The profession that describes itself as powerless negotiates like it. The one that describes itself as the enterprise’s stewards (the people who prevent regret, not just cut costs) negotiates like THAT. So: what’s your count, one to five? And the harder question, which sentence would your CFO say describes your function?

Genuine question, and I suspect the answers will be uncomfortable: does your savings methodology capture what the saving costs elsewhere? The number usually contains a before price, an after price, and a volume assumption. What it rarely contains: expedite freight when the cheaper supplier misses a window, requalification engineering, the quality escape that surfaces 18 months later, the allocation you lose in the next shortage because you squeezed a supplier who now prioritizes someone kinder, and the credibility you spent winning this one that you will not have for the next one. I’m not accusing anyone of cooking numbers. Every one of those costs lands in a different budget, in a different quarter, under a different name. The system is not lying. It is just short-sighted by design. Two questions for the group: 1. Has anyone here successfully changed how their organization defines a saving? What did it take? 2. Has anyone got a Total-Cost model that finance actually accepted rather than politely ignored? If you have made this work, I would like to learn from you, and so would about 200 other people reading this thread.

Why do Finance and Procurement fight, when we supposedly want the same thing? Here is my theory, and I would like it stress-tested by people who live it. We do not want the same thing. Finance is accountable for a number inside a period. Procurement is accountable for a commitment that spans years. Those mandates are structurally in tension, and the tension is designed into the org chart, not caused by anyone’s personality. So when Finance sets a savings target that everyone privately knows will damage a supplier you cannot afford to lose, they are not being reckless. They are protecting what they are measured on. Exactly as you are. The most effective move I have watched, and I only saw it work once it was tried early: go to Finance BEFORE the target is set, and ask what number they need to defend and to whom. In one case the honest answer was not a percentage at all, it was a cash-timing problem in a single quarter. Payment terms and phasing solved it without a single supplier getting squeezed. Questions: 1. Has anyone here got a genuinely functional relationship with their CFO’s team? What made it work? 2. And for the pessimists: is the tension actually resolvable, or is the best we can hope for a well-managed truce?

An experiment I’d like this group to run with me. For the next two weeks, every time an urgent request lands on your desk, write down two dates: when it became urgent to you, and when the underlying decision was actually taken by someone else. My prediction, based on doing this with client teams for years: the gap will average somewhere between three and eight weeks. And in almost every case, the slack was consumed upstream by people making individually reasonable choices, engineering waiting on a spec, sales protecting a close date, finance holding a budget. By the time it reaches procurement, all the time has been spent by other people, and what arrives is an emergency with your name on it. Then the organization concludes that procurement is slow. The point of the experiment is not to complain. It is that the log becomes evidence, and evidence is the only thing that has ever changed a resourcing conversation. Anyone tried something like this? And what did your leadership do when you showed them?

POLL: When a supplier deal goes badly in your organization, who actually wears it? ○ Procurement ○ The stakeholder who chose the supplier ○ Nobody, we quietly move on ○ The supplier The answer tells you more about how your function is valued than any org chart will. If it is procurement, and procurement did not make the decision, you are carrying accountability without authority. That is structural. It will not be fixed by working harder or communicating better. If it is “nobody, we move on,” your organization has no learning loop, and will buy the same regret again in about three years, from a different supplier, with a different logo on the deck. Vote, and then the harder question: has anyone here successfully changed the answer at their company? I am collecting the mechanics.

A case worth arguing about, and it is entirely on the public record: Boeing’s 787 supplier strategy. The logic was elegant. Push more design and build out to a global partner network, let them carry development cost, keep the core lean. Every individual sourcing decision was defensible on its own terms. What followed is well documented: years of delay, extensive rework, and a company that ended up acquiring suppliers and pulling work back in-house to recover control it had traded away. The question I want to put to this group, and I am not interested in dunking on anyone: Was that a procurement failure, an engineering failure, or a governance failure? Because I would argue it was none of the three. It was an accountability vacuum. Every decision had an owner. The AGGREGATE had no owner at all, which means the slow transfer of capability out of the enterprise was nobody’s job to notice. Which raises the question I actually care about: in your organization, who owns the aggregate? Who is accountable for what the company will no longer be able to do in five years? If your honest answer is “nobody,” you are not unusual. But I would argue that job belongs to procurement, and that claiming it is the most direct route this function has to real influence. Push back on me. I would rather be corrected than agreed with.

Has anyone here ever squeezed a supplier so successfully that you created a monopoly? I have watched it happen more than once and it always starts as good news. Year one: they accept terms that make your team look excellent. Year two: they accept again, because by now they need the volume. Their margin thins, investment stops, good engineers leave. Meanwhile competitors quietly exit a category that has stopped being worth serving. Year three: they are the only one left who makes the part. Weak, indispensable, and not especially fond of you. Every individual negotiation was a win. The aggregate was a trap, and it was built by winning. Two questions: 1. Has anyone actually had to unwind this? What did recovery cost, and did it work? 2. Does anyone’s organization formally track supplier financial health as a risk metric, and did that tracking ever stop a deal that finance wanted? I ask the second one because I have heard a lot of talk about supplier health and seen very little of it with teeth.

A claim I’d like this group to try to disprove: most supplier disputes are decided before the first meeting. Not caused. Decided. My reasoning. By the time you sit down, the following are usually already fixed: whether your stakeholders agree on what you actually want, whether anyone has mapped what the other side is protecting, whether a walk-away exists in writing, and whether the timeline was set by you or inherited from someone else’s planning failure. Every one of those is settled in advance. The meeting is mostly where the consequences get collected. If that is true, it has an awkward implication: the hours we spend rehearsing what to say in the room are being spent on the least decisive part of the process. So, argue with me: 1. What is the highest-leverage hour of preparation you do, specifically? Not “research the supplier”, the actual thing you do with that hour. 2. Has anyone here ever walked into a negotiation genuinely under-prepared and won anyway? What saved you? I am serious, the exceptions are where the interesting learning is.

Something I think we get backwards constantly: aggression is not a sign of strength in a negotiation. It is usually a sign of the opposite. Leverage is structural. You have alternatives or you don’t. It exists whether or not anybody in the room is behaving loudly. Pressure is a performance. It is what people apply when they are worried their leverage will not survive examination. Which means the counterpart who raises their voice is telling you the argument is not working on its own merits. The one with real leverage rarely needs to raise anything, because the facts are doing the work and everyone can see it. I’ve found this reframe changes how the whole room feels. Loud stops being threatening and starts being informative. Two things I want from this group: 1. Counter-examples. Has anyone met a counterpart with genuine, overwhelming leverage who was ALSO loud and aggressive? I want to know if my theory breaks. 2. The best example you’ve seen of someone staying completely calm against an aggressive counterpart. What did they actually do, minute to minute? Point two is the one I’d most like to steal for my workshops, and I’ll credit whoever gives me the best answer.

The person who prevents a disaster and the person who never noticed the risk look identical from the outside. That is the tax this profession pays, and I have never seen it properly discussed. When you stop a crisis, nothing happens. And “nothing happened” is indistinguishable from “there was never anything to worry about”, which is an interpretation always available to whoever found you inconvenient at the time. Meanwhile the colleague who created a crisis and then heroically resolved it is standing in a room full of applause. Firefighting is visible. It has a timeline and a photograph. This is not unique to us, safety, security and maintenance all live with it. But procurement seems to have accepted it more quietly than most. So: how do you make prevention visible in your organization? Some teams write a one-paragraph prevented-regret note after every major deal, what future problem did we stop, what would it have cost, and send a digest up quarterly. It is the only mechanism I have seen work. If you have found something better, I would genuinely like to know, and so would everyone reading this. This might be the biggest unsolved measurement problem in the profession.

Most procurement teams think they are negotiating with suppliers. I’d argue the supplier is often the easy part. The real negotiation happens with engineering, who has already chosen the vendor. With finance, who set the target before anyone asked what was possible. With the stakeholder who promised a date. With legal, protecting a scar from a deal you never saw. With leadership, who will judge the outcome by a metric nobody agreed to in advance. By the time you meet the supplier, you are carrying an internal position that was assembled by five people who were never in a room together. And then we wonder why the negotiation feels impossible. Question for the group, and I want the tactical answer, not the theory: what specifically do you do to align your own building BEFORE the external negotiation starts? Who do you talk to, in what order, and what do you ask them? I have my own method and I will happily share it in the thread, but I would rather hear yours first, because I suspect several of you are doing something smarter than I am.

I have spent 25 years collecting procurement disasters, and I have come to believe they all have the same four ingredients. I want to know if this group can break the pattern. One: somebody knew. There is always a person, usually mid-level, who raised the concern early and was overruled or thanked and forgotten. Two: the decision was made under time pressure that, examined afterwards, had no real internal cause on either side. Three: nobody had mapped what the other party was actually protecting, so the deal was built on stated positions. Four: the cost arrived later, in a different budget, under a different name, by which point the causal chain was invisible. That is every horror story I have ever taken a statement about. Not similar. The same. So, two questions: 1. Can you give me a genuine counter-example, a disaster that had none of these four? I would like to be wrong, because if I am right, then these things are not bad luck, they are a repeatable process. 2. If you recognize all four: which one is easiest to interrupt in your organization, realistically, starting Monday? Anything repeatable can be interrupted. That is the only optimistic thing about this list.

Where did you learn what you were allowed to ask for? Strange question. Stay with me, because I think it explains more about negotiation outcomes than any tactic does. Long before the meeting, you have already decided what is reasonable to request. That ceiling was set somewhere: by a boss who once told you not to be difficult, by a culture where pushing back read as ingratitude, by a first job where the senior buyer got what he wanted by being loud and you decided you never wanted to be that person. And so you open at a number that is safe. Not because the deal required it. Because you did. I have watched extremely capable people concede, alone, at their desk, at 11 PM, before the counterpart has said a word. The negotiation was over before it started, and the other side never even knew they had won something. The tactics we teach sit on top of this. They cannot fix it. So the honest question for the group: what does your inner negotiator concede most easily, price, scope, or timeline? And where do you think you learned it? Answer as honestly as a public forum allows. I’ll go first in the comments, and mine is not flattering.