Skip to main content
Steady at the Top
← All articles

What to do when a business partner breaks an important promise

When a business partner breaks an important promise, establish the commitment and its consequences before deciding how much further reliance is justified. Seek a concrete repair, with an owner and evidence of completion. Use qualified advice for rights, remedies, or changes to existing obligations.

Trust is confidence in the dependability of someone or something. The APA Dictionary of Psychology’s 2018 entry describes interpersonal trust in terms of relying on another party to do what they say they will do.

That distinction makes future conduct central to the decision. An explanation or apology can matter, but it is different from evidence that the missed commitment has been repaired. You can listen to the account while evaluating the next dependency separately.

Establish which promise failed

Start with the actual commitment: who undertook to do what, by when, under which conditions? Find the relevant agreement and communications. Identify which parts both sides accept and which remain disputed.

A missed deadline may be a clear failure. It may also depend on an input that another party did not supply. Establishing the facts does not erase harm; it helps identify what must change.

Avoid beginning with a total verdict on the partner’s character. “The approved materials did not arrive before the agreed launch” can lead to investigation and repair. “You are impossible to trust” can obscure the specific obligation.

The stakeholder-expectations map helps identify everyone who relied on the commitment. The operational impact may extend beyond the two executives discussing it.

The missed commitment carried into the evening

In a composite private scene, a founder checks a partner’s message after a family outing. A promised customer introduction has not happened, and the partner offers another general assurance. The founder drafts an immediate reply agreeing to expand the relationship anyway.

The desire to restore an easy working relationship is understandable. The expansion is still a new decision. Before approving it, the founder needs to know what happened to the first commitment and whether the next one depends on the same unresolved condition.

Write down the missed introduction, its business consequence, and the specific evidence required before expanding reliance. That can move the question from repeated evening messages into an authorized commercial review.

The private disruption illustrates an unresolved dependency. It does not prove deliberate deception or establish a legal remedy.

Apply a partner repair-and-reliance checkpoint

A partner repair-and-reliance checkpoint is a proposed method for separating the past breach, the repair, and the next commercial commitment. It does not promise that trust will return or that the partnership should continue.

If the matter involves material loss, disputed obligations, regulated activity, fraud concerns, or another legal issue, obtain qualified advice. Preserve relevant records. Do not independently withhold payments or stop contracted performance because confidence has fallen.

1. Verify the obligation and the observed failure

Collect the relevant agreement, messages, timeline, and work record. State what was promised and what occurred. Note any conditions that affect whether the obligation was due.

Ask the partner to confirm or correct the account. If they dispute it, record the difference accurately and identify the proper resolution route. Do not describe a contested conclusion as a mutually accepted fact.

Separate a business expectation from a legal determination. Counsel should assess enforceability and remedies. Operational leaders still need to understand the event so they can manage affected work.

2. Identify the consequence and current exposure

Describe the actual effect on customers, schedules, resources, and dependent commitments. Label estimates and possible effects separately from confirmed consequences.

List what still relies on the partner doing the same kind of work. A missed introduction might affect one prospect. A missed technical dependency might affect several active implementations.

Ask the appropriate owners what can be protected or resequenced within existing authority. Do not create a second breach by taking an unreviewed defensive action. Protection must fit the company’s obligations and the advice it receives.

3. Request an account and an observable repair

Ask what prevented performance, which responsibility the partner accepts, and what they can now do. The explanation should inform the repair rather than replace it.

A useful repair names the action, owner, deadline, dependencies, and evidence of completion. If the original opportunity has passed, acknowledge that completing the old task may not restore the lost outcome.

Do not demand a promise the partner cannot support. A smaller feasible remedy may be more informative than a sweeping assurance. Have authorized people assess whether it is acceptable, including any legal or commercial consequences.

4. Decide the terms of further reliance

Evaluate the next proposed commitment separately. Consider the importance of the dependency, available alternatives, evidence from the repair, and the cost of another failure.

You may have authority to defer a new optional commitment while existing duties continue. You may need board, legal, or contractual approval for other changes. Establish that distinction before acting.

If the decision requires board approval, use a clear board decision request. State the exposure, options, and recommendation. Do not ask the board to endorse a general feeling that the partner is now good or bad.

5. Review performance before broadening the arrangement

Inspect whether the repair happened under the agreed conditions. Confirm the result with the people who use it, rather than relying only on the partner’s announcement.

If the action is incomplete, identify the unresolved dependency and the authorized next step. Repeatedly moving a deadline without revisiting exposure can preserve uncertainty indefinitely.

If the action succeeds, decide what that evidence supports. One completed task may justify a limited next commitment without establishing reliability for a larger or different obligation.

A conversation that keeps repair and expansion apart

Imagine a hypothetical partner who promised an introduction before a buying window closed. The window has passed. The partner now asks the company to fund a joint event.

You could say:

“We agreed on the introduction before the customer’s review, and it did not happen. We need to understand that failure and the remaining options. The event funding is a separate decision. Before recommending it, I need an agreed repair account and a plan for the dependencies it creates.”

This wording requires a factual basis and appropriate authority. It does not threaten a remedy or declare that the event must be rejected.

The partner may explain that the customer contact left unexpectedly. That information matters. The next question is why the company was not informed and what communication process could prevent another dependent commitment from being made on outdated assumptions.

A plausible explanation can reduce uncertainty about the event while leaving a communication failure unresolved. Keep both findings in the record.

Compare each side’s account of responsibility

Ross and Sicoly’s 1979 experiments found egocentric patterns in recall and responsibility attribution. Their work gives a reason to check your own contribution account as well as the partner’s.

You may remember repeated requests for confirmation. The partner may remember waiting for a document from your team. Compare the sequence and identify whether either missing action affected performance.

The research does not require dividing responsibility equally. A clear failure can remain clear after investigation. The point is to make the account accurate enough to support a remedy and a future decision.

If the evidence remains incomplete, state what is missing. Do not resolve uncertainty by choosing whichever explanation makes the relationship easier to continue.

Allow people to report failure early

Edmondson’s 1999 research describes team psychological safety as a shared belief about interpersonal risk. Applied cautiously here, it raises a practical question about whether either organization can report a failing commitment before the deadline passes.

The cited work does not validate this partner checkpoint. It supports examining the team conditions around candid reporting. An executive promise to be transparent means little if project staff are penalized for disclosing delays.

Agree on how a risk should be reported, to whom, and by when. Make clear that reporting a risk does not erase responsibility for the work. It gives the authorized people a chance to respond.

If the breach affects employees’ trust in your own leadership, use the employee promise-repair guide. Explain your company’s responsibility rather than attributing every consequence to the external partner.

Bring new decision makers into the full history

A new director or partner executive may hear only the latest explanation. Give them an accurate summary of the commitment, failure, impact, repair, and current exposure through the proper confidential channel.

The new-director integration guide addresses the broader need for decision context. In this case, the relevant history prevents a new participant from treating an uncompleted repair as a fresh, uncomplicated request.

Do not use the summary to recruit an ally against the partner. Include their response and any evidence that changed your initial view. Distinguish the record from management’s recommendation.

A shared history also reduces repeated renegotiation of basic facts. The next discussion can focus on the unresolved decision instead of starting again with competing recollections.

Decide whether the repair supports a future relationship

At the checkpoint, ask whether the partner acknowledged the relevant responsibility, delivered the agreed action, and changed the condition that produced the failure. Each answer may have different supporting evidence.

A completed apology conversation does not require immediate restoration of every dependency. A continuing concern also does not authorize indefinite punishment outside the company’s rights. Review the actual commitments and options.

If the relationship continues, state the next bounded reliance and its review point. If it changes or ends, follow the applicable agreement and professional advice. Keep customer and employee communications accurate.

The useful outcome is an explicit decision about what the company will rely on next, supported by the partner’s observed conduct and the company’s actual authority.

Sources

Steady at the Top