The Trust Paradox: Why Protecting Against Bad Actors Means Building Better Partnerships

The Imperative of Building Resilient Partnerships

The advice sounds reasonable: prepare for the worst, hope for the best, and protect yourself when separating from business partners. Enjoy The Work's recent article about founder conflicts presents two stories where preparation made the difference between chaos and control. One CEO got ambushed by a co-founder who turned hostile. Another anticipated conflict and built safeguards. The lesson seems clear: armor up.

But this framework, while tactically useful, presents a dangerous oversimplification. It divides the world into good actors and bad actors, suggests that character reveals itself only under stress, and recommends defensive preparation as the primary solution. This perspective misses three critical realities about business partnerships: the role leaders play in creating conflict, the costs of defensive postures, and the more important question of how to select and build relationships that don't require armor.

I spent fifteen years as a COO and advisor to venture-backed companies. I've watched partnerships thrive and implode. The pattern I've observed differs from the one presented in this article. Conflicts rarely involve villains and victims. They involve misalignment, poor communication, and leadership failures that compound over time.

The Binary Trap

The article frames partnership conflicts through a binary lens: good actors versus bad actors. One co-founder behaves with integrity, the other becomes destructive. One founder wants an honorable separation, the other wages a disinformation campaign.

This framing feels satisfying because it's simple. It tells us who to blame. But it obscures the more complex reality of how business relationships deteriorate.

Consider the first story the article presents. Two co-founders split 50-50, then diverge in their vision. One focuses on product, the other on customers and investors. The externally-facing founder begins "selling a vision that drifted from reality" and conducts "private conversations and emails" with investors and board members. They're "no longer in lockstep."

The article presents this as the bad actor revealing himself. But I see a different story: two founders who failed to maintain alignment as their company evolved. The CEO describes the conversation as "honorable, clear, and humane," but from the co-founder's perspective, he may have felt blindsided by a separation he didn't see coming.

Research from Noam Wasserman at Harvard Business School, published in his 2012 book "The Founder's Dilemmas," found that 65% of startups fail due to co-founder conflict. But his research also revealed that these conflicts typically stem from predictable tensions around roles, equity, and decision-making authority, not from one founder suddenly revealing bad character.

The distinction matters. If conflicts arise from hidden character flaws, preparation is the answer. If they arise from structural and communication failures, prevention looks entirely different.

What Defensive Postures Cost

The article advocates for what it calls "armoring up": building workback plans, eliminating single points of failure, preparing communications, and engaging counsel before difficult conversations. These tactics are practical and sometimes necessary.

But defensive preparation carries costs the article doesn't acknowledge.

When leaders approach partnerships with contingency plans for betrayal, they change the nature of the relationship. Trust requires vulnerability. The most productive partnerships involve sharing control, exposing weaknesses, and making yourself dependent on another person's competence and goodwill.

Amy Edmondson's research on psychological safety at Harvard Business School demonstrates that teams perform best when members feel safe taking interpersonal risks. Her 1999 study in Administrative Science Quarterly found that high-performing teams actually reported more errors than low-performing ones, not because they made more mistakes, but because they felt safe admitting them.

The same principle applies to leadership partnerships. The relationships that produce exceptional results involve founders who can say "I don't know" or "I was wrong" or "I need help" without triggering defensive responses. Armoring up makes those conversations harder.

I advised a CEO who approached a co-founder conversation about role changes with the defensive preparation the article recommends. He consulted lawyers first, backed up code, prepared for the worst. His co-founder sensed the defensive posture and responded in kind. What might have been a collaborative conversation about evolving roles became an adversarial negotiation. The preparation didn't prevent conflict; it created it.

This isn't an argument against ever preparing for difficult conversations. It's a recognition that preparation itself sends signals. When you treat someone as a potential threat, they often become one.

The Selection Problem

The article's most significant omission is its failure to address how leaders choose partners in the first place. It asks, "Can I trust this person? Will they behave with decency when things are hard?" But it offers no framework for answering these questions before conflicts emerge.

This matters because selection is the highest-leverage intervention in partnership dynamics. Research by Michael Morris at Columbia Business School, published in the Journal of Business Venturing in 2013, found that founding teams with prior working relationships had significantly lower conflict rates than teams formed through networking or introduction.

The reason isn't mysterious. Working together reveals how people handle stress, disagreement, and failure. You learn whether someone takes responsibility or deflects blame, whether they communicate directly or triangulate through others, whether they prioritize the team's success or their own position.

But most founders skip this step. They choose co-founders based on complementary skills, shared enthusiasm, or social connections. They commit to 50-50 equity splits before they've weathered any storms together. Then they act surprised when conflict emerges under pressure.

The better question isn't "how do I prepare for partnership failure?" It's "how do I select partners who won't require this preparation?" This means:

• Working together before formalizing partnerships. Not just casually, but in situations with real stakes and limited resources. Y Combinator's Michael Seibel recommends founding teams spend at least six months working together before incorporating.
• Testing specific conflict scenarios. Patrick Lencioni's work on team dynamics suggests directly discussing hypothetical conflicts: What happens if we disagree about a major pivot? How do we handle one person wanting to leave? What if we need to fire a mutual friend? Partners who can't have these conversations comfortably before conflict arises won't handle them well during conflict.
• Aligning on values and decision-making frameworks. Brené Brown's research on trust, published in "Dare to Lead," identifies clarity as one of seven trust elements. She found that unclear expectations are one of the most common trust breakers in organizations. Founders need explicit agreements about how they'll make decisions, what they'll prioritize when values conflict, and what behaviors are non-negotiable.
• Structuring equity and control separately. The assumption that co-founders must split ownership 50-50 creates power struggles. Research from Joel Spolsky and others suggests that vesting schedules, decision-making protocols, and clear role delineation matter more than exact equity percentages for partnership stability.

When Preparation Becomes Protection

None of this means preparation is wrong. There's a version of preparation that serves partnership health rather than undermining it.

The difference is transparency. The article advocates preparing for conflict without the partner knowing, treating them as a potential adversary. The alternative is building protective structures collaboratively.

I worked with a founding team that created what they called a "partnership prenup" during their first year. They outlined how they'd handle various scenarios: role changes, performance issues, voluntary departures, terminations. They specified decision-making processes and conflict resolution mechanisms. They agreed on equity vesting terms and buy-sell arrangements.

This wasn't defensive preparation; it was collaborative design of a resilient system. Both founders understood the structures and why they existed. When conflicts emerged, they had a framework for addressing them. The structures didn't prevent disagreement, but they prevented disagreement from becoming destructive.

This approach aligns with research from Carsten De Dreu at the University of Amsterdam, whose 2008 meta-analysis in the Journal of Applied Psychology found that task conflict (disagreement about approach) can improve team performance when relationship conflict (personal antagonism) remains low. Collaborative structures separate the two types of conflict.

The Missing Context

The article presents founder conflicts as interpersonal dramas, but they often reflect deeper structural problems in how we fund and build startups.

The venture capital model creates conditions for founder conflict. It requires rapid growth, which demands role specialization. The CEO who thrived as a generalist in a 10-person company struggles in a 100-person organization. The CTO who built the first version can't architect for scale. These aren't character failures; they're predictable growing pains.

Brad Feld and Jason Mendelson address this in "Venture Deals," noting that founder dilution and role evolution are sources of recurring conflict in VC-backed companies. The typical solution is to replace or reassign founders whose skills no longer match company needs. But this transition is traumatic because we conflate role fitness with personal value.

The article's second story illustrates this problem. A CTO can't ship product, makes excuses, deflects accountability. The CEO decides it's time for a change. This is framed as the CEO making a hard but necessary decision.

But I'm curious about the earlier story. How did this CTO become so disconnected from delivery? What communication breakdowns preceded this crisis? Did the CEO provide clear expectations, regular feedback, and support? Or did he avoid difficult conversations until the situation became terminal?

Kim Scott's "Radical Candor" framework suggests that most leadership failures stem from ruinous empathy, avoiding hard feedback to spare feelings in the short term, then delivering devastating feedback when performance problems become undeniable. This pattern creates the very conflicts the article describes.

A Different Framework

Instead of dividing the world into good actors and bad actors, leaders need a framework that acknowledges complexity and emphasizes prevention.

• Start with better selection. Choose partners you've worked with under stress. Prioritize demonstrated behavior over credentials or enthusiasm. If you can't work together first, at least have explicit conversations about conflict scenarios before committing.
• Build transparency into structures. Create partnership agreements, vesting schedules, and decision-making frameworks collaboratively. Make the protection mechanisms visible and mutual, not secret and one-sided.
• Maintain continuous alignment. Weekly or biweekly founder meetings focused on alignment, not just operations. Use structured frameworks like Patrick Lencioni's "6 Critical Questions" to surface and resolve diverging perspectives before they become entrenched positions.
• Give feedback early and often. Address small misalignments before they compound. If you notice a partner overpromising to investors, say something immediately. If you see concerning patterns in how they handle stress, discuss it directly. Waiting for a crisis to address these issues makes conflict inevitable.
• Separate role fitness from personal worth. Create a culture where role changes or departures don't carry the weight of personal failure. Some of the healthiest founder transitions I've seen involved founders moving to advisory roles or leaving with equity intact and relationships preserved because everyone understood that role fit and contribution are distinct from value as a person.
• Prepare collaboratively, not defensively. If you sense a difficult conversation coming, the first preparation step should be telling your partner: "I want to discuss something challenging, and I want to make sure we both feel prepared to have this conversation productively. Can we set aside time and maybe agree on some ground rules?"

The Real Test of Character

The article suggests that character reveals itself under pressure, and I agree with this claim. But I'd argue that the character being tested isn't just the co-founder who might react badly. It's also the CEO who decides how to approach the conversation.

Leaders who treat partners as potential adversaries often create adversaries. Leaders who approach difficult conversations with transparency, respect, and genuine concern for the other person's wellbeing usually get better outcomes.

This doesn't mean everyone responds well to dignified treatment. Some people do behave destructively when their interests feel threatened. The article's examples may accurately represent situations where one partner acted poorly.

But I'd want to hear the other side of these stories. What did the conversations look like from the co-founders' perspectives? Did they feel respected and heard? Were they involved in finding solutions? Or did they feel ambushed, despite the CEO's intentions?

The article says one CEO thought his approach was "honorable, clear, and humane," but his co-founder responded by locking others out of source code and launching a disinformation campaign. That's certainly destructive behavior. But it's also possible that what felt honorable to the CEO felt like a betrayal to the co-founder. Perhaps the clear, humane conversation happened after months of deteriorating trust and indirect communication.

We can't know without hearing both perspectives. And that's precisely the problem with the good actor/bad actor framework. It allows us to tell ourselves comforting stories where we're reasonable and others are unreasonable, where we handle conflict with grace and others respond with destruction.

What Leaders Should Actually Do

If you're building a company or already navigating a partnership, here's what research and experience suggest:

• Invest heavily in selection. Don't commit to co-founder relationships without testing them under realistic conditions. The time spent working together before formally partnering pays dividends for years.
• Make alignment practices routine. Don't wait for misalignment to force alignment conversations. Create regular forums for discussing vision, values, and strategy. Make these conversations normal, not crisis-driven.
• Address concerns immediately. If you notice behavior that concerns you, from overpromising to missed commitments to concerning patterns in how they treat others, say something right away. Direct feedback delivered early usually generates far less conflict than accumulated grievances delivered all at once.
• Build protective structures collaboratively. Partnership agreements, vesting schedules, and separation protocols should be discussed and designed together. Transparency about protection mechanisms reduces the likelihood you'll need them.
• Get outside help before you need it. Work with a coach, therapist, or advisor who can help you navigate partnership dynamics before they become crises. Couples therapy for business partners isn't just acceptable; it's wise.
• If you do need to have a difficult conversation about roles or separation, prepare by getting clear on your own motivations and desired outcomes. Consult with legal counsel and advisors about structural considerations. But then have a direct conversation with your partner before you take unilateral action. Give them a chance to respond with dignity.

The article's advice about having workback plans and eliminating single points of failure makes sense if you've already determined a separation is necessary and anticipated a hostile response. But the first conversation shouldn't happen after you've already built these defenses. It should happen when you first notice serious misalignment.

Explore further insights on selecting trustworthy partners and maintaining healthy business dynamics here.