What Creators and Innovators Can Learn from Would You Do That to Your Mother?
An app developer is finalizing the cancellation flow for his new productivity tool, and his growth advisor suggests a survey, a discount offer, and a confirmation step before the cancel button appears, all standard tactics to reduce churn. He mocks it up, then imagines his own mother trying to cancel a subscription she no longer uses, clicking through four screens designed to wear her down. Not every creator has a warm relationship with their mother, so he also pictures a person you care about hitting the same wall. He strips the flow to one click and a single honest question about why.
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 new features against a basic decency standard
Before shipping a feature, onboarding flow, or pricing model, a creator can ask whether it would be acceptable applied to someone they deeply respect encountering the product tired and skeptical, not excited. This catches manipulative patterns before they ship, the fine print, the dark pattern button, the pre-checked box, because they tend to fail badly when explained plainly rather than justified using industry-standard growth language.
Creators normalize manipulative patterns because competitors use them too, treating industry standard as a defense.
Before launching a growth tactic, describe it plainly, in one sentence, to someone you respect and watch your own reaction to explaining it.
Separating genuine value from extracted convenience
Some product decisions genuinely serve users, like an onboarding flow that actually teaches the product. Others exist purely to extract revenue or attention while creating the appearance of user benefit, like notifications tuned for anxiety rather than usefulness. Creators need to sort their own feature list honestly, since features that exist mainly to extract value are the ones that will most embarrass them if a respected friend asked directly why the product works that way.
Creators justify extractive design as necessary for a sustainable business model, without testing gentler alternatives first.
List your top five monetization or engagement mechanics and ask which ones you would still ship if your growth targets did not depend on them.
Redesigning the product around respect for the user
Once a manipulative pattern is identified, redesign work means finding a version that still supports a sustainable business without treating users as targets to be worn down. This can mean an honest cancellation flow, transparent pricing, or notifications a user controls. Respecting users this way often produces better retention over time, because trust compounds, while extraction produces short-term metrics that erode as users notice and quietly leave for good.
Creators soften the language of a manipulative flow without removing the underlying mechanic, so the deception continues in gentler wording.
Prototype the redesigned flow with real early users and ask them directly whether it feels respectful compared to the original.
Making the standard part of how you build, not a one-time launch decision
The habit of testing new features against basic decency fades quickly once a product scales and a larger team takes over decisions the founder once made alone. Creators who sustain the standard build it into design reviews, product principles, and onboarding for new hires, so it survives beyond their personal attention. The goal is a durable design value baked into how the whole team ships, not an early promise made in a founder's launch post and later forgotten.
Growth and integrity compete directly whenever a manipulative tactic demonstrably increases a metric leadership cares about. A creator under investor pressure may face real consequences for refusing a tactic that competitors use freely. There is no universal formula for resolving this tension; the creator must judge, case by case, whether the growth gained is worth the trust it quietly spends, and whether that trade still looks reasonable a year later.
Name one thing, honestly
Which feature in your product would you be uncomfortable explaining honestly to someone you respect? Where has a growth metric started to matter more than whether users feel respected by your product?
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 flow with real early users and ask them directly whether it feels respectful compared to the original.