What Entrepreneurs Can Learn from Would You Do That to Your Mother?
A founder is finalizing the refund policy for her subscription box before launch. Her cofounder wants a strict no-refund clause after seven days, arguing it protects cash flow. She imagines her own mother opening a damaged box, told the window had closed by two days, and quietly deciding never to order again rather than make a fuss. If a mother figure is not the easiest relationship to picture warmly, imagine any person you care about instead. She rewrites the clause to allow judgment calls, and the team argues about whether that will get exploited.
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
Testing policies against a simple human standard
Before locking in terms of service, pricing tiers, or support scripts, run each one through a plain question: would this be fine if it happened to someone you love. This is faster than a legal review and catches a different problem, one that is technically defensible but still feels lousy to receive. Founders often discover the test fails not because a policy is malicious but because it was written to solve an internal problem, like a small number of abusers, by inconveniencing everyone else.
Founders assume that because they would never abuse a policy, no one else would notice or mind it either.
Before publishing any customer-facing policy, read it aloud as if explaining it to a specific person you care about, and note where you would feel embarrassed.
Separating true protections from convenient defaults
Many startup policies exist because they were fastest to build, not because they serve customers. A cancellation flow buried three menus deep protects revenue short term; a support macro that always blames the user protects the team from admitting fault. Entrepreneurs need to sort their rulebook honestly, distinguishing rules that genuinely protect the business and its customers from rules that only protect the founder's time or the quarter's numbers.
Under funding pressure, every convenience gets relabeled a necessary protection, and the distinction quietly disappears.
Once a quarter, list every customer-facing rule and mark each one business-protection or customer-protection, and challenge yourself to justify each protection out loud.
Rebuilding around dignity once problems surface
Once a policy is identified as convenient rather than caring, the harder work is redesigning it without breaking the business. This usually means keeping the legitimate protection while removing the part that burdens the customer. A cancellation flow can stay simple to build while still being honest and quick. This is design work, not sentiment, and it often produces a better outcome because customers notice and repeat.
Founders redesign the customer-facing language without changing the process, so new wording papers over the same friction.
Prototype the redesigned policy with five real customers before shipping it company-wide, and ask them directly whether it feels respectful.
Making the test a habit, not a launch checklist
The human test is easy to apply once, during a big policy rewrite, and easy to forget once the business is running. Entrepreneurs who keep it alive build it into recurring rituals: a standing agenda item in weekly reviews, a question in the onboarding doc, a prompt whenever a policy is proposed. The goal is a reflex, not a one-time audit, so that as the company scales past the founder's direct oversight, the standard survives in habits rather than memory.
The tension shows up between speed and dignity. An entrepreneur under deadline pressure will often choose the faster, less humane version, reasoning it can be fixed later once there is more revenue. Later rarely comes on its own; convenience calcifies into default quickly. Founders have to decide, deliberately, which corners are acceptable to cut now and which would be unacceptable if a person they loved hit them on day one.
Name one thing, honestly
Which of your current customer-facing policies would you be uncomfortable explaining to someone you love? Where in your business has speed quietly become an excuse for avoiding a harder, kinder redesign?
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
Prototype the redesigned policy with five real customers before shipping it company-wide, and ask them directly whether it feels respectful.