How the Ben Franklin Effect turns critics into advocates

In 1736, Benjamin Franklin wanted to win over a rival politician in the Pennsylvania assembly. He asked to borrow a rare book from the man's personal library. The favour was granted, the book returned promptly, and the rival later became a friend for life. Psychologists now call the dynamic behind it the Ben Franklin effect.

For service designers, team leaders, and consultants in Australia, the lesson is quietly powerful. Asking for help gives someone a reason to see you as worthwhile. The mechanism runs through customer experience, employee engagement, and the way a consultancy turns a sceptical first conversation into long-term advocacy.

The historical spark that started it all

Franklin's move looked irrational. His peers secured allies through deference or patronage, not by asking rivals for favours. Yet the man who lent the book later campaigned alongside Franklin and supported his policies, a shift that puzzled his contemporaries.

What Franklin had stumbled on was attitude change driven by behaviour. He gave his rival a piece of evidence, in the form of an action, that the two of them could coexist. The rival, having acted generously, adjusted his internal story to match the kind of person who acts generously.

The psychology of asking and receiving

The mechanism sits inside self-perception theory, developed by Daryl Bem. Bem argued that people infer their own attitudes by watching their own behaviour. Handing a colleague a book is not just being nice; it is giving yourself a piece of data about who you are.

A mild tension follows between "I helped this person" and "I do not particularly like this person." The first fact is concrete, the second is vague, so the mind resolves the tension by upgrading the second. Liking grows to match the action.

In Melbourne and Sydney, professional cultures prize the "fair go" and mateship, but reward scepticism. When a colleague has done you a small favour, the egalitarian norm makes it easier to update your view of them, because updating feels like a fair response to what they did.

A wider toolkit of soft influence

The Ben Franklin effect sits alongside other principles. Each works through a different psychological channel, and the right choice depends on the moment.

Principle	Trigger	When to use	Overuse risk
Ben Franklin effect	Small favour	Undecided or opposed	Manipulative if too large
Reciprocity	Give first	Open a closed door	Feels transactional
Authority	Expertise	Low trust, high stakes	Compliance without buy-in
Social proof	Others' behaviour	Ambiguous situations	Collapses if group shifts
Commitment	Small "yes"	Need follow-through	Locks people in

These tools are not interchangeable. Asking for a favour is a relationship move, while reciprocity is a transaction. Authority speaks to the head and social proof to the herd. Picking the wrong one is how leaders end up with compliance instead of commitment.

Designing services that invite small commitments

Service design is full of moments where a customer becomes an advocate or is pushed the other way. A common mistake is to over-rely on reciprocity, flooding new users with discounts, then wondering why churn stays high. The Ben Franklin effect suggests a different rhythm: invite small contributions early.

An onboarding flow that asks the user to name a goal, upload a sample, or share a constraint turns the product into something they have shaped. The pattern shows up in software templates and in New South Wales government services that ask citizens to confirm their own details. Engagement rises because the user has put something in.

The same logic runs through employee experience. A new starter asked to suggest a small improvement in their first week feels more invested than one who is only told what to do. A consultant who asks a client team to draft the first version of a workshop agenda gets a different quality of conversation. For leaders who want a deeper look at the ethics of encouraging others, the work at in encourage leading explores the boundary between genuine support and pressure.

Leading teams and converting skeptics

The hardest application is the most local: a team meeting where one person keeps pushing back, a client who has decided you are wrong, a peer who treats every idea with suspicion. Here the effect earns its reputation, because the alternatives are limited. You cannot flatter a sceptic into supporting you or out-argue someone who is not listening.

Ask for a specific, small contribution instead. "Can you red-pen this section?" "Which two competitors are we misreading?" "Could you sit in on Thursday's user interview?" The ask reframes the relationship. The sceptic is no longer an audience for your work; they are a participant in it.

In Australian organisations, this fits the pull toward egalitarianism and the instinct to dislike the tall poppy. Senior people who ask for help from junior staff send a quiet signal that the hierarchy is not the whole story. Teams respond with more honest feedback, and the leader gets the early warning that prevents costly pivots. A useful companion idea is recognising when a sunk cost keeps a team attached to a poor decision, which Nick explores in the sunk cost fallacy.

Reading the room in Australian workplaces

Australia is not a uniform market. In the resources sector in Western Australia, directness is the norm and indirect asks read as evasive, so a clear, bounded request works better than a hedged one. In professional services in Sydney and Melbourne, the same request can be wrapped in more context without losing impact.

Australian English gives you tools. Phrases like "no worries," "she'll be right," and "happy to help" signal a relational register that fits the small-favour pattern. The danger is leaning on them so heavily that the ask disappears into the politeness. The effect requires the ask to be visible enough that the other person registers they have done something.

Tall poppy syndrome cuts the other way. A leader seen as too polished or too certain invites being cut down. Asking for help on something the leader cannot do alone softens that instinct and turns the tall poppy into a colleague, which is the shift the Ben Franklin effect is built to produce.

Putting it into practice without overplaying your hand

The effect is small, and that is its strength. A request that is too large, frequent, or public starts to feel like exploitation. The rule is to ask for something the other person can give easily, costs them little, and connects to the relationship you want.

For a service designer, this might mean inviting a customer to beta-test a single feature. For a team leader, asking a sceptic to chair one meeting. For a consultant, asking a difficult client to introduce you to one of their peers. Each request is small, but each gives the other person a reason to revise their view of you.

Used well, the Ben Franklin effect is one of the cheapest pieces of behavioural science in your toolkit. Used badly, it becomes a gimmick. The difference is whether the ask is genuine, the gratitude is real, and the relationship can carry the weight. If you want to see how this sits inside a broader behavioural approach to service and experience design, Nick Naumof works with organisations across Australia on these questions, from research through to workshop design and team training.