You need to sign in or sign up before continuing.
Reflection — An Honest Take 8 min

Honest Take — Before You Begin

Honest Take — Module 4: Influence — The Cialdini Foundations #

The thing I most want to say about this module is that it is deceptively easy, and the temptation will be to finish it quickly and feel like a competent student. Cialdini's prose is friendly. The seven principles fit on an index card. Pre-Suasion is shorter than Influence. You will be tempted to absorb all of it in two weeks and move on. Don't. The module is scheduled at three weeks because the practice of noticing is what takes the time, and the noticing cannot be shortcut. Within forty-eight hours of finishing the reciprocity chapter you will notice three to five reciprocity dynamics operating on you — gifts received that produce a faint sense of obligation, free trials that have quietly biased you toward purchase, kindnesses you find yourself wanting to repay disproportionately. The noticing will be uncomfortable; you will feel briefly paranoid, as if everyone is running plays on you. The paranoia resolves in about a week into competent observation. This is the normal arc. Trust it, and read at the pace the practice requires rather than the pace the prose allows.

A failure mode worth naming early, because it is the engineer's signature misdeployment: engineers reading Cialdini over-deploy social proof first, because it is the most operationally engineer-friendly principle — empirical, quantifiable, measurable — and under-deploy unity, because unity requires a relationship orientation engineers tend to underweight. The result is communication that cites social proof competently (download counts, customers, GitHub stars, testimonials) while failing to build the felt sense of shared identity that makes the social proof land. If you market anything — a product, a consultancy, an open-source project, yourself in a job search — audit your existing material for exactly this imbalance. The citations will be fine; the we, who care about what you care about layer will be underdeveloped. The fix lives in Pre-Suasion's attention-channeling and identity-priming chapters.

The ethical line in this module is the one most readers never draw cleanly, so here is my best attempt at drawing it. You can deploy a principle ethically when (a) the underlying claim is true, (b) the deployment serves a goal you would defend in public, and (c) the recipient, if they understood the deployment fully, would not feel manipulated. The third condition is the hard one, and the honest test for it is: would I be embarrassed if the person on the other side read my notes? If yes, the deployment is over the line. This test is more demanding than it sounds. It excludes a substantial fraction of standard sales tactics, most of what passes for growth hacking, and most of LinkedIn's content strategy. It includes the cold email that makes a genuine and specific case for value, social proof that communicates real traction, authority cited from genuinely-held expertise, scarcity invoked when the scarcity is real. The test does not leave you handicapped — there is plenty of ethical influence available. It does exclude what marketing-popularizer culture treats as standard operating procedure. That exclusion is the curriculum's intended outcome, not its bug.

One blind spot in Cialdini himself to carry with you: his research is heavily tilted toward short interactions — the thirty-second pitch, the one-time donation, the brief encounter with a message. The principles transfer to long professional relationships, but the parameters change, and what works in thirty seconds often misfires across thirty months. Your client relationships, your manager relationship, your community standing all live in the long-interaction regime, where the appropriate frequency and intensity of deployment is much lower than the source material suggests. Over-deployment in long relationships reads as transactional, and transactional is corrosive on a timescale of quarters — slow enough that you won't connect the corrosion to its cause unless you've been warned. Consider yourself warned.

The Influence Audit checkpoint — cataloging where you have deployed these principles unconsciously, including in ways you may not be proud of — is the module's conversion mechanism from reading into self-knowledge. Reading Cialdini without the audit produces a person who can name the principles but cannot see themselves using them. The audit is uncomfortable by design and is, by my estimate, one of the highest-value-per-hour deliverables in the curriculum. Do it.

Conclusion #

This module changes the texture of professional communication permanently. Once you have the Cialdini catalog you cannot un-have it; every email, every meeting, every landing page, every political move becomes visible at a layer that was previously invisible. The visibility is the point. What you do with the visibility is the ethical work, and the ethical work — the three-condition test, applied honestly, including to your own past behavior — is harder than the reading. Let the reading be a gateway, not an arrival.

Predictions #

  • You will finish Influence faster than the estimate, and Pre-Suasion slower — its attention-channeling ideas compound over weeks rather than landing in days.
  • Within forty-eight hours of finishing Influence, you will notice principles deployed on you in three to five contexts, feel mildly paranoid for about a week, and then settle into observation.
  • You will over-deploy social proof and under-deploy unity in your first deliberate applications. Re-read the identity-priming chapters when you notice the imbalance.
  • Any marketing or self-presentation material you already have will look simultaneously better and worse in retrospect — better where you intuited principles correctly, worse where you missed obvious deployments or over-deployed without realizing.
  • The Influence Audit will be the most uncomfortable checkpoint so far, and the deployments-you-would-not-defend-in-public list will be longer than you expect. Both are evidence the module is working.
  • Within three months, you will decline a tactically attractive deployment on integrity grounds, and the decline will cost you something concrete — a deal, a sign-up, a yes. The cost will feel disproportionately painful because it was avoidable. The pain is the price of the integrity you said you wanted to keep.
  • In one long-running professional relationship, you will catch yourself mid-deployment — about to use a principle at short-interaction intensity — and dial it back. That catch, arriving in real time, is the module fully installed.
  • The would-I-be-embarrassed-if-they-read-my-notes test will become the part of this module you still use a decade from now, after the seven principles have blurred back into background knowledge.