📘 Editor’s note: This is Part 2 of my series on the BJ Fogg Behavior Model, focused specifically on the three trigger types (Spark, Facilitator, Signal) and how they map to the Octalysis Core Drives. For the complete, 7,500-word deep guide to the full model — B = MAP, the six factors of Ability, critiques, neuroscience, and how the whole thing integrates with Octalysis — read the pillar first.
→ The complete guide: BJ Fogg Behavior Model: S-Tier Designer’s Guide (B=MAP)
BJ Fogg’s B=MAP model gives us Motivation, Ability, and Prompt. But it treats all prompts as equal. They’re not. In Part 1, we broke down Ability and Motivation through the Octalysis Framework. Now let’s look at the piece that actually makes things happen: the trigger.
Note: BJ Fogg renamed “triggers” to “prompts” in his updated model. I personally preferred “trigger” (it’s more visceral and accurate), but I’ll use both terms here.
- About Yu-kai Chou
- Hope and Fear in Fogg’s Model
- The Three Types of Triggers (Prompts)
- The Spark: Adding Motivation When Ability Is High
- Make the Spark a Black Hat Trigger
- The Facilitator: Making Hard Things Easy
- The Signal: A Simple Nudge
- Mapping Fogg’s Triggers to Octalysis Core Drives
- Where Most Designers Get Triggers Wrong
- BJ Fogg’s Lasting Contribution
- Related Reading
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 & 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.
Hope and Fear in Fogg’s Model
Fogg identifies Hope and Fear as two of the core motivators in his model. From an Octalysis perspective, these map cleanly onto specific Core Drives.
Hope is Core Drive 7: Unpredictability & Curiosity combined with Core Drive 2: Development & Accomplishment. You hope for a positive outcome you can’t fully predict, while also anticipating the feeling of achievement when it arrives.
Fear maps to Core Drive 8: Loss & Avoidance. You’re afraid of losing something: your progress, your money, your social standing.
What I find interesting is that Fogg treats Hope and Fear as a simple motivation pair, but Octalysis reveals that Hope is actually a blend of two distinct drives: the excitement of the unknown (CD7) and the pull of potential accomplishment (CD2). This matters for designers because you can strengthen “Hope” by leaning into either drive independently.
The Three Types of Triggers (Prompts)
BJ Fogg identifies three types of triggers, each designed for a different situation on the Motivation × Ability graph. This is where his model gets specific and practical.
The Spark: Adding Motivation When Ability Is High
The Spark is for users who can do the thing but don’t want to. They have the ability. It’s easy, it’s accessible, it takes minimal effort. But they lack motivation.
The Spark adds that missing motivation. It’s the email that says, “Hey! Your friend on Facebook just sent you a message!” You already know how to click a link. You’re already on your phone. The Spark doesn’t make the action easier. It gives you a reason to care.
From an Octalysis perspective, Sparks lean heavily on Core Drive 8 (Loss & Avoidance) and Core Drive 7 (Unpredictability). “Someone sent you a message” triggers curiosity (who was it? what did they say?) while also creating a mild fear of missing something socially important.
Make the Spark a Black Hat Trigger
In most cases, the Spark should be a Black Hat Trigger.
This happens with our Octalysis Design Challenges inside Octalysis Prime, where we include the upcoming deadline in the notification.
If we chose to serve up a White Hat Trigger like, “Good luck as you continue working on your Design Challenge,” the trigger may not drive the desired action. The member thinks, “That’s nice,” and goes back to whatever they were doing.
But a message like, “Your Design Challenge submission closes in 24 hours. You’ll lose your streak if you don’t submit.” That’s Core Drive 8 combined with Core Drive 6: Scarcity & Impatience. The deadline creates urgency. The potential loss creates action.
White Hat motivation feels good but doesn’t always compel immediate behavior. Black Hat motivation feels urgent and drives action right now.

The Facilitator: Making Hard Things Easy
The Facilitator is the opposite scenario. The user has plenty of motivation but lacks the ability to act. The action feels confusing, expensive, or time-consuming.
The Facilitator’s job is to reduce friction. “Hey, you should do it. And if you didn’t because it’s hard, let me make it easy for you.”
Maybe it’s a software wizard that walks you through installation. Maybe it’s a counselor who helps you navigate career choices. Maybe it’s a coupon that drops the price from painful to acceptable.
In Octalysis terms, Facilitators work by attacking the Anti Core Drives, the friction elements that block motivation from converting into action. If Core Drive 2 makes you want to learn a new skill, but the course requires 40 hours and $500, the Facilitator reduces those barriers so your motivation can actually reach the action line.
This is also why Anti Core Drives matter so much in behavioral design. You can have every Core Drive firing at full strength, but if the path to action is blocked by complexity, cost, or confusion, nothing happens.

The Signal: A Simple Nudge
The Signal is the easiest trigger type. The user already has high motivation and high ability. They just haven’t done it yet.
In that case, all you need is a simple “Hey, do it.” A calendar reminder. A push notification. A sticky note on the fridge.
Think about taking your daily vitamin. You want to (motivation: health). It takes two seconds (ability: trivial). You just forget. The Signal is your phone buzzing at 8 AM: “Take your vitamin.” That’s it. No persuasion needed.
The Signal connects to what BJ Fogg later developed into Tiny Habits, the idea that if you anchor a desired behavior to an existing routine (the existing routine serves as the Signal), you can build habits without needing external motivation at all.
Mapping Fogg’s Triggers to Octalysis Core Drives
Here’s how I think about the relationship between Fogg’s three trigger types and Octalysis:
- Spark (high ability, low motivation) → Activate Black Hat Core Drives: CD6 (Scarcity), CD7 (Unpredictability), CD8 (Loss & Avoidance). These create urgency and emotional compulsion.
- Facilitator (high motivation, low ability) → Reduce Anti Core Drives and lean on CD3 (Empowerment of Creativity & Feedback). Make the path clear, give the user tools, show them they can do it.
- Signal (high motivation, high ability) → Light touch. CD4 (Ownership & Possession) reminders (“Your streak is at 14 days”) or simple CD5 (Social Influence) cues (“Your friend just completed their workout”) can serve as the nudge.
Fogg’s model tells you which trigger type to use. Octalysis tells you how to build it.
Where Most Designers Get Triggers Wrong
The most common mistake I see is using a Signal when the user needs a Spark.
Companies send reminder emails to dormant users (“Hey, come back!”) and wonder why nobody comes back. The user isn’t forgetting your app. They don’t have a reason to care. You need a Spark that reignites motivation, not a Signal that assumes motivation already exists.
This is the same problem I describe with Points, Badges, and Leaderboards. Teams add surface-level game mechanics (which are just Signals) to a product where users lack core motivation. No number of badges will create motivation that isn’t there. You need to design for the 8 Core Drives first.
Conversely, many onboarding flows use Sparks (emotional appeals, hype videos) when the user already wants to use the product but can’t figure it out. They need a Facilitator, not more motivation.
BJ Fogg’s Lasting Contribution
BJ Fogg is a pioneer in our industry. His research from the Stanford Behavior Design Lab — which he founded in 1998 — has been cited over 20,000 times, and Stanford students from his lab co-founded Instagram and launched the Center for Humane Technology.
Although I don’t love his rename from “triggers” to “prompts,” there is a lot we can learn from his methods, especially Tiny Habits, which I recommend.
What I’ve tried to show in Part 1 and this post is that you can take an established model, examine it through a different lens, and reach deeper conclusions. The Fogg Behavior Model describes the mechanics of behavior. Octalysis explains the motivational engine behind those mechanics.
That’s the value of thinking for yourself. Respect the pioneers, learn their frameworks, then push further.
Related Reading
- BJ Fogg Behavior Model: B=MAT(P) Extended, Part 1 of 2
- The Octalysis Framework for Gamification & Behavioral Design
- White Hat vs Black Hat Gamification
- Anti Core Drives in Gamification
- Points, Badges, and Leaderboards: The Gamification Fallacy
- What is Gamification?
- Books by Yu-kai Chou





