What Entrepreneurs Can Learn from How to Have Impossible Conversations
Dana had spent two weeks building the case: their four-person startup needed to drop the shared spreadsheet they used for client deliverables and adopt a proper task-tracking board. She walked into the Monday meeting with slides and a timeline. Her co-founder, Marcus, cut her off after the third slide. "We tried a new system in January and it fell apart in a week," he said. Dana pushed harder, listing teams that had switched successfully elsewhere. Marcus folded his arms and answered in monosyllables the rest of the meeting. By Friday the topic hadn't moved, and Dana still didn't know why Marcus resisted — she had never asked him. She had spent the meeting trying to win, not to understand what he was protecting.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Curiosity Before You Pitch Your Position
In a founding team, every disagreement carries the weight of the company, which tempts people to treat a co-founder's hesitation as an obstacle rather than a position worth understanding. Curiosity before persuasion means postponing the pitch long enough to ask what your co-founder has seen or worried about first.
Two co-founders disagree about replacing their shared spreadsheet with a task-tracking tool, and the one pushing for change assumes the other's resistance is discomfort with new software, launching into a feature comparison instead of asking what made him wary.
Before proposing a process change, ask one open question about the other person's history with similar changes — "What happened last time something like this got tried here?" — and let them finish before presenting your case.
Ask Instead of Asserting the Roadmap
Founders are used to asserting a vision, since that is often what raises money, but the same instinct flattens conversations with the people who could tell you your plan has a hole in it. Asking instead of asserting trades a persuasive claim for a real question that invites someone to explain their reasoning.
When a co-founder goes quiet during a planning meeting, the other fills the silence with more reasons the plan is right, confirming the meeting isn't a real conversation, so the quiet one stops contributing at all.
When a teammate resists a decision you've already settled, ask them to describe what a bad outcome would look like from their seat, then repeat back what you heard before responding.
Naming Your Own Uncertainty as a Founder
Admitting you might be wrong feels dangerous when your name is on the company, but a founder who never voices uncertainty trains the team to hide it too. Naming your own uncertainty first, by flagging the part of your plan you're least sure about, signals that disagreement is safe here.
A founder announces a new task-tracking system as though the decision is settled and risk-free, so when a teammate raises a real concern about the timeline, it lands as a challenge to authority instead of useful information.
When introducing a new process, say out loud which part of it you're least confident about before asking anyone for feedback.
Knowing When to Let a Disagreement Rest
Not every disagreement between co-founders needs to end in agreement during the same meeting. Some decisions can be tabled for a week while both people gather more information, and a founder who can say "let's each think about this and revisit Thursday" without treating it as a loss preserves the partnership the company depends on. Letting a conversation rest matters more for a founding team's health than winning any single debate.
Curiosity and decisiveness pull in different directions when a deadline is close: understanding a co-founder's hesitation takes time you may feel you don't have. The balance is scope, not abandonment — spend ten focused minutes asking real questions before defaulting to your original plan, rather than skipping the questions or letting the conversation run unbounded. Protecting a small amount of curious listening even under pressure keeps the partnership intact for the next decision.
Name one thing, honestly
Which recent disagreement with a co-founder or teammate did you resolve by winning the argument, and what might you have learned had you asked one more question first?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
When introducing a new process, say out loud which part of it you're least confident about before asking anyone for feedback.