DEV Community: Ribin K Roy

Behavioral Design Unpacked: Nudges, Funnels & Persuasion | UX Unpacked #3

Ribin K Roy — Mon, 02 Nov 2026 15:39:05 +0000

Why This Matters to You

You've spent weeks designing a feature. You launch it—and nobody uses it.

The problem might not be bad design. It might be that you're missing how behavior actually works.

Over the past three articles in UX Unpacked, I've walked through the frameworks that explain why people do what they do online. But here's what I realized: these aren't separate tools. They're connected layers of the same system.

This fourth installment combines everything we've covered into one actionable framework:

Nudge Theory — How choice architecture shapes decisions
CREATE Action Funnel — Why users drop off before acting
Persuasive Technology — How products build lasting behavior change

By the end of this article, you'll see behavioral design as a cohesive whole—not isolated concepts.

Let's connect the dots.

The Big Picture: Three Layers of Influence

Think of behavioral design as three concentric circles.

The outermost layer is persuasive technology—the broadest category. It's any technology designed to change attitudes or behaviors through persuasion rather than coercion. Everything else sits inside this.

The middle layer is nudge theory—specific techniques for steering choices without forbidding options. Defaults, framing, social proof, simplification. These are tactical moves within a larger persuasive strategy.

The innermost layer is the CREATE Action Funnel—the moment-to-moment decision process where all of this plays out. Every nudge, every persuasive element, has to pass through these six gates to actually change behavior.

💡 Design Principle: Work from the inside out. If someone can't cross the CREATE funnel, no amount of persuasion or clever nudging will help. Fix the bottlenecks first.

Layer 1: CREATE—Where Behavior Actually Happens

Steve Wendel's CREATE Action Funnel describes the six stages before action occurs. Every product interaction passes through these gates.

Cue

The trigger that gets you thinking about taking a specific action.

LinkedIn sends push notifications. HomeAway sends follow-up emails. A red badge appears on an app icon. These are cues—and they exist whether you design them intentionally or not.

Most teams forget the cue entirely. They assume users will form habits spontaneously. That almost never happens.

Reaction

Your instinctive first response to the idea of taking the action.

"Oh man, better check what's happening." versus "Ugh, create a profile?!"

This happens before rational thought. Emotional. Automatic. Your design's tone, timing, and context set the stage here.

Evaluation

A more rational cost-versus-benefit analysis.

"I like LinkedIn's content—this time will be no different." versus "Will a 5-star rating matter when I barely use this platform again?"

Benefits must outweigh perceived costs. When they don't, users drop out.

Ability Check

Seeing whether you can even take the action right now.

"I definitely have the ability—just tap the icon." versus "Can I do this on my phone? Will it take five minutes?"

Friction kills momentum. The easier the path, the higher the conversion.

Time Pressure

Determining whether it's urgent to act now.

"I should see if there are trending topics today." versus "Dammit, this link expires soon."

Genuine urgency helps. Manufactured scarcity backfires. Know the difference.

Experience

The act of taking the action and the feelings that come with it.

"That was a productive two minutes." versus "The link expired anyway. Whatever."

This feeds back into future reactions. Good experiences build habits. Bad ones create avoidance patterns.

💡 Critical Insight: The funnel is cyclical. The experience informs the next reaction. First impressions aren't just important—they're permanent.

Layer 2: Nudges—Steering Without Pushing

Within each CREATE stage, you can deploy nudges—any aspect of choice architecture that alters behavior predictably without forbidding options or changing economic incentives.

Defaults at the Evaluation Stage

Pre-filled templates reduce decision paralysis. Opt-out donation systems tripled participation rates compared to opt-in. Set helpful defaults that align with user goals, not just business metrics.

Framing During Reaction

"90% success rate" lands differently than "10% failure rate." Positive framing activates approach motivation. Negative framing triggers threat response. Choose based on desired outcome.

Social Norms Across All Stages

"Most users complete setup in two minutes." Shows what others do. Leverages conformity drive. Builds trust through collective behavior.

Salience at the Cue Stage

Place important buttons in prime real estate. Make choices impossible to miss. Visibility precedes everything else.

Timing Within Time Pressure

Request ratings after task completion, not interruption. Ask when value is fresh, not forgotten. Context determines receptivity.

Simplification in the Ability Check

Reduce form fields from ten to three. Remove friction ruthlessly. Every extra step is a leak in your funnel.

Feedback Loops Reinforcing Experience

Show profile completion percentages. Track progress visually. Make invisible effort visible.

💡 Design Tip: Multiple nudges compound. Stack them carefully. Too many create pressure. Too few create indifference.

Layer 3: Persuasive Technology—The Engine Underneath

B.J. Fogg identified three ways technology functions persuasively. Understanding which role your product plays helps you design more intentionally.

Technology as Tools

Increase ability by making actions easier or restructuring them entirely. Installation wizards. Auto-categorization. One-click ordering.

When it works: Completion rates rise. Users accomplish more with less effort.

When it fails: Additional features add complexity instead of removing it.

Technology as Media

Use narrative and interactivity for rehearsing behavior, building empathy, exploring causal relationships. Simulation games. Visualizations. Procedural rhetoric through mechanics.

When it works: Users internalize lessons through experience rather than instruction.

When it fails: The experience feels manipulative or preachy.

Technology as Social Actors

Apply social influence through language, assumed roles, and presence. Embodied conversational agents. Helpful interfaces. Apologies and greetings that mimic human interaction.

When it works: Trust builds naturally. Users feel understood.

When it fails: Uncanny valley kicks in. Humanity feels manufactured.

💡 Critical Warning: Users respond to computers as social actors even when they shouldn't. This automaticity demands extra responsibility. The asymmetry—technology knows you, you don't know it—creates power imbalance.

The Audit: Eight Questions

Pick a behavior you're trying to encourage. Run it through this checklist.

1. Have I made the cue visible? Is the button above the fold? Do users know when to act? Is it clear what happens next?

2. What's their initial reaction? Am I assuming positivity or expecting skepticism? Tone and context matter more than I admit.

3. Do benefits outweigh costs? If I were the user, would I feel this was worth my time? Be honest about the trade-off.

4. Can they actually do it right now? How many clicks or taps? Does it interrupt their current flow? Friction compounds silently.

5. Is there genuine urgency—or manufactured scarcity? Countdown timers work once. After that, users recognize the pattern. Authentic constraints only.

6. What experience am I creating? Positive reinforcement or surveillance? Celebration or judgment? Trust builds slowly, destroys fast.

7. Which functional mode dominates? Tool, media, or social actor? Mixing modes without intention creates confusion.

8. Am I respecting freedom of choice? Can users opt out? Is the exit obvious? Is consent reversible?

Any answer feels unclear? That's where iteration starts.

Ethics: The Red Lines

Thaler and Sunstein emphasized two rules for libertarian paternalism:

Help people do what they already want to do. Preserve their freedom to choose.

Ask yourself: Would I be comfortable if everyone knew how I designed this choice?

Good practices:

Help people succeed at goals they hold
Preserve autonomy with obvious opt-outs
Build long-term trust over short-term engagement

Red flags:

Fake countdown timers creating artificial urgency
Hidden fees buried in checkout flows
Forced continuity trapping subscriptions
Confirm-shaming guilt-tripping opt-outs
Roach motel patterns easy to enter, impossible to leave

Dark patterns extract value at user expense. Ethical design creates mutual success.

💡 Final Word: With great power comes responsibility. The question isn't whether your design persuades—it's whether it does so transparently.

What Research Shows

Despite promising results, three challenges persist across all frameworks.

Technical limitations: Self-report systems carry bias and recall errors. Sensor-based monitoring struggles with ambiguity. Predicting human behavior remains difficult—especially for precisely timed interventions.

Measurement difficulties: True randomized controlled trials are rare. Most participants self-select, meaning they may already be adopting desired behaviors. Meta-analyses show evidence remains controversial. Long-term studies are hard but necessary.

Ethical uncertainty: Manipulating feelings and desires remains debated. Persuasive backfires—where technology triggers the bad behavior it was designed to reduce—are real risks. A weight-loss app obsessed with calories might trigger disordered eating patterns.

But some things do work consistently. Health coaching combining goal-setting, education, and progress tracking produces sustainable change. Feedback on electricity consumption typically yields 5-12% savings. Awareness of environmental, financial, and health benefits makes eco-friendly behaviors more attractive.

Case Study: LinkedIn Works, HomeAway Doesn't

Let's apply everything at once to two real examples.

LinkedIn succeeds because:

The cue is always visible (home screen icon)
Expectations are met consistently (relevant content)
Ability is nearly effortless (tap and scroll)
Urgency is subtle, not manufactured
Experience delivers value quickly (2-minute productivity)

Even after disabling push notifications, checking continues because the underlying value persists. The habit forms around the tool itself, not the interruption.

HomeAway fails because:

The cue arrives late (after vacation ends)
Initial reaction is frustration ("I already did this")
Benefits feel distant (rating matters someday, maybe)
Ability is uncertain (can I do this on my phone?)
Time pressure feels coercive (expiring links)
Experience disappoints (link invalidates)

Every CREATE stage had friction. Multiple nudges tried to compensate but couldn't overcome fundamental design failures.

The lesson: You can't nudge a broken funnel. Fix the foundation first.

Apply This Tomorrow

You don't need to rebuild your entire product.

Find one behavior you're struggling to encourage. Map it against all three layers:

Start with CREATE. Where do users drop off? Is it visibility? Friction? Motivation?

Add nudges at that specific bottleneck. Don't scatter tactics randomly. Target the leak.

Then consider which persuasive mode serves best. Tool for efficiency. Media for understanding. Social actor for connection.

Start small. Track changes. Iterate based on actual behavior—not assumed motivations.

Coming Next in UX Unpacked

This series continues building fluency in behavioral design:

Spectrum of Thinking Interventions—automatic nudges versus deliberate reflection. When to trigger System 1 versus System 2, and why choosing the wrong point backfires.

Behavioral Science Foundations—the interdisciplinary study of human behavior across psychology, sociology, and anthropology. How these principles enhance engagement, usability, and satisfaction in UX.

Each piece stands alone while connecting to the bigger picture.

Final Thought

Behavioral design doesn't promise transformation. But it does give you vocabulary for what already shapes every interaction.

You're always designing choice architecture. The question is whether you're doing it consciously.

Work from the inside out. Fix funnels before nudging. Measure before optimizing. Build trust before extracting value.

About the Author

I'm Ribin K Roy—software developer, UI/UX designer, and student learning in public. I document what I pick up along the way.

This series exists because I've found that the best way to solidify my own understanding is to write it down in plain language. If you're new to UX design or just want to brush up on fundamentals without wading through dense textbooks, welcome. You're in the right place.

If you found this helpful, subscribe or follow wherever you're reading. The next article drops soon.

Sources Cited

Wendel, Steve. A Method to Persuade. HelloWallet internal framework.\
Thaler, Richard H. & Sunstein, Cass R. Nudge: Improving Decisions About Health, Wealth, and Happiness. 2008.\
Fogg, B.J. Persuasive Technology: Using Computers to Change What We Think and Do. Morgan Kaufmann, 2003.\
Nerlikar, Rajesh. Behavioral Science Crash Course: CREATE Action Funnel. Action Design ATX, 2019.

Nudge Theory in UX Design: Complete Guide | UX Unpacked #2

Ribin K Roy — Wed, 19 Aug 2026 10:48:42 +0000

Why This Matters to You

Imagine you've spent weeks designing a feature. You launch it — and crickets. Nobody uses it.

Sound familiar?

The problem might not be bad design. It might be that your users simply can't find the choice in front of them.

This brings us to Nudge Theory.

Named and popularized by American academics Richard H. Thaler and Cass R. Sunstein in their 2008 book 'Nudge: Improving Decisions About Health, Wealth, and Happiness', this framework has been cited in over 1,900 academic papers and adopted by product teams worldwide. It's also one of the most practical frameworks in design. Five minutes to explain. Lifetime to master.

By the end of this article, you'll be able to:

Design choices that guide decisions without forcing compliance
Diagnose why features aren't being adopted
Apply ethical nudges to improve user outcomes immediately

This is the second installment of UX Unpacked — a series where I break down essential UX concepts, one framework at a time. Each piece stands alone while building toward deeper fluency. No jargon dumps. No gatekeeping. Just clarity.

"This article explains concepts from 'Nudge: Improving Decisions About Health, Wealth, and Happiness' by Richard H. Thaler and Cass R. Sunstein (2008), based on earlier research by Daniel Kahneman and Amos Tversky."

Next, we'll cover Persuasive Technology.

Let's begin.

The Core Formula:

Choice Architecture

Here's the entire model in one line:

"A nudge is any aspect of the choice architecture that alters people's behavior in a predictable way without forbidding any options or significantly changing their economic incentives."

Or, translated into plain English:

You design the environment. People make the choice. You steer without pushing.

No mandates. No punishments. No taking options away.

The Three Ingredients

1. Libertarian Paternalism — The Philosophy

Thaler and Sunstein coined this term to describe Nudge theory's ethical backbone.

It sounds contradictory. Let me unpack it.

Type	What It Means	Example
Libertarian	Preserve freedom of choice	Users can still opt out of any nudge
Paternalism	Guide toward beneficial outcomes	Help people save more for retirement

💡
Design Tip: Never use nudges to manipulate. Use them to help people do what they already want to do.

The goal isn't to control. It's to make good choices easier.

2. Humans vs. Econs

Traditional economics assumes people are rational calculators. Thaler and Sunstein call these imaginary beings "Econs."

Real people? They're "Humans."

Humans make decisions based on instincts, emotions, and mental shortcuts. We're lazy. We're optimistic. We follow the crowd. And that's okay — these traits helped our species survive.

But in modern systems, they create blind spots.

Factor	What It Means	Example
Procrastination	Delay hard decisions	Default options reduce inertia
Loss Aversion	Fear losing more than gaining	Frame as gains, not losses
Social Proof	Follow the herd	Show what others do
Present Bias	Choose immediate over long-term	Break tasks into smaller steps

💡
Design Tip: Don't fight human nature. Work with it.

3. The Nudge Toolkit

Thaler and Sunstein identified several heuristic tendencies that act as nudges. Here are the core ones for UX:

Nudge Type	When to Use	Example
Defaults	High inertia situations	Opt-out organ donation increased donations 3x
Framing	Perception needs shifting	"90% success rate" vs "10% failure rate"
Social Norms	Conformity drives behavior	"Most users complete setup in 2 minutes"
Salience	Attention needs directing	Place important buttons in prime real estate
Timing	When you ask matters	Request rating after task completion
Simplification	Complexity causes abandonment	Reduce form fields from 10 to 3
Feedback Loops	Progress needs visibility	Show profile completion percentage

💡
Design Tip: Multiple nudges compound. Stack them carefully for maximum impact.

The Nudge Line: Where Behavior Happens

Imagine a graph showing choice visibility on the vertical axis and ease of action on the horizontal axis, with a line separating where behavior happens from where it doesn't.

Key insights:

If a choice is very easy, you need less visibility

If a choice is hidden, you need extreme ease

Either side of the equation can compensate for the other

What's below the line? Nothing happens. Fix one variable, and you cross the threshold.

How to Audit Your Design (The Right Order!)

When a feature isn't getting adoption, designers often blame motivation. "Users just don't care!"

But that's usually wrong.

Follow this checklist instead:

Step 1: Can users see the choice?

Is the button visible above the fold?
Do they know when to act?
Is it clear what happens next?

Fix: Improve salience. Make it impossible to miss.

Step 2: Is it easy enough?

How many clicks/taps does it take?
Are there unnecessary forms?
Does it fit into their current flow?

Fix: Apply simplification. Remove friction ruthlessly.

Step 3: Only then — what's the default?

Are users opting in or staying out?
Could a smart default help without coercion?
Can they change it easily later?

Fix: Set helpful defaults. Respect the ability to change.

💡
Remember: Fixing visibility and ease is the priority. If your choice is invisible or takes 20 minutes, no amount of motivation will help.

Real-World Example: Google Forms

Google Forms became the go-to survey tool by mastering several nudges simultaneously.

Nudge	How Google Delivered It
Defaults	Pre-filled templates reduce decision paralysis
Simplification	Drag-and-drop interface requires zero technical skill
Social Norms	"Used by millions" signaling creates trust
Feedback	Real-time preview shows exactly what respondents see
Salience	Clear CTA: "Send form" button always visible

Result? Millions of daily active users. Because good choice architecture removes barriers.

Apply This to Your Design Today

Pick a behavior you're trying to encourage. Now ask:

Question	Your Answer
Is there a clear, visible choice?	Yes / No
Is the path of least resistance aligned with the desired behavior?	Yes / No
Are you respecting freedom of choice?	Yes / No
Could this be perceived as manipulative?	Yes / No

Any box unchecked? That's your fix.

A Word on Ethics

With great power comes responsibility.

Thaler and Sunstein emphasize two rules:

Help people do what they already want to do.
Preserve their freedom to choose.

💡
Ethical Framework: Ask: "Would I be comfortable if everyone knew how I designed this choice?"

Good nudges:

Help people succeed — Organ donation, retirement savings, health outcomes
Preserve autonomy — Opt-out is always available and obvious
Build long-term trust — Not short-term engagement at the cost of reputation

Bad nudges:

Exploit for profit — Fake countdown timers, hidden fees, forced continuity
Trap users — Confirm shaming, roach motel patterns
Hide information — Small print, buried settings

Avoid dark patterns. Design for user success, not just business metrics. Long-term trust beats short-term wins.

What's Coming Next in This Series Upcoming articles will cover:

Persuasive Technology — BJ Fogg's work extended into product design

Hick's Law and decision fatigue

Jakob's Law and user expectations

Peak-End Rule for memory retention

Fitts's Law and target sizing

Each piece builds on the last while standing alone for new readers.

My goal is to make these concepts accessible to anyone starting in UX — no jargon dumps, no gatekeeping.

Wrapping Up

Nudge Theory doesn't promise magic. But it does give you:

A diagnostic framework for stuck features
A prioritized checklist for improvement
A common language for your team

Remember: Choice architecture shapes behavior. Design it responsibly.

About the Author

I'm Ribin K Roy — software developer, UI/UX designer, and student learning in public. I document what I pick up along the way.

If you found this helpful, subscribe or follow wherever you're reading. The next article drops soon.

UX Unpacked

Ribin K Roy — Sat, 01 Aug 2026 15:53:41 +0000

Essential frameworks, one concept at a time

Why This Matters to You

Imagine you've spent weeks designing a feature. You launch it — and crickets. Nobody uses it.

Sound familiar?

The problem might not be bad design. It might be that your users simply weren't set up to take the action you wanted.

This brings us to the Fogg Behavior Model.

Created by Dr. BJ Fogg at Stanford University, this framework has been cited in over 1,900 academic papers and adopted by product teams worldwide. It's also one of the simplest frameworks in design. Five minutes to explain. Lifetime to master.

By the end of this article, you'll be able to:

Predict when users will perform a behavior
Diagnose why a feature isn't being adopted
Apply practical fixes to your designs immediately

This is the first installment of UX Unpacked — a series where I break down essential UX concepts, one framework at a time. Each piece stands alone while building toward deeper fluency. No jargon dumps. No gatekeeping. Just clarity.

Let's begin.

The Core Formula:

B = MAP Here's the entire model in one line:

Behavior = Motivation × Ability × Prompt

Or, translated into plain English:

A behavior happens only when Motivation, Ability, and a Prompt all align at the same moment.

If any one of these three pieces is missing, nothing happens.

No complexity. No hidden variables. This is the ceiling and the floor.

The Three Ingredients

1. Motivation — Do I want to do this?

Motivation is your user's desire to perform an action. The catch: motivation fluctuates wildly. A user who's highly motivated today might be unmotivated tomorrow.

Three sources of motivation:

Type	What It Means	Example
Person	Internal desire	I love cooking, so I download recipe apps
Advantage	External reward or consequence	I complete tasks to earn a bonus
Context	Environmental influence	Everyone in my team uses Slack, so I do too

💡
Design Tip: Don't try to manufacture motivation from scratch. Instead, connect your feature to motivations that already exist in your users' lives.

2. Ability — Can I do this easily?

Ability is about simplicity. Even highly motivated users won't act if something is too hard.

Five factors that make things harder:

Time — Does it take too long?
Money — Is it expensive?
Physical effort — Does it require clicking 20 times?
Mental energy — Is it confusing?
Routine fit — Does it disrupt their workflow?

💡
Design Tip: The easiest fix is almost always to reduce friction. Remove steps, pre-fill fields, default to sensible choices.

3. Prompt — Am I reminded to do this?

The prompt is your trigger. Without it, no matter how motivated or able your user is, nothing happens.

Three types of prompts:

Type	When to Use	Example
Facilitator	High motivation, low ability	A step-by-step wizard guides setup
Signal	High motivation, high ability	A subtle icon reminds them to click
Spark	Low motivation, high ability	A limited-time offer nudges them to act

💡
Design Tip: Prompts should be timely and noticeable — but not annoying. A well-placed button beats an ignored notification.

The Action Line: Where Behavior Happens

Imagine a graph showing motivation on the vertical axis and ability on the horizontal axis, with a curved line separating where behavior happens from where it doesn't.

Key insights:

If a behavior is very easy, you need less motivation
If a behavior is hard, you need lots of motivation
Either side of the equation can compensate for the other

What's below the line? Nothing happens. Fix one variable, and you cross the threshold.

How to Debug Missing Behavior (The Right Order!)

When a feature isn't getting adoption, designers often blame motivation. "Users just don't care!"

But that's usually wrong.

Follow this checklist instead:

Step 1: Is there a prompt?

Can users find the button?
Do they know when to act?
Is it clear what happens next?

Fix: Make the prompt visible and well-timed.

Step 2: Is it easy enough?

How many clicks/taps?
Are there unnecessary forms?
Does it fit into their current flow?

Fix: Remove friction. Make it stupidly simple.

Step 3: Only then — do they want to?

What's in it for them?
Does it connect to an existing desire?
Have you removed barriers that kill motivation?

Fix: Tie your feature to real user goals, not business goals.

💡
Remember: Fixing motivation is the last resort. If your prompt is invisible or your flow takes 20 minutes, no amount of excitement will help.

Real-World Example: BeReal

BeReal exploded in popularity by nailing all three ingredients.

Ingredient	How BeReal Delivered It
Prompt	Daily notification at a random time — surprising and impossible to ignore
Ability	One photo, under 2 minutes, no editing. Stupidly simple
Motivation	Authenticity + social connection + FOMO among Gen Z

Result? Apple's 2022 iPhone App of the Year. All because all three converged.

Apply This to Your Design Today

Pick a behavior you're trying to encourage. Now ask:

Question	Your Answer
Is there a clear, timely prompt?	Yes / No
Is the action as easy as possible?	Yes / No
Does the user genuinely want to do this?	Yes / No

Any box unchecked? That's your fix.

A Word on Ethics

With great power comes responsibility.

Dr. Fogg himself emphasizes two rules:

Help people do what they already want to do.
Help people feel successful.

Avoid dark patterns: fake countdowns, hidden costs, manipulative notifications. Design for user success, not just business metrics. Long-term trust beats short-term wins.

What's Coming Next in This Series Upcoming articles will cover:

Mental models for interaction design

Hick's Law and decision fatigue

Jakob's Law and user expectations

Peak-End Rule for memory retention

Fitts's Law and target sizing

Each piece builds on the last while standing alone for new readers.

My goal is to make these concepts accessible to anyone starting in UX — no jargon dumps, no gatekeeping.

Wrapping Up

The Fogg Behavior Model doesn't promise magic. But it does give you:

A diagnostic framework for stuck features
A prioritized checklist for improvement
A common language for your team

Remember: B = MAP. When a behavior isn't happening, one piece is missing. Find it, fix it, move on.

About the Author

I'm Ribin K Roy — software developer, UI/UX designer, and student learning in public. I document what I pick up along the way.

If you found this helpful, subscribe or follow wherever you're reading. The next article drops soon.