The vendor who won’t move on price. The distributor who keeps missing delivery windows and blaming supply chain. The linen service that keeps shorting the order and offers credits instead of fixing the system. Every operator has at least one vendor relationship that is stuck in a recurring positions conflict — the same argument, the same outcome, the same frustration.
The position the vendor is defending is rarely the price or the delivery window. It is the account’s perceived value to their business, the precedent a concession would set across their portfolio, or the internal approval chain that makes flexibility operationally difficult. The operator who argues only at the price level is arguing at the wrong level.
The interest the operator is protecting is rarely the money. It is the reliability that protects the Guest experience, the predictability that makes the Profit line plannable, and the trust that the vendor relationship is supposed to provide. The operator who only argues the price has not communicated what the relationship actually requires.
The Profit discipline of [Positions vs. Interests]: before any vendor negotiation, name your interest and ask for theirs. Not as a tactic — as a genuine attempt to find the overlap. The vendor whose interest is account retention will find flexibility that the vendor who thinks the operator is negotiating price cannot find. The operator whose interest is reliability will accept terms that the operator who thinks they are negotiating cost will not accept.
The negotiation that moves from positions to interests is not softer than the positional negotiation. It is more accurate — and accurate negotiations produce better outcomes than hard ones, because both parties are solving the right problem instead of winning the wrong argument.
[Embedded Repair] | IL Every shift produces errors. Every building produces a repair dynamic whether the operator designed one or not. The default repair dynamic is either blame (errors get punished, which makes them hide until they compound) or ignore (errors go unacknowledged until they become a Guest problem). The designed version is the repair reflex — the cast that catches errors early, surfaces them without fear, resets collectively, and treats recovery as a normal part of performance rather than an exception to it. Not resilience as a personality trait — resilience as a structural discipline built into how the cast operates together. Pairs with [Leadership Recovery] (Performance) — [Leadership Recovery] is the operator’s individual repair discipline; [Embedded Repair] is the team’s collective one. Pairs with [Peer Accountability] — the repair reflex runs laterally before it runs top-down; the cast that holds each other to the standard catches errors before they require management intervention. Pairs with [Social Friction] — high-friction environments suppress the repair reflex; errors hide because surfacing them feels risky. Low-friction environments accelerate repair because errors surface before they compound. Pairs with [Poise] — poise is the individual anchor under pressure; [Embedded Repair] is the collective anchor.
