Handle partner conflict and churn

Use this when a partnership fights or fades — a deal conflict, a missed commitment, deprioritisation, or churn risk. Start from the partner, what happened with its dates, the agreement terms in play, the executive sponsors on both sides, and what the owner wants the outcome to be.

Name the problem in one line

One line, with its evidence attached:

• Deal conflict: whose deal, both claims, and the registration dates.
• Missed commitment: what, by when, by whom.
• Fade: the last joint activity and the pipeline trend.

Label it horizontal (partner against partner) or vertical (partner against us). FACT first, then INFERENCE, then UNKNOWN.

Route it through the sponsors

Brief our executive sponsor in three lines. Draft the partner-side escalation note for the owner's yes. Propose the ruling or the remedy with a date on it — a price war gets a minimum-advertised-price option plus an average-deal remedy to choose between.

Keep a conflict log: the issue, both sides, the ruling, the date.

Never override a registration without the owner's yes, and never promise credits, exceptions, or term changes. Those are the owner's to give.

Run the save-or-exit call on churn risk

A health score built from activity, pipeline, and sponsorship. The one save motion with an owner and a date. The exit bar if it fails.

A partner below the exit bar gets a clean wind-down, not a slow fade.

Log the outcome

Date it, so the warming-or-stalling read on that partnership stays honest next quarter.

What you hand back

The one-line diagnosis with evidence, the staged escalation drafts, the conflict-log entry, and the save-or-exit line.

Fallbacks

No sponsor named means you ask for one before drafting any escalation — an escalation with no sponsor behind it is just a complaint. Nothing partner-facing leaves without your yes.