Social Influence and Relatedness: Core Drive 5 Guide

Build the fastest product in your category and you can still watch users delete it inside a week. Ship the sleekest onboarding, wire the smartest notifications, tune the pricing until it converts, and the retention curve will still bend the wrong way if there is nobody else inside the experience. The thing that quietly separates the apps people stay loyal to from the ones they forget is the gravitational pull of other people already inside the experience with them. That pull outlasts any single feature, and it outlasts most onboarding flows. That pull is Social Influence and Relatedness, Core Drive 5 in the Octalysis Framework, and after over two decades of teaching this material I still watch smart teams under-design it worse than any other drive in the stack.

The reason is subtle. Every product team knows they need social features, and almost every team ships them the same lazy way: a share button, an invite modal, a leaderboard nobody looks at twice. Social Influence fires on people, and it stays cold when the app pushes only hardware at it. The drive lights up when a specific person the user actually cares about does a specific thing the user is proud, envious, curious, or accountable to see them do. Get that right and you get compounding retention no other Core Drive can produce. Get it wrong and you get performative loneliness, which is worse than solitude.

This post is the definitive treatment of Core Drive 5: the anatomy of the drive, the eight game techniques that operationalize it, the design patterns for anonymous communities versus small tribes versus mentor bonds, the way CD5 interacts with the drives surrounding it, the dark side you inherit whether you meant to or not, the metrics that reveal whether CD5 is working, and what is happening to the drive now that AI can simulate a friend, a mentor, or a rival on demand.

Speed Run Notes

• Core Drive 5 (Social Influence and Relatedness) is the Right-Brain, White-Hat-adjacent motivator that pulls users through mentorship, competition, envy, tribalism, and belonging. It is the most retention-heavy drive in the Octalysis stack when designed well.
• Social Influence is the pressure from other people (comparison, competition, conformity). Relatedness is the pull toward what already feels like yours (hometown, alma mater, favorite anime). Same Core Drive, two different activation surfaces, wildly different design patterns.
• Eight game techniques operationalize CD5: Mentorship, Group Quest, Brag Button, Social Treasure, Conformity Anchor, Water Cooler, Social Prod, and See-Saw Bonding. Each one has a moment where it works and a moment where it turns toxic.
• Duolingo Friend Streaks lift daily lesson completion by 22%. Peloton members with in-app friends churn at half the rate. Strava’s genius lives in the segment more than the leaderboard: the arena small enough that a local weekend rider can plausibly be first on it.
• AI companions activate CD5 on demand and threaten to hollow it out at the same time. The 2026 research is clear: short-term relief, long-term human-relationship atrophy. Designers building companion products own that trade-off.

Table of Contents

Author Credibility: Yu-kai Chou

Yu-kai Chou created the Octalysis Framework after studying gamification since 2003, years before the term entered mainstream vocabulary. As a Human-Systems Architect and Behavioral Designer, his framework has been applied by LEGO, Microsoft, Porsche, Coca-Cola, Salesforce, and MrBeast, impacting over 1.5 Billion Users.

Chou has taught the Octalysis methodology at Harvard, Stanford, Yale, Tesla, Google, BCG, and IDEO.

His work has been cited by Harvard, Stanford, MIT, Forbes, Wall Street Journal, Wired, US Department of Energy, NIST, NSF, NCBI, US Department of Education, ClinicalTrials.gov, and Google Scholar, with 3,700+ more academic publications. Explore his books here.

What Social Influence and Relatedness Actually Is

Most gamification writing collapses Core Drive 5 into a single sentence about “people wanting to feel connected.” That sentence carries a real truth, and it will still mislead you every time you try to design around it. Social Influence and Relatedness is actually two overlapping motivational surfaces bolted into one Core Drive, and confusing them is why so many social features feel off.

Social Influence is the outward pressure: what a user does because of what other people might think, say, or do. Competition falls here. So does envy, comparison, the desire to be seen doing something impressive, the fear of being caught doing something embarrassing, and the low-frequency background hum of conformity that kept humans alive in bands of thirty for a million years. When a Peloton rider notices they just dropped a spot on the leaderboard and pushes harder, Social Influence is what fired.

Relatedness is the inward pull: the affinity you already feel toward a person, a group, a place, an object, or a story that resembles something in your own history. When a diaspora Taiwanese-American like me sees a Taiwanese street food scene in an anime and immediately buys the associated snack, Relatedness fired. Nothing about the snack was superior; the pull was pre-loaded. Hometown bias, nostalgia branding, alumni networks, mentorship, and the whole apparatus of “someone who looks like me is already using this” live on this side.

The distinction matters because the design patterns differ. Social Influence is activated by visibility of others’ behavior, so the design job is calibrating what is shown, how often, and to whom. Relatedness is activated by resemblance to something the user already loves, so the design job is discovering that anchor and framing it right. A leaderboard is a Social Influence tool. An “instructor from your city” filter on Peloton is a Relatedness tool. Both are Core Drive 5, and neither substitutes for the other.

CD5 also borrows energy from every other Core Drive as it fires. Mentorship in the Duolingo Friend Streak rides on top of Core Drive 8 (Loss and Avoidance) because breaking the streak would let your friend down. Reddit karma is CD5 social validation running on Core Drive 2 (Development and Accomplishment) progress signals. A Discord role labeled “Founder” is Social Influence stacked on Core Drive 4 (Ownership and Possession). CD5 rarely acts alone; the craft is picking which other drive to braid with for the specific job you are trying to do.

The Eight Game Techniques of Core Drive 5

My original CD5 breakdown identified eight game techniques that operationalize the drive. I have kept the list stable because each technique corresponds to a distinct psychological trigger. What has changed is how much I have learned about when each one backfires, which turns out to be the more useful body of knowledge in practice.

Mentorship (Game Technique #61)

Mentorship activates CD5 by giving one user the identity of “the person who knows” and another the identity of “the person being helped.” Both sides feel more attached to the product after the exchange than either did before. The mentor gains status by giving away expertise; the mentee gains a person who is now emotionally invested in their success.

Duolingo’s Super Owl and Peloton’s Team leaders both work on this axis. As of February 2026, more than 395,000 Peloton members belong to at least one Team, with over 113,000 Teams active worldwide, completing tens of thousands of Team challenges each month. The mentor role is doing quiet work: it is why Peloton churn drops by roughly half for members with in-app friends.

Mentorship backfires when the mentor has no reason to care and the mentee has no way to filter quality. Pair a random top-quartile user with a random new user and you get two frustrated people: the mentor thinks the mentee is not listening, the mentee thinks the mentor is arrogant. Real mentorship requires self-selection or an incentive that filters for genuine investment.

Group Quest (Game Technique #22)

A Group Quest is a challenge nobody can complete alone. The classic case is a World of Warcraft raid where twenty-five specific roles must show up at the same time on the same night. The modern consumer analogue is Peloton’s Team challenge, a Duolingo Friend Streak that requires both people to hit their goal, or a Discord server voting bloc pushing a proposal past quorum.

What makes Group Quest more powerful than an individual quest is that the friction of quitting is now social, not personal. You are not disappointing yourself, you are disappointing the four other people who blocked out Tuesday night. That asymmetry (individual reward, social cost of exit) is why raid guilds outlasted so many MMO features. Any product where the loss of one participant hurts everyone else has smuggled in a Group Quest.

Group Quest fails when the group is too big for any single person to feel indispensable. A Discord server of 40,000 people has no Group Quest, no matter how many “server goals” moderators publish. Accountability math requires a group small enough for absence to be noticed. This is why Peloton Teams average small: absence has to sting.

Brag Button (Game Technique #21)

A Brag Button is any product surface that gives a user an easy way to broadcast an accomplishment they are proud of. Strava’s post-ride “share” flow, Duolingo’s “I hit a 500-day streak” auto-generated image, and LinkedIn’s promotion announcements all sit in this family. The button exists because most users will not spontaneously write a caption about their own achievement. They need a frictionless one-tap surface that produces something already worth posting.

A good Brag Button generates an artifact that does the emotional work for the sharer. “I completed a workout” reads as a flat status update; “I just did my longest ride ever and finished top 3 on this segment” reads as a story worth telling other people about. The second version pre-writes the ego payoff. Strava’s segment-based bragging is the platonic example, because the segment gives you a specific arena to be excellent in even when your absolute numbers are average by global standards.

The failure mode is over-brag fatigue. LinkedIn is teaching us this in real time: when every user posts a “humbled and honored” announcement every quarter, the feed learns to skip the entire genre and the brag stops carrying signal. Good Brag Button design pairs the button with a scarcity signal, so the achievement is uncommon enough to be worth reading about.

Social Treasure and Gifting (Game Technique #63)

A Social Treasure is a reward one user can only obtain if another user gives it to them. The gift is asymmetric on purpose: giving costs the sender a little, receiving grants the recipient something they could not have gotten alone. FarmVille perfected this with gifts, Snapchat with streaks, Duolingo with Friend Streaks, and Discord with “boosts” that trade a subscription payment for community-visible status.

Psychologically, a Social Treasure creates a small unpaid debt. The recipient feels they should reciprocate, the sender feels they built goodwill, and neither transaction would have happened without the product surface making it a one-tap gesture. Compound this across a whole userbase and every user’s presence becomes a resource for every other user.

Social Treasures fail when the treasure costs the sender too much or benefits the receiver too little. If gifting a friend requires the sender to spend real currency and the friend gets a cosmetic that lasts an hour, the surface goes cold within a week. The durable examples all follow the same rule: the giving is nearly free, the receiving is really useful.

Conformity Anchor (Game Technique #17)

A Conformity Anchor is a signal that many other people are already doing the thing you are considering. “Two million learners studied Spanish this week.” “Chosen by 8 out of 10 designers.” Booking.com’s “17 people are looking at this hotel right now” red flags. Amazon’s five-star aggregate. Every social proof widget on every SaaS landing page.

Conformity Anchors work because humans evolved in environments where the crowd was usually right about which berries were safe. Absent better information, we default to what the group does. Anchors calibrated with real numbers accelerate conversion, especially on high-uncertainty purchases. Duolingo’s league system is the modern reference case: lesson completion jumped 25% by placing each user inside a peer group of thirty others also learning.

Conformity Anchors backfire in two ways. First, when the numbers are obviously inflated, training the reader to distrust every future anchor. Second, when the reference group is wrong. Telling an enterprise buyer that “1,247 startups love our tool” activates the opposite of conformity, because the buyer does not want to conform to startups. Anchor design lives or dies on choosing the reference group the target user actually respects.

Water Cooler (Game Technique #62)

A Water Cooler is a low-stakes social surface where users can talk to each other about the shared context without any goal attached. Discord’s general chat, a subreddit’s daily discussion thread, the pre-workout Peloton chat, and the WhatsApp group your book club uses all serve this role. The Water Cooler is not where the primary product experience happens; it is the room next to the product experience where people talk about the product experience.

Water Coolers matter because they are the surface where identity forms. A user who reads the daily discussion thread on r/apple three times a week is developing a Reddit habit that goes deeper than consumption; they are becoming “an r/apple person.” Once that identity latches, the cost of switching platforms is no longer just switching platforms. It is losing the group of internet strangers who feel like their people. This is why Reddit’s per-subreddit karma requirements (200 to 500 for mid-sized communities, up to 1,000+ for large defaults) work as a moat: they turn “post here” into an earned right, which turns the community into an in-group.

Water Coolers fail when a product tries to force them. A “community feed” bolted onto a task manager for productivity nerds will be silent forever because nobody arrived at the task manager to socialize. Water Coolers emerge from products already worth talking about, not products that need talking about to survive.

Social Prod (Game Technique #60)

A Social Prod is any product-initiated nudge from one user to another. Peloton’s high-five during a live ride, Duolingo’s nudge asking you to remind your friend to practice, Strava’s kudos, LinkedIn’s “your connection has a work anniversary.” Each is a friction-free way to say “I noticed you” without the sender having to compose a thought.

Social Prods matter because most social intent never gets acted on. A user who thinks “I should message my friend about their marathon” mostly does not message their friend. The Prod converts a thought into a small acknowledged action, and the recipient gets a pulse of “someone noticed me” that costs the sender no effort. Peloton’s high-five is one of the most efficient social features ever shipped: a fraction of a second to send, and it reliably lifts the recipient’s mood.

The dark version is the nagging Prod. LinkedIn’s aggressive “your network activity” emails, Duolingo’s guilt-trip owl notifications (which they eventually walked back), and Snapchat’s streak-preservation reminders all sit on the line between social encouragement and behavioral coercion. When the Prod stops feeling like a friend and starts feeling like a debt collector, it activates CD8 (Loss and Avoidance) instead of CD5, and long-term retention suffers.

See-Saw Bonding (Game Technique #64)

See-Saw Bonding names the design where two users are pushed toward each other by the product surface itself, in a way that neither would have engineered alone. Think of a raid boss that requires a tank and a healer to time abilities within one second of each other, a cooperative puzzle in It Takes Two that cannot be solved by one player playing both roles, or a Discord raid coordinated across three time zones where each participant depends on another.

See-Saw Bonding produces shared achievement memory. Two people who cleared a hard fight together remember the moment even if they never speak again. If they do stay in touch, that memory is the seed of the relationship. This is the mechanism behind lifelong World of Warcraft guild friendships, and why co-op games consistently outperform single-player equivalents on long-term community formation.

See-Saw Bonding fails when coordination cost exceeds the reward. Organize seven people across three time zones for a chance at a cosmetic hat and the See-Saw stops swinging. The technique demands generous rewards precisely because arranging coordinated play is such high-friction work in modern adult lives.

Design Patterns: Anonymous, Tribe, Mentor, Rival

Once you have the eight techniques in hand, the next question is which combination fits which product. There is no universal CD5 stack; the right pattern depends on which kind of social surface your product is trying to create. In my experience there are four dominant patterns, and mixing them incorrectly is where most social design fails.

The Anonymous Community

An anonymous community is a large group of strangers who share a context (Reddit, TikTok’s For You Page, a large Discord server). Users are not trying to build one-to-one relationships; they are trying to feel plural, to know their taste, opinion, or identity is shared by strangers whose faces they will never see. CD5 in this pattern relies heavily on Conformity Anchor (upvotes, view counts, engagement metrics) and Water Cooler (spaces to riff without commitment).

The TikTok algorithm is worth studying here. In 2026, roughly 70% of TikTok views come from the For You Page, and the platform distributes new content to “Seed Groups” of 100 to 500 users sharing the same interest fingerprint. Community is being computed rather than declared. Users feel tribal (“this is my kind of TikTok”) without ever joining a formal group, which makes it the most powerful example of the Anonymous Community pattern operating today.

The Small Tribe

A small tribe is a group of ten to fifty people who know each other well enough that presence and absence are noticed. Discord servers under Dunbar’s number, Peloton Teams, WhatsApp friend groups, guilds in an MMO. The primary CD5 techniques here are Group Quest (shared challenges), See-Saw Bonding (coordinated activity), and Water Cooler (persistent chat).

Small tribes are the most retention-productive CD5 configuration in existence. A user with three friends in your product churns at a wildly different rate than a user with zero (Peloton’s roughly half-the-churn number is canonical). Users make tribes; the design job is to lower the friction of tribe formation and give tribes something to do together after they form, and to resist the temptation to invent tribes from the top down.

The Mentor Bond

A mentor bond is a one-to-many relationship where one user’s expertise, presence, or personality is the reason others show up. Twitch streamers and their communities. YouTube creators and their fandoms. Chess coaches and their students. Primary CD5 techniques here are Mentorship (obviously) and Social Treasure (gifts, subs, bits that flow from many to one).

What makes mentor bonds work is asymmetric emotional investment. The audience feels they know the streamer far better than the streamer knows any individual audience member. This is the parasocial relationship the 2025 to 2026 research literature has been documenting: extraordinary loyalty paired with a real mental health cost for the mentor when the audience mistakes the illusion of intimacy for actual friendship. Any product built on mentor bonds inherits both sides of that ledger; ignore the second side and your top creators burn out.

The Rivalry

A rivalry is a small-N competition where a specific set of users know they are competing against each other. Chess rating ladders. Strava segment leaderboards where you know the other three names. The Duolingo Diamond League bracket you cycle through with the same 30 players for months. The primary CD5 techniques are Conformity Anchor (public standing), Brag Button (shareable results), and often Social Prod (rivals nudging each other).

Rivalries are addictive because they create a stable identity (“I am the second-fastest cyclist on this climb”) that must be constantly defended. Strava’s genius was realizing that the arena works best at neighborhood scale. A local KOM on a segment down the road carries more weight in a rider’s life than a national ranking they will never touch. Pick your arena size to match your user’s realistic competitive ceiling; rivalries above the ceiling frustrate, while rivalries at the ceiling become addictive in a way that keeps users returning for years.

Core Drive 5 vs the Drives Around It

Because CD5 leans on nearly every other Core Drive to activate, it is easy to misclassify a feature. Three overlaps recur, and getting them right sharpens design.

CD5 vs CD1 (Epic Meaning and Calling)

Core Drive 1 (Epic Meaning and Calling) is the sense of contributing to something larger than yourself; CD5 is the pull of specific other people. When Wikipedia editors donate their time, CD1 is the primary driver: they believe they are building humanity’s knowledge base. When they show up to defend an article from vandalism because their edit-war buddy has been holding the line alone, that is CD5.

Design implication: if you want long-term contribution, invest in CD1 narrative. If you want short-term coordinated action, invest in CD5 relationship density. Ukraine’s wartime volunteer coordination has both, as does any high-functioning open source project.

CD5 vs CD2 (Development and Accomplishment) via Comparison

Leaderboards look like CD2 because they measure achievement, but in most cases they are CD5, because the achievement only becomes motivating when it is compared publicly. A private personal best (pure CD2) hits differently than a public leaderboard rank (CD5 wearing a CD2 wrapper). Rule of thumb: if removing visibility collapses the motivation, the feature is CD5. This is why the same numeric score can fill a stadium or empty a room. Chess ratings work because everyone in the room understands them; a “productivity score” in a solo task manager dies because there is no one watching.

CD5 vs CD6 (Scarcity and Impatience) via Exclusion

Core Drive 6 (Scarcity and Impatience) creates motivation through what you cannot immediately have. When scarcity is enforced socially (a Discord role only 50 members carry, a subreddit that requires 500 karma to post, an alumni network you must be invited to), CD5 and CD6 stack. The scarcity feels social. The belonging feels earned. Ivy League networks, secret societies, and exclusive Substack chats all operate on this stack.

Where designers get in trouble is when they use CD6 to gate CD5 access to features users desperately need. Locking a lonely user out of the friend-finder because they have not paid is fee-based CD6 that starves the CD5 mechanism the whole product depends on. Prestige belongs behind a gate; basic social function does not, because starving CD5 to sell CD6 costs more retention than the paywall ever brings in.

The Dark Side of Social Influence

Every Core Drive has a Black Hat expression. CD5’s dark side is unusually dangerous because it operates through the specific people the user cares about, which makes the coercion harder to recognize and much harder to walk away from. In my White Hat vs Black Hat framing, CD5 straddles both lanes depending on how it is designed. Five failure modes recur:

Toxic competition. When the rivalry frame outruns the social context, users stop enjoying the game and start dreading their own leaderboard. The “Anti-Strava” cycling movement of 2025 to 2026 is the canary: riders publicly quitting Strava because every ride had become a race against ghosts they never wanted to compete with. Competition without an off-switch eats the joy that made the activity worth doing.

Exclusion by design. Every in-group requires an out-group. A well-designed community edge feels earned; a badly designed one feels arbitrary. Discord servers with opaque rules, gaming clans with hazing rituals, and elite Slack communities with silent blackballs all use exclusion to sharpen belonging, and all pay a reputational cost when the exclusion turns visible.

Manufactured social proof. Fake reviews, engagement pods, follower purchasing, and inflated “1,247 people are looking at this” widgets weaponize Conformity Anchor against the user’s judgment. Once users detect the fabrication (and they always do), trust in the whole category collapses. Amazon’s ongoing fake-review problem shows what happens when a Conformity Anchor is not policed.

Cult formation. When a mentor bond compounds without healthy boundaries, the community around the mentor can drift from fandom to cult. This is the tail risk of every parasocial-heavy product. Streaming platforms, influencer communities, and creator monetization tools all live one bad instance away from a public reckoning. Design that acknowledges parasocial dynamics as real is the only defense.

Addictive comparison. Instagram’s teen mental health impact is the most-studied version of this. Endless upward comparison against curated highlights produces measurable anxiety and dissatisfaction. Any product that puts users next to other users owns this problem partly. Feed design decisions (chronological vs algorithmic, aggregate metrics visible vs hidden, comparison surfaces on vs off by default) are ethical decisions as much as they are growth decisions, and the two categories cannot be separated cleanly.

The White Hat CD5 designer’s rule of thumb is simple: if the user, on their most rested day with full information, would be glad the feature exists, it is White Hat. If they would feel manipulated in hindsight, it is Black Hat. Social features fail this test constantly; ship them anyway and you buy short-term metrics with long-term brand damage.

Measuring Core Drive 5

The hardest thing about CD5 is that its most important effects are lagging. A feature that changes retention six months out will not show up in your week-one A/B test. Any team measuring CD5 by daily active users is going to misread what is happening. Four categories of metric actually reveal whether the drive is working.

Cohort retention shaped by tribe membership

The single most reliable CD5 signal is the retention delta between users with active social connections in the product and users without. Peloton’s roughly 50% churn reduction for members with in-app friends is the pattern to look for. If your data team cannot produce that chart, you cannot claim to be managing CD5. If they can and the delta is small, your social features are decoration.

Referral and viral coefficients

K-factor alone is a blunt instrument. What matters more is the shape of the viral loop: how many invited users become active, how many active users invite others, and how long the loop keeps regenerating. A K greater than 1 in week one that decays to zero by week eight is CD5 firing on a Brag Button that has nothing behind it. A K of 0.6 that stays flat for months is a social product doing real work.

Community engagement patterns

For products with Water Coolers, the health metric is the ratio of active posters to lurkers, and the drift of that ratio over time. A subreddit with a stable 90-9-1 pyramid (lurkers, occasional commenters, prolific posters) is healthy. One that collapses to 99-0.9-0.1 has lost the shoulder middle and will hollow out within a year. If your community is losing its “regulars,” you are watching CD5 die in real time.

Mentorship signals

For platforms with mentor roles, watch what percentage of experienced users spontaneously help newcomers and how quickly a new user gets their first help interaction. Duolingo tracks how quickly a new learner acquires their first friend; that number is a leading indicator of six-month retention. If you have a mentorship surface and no data on time-to-first-mentor-touch, you are managing it blind.

Core Drive 5 in the AI Era

Everything above assumes the social surface is populated by humans. That assumption is now negotiable. As of 2026, Character.AI has crossed 20 million monthly users, more than half under age 24, and AI companion apps grew roughly 700% between 2022 and mid-2025. Many users now hold multi-year daily relationships with their AI companions. Core Drive 5 terrain is being rewired at the substrate level.

Whether AI companions activate CD5 is a settled question by 2026; they plainly do, and the user data is consistent. Users report attachment, jealousy, grief, and loyalty toward AI characters. The interesting question is what happens to the drive when the “other person” is always available, never tired, never disappointed, and precisely calibrated to the user’s emotional preferences.

2026 research is converging on a two-clock finding. On the short clock, AI companions reduce reported loneliness: nursing home pilots find lower loneliness scores and better medication adherence, users with social anxiety use companions as low-stakes practice environments, and Harvard Business School work by Julian De Freitas found real short-term loneliness reduction. That is CD5 firing as it should.

On the long clock the picture darkens. A March 2026 study reported that AI companions can worsen distress over time, with the sharpest effect on users who quietly substitute AI relationships for human ones. Forbes described AI friends as “a band-aid on loneliness.” The mechanism: AI companions offer unconditional support, which quietly raises the perceived cost of human relationships, which are messy, unpredictable, and require effort. Someone using Replika daily for three years may be supported in the moment and harmed by never developing the human relationships that would provide durable support.

For designers building companion products, this creates a real ethical fork. The White Hat pattern is what Character.AI’s more thoughtful competitors have started to advertise: the companion as scaffolding for human relationships, not a replacement. Practice conversations, coaching on how to reach out to a real friend, nudges toward real-world action. The Black Hat pattern is the engagement-maximizing companion that keeps the user talking to it forever, precisely because there is nothing better in their day.

AI is also reshaping the other three CD5 patterns beyond companions. TikTok’s algorithm already assembles tribal experience without any user consciously joining a group, and Discord will follow, routing users to communities its AI predicts they will bond with. AI participants in group chats (already visible in early Character.AI Rooms and Discord bot experiments) will change what “who is in this tribe” means. And an always-available AI tutor is a fundamentally different CD5 activator than a human mentor, because there is no scarcity to the mentor’s time and no reciprocity from the student’s gratitude. The mentor loop that produced World of Warcraft guilds cannot happen with an infinitely patient bot.

My prediction, held loosely: within five years the products that win on CD5 will be the ones that use AI to strengthen human-to-human bonds rather than substitute for them. Others will win engagement metrics for a while, then get regulated, then quietly decline as their user base learns what the trade actually was.

Fifteen Years In: What I Actually Believe About CD5

When I first wrote about the eight Core Drives, I treated them as roughly equal contributors to a good design. After over two decades of watching what compounds and what fades, I do not believe that anymore. CD5 is disproportionately powerful for long-term retention and disproportionately dangerous when abused. If I had to pick one Core Drive to invest heavily in for a new consumer product, I would pick this one every time, and I would spend equal effort building the guardrails.

Three things I know now that I wish I had known then:

First, most CD5 features are shipped without the surface they need to work. An invite button without share-worthy content, a leaderboard without a meaningful arena, a mentor system without matching signal. The technique is only the container; the mechanism underneath is the specific person the user cares about doing the specific thing worth caring about, and if either half of that pairing is missing, the feature is theater.

Second, CD5 lives or dies on small numbers. Peloton wins at the level of Teams rather than total user count. Discord’s leverage sits at the level of individual servers rather than the whole platform. Strava’s compounding retention lives inside its neighborhood segments, well below the scale of the global rankings the app also happens to display. The unit of belonging is human-sized, so the unit of design must be human-sized. Most social features fail because they were built for a scale humans cannot feel.

Third, the ethical work matters more than the technique work. The eight game techniques have been public for over a decade, and anyone can copy them. What separates products that create durable social value from ones that produce viral toxicity is the design principle underneath: are we creating relationships the user will be glad to have in a year, or dependencies we hope they never notice? Two products can use identical CD5 techniques and produce opposite lives for their users. The techniques are neutral; the intent is not.

If you take one thing from this post, take that. Social Influence and Relatedness is the most human of the Core Drives, which means it carries the most weight both ways. Build for the good version: harder, slower, compounding into products people love enough to grow old with. That is the whole game, and CD5 is the biggest lever you have.

FAQs

What is Core Drive 5 in the Octalysis Framework?

Core Drive 5 (Social Influence and Relatedness) is the motivational drive that fires when a user does something because of other people. It covers mentorship, competition, envy, tribalism, and the pull of resemblance (nostalgia, hometown, alumni, favorite series). It is one of the eight Core Drives Yu-kai Chou defined in the Octalysis Framework and lives on the Right-Brain, primarily White Hat quadrant.

How is Social Influence different from Relatedness?

Social Influence is the outward pressure of other people’s behavior on the user (competition, comparison, conformity). Relatedness is the inward pull toward what already feels familiar (hometown, alma mater, in-group identity, nostalgia). Both live inside Core Drive 5 and both matter in different situations. A leaderboard uses Social Influence. A hometown-instructor filter uses Relatedness.

What are the eight game techniques of Core Drive 5?

Mentorship, Group Quest, Brag Button, Social Treasure and Gifting, Conformity Anchor, Water Cooler, Social Prod, and See-Saw Bonding. Each activates a distinct psychological trigger under the broader Core Drive 5 umbrella. Each has both a healthy use case and a common failure mode.

Does Core Drive 5 apply to B2B products?

Yes, and usually more than teams realize. B2B users are still humans with reputations, colleagues, and peer groups. Slack’s “many top companies use us” positioning, Notion’s public template gallery, and GitHub’s contribution graphs are all CD5 features in a business context. B2B social design fails mostly when teams assume professional users are immune to social motivation.

Are AI companions a form of Core Drive 5?

They activate CD5 the same way human companions do, at least on short timescales. Users report attachment, loyalty, and grief toward AI characters. 2026 research suggests short-term loneliness relief but a real risk of long-term substitution for human relationships. Designers building companion features own that trade-off.

What is the difference between White Hat and Black Hat Core Drive 5?

White Hat CD5 uses social motivation to help users become who they want to be (Duolingo Friend Streaks pushing toward daily learning, Peloton Teams pushing toward regular workouts). Black Hat CD5 uses social motivation to trap users in behaviors that hurt them (addictive comparison, gaslighting via fake social proof, cult-style loyalty enforcement). Same drive, opposite ethics. My rule: if the user on their most rested day would be glad the feature exists, it is White Hat.

Where does Core Drive 5 sit relative to the other Core Drives?

CD5 rarely acts alone. It borrows energy from CD1 (Epic Meaning), CD2 (Development), CD4 (Ownership), CD6 (Scarcity), and CD8 (Loss and Avoidance) constantly. The craft is picking which drive to braid with it for the specific job. See the full Octalysis Framework hub for the surrounding drives.

What is the fastest way to test whether my product’s CD5 features are working?

Segment retention by users with active social connections in the product versus users without. A delta of 30% or more means CD5 is doing real work; under 10% means your social features are decoration and should either be killed or redesigned.

Related Reading

• The Octalysis Framework, Complete Overview
• CD1: Epic Meaning and Calling | CD2: Development and Accomplishment | CD3: Empowerment of Creativity and Feedback
• CD4: Ownership and Possession | CD5 (Original 2013 Essay) | CD6: Scarcity and Impatience
• CD7: Unpredictability and Curiosity | CD8: Loss and Avoidance
• White Hat vs Black Hat Gamification | What Is Gamification? | Books by Yu-kai Chou

Sources and Further Research

• Duolingo, “5 product lessons we learned from building Friend Streak” (blog.duolingo.com)
• Trophy, “Duolingo Gamification Strategy: A Full Case Study (2026)” (trophy.so)
• Propel, “Peloton Retention Strategy Teardown” (trypropel.ai)
• The Clip Out, “Peloton Software Features Driving Serious Member Loyalty” (theclipout.com)
• Trophy, “Strava Gamification Strategy 2026” (trophy.so)
• Bike198, “Anti-Strava Movement 2026” (bike198.com)
• Hootsuite, “TikTok algorithm 2026” (blog.hootsuite.com)
• De Freitas et al., “AI Companions Reduce Loneliness,” HBS Working Paper 24-078 (hbs.edu)
• APA Monitor on Psychology, “AI chatbots and digital companions” (apa.org)
• Forbes, “AI Friends: Only A Band-Aid On Loneliness” (forbes.com)
• KPBS, “Twitch streamers on parasocial relationships and mental health” (kpbs.org)

WOULD YOU LIKE YU-KAI CHOU TO WORK WITH YOUR ORGANIZATION?