The Ethics of Persuasion — Where Selling Crosses Into Manipulation

Build a personal ethical framework for when persuasion is service and when it is harm. Apply the framework to specific product decisions in your own work, to your own sales conversations, and to evaluating what others (employers, vendors, politicians, family) are trying to get you to do. This module is contract design for human-system interactions. You are declaring the API guarantees you offer to anyone you persuade — what they can rely on, what you will never do, what happens when the contract is breached and how the system recovers. The ethics statement is your LICENSE file plus your CODE_OF_CONDUCT.md, applied to every conversation in which you are trying to move someone to action. Most engineers think of "ethics" as either a feature flag (on for the things they care about, off for the things they don't) or a compile-time check (you set the policy once and never look at it again). The right model is runtime invariants: assertions that fire on every interaction, that can be reviewed and updated, and that cause the system to fail visibly rather than silently when violated. There is a second engineer's frame worth carrying. Cialdini's principles, deployed badly, are SQL injection on humans — they exploit predictable parsing of social signals to inject behavior the human did not consent to. Your ethics framework is the input sanitization layer for your own outputs. You are committing to never send a payload that you would consider an injection attack if you received it. The Frankfurt essay is the spec for the difference between "lies" (intentional injection) and "bullshit" (laziness about whether the payload is safe). Write the framework as if the next person you interact with — a customer, a hire, a partner — has every right to assume your output is sanitized.