What Leaders and Managers Can Learn from Venture Deals
Dana ran a mid-sized product team and had just been handed a reorg memo from the VP above her: new headcount, new reporting lines, a deadline to accept by Friday. She almost forwarded it to her team as final, the way she always treated directives from above. Instead she reread it the way she imagined a founder reading a term sheet, asking which lines were truly non-negotiable and which were just the first draft of someone else's convenience. She went back with two specific counters, framed around what the reorg was actually protecting: continuity on a key project, clear accountability. Both were granted, because she had asked precisely instead of complying silently. Her team kept the manager they trusted, and Dana learned that memos from above are opening positions, not verdicts.
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
The Directive Is a Draft, Not a Verdict
Most instructions from leadership carry more flexibility than their tone suggests, because they were often written quickly under someone else's pressure. Treating a budget cut, a deadline, or a new policy as open for clarification, rather than scripture, mirrors the founder's discovery that a term sheet starts talks rather than ending them.
Managers once told to just execute pass that same silence downward, training their own teams never to question anything either.
When a directive will cost your team real capacity, ask one specific question about what it protects before relaying it as final.
Reading What Each Side Is Actually Protecting
Every stakeholder is defending something often invisible in the memo itself: a VP protecting their numbers, a report protecting bandwidth, a peer protecting headcount. Reading past the stated ask to the underlying concern is the same skill the book teaches about liquidation preferences and control terms, aimed at org charts instead of cap tables.
Leaders argue against the literal words of a request and miss the fear actually driving it, guaranteeing a rematch later.
Before a tense conversation, write one sentence naming what the other person is protecting, not what they are asking for.
Choosing Which Battles Are Worth Your Capital
Not every disagreement deserves your full authority. Some issues are structural, shaping decision rights or how success gets measured, while others are cosmetic and resolve themselves. Leaders who spend equal energy on both end up with less credibility for fights that matter.
New managers fight visibly over small process details while quietly accepting a decision-rights change that haunts their authority for a year.
Before escalating, ask whether it changes who decides, who gets credit, or who bears risk; if none apply, let it go.
The Working Relationship Outlasts the Win
A negotiation won at the expense of trust is rarely worth winning in an organization you plan to stay in. The people you negotiate with today, a boss, a peer, a direct report, are the same people you will depend on for your next project and your next hard conversation. Leaders who treat internal negotiation as a step in an ongoing relationship generally end up with more durable influence than those who treat each round as a discrete contest to win outright.
Picking your battles carefully and protecting relationships can conflict when the battle that matters most is also the one your counterpart cares most about. The way through is transparency about stakes: naming clearly why a decision-rights issue matters to you turns a fight into a negotiation both people can respect afterward.
Name one thing, honestly
What directive did you accept at face value this year that you now suspect was negotiable?
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
Before escalating, ask whether it changes who decides, who gets credit, or who bears risk; if none apply, let it go.