Two Restaurant Divorces in One Week
This week I learned of two restaurant divorces, and I took the news hard.
One couple's restaurant has been open only a couple of years. The other has been open for just a few months. Both have young children and their other baby (the restaurant they own together).
I'm heartbroken for both of them.
Rarely do we go into relationships, be they marriages, business partnerships, or even roommate situations, thinking about all the things that could go wrong. But humans are complicated, and things change. Or surface. And I think we can do more to equip ourselves for these curveballs.
As a mediator, most of my work happens after the damage is done. But increasingly, I find myself wishing I'd been in the room six months earlier.
The Patterns I See
By the time I'm approached, the restaurant is already open, the team is hired, and the pressure is high. The partners who founded the place (who were going to be BFFs) are trying to run a company together without any shared structure for how decisions get made.
This can play out in many ways:
The chef and operations partner, six months in. The chef wants to add another cook on the line to protect food quality and avoid burnout. The operations partner is watching labor percentages and pushes back. Both believe they’re protecting the business, but they never agreed on how staffing decisions would be made. Now every schedule review becomes a negotiation.
Different communication styles under stress. One founder processes out loud and wants to talk things through constantly. The other prefers to think privately and come back with a decision once they've sorted it out. The first interprets silence as avoidance. The second experiences constant discussion as pressure. Neither knew this about the other until the pressure was on.
Unclear authority playing out on the floor. The GM receives two different instructions. Founder A says, "Don't comp anything unless it's a real problem." Founder B says, "Take care of the guest; just make it right." Now the GM is constantly trying to read the room and guess which founder will care more. Eventually, the management team starts going to whichever founder will give them the answer they want.
These are smart, capable, well-intentioned partners who simply never built the infrastructure to handle disagreement.
The Infrastructure You’re Not Budgeting For
Most restaurants budget obsessively for physical infrastructure but almost nothing for relational infrastructure.
Restaurants spend on:
Buildout
Equipment
Consultants
Branding
PR
But almost nothing on:
Founder alignment
Decision frameworks
Conflict structures
Yes, you need the right people at your opening party. And you certainly need a preventative maintenance plan for the HVAC that's definitely going to stop working on the hottest day of summer.
But you also need clarity around:
Decision rights
Communication styles
How disagreement works
Authority structures
Unresolved resentment
Restaurant partnerships are particularly vulnerable to this gap. You're combining high-stress operational environments, razor-thin profit margins, intensely personal creative investment, and long, late hours. It's a pressure cooker. And most founders walk into it assuming alignment will happen naturally because they trust each other.
But trust isn’t a decision-making framework, nor is friendship an operating structure.
What if Founder Alignment Were a Pre-Opening Cost?
Imagine if you budgeted for relational infrastructure the same way you budget for your buildout.
You could invest in:
Defining roles
Decision authority
Conflict protocols
Communication expectations
Values
Exit scenarios
This is preventative maintenance for the things most likely to blow up your business, and understanding the difference between prevention and repair is important.
Prevention happens when the relationship is still optimistic. People still like each other; they're inclined to give grace, and no one is on the defensive yet. Also, the audience is small.
Repair happens when the stakes are higher. People are exhausted. Patience is thin. Staff are now witnessing the conflict. More money is involved. The business is already at risk.
Prevention is easier and cheaper, and it doesn't require a crisis to justify the conversation.
Separation Isn’t the Problem
I heard a comedian once tell an audience he and his wife were getting a divorce. The crowd gave a loud, sympathetic "awww/boo." To which he responded: "No happy marriage ever ends in divorce!"
It's a funny line. It's also true. Separating isn’t inherently a bad thing. Some partnerships should end, and not every business relationship is meant to last forever. But, you can dissolve a partnership well or dissolve it poorly. The difference is whether you did the work upfront or at least had a framework when things got hard.
Two Tools You Can Use
I've created two worksheets to help founders build this infrastructure: one for before you open, and one for when conflict has already arrived.
Pre-Opening Founder Alignment Worksheet
If you're considering a partnership, download the Pre-Opening Founder Alignment Worksheet and work through it together. Block 90 minutes. Answer the questions individually first, then compare notes.
The goal here isn't perfect agreement, but clarity. You need to know where you align and where you differ before the pressure hits.
Pre-Opening Founder Alignment Worksheet
Founder Separation & Business Stewardship Planning Worksheet
If you're already in partnership and feeling friction, download the Separation & Business Stewardship Planning Worksheet. You don't have to be separating to use it; sometimes just naming the structure helps reset the dynamic.
This can help create structure so the business can function despite personal conflict.
Founder Separation & Business Stewardship Planning Worksheet
And if you need help facilitating these conversations, that's what I do. The most effective way to prevent catastrophic misalignment is consistent dialogue with a third party who can help partners really hear each other.
You wouldn't open a restaurant without fire suppression. Don't open without relational infrastructure.

