Influence & Persuasion

Internalize Cialdini's seven principles of influence (reciprocity, liking, social proof, authority, scarcity, commitment & consistency, unity) and Pre-Suasion's meta-principle of channeled attention. Recognize the principles firing in your own decisions, daily. Recognize them deployed on you by sophisticated counterparts. Decide which tools you will use deliberately, which only reciprocally, and which you refuse on principle — Module 5 then asks you to systematize the third category. The seven principles map onto patterns you already evaluate in product engineering — which lets you reason about ethical use the way you reason about good vs bad code. Social proof is the GitHub-stars heuristic: rational Bayesian updating on imperfect information when the stars are real; corrosive when they're fake — and anyone who has run an open-source project already has the instinct for why fake stars poison the well. Authority is the citation pattern: quoting the framework guides in a code review changes how the thread behaves; visible track record does the same in a negotiation. Reciprocity is give-first open source: maintainers who give for years find the community generous when they finally ask. Commitment & consistency is the public roadmap: publishing it makes you likelier to ship it — the ethical version of the lever, pointed at yourself. Scarcity is the limited-release pattern: real manufacturing constraints inform; countdown timers that reset on reload are the dark version, and the test is simply whether the constraint is true. Where the lens lies: these aren't code patterns to deploy; they're patterns of human cognition you are either honoring or violating. The line is the subject of the next module — but the working test fits in a sentence: if the other party could later see exactly which principle you used and would still call the communication honest, you persuaded. If they'd feel manipulated, you crossed.