Renegotiation Notice Protocol¶

Standard renegotiation procedure — instantiates Overcommitment Prevention

Defines how and when affected parties are told — early and in a standard form — that a commitment must be reduced, delayed, or cancelled.

Renegotiation Notice Protocol governs the downside of commitment management: when a promise can no longer be kept as made, it specifies the legitimate way to cut or rescope it, and exactly how, when, and to whom that change is communicated. Its distinguishing property is acting after acceptance — the only mechanism here that operates on the way down — on the premise that trust is destroyed by silent failure far more than by an early, well-formed renegotiation. It decides no intake; it makes reducing a promise a legitimate, orderly move instead of a broken one.

Example¶

A publisher realizes a lead spring title will miss its date — the author needs eight more weeks. Without a protocol, the house stays silent and hopes, then scrambles in April. With one, the cancellation-or-rescope rule fires as soon as the slip is credible: the title is formally rescoped (new on-sale date, revised print run), and the notification rule pushes standardized notice — to retailers, the sales force, and marketing — within a set window, with revised commitment terms attached (new on-sale date, adjusted co-op). Retailers reslot the title calmly, months out, instead of pulling it angrily at the last minute. The promise still changed, but the relationship survived because the change was early, owned, and specified.

How it works¶

The signature is a legitimate reduce path coupled to a disciplined notice. Two rules act together: (1) a cancellation-or-rescope rule that authorizes reducing a commitment when conditions change, so impossible promises are not kept alive until they fail; and (2) a notification rule specifying trigger, timing, audience, and content, so affected parties learn early, in a predictable form, with restated terms. Speed and standardization are the levers — the same bad news lands very differently early and templated versus late and improvised.

Tuning parameters¶

Notice trigger — how certain a slip must be before notice fires. Early triggers preserve trust but risk false alarms and churn.
Lead-time target — how far ahead affected parties must be told. More lead time is kinder but commits you to admitting bad news sooner.
Audience scope — who is notified (only the counterparty, or all downstream dependents). Wider is more honest but can amplify reputational damage.
Rescope-versus-cancel default — whether the rule prefers shrinking a commitment or dropping it. Rescoping preserves partial value; cancelling frees capacity cleanly.
Message standardization — a fixed template versus bespoke notice. Templates are fast and fair; bespoke is warmer but slower and inconsistent.

When it helps, and when it misleads¶

Its strength is protecting credibility — the scarcest capacity of all — by replacing silent failure with early, orderly renegotiation, and giving the system a legitimate way to shed impossible promises before they collapse. Its limit is that it manages the communication and legitimacy of a reduction, not the delivery: a beautifully-noticed cancellation is still a cancellation, and over-use trains stakeholders to distrust every promise. The classic misuse is weaponizing it to normalize chronic under-delivery ("we always renegotiate"), or firing notice so late it is a fait accompli dressed as consultation. The psychological contract — the unwritten expectations behind a promise — survives an early renegotiation far better than a hidden breach, which is the whole reason to notify early.^[1] The discipline is to trigger on honest early signals, not once failure is unavoidable, and to keep renegotiation rare enough that a notice still means something.

How it implements the components¶

Renegotiation Notice Protocol realizes the reduce-and-communicate side of the archetype:

cancellation_or_rescope_rule — the legitimate authority to reduce or drop a commitment when conditions change, so impossible promises are not kept alive until failure.
stakeholder_notification_rule — specifies who is told, when, and in what form when a commitment changes.
commitment_terms — the change is expressed as revised terms (new scope, date, consequences), keeping the renegotiated promise concrete.

It manages commitments on the way down and does not decide intake (Portfolio Intake Gate), set the cap (Commitment Budget), or detect the trouble in the first place (Commitment Burndown Review).

Instantiates: Overcommitment Prevention — it is how the system legitimately reduces a commitment once one no longer fits, without breaking trust.
Consumes: Commitment Burndown Review surfaces the commitments that can no longer be kept and must be renegotiated.
Sibling mechanisms: Portfolio Intake Gate · Commitment Burndown Review · Commitment Budget · Sales Capacity Alignment Review · Backlog Commitment Review · Capacity Dashboard · Calendar Capacity Audit · Budget Encumbrance Control · Intake Capacity Checklist · Work-in-Progress Cap

References¶

[1] The psychological contract is the set of unwritten mutual expectations between parties beyond the formal terms. Organizational-behavior research treats its violation — an unmet expectation, especially one hidden until too late — as more corrosive to trust than a renegotiated one. This protocol is built to renegotiate the explicit terms before the implicit contract is breached. ↩