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.
Why this matters
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. 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: decide together how you'll communicate, how often, in which meetings, and how you'll give and receive feedback. Make the assumptions explicit before they collide.
What this means
- Proactively design your most important working relationships.
- Clarify expectations, cadence, communication preferences and decision rights.
- Apply this to cofounders, execs, reports, advisors and key partners.
What good looks like
- Each key relationship has a contract: decision rights (what needs both of you), communication do's and don'ts, feedback cadence, and "what I need from you / what you need from me."
- Hard rules exist where it runs hot — like every salary or personal decision going through the management group together, because one founder's solo yes is everyone else's unfairness.
- The calendar shows the relationship being maintained: strategy time, check-ins and social time, not just operations.
Where founders get it wrong
- The ops-only weekly: a meeting that discusses everything except the strategy and the relationship itself.
- The unilateral yes: one founder grants a raise or a bonus solo, and the resentment lands on the whole org.
- Assuming the agreement is obvious. It never is — unexpressed expectations are pre-booked conflicts.
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.