What Entrepreneurs Can Learn from How to Say It to Seniors
Priya ran the operations side of her growing company when she decided it was time to replace the spreadsheet-based inventory system her father, the company's founder, had built by hand thirty years earlier. She presented the new software in one meeting, expecting gratitude for the time it would save everyone involved. Instead he stopped attending the weekly numbers review entirely. Priya assumed he was simply being stubborn about new technology, so she rolled out the new system without him and quietly archived his old reports. Only months later, over a slow dinner, did he admit the spreadsheet had been the last place in the business where his own judgment still outranked a dashboard. Priya had solved a straightforward logistics problem and, without meaning to, erased the one seat he had left at the table.
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
Resistance as a signal, not a character flaw
When a co-founder, veteran employee, or parent who built the business pushes back on a change you know is sensible, the reflex is to read it as stubbornness or fear of technology. Often it is more specific: a fear of becoming irrelevant to the thing they spent decades building. Treating that resistance as data about what someone is protecting, rather than an obstacle to route around, changes what you do next.
A founder ships the "obviously better" process without the resistant person, then wonders why morale or trust quietly erodes afterward.
Before overriding a resistant veteran's objection, ask them directly what they're worried the change will cost them personally, not just operationally.
Hearing the real objection under the business case
A disagreement about a new hire, tool, or reporting structure is rarely only about the tool. It is often about whether someone still has a meaningful role or is being quietly phased out. Founders who argue only the business case miss the identity case underneath, and no amount of ROI data resolves a fear about relevance.
The founder wins the argument on the numbers and loses the person's trust and institutional knowledge in the same conversation.
Name the unspoken stake out loud, such as "I want to make sure this doesn't push you out of the decisions that matter to you," before making your case.
Building the ask around their need for a real seat
Once you know what someone is protecting, design the change to preserve it, not dismantle it. Give the resistant party a genuine choice among options, a defined area where their judgment still governs, or a visible role in shaping the transition. This isn't about slowing good decisions; it's about making the decision something the other person can own, not merely accept.
Offering a symbolic title with no real authority behind it, which reads as condescension rather than respect.
Identify one specific decision in the new system that the resistant person will still fully own, and say so explicitly before rollout.
Succession and trust are built in rounds, not a single meeting
Whether it is a parent handing off a family business or an employee adjusting to a new structure, these transitions rarely resolve in one well-crafted conversation. Expect the same concern to resurface in different forms over months, and treat each return as normal progress, not proof the earlier conversation failed. Founders who stay with it tend to get further than those looking for one decisive pitch.
Founders often feel the pull between listening patiently and moving at startup speed, especially when investors create real deadlines. When these compete, separate the timelines: give trust-building the longer runway it needs, while carving out one narrower, honestly-communicated decision that must move faster, rather than forcing the whole relationship onto the business's clock.
Name one thing, honestly
Where in your business are you mistaking someone's need to still matter for simple resistance to change?
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
Identify one specific decision in the new system that the resistant person will still fully own, and say so explicitly before rollout.