Capability 13 · Lead Others
Build Incredible Relationships
Two cofounders replaced their ops-only weekly with a relationship contract, a monthly strategy offsite and a social dinner — the arguments stopped being about the wrong things.
Founders say
“We have a weekly meeting, sure. We talk about ops for an hour. We haven't talked about how we're actually working together in about a year.”
Where you are today
- Every working relationship runs on assumptions — you assume they'll ask for help; they assume they should figure it out alone.
- Salary and personal decisions get made ad hoc, and every one of them triggers someone.
- Cofounder time is 100% operations: no strategy time, no relationship time, no fun.
Where you’re headed
- The important relationships run on explicit agreements: what we decide together, how we communicate, how we exchange feedback.
- A monthly rhythm exists — a deep strategy session away from the office, a check-in, and a social dinner.
- When friction shows up, there's a shared playbook for it, agreed before you needed it.
The majority of conflict comes from implicit assumptions. You're assuming one thing, they're assuming another, and the conflict happens in the gap: I assume you'll tell me when you're stuck; you assume you're meant to figure it out alone. Neither of us said it out loud, so neither of us knows we disagree — until the day it costs something. Unexpressed expectations are pre-booked conflicts. So the single highest-leverage move — for a new manager, for cofounders, honestly for friendships and romantic relationships too — is to proactively define the relationship before you need to: how you'll communicate, how often, in which meetings, and how you'll give and receive feedback.
What goes in the contract
Decision rights first: which things we discuss together, which one person can decide, which are sole responsibilities. Put hard rules where it runs hot. At my own startup the rule was that any salary or personal decision had to go through the management group together — because one cofounder's solo yes to a raise is everyone else's unfairness, and the resentment lands on the whole org. Then the two questions that fill in the rest: "What do you need from me, and what do I need from you?" — written down as be/do lists: always be as clear as possible with objectives, give me the resources you think will be useful, be proactive, be assertive.
The contract also fixes the commonest cofounder failure: the ops-only weekly, an hour of operations every week and not a minute on strategy or on the relationship itself. The cadence I recommend: a monthly deep strategy session away from the office — at least a couple of hours thinking about the future — at least one check-in, and one social dinner a month. If the calendar only shows operations, the relationship is running on fumes and assumptions.
Write it down, then keep it alive
The design conversation produces an artifact: the Relationship One-Pager — purpose, expectations, working norms and repair rules on a single page you both sign off. Then maintenance: the 1:1 is where the agreement gets exercised, a KSS cadence keeps the feedback flowing both ways, and a recurring Happiness Check catches drift before it becomes distance.
Beyond the inner circle, the same discipline scales: score the people the company most depends on — cofounder, reports, board — on the Stakeholder Map, so people-risk gets a location instead of staying a vague feeling.
What you can do right now
- Draft the contract with your cofounder. Decision rights, communication preferences, cadence, tension points, repair rules. An hour now saves a year of friction. Relationship Design Canvas →
- Ask the two questions. "What do you need from me?" and "What do I need from you?" Write the answers as be/do lists: be clear with objectives, give me the resources, be proactive.
- Book the monthly three. One deep strategy session offsite (at least a couple of hours on the future), one check-in, one social dinner. Recurring, starting this month.
- Agree the don'ts. Start with the classic: nothing critical over Slack. Praise in public; anything remotely critical over the phone or in person.
The toolkit
Work with Ben
Want help installing this?
Outstride OS is the system behind Ben's founder coaching — pre-seed to Series C. If this page names something you are living right now, start a conversation.