What Entrepreneurs Can Learn from Fierce Conversations
Priya co-founded a twelve-person analytics startup with a friend from business school. For months she noticed her co-founder spending engineering time on a feature almost no customer had asked for, but she kept it light in their weekly syncs, dropping hints like "worth checking the roadmap against sales calls" and hoping he would connect the dots himself. He didn't. Investors started asking pointed questions about slipping deadlines, and Priya answered with reassuring generalities instead of naming the real problem out loud. By the time she finally sat him down and said plainly that the feature was burning their runway with no customer behind it, three months and most of their cash reserve were gone. Her co-founder was furious not at the feedback itself but at how long she had waited to give it to him straight.
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
Naming the real issue
Founders often diagnose a slipping metric — churn, a missed deadline, a cofounder conflict — as the problem itself, before they've named its actual cause, because naming the cause plainly can feel like assigning blame inside a small, fragile team.
A founder tells the team to "move faster" when the real issue is that two people are quietly building incompatible versions of the same feature.
Before your next team or investor update, write one sentence naming the specific decision or behavior actually causing the problem, not the surface metric, and say that exact sentence out loud in the room.
Saying it plainly and specifically
Founders learn early to pitch with polish, and that same instinct toward persuasive framing creeps into internal feedback, turning a direct concern into a diplomatic paragraph nobody can act on.
A founder tells a struggling salesperson their "energy has felt a little different lately" instead of naming the missed targets and the specific accounts at risk.
Draft feedback as one plain sentence with a name, a behavior, and a number or date attached, then check whether a stranger reading only that sentence would know exactly what to do next.
Staying in the conversation when it gets uncomfortable
When a hard conversation with a cofounder or early employee turns tense, a founder juggling a dozen priorities feels a strong pull to end the meeting early and "let things cool off," which usually just postpones the real decision.
A tense equity conversation gets adjourned at the first sign of anger and is never fully reopened, so quiet resentment ends up shaping decisions for the next year.
When you feel the urge to end a tense conversation early, name that urge out loud — "I want to wrap this up because it's gotten uncomfortable" — and ask for five more minutes instead.
Making it a habit, not a crisis measure
Building direct conversation into a regular rhythm matters more for founders than almost anyone, because a startup's problems compound weekly, not annually. A short, honest check-in with a cofounder or key hire every week, even five minutes long, catches a diverging roadmap or a quiet resentment while it is still cheap to fix. Waiting for the quarterly all-hands or the next fundraising crunch to have the real conversation means addressing it only after it has already cost you runway, trust, or a cofounder.
A founder who has learned to name problems plainly can be tempted to do it in front of the whole team for efficiency, but staying present through discomfort works best one-on-one first, where the other person can react honestly instead of performing composure for an audience. Raise the plain version privately, then bring the resolved, calmer version to the wider group once it no longer needs an audience to manage.
Name one thing, honestly
What problem in your company have you been describing in softer language than you actually believe, and who is the one person who has never heard the direct version?
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 you feel the urge to end a tense conversation early, name that urge out loud — "I want to wrap this up because it's gotten uncomfortable" — and ask for five more minutes instead.