A Partner Makes a Big Decision Without Consulting You: Decision Tree

Why this matters

You find out after the fact: your partner hired someone, signed a vendor, cut a price, committed the shop to something big, and never picked up the phone. The sting is real, and the temptation is to react hot, in front of the crew or the customer. Do not. How you handle the next hour decides whether this becomes a fixed process or a permanent crack in the partnership. The move is to contain first, judge second, and fix the system third, in that order.

First move: do not detonate in public

Before anything else, protect the business in front of the people watching.

  • Do not overrule your partner in front of staff or a customer. A public fight between owners tells everyone the ship has no captain, and it is very hard to walk back.
  • Do not touch anything irreversible in anger. No canceling the hire, unwinding the contract, or firing back with your own unilateral move to even the score.
  • Get the conversation private, and get it soon. "Let's talk, just us, today." Cool enough to think, fast enough that it does not fester.

Then ask: was it inside their authority

This is the fork the whole thing turns on. Go back to what the two of you actually agreed, in writing or by clear practice, about who can decide what. See related: Partnership Roles and Decision Rights From Day One.

  • If the decision was inside their agreed authority, then this is not a betrayal, it is your authority map working as designed, and your discomfort is the signal. Maybe the boundary is drawn in the wrong place. That is a conversation about redrawing the line, not about their conduct. Own that distinction honestly.
  • If the decision was outside their authority, in a tier that required both of you, then a real boundary was crossed, and you move to the next question.

If a boundary was crossed: read the intent

Not every overstep is the same. Sort it before you respond.

  • An honest overstep: they believed it was theirs to call, or it was time-sensitive and they could not reach you, and they told you promptly. This is a process gap, not a character problem. Tighten the definition of what is joint, agree on how to reach each other under time pressure, and move on.
  • A pattern: this is the third time, and the boundary keeps sliding in their favor. Now it is not about one decision, it is about whether the agreement means anything. Name the pattern directly, not just the latest instance.
  • Bad faith: they hid it, worked around you on purpose, or committed the shop knowing you would have said no. This is the serious one, and it goes to the dispute mechanism in your agreement, with advisors or a mediator involved. See related: The Partnership Is Failing and You Need to Dissolve It Decision Tree.

Contain the damage on the decision itself

Separately from the relationship, deal with the thing they committed to:

  • If it is reversible and wrong, unwind it together, calmly, and let your partner make the call to whoever was on the other end, so the shop still speaks with one voice.
  • If it is done and binding, accept it, extract the lesson, and put your energy into the process fix so it does not recur. Fighting a signed commitment usually costs more than the commitment did.

The recap

Contain in public, talk in private, then ask the one question that sorts everything: was it inside their authority or not. Inside means fix your boundary map. Outside means read the intent, an honest overstep gets a process fix, a pattern gets named as a pattern, bad faith goes to your dispute process. Handle the relationship and the committed decision as two separate problems. The goal is not to win the argument, it is to make sure the next big decision runs through both of you.

References

  • U.S. Small Business Administration (SBA), guidance on partnership governance and decision-making
  • American Bar Association, general guidance on partnership and operating agreements
  • See related: Partnership Roles and Decision Rights From Day One; The Partnership Is Failing and You Need to Dissolve It Decision Tree