HAPA / Health Action Process Approach by Ralf Schwarzer: An S-Tier Behavioral Designer’s Guide

Most behavior-change apps die at the same point. Not at the install. Not at the sign-up. At the gap between “I want to change” and “I changed today.” That gap has a name in health psychology — the intention-behavior gap, and Ralf Schwarzer’s Health Action Process Approach is the cleanest map of where products keep falling into it.

HAPA does something almost no popular behavior framework does. It treats motivation and willpower as two completely different problems with two completely different cures. The Fogg Behavior Model says B = MAP and stops. The Theory of Planned Behavior says intention predicts behavior and stops. HAPA says: forming an intention takes one set of beliefs, executing on it takes a different set of beliefs, and a product that only solves the first half is shipping half a behavior-change tool.

If you’ve ever wondered why a health app’s onboarding is brilliant and its 60-day retention is a slaughterhouse, you’ve already met HAPA. You just didn’t know its name.

Below is the S-Tier Behavioral Designer’s read on what Schwarzer actually built, where most product teams misuse it, what the Octalysis Framework adds that Schwarzer himself didn’t, and the specific design moves you should be making this quarter if your product depends on someone doing the same thing more than three Tuesdays in a row.

Speed Run Notes

• HAPA splits behavior change into two phases: Motivational (forming intention) and Volitional (acting on it), separated by Heckhausen’s Rubicon. Most products design phase one and lose users in phase two.
• Risk Perception, Outcome Expectancies, and Action Self-Efficacy form the intention. Risk Perception is the weakest of the three; designing around fear alone is the classic novice mistake.
• Action Planning (when, where, how) plus Coping Planning (what to do when the plan fails) is the volitional engine. Meta-analyses put Coping Planning as the single highest-leverage variable in the model.
• HAPA gives you three user states (Preintenders, Intenders, Actors) that each demand a different design surface. Shipping one onboarding for all three is why activation curves stall.
• Self-efficacy fractures into Action, Maintenance, and Recovery flavors. Recovery Self-Efficacy is the lapsed-user lifeline that almost every habit app under-engineers.
• HAPA pairs with Octalysis cleanly: Risk Perception is a CD8 diagnostic, Outcome Expectancies map to CD1+CD2, Action Self-Efficacy to CD4+CD3, the plans to CD4 ownership surfaces. Once you see it, you can’t unsee it.

About the Author

HAPA showed up in my work the same way most behavioral science does: through a client problem the existing playbook couldn’t solve. A health-coaching platform had an onboarding conversion that any growth team would envy and a 90-day retention curve that any growth team would hide. The diagnosis from their analytics vendor was “low motivation.” The diagnosis from HAPA, after one afternoon of mapping their funnel against Schwarzer’s two phases, was that they had designed an exceptional Motivational-phase product and shipped nothing for the Volitional phase. Once we wired Action Planning, Coping Planning, and Recovery Self-Efficacy surfaces into the post-activation loops, 90-day retention moved more than any onboarding A/B test had ever moved it. That experience — and a decade of variations on it across health, finance, and learning products — is why HAPA gets its own pillar in this library, and why I treat it as the single most under-cited model in commercial behavior-change design.

What Is the Health Action Process Approach?

The Health Action Process Approach is a model of health behavior change developed by Ralf Schwarzer at the Freie Universität Berlin, first published in 1992 and refined through the 2000s into the version most researchers and product teams use today. HAPA is a hybrid model — it borrows the construct of intention from the Theory of Planned Behavior, the construct of self-efficacy from Albert Bandura’s Social Cognitive Theory, and the action-phase logic from Heinz Heckhausen and Peter Gollwitzer’s Rubicon Model. What Schwarzer added is the explicit, mechanical separation between forming an intention and acting on one.

In HAPA, behavior change happens across two phases. The first is the Motivational phase, sometimes called the pre-decision phase. Here a person weighs risks, considers outcomes, and assesses their own capacity. Three constructs do most of the work: Risk Perception (do I believe this is a real threat to me?), Outcome Expectancies (do I believe the behavior will deliver the result I want?), and Action Self-Efficacy (do I believe I can do this in the first place?). Together they produce an intention.

The second is the Volitional phase, sometimes called the post-decision phase. Here a person who already intends to change must build the cognitive scaffolding for actually doing it. Two kinds of planning carry most of the load: Action Planning (the specific when, where, and how) and Coping Planning (the contingency strategy for when the original plan breaks). Two newer self-efficacy variants enter at this stage: Maintenance Self-Efficacy (can I keep this going under fatigue and competing demands?) and Recovery Self-Efficacy (can I get back on after I fall off?). Together these produce the actual behavior.

The boundary between the two phases is called the Rubicon, after Heckhausen’s borrowing of Caesar’s famous river-crossing. Once an intention is formed, the decision has been made and the cognitive task changes. You are no longer asking “should I?” You are asking “how exactly?” HAPA’s clinical and applied power comes from honoring this shift rather than pretending behavior change is one continuous motivational gradient.

One more piece is non-obvious until you’ve used the model on a real product. HAPA classifies people into three mutually exclusive stages: Preintenders, Intenders, and Actors, defined by where they are relative to the Rubicon. Preintenders haven’t decided. Intenders have decided but aren’t doing. Actors are doing. Each stage responds to a different intervention, and one of the most common product mistakes in behavior change is delivering Preintender content to Intenders or Actor content to Preintenders.

The Motivational Phase: How Intentions Are Built

Risk Perception: The Weakest of the Three Levers

Risk Perception is the question “how vulnerable am I to this threat?” In smoking cessation, it’s the perceived chance of getting lung cancer. In financial behavior, it’s the perceived chance of running out of money in retirement. In learning products, it’s the perceived chance of falling behind professionally if you don’t keep up. Researchers measure it as a function of perceived susceptibility and perceived severity, and HAPA assumes it contributes to intention formation but rarely dominates.

This is the first place a novice designer will misuse the model. Risk Perception is the lever the public-health establishment reaches for first because it’s the easiest to fund and the cheapest to test. Run a fear-appeal ad and measure intentions a week later. The trouble is that across hundreds of trials, Risk Perception turns out to be the weakest of the three Motivational-phase predictors of intention. Schwarzer’s own work, and subsequent meta-analyses by Sheeran, Maki, Montanaro, and others, consistently find that Outcome Expectancies and Action Self-Efficacy explain more of the variance in intention than Risk Perception does, often by a factor of two or three.

The product implication: an app that opens with statistics about how likely a user is to suffer some bad outcome is leaning on the least effective of the three levers. Users either dismiss the risk as not applying to them — what Neil Weinstein called “unrealistic optimism” — or they accept it, develop avoidance behavior toward the app itself, and uninstall. Risk Perception belongs in the model, but it should not be the load-bearing wall.

Outcome Expectancies: The Pro and Con List the Brain Actually Runs

Outcome Expectancies are beliefs about what will happen if the behavior is performed. They split into positive expectancies (“if I exercise three times a week, I’ll have more energy at work, sleep better, and feel less ashamed at the doctor’s office”) and negative expectancies (“it’ll cost me 90 minutes a week, my knees might complain, and my friends will mock the gym selfies”). Net positive expectancy predicts intention robustly across the HAPA literature.

The design lesson is that the brain does in fact run a mini pro-and-con list, and a product that surfaces both sides of that list honestly outperforms one that only sells the positive case. Apps that pre-empt the cost side — “this will take 12 minutes a day, here’s what you’ll likely give up” — tend to produce sturdier intentions than apps that only describe the upside. This is counterintuitive to marketing instincts but consistent with how Outcome Expectancies actually update in the user’s head.

Outcome Expectancies also have a time horizon, and the time horizon is where most behavior-change products fail. Distal outcomes (“you’ll live longer”) motivate weakly. Proximal outcomes (“you’ll sleep better tonight”) motivate strongly. The single most under-used trick in commercial HAPA design is the deliberate generation of proximal positive expectancies: outcomes the user will plausibly notice within seven days — alongside the distal ones the marketing team wants on the homepage.

Action Self-Efficacy: The Belief That You Can Even Start

Action Self-Efficacy is Bandura’s construct: the belief that you personally are capable of initiating the target behavior. Across HAPA studies, it is consistently the strongest single predictor of intention, stronger than either Risk Perception or Outcome Expectancies alone. If you only had room for one Motivational-phase intervention, this is the one you’d run.

Three things build Action Self-Efficacy in product contexts. The first is mastery experience, letting the user do a tiny version of the target behavior successfully inside the product. Duolingo’s first-lesson translation, before any account is created, is a textbook Action Self-Efficacy intervention. The user hasn’t intended anything yet, but they’ve already done a small version of the thing they’re considering committing to. The intention forms partly because the doubt about capacity has already been resolved.

The second is vicarious experience, seeing someone whose situation resembles yours succeed at the target behavior. This is why testimonial pages on health and fitness products that match the user demographically out-convert generic-success-story versions. The third is social persuasion combined with reduced anxiety. A coach or interface that explicitly says “people like you can do this” while also reducing the perceived cost of trying tends to build self-efficacy faster than either move alone.

The novice mistake here is treating Action Self-Efficacy as confidence-in-general. It isn’t. It’s domain-specific belief about initiating a particular behavior. A user can have rock-solid self-efficacy about coding and zero self-efficacy about flossing. Designing for Action Self-Efficacy means addressing the specific doubt about the specific behavior, not delivering generic motivational copy.

The Volitional Phase: How Intentions Become Behavior

Action Planning: Specifying the When, Where, and How

Action Planning is the cognitive process of specifying the situational conditions for the behavior — when it will happen, where it will happen, and what the entry move looks like. “I will exercise more” is an intention. “I will do twenty minutes of strength training on Monday, Wednesday, and Friday at 6:45 AM in my apartment using the dumbbells in the closet” is an Action Plan. The difference is mechanical: an Action Plan binds the behavior to specific situational cues so that when those cues arrive, the behavior fires with less deliberation.

Peter Gollwitzer formalized this construct as “implementation intentions”, if-then plans of the form “if Situation X arises, then I will perform Behavior Y.” A meta-analysis by Gollwitzer and Sheeran in 2006 across 94 studies found a medium-to-large effect (d ≈ 0.65) of implementation intentions on goal achievement, controlling for the strength of the underlying intention. That d ≈ 0.65 is the most quotable number in behavior-change psychology, and it’s the single number every product person should know cold. It means that asking your user to write down where and when they will perform a behavior produces, on average, a bigger effect than most clinical interventions and most marketing interventions you’ll ever run.

HAPA inherits the implementation-intention construct from Gollwitzer and bolts it into the Volitional phase as Action Planning. The product implication is that any commitment surface in your app — a goal-setting flow, an onboarding step, a planning widget: should be doing implementation-intention work, not just intention work. The difference between “I want to walk more” stored in your database and “On weekdays at 12:15 PM I will walk from the office to the coffee shop two blocks away” stored in your database is, mechanically, what determines whether the behavior fires.

Coping Planning: The Highest-Leverage Variable in the Model

Coping Planning is the cognitive process of specifying what you will do when the Action Plan breaks. “If I get to the gym and it’s too crowded, then I will do a bodyweight routine in the side hallway.” “If I miss my morning workout because of a work meeting, then I will do twenty minutes after dinner instead.” Coping Planning is also a class of implementation intention, but its trigger is a specific anticipated failure mode rather than a normal situational cue.

Schwarzer’s empirical work and subsequent reviews by Hagger and Luszczynska have repeatedly found Coping Planning to be a stronger predictor of long-term behavioral maintenance than Action Planning alone. The pattern is clean and consistent: products that build only Action Plans get a short-term lift; products that build both Action and Coping Plans get a maintenance curve that doesn’t collapse the first time something inconvenient happens.

This is the single most under-engineered layer in commercial behavior-change products. Almost every habit app I’ve seen will help a user form an intention and many will help them write a plan. Almost none will sit the user down and ask “what’s going to break this plan, and what’s your move when it does?” That question takes 30 seconds to ask and predicts 12-week adherence better than any onboarding tutorial. Adding it to a product is the closest thing to a free lunch in behavioral design.

Maintenance and Recovery Self-Efficacy: The Lapsed-User Lifeline

HAPA decomposes self-efficacy into three flavors across the two phases. Action Self-Efficacy lives in the Motivational phase and predicts whether someone forms an intention. Maintenance Self-Efficacy and Recovery Self-Efficacy live in the Volitional phase and predict whether they keep going.

Maintenance Self-Efficacy is the belief that you can keep up the behavior under conditions of fatigue, boredom, competing demands, and waning novelty. This is the construct that explains why Week 6 of a behavior change is harder than Week 1. The novelty has faded, the motivation that built the original intention has decayed, and the behavior is competing with everything else in the user’s life. Designing for Maintenance Self-Efficacy means giving users tools to expect, anticipate, and survive this dip, including normalizing it explicitly. Apps that say “Week 6 is when most people consider quitting; here’s what to do” outperform apps that hide the dip.

Recovery Self-Efficacy is the belief that you can get back on after you’ve fallen off. This one is rarely on a product team’s radar and almost always the difference between an app that retains lapsed users and one that doesn’t. A user who skips a workout, misses three days, then opens the app is in a delicate cognitive state. If the app shames them, even subtly — a broken streak counter, a guilt-trip notification, a passive-aggressive “you missed a day” — they uninstall. If the app says “welcome back; here’s a tiny re-entry sequence calibrated to your last 30 days,” they recover. The design move is to detect lapsed users not as failures to re-engage but as users in a specific cognitive state who need a Recovery Self-Efficacy intervention.

The lapsed-user welcome surface is, in my client work, the single highest-ROI Volitional-phase intervention available to a product. It costs almost nothing to build and prevents the cliff drop that kills most habit apps after Week 8.

Preintenders, Intenders, Actors: Three Users, Three Designs

Most product teams design one onboarding flow and one set of in-product surfaces and expect them to work on every user. HAPA tells you why that doesn’t work: at any given moment, your users are in three completely different cognitive states.

Preintenders haven’t decided yet. They downloaded the app because something nudged them, a friend, an ad, a doctor’s appointment. But they’re still doing the pro-con math. Showing them a calendar-style commitment widget on screen two is asking them to make a decision they haven’t yet made. The Preintender’s correct surface is information that updates Outcome Expectancies and Action Self-Efficacy: short demos, peer success stories that match their demographic, and the smallest possible mastery experience. Pushing a Preintender into the Volitional phase before they’ve crossed the Rubicon produces reactance and uninstall.

Intenders have decided but haven’t acted. Their cognitive task is no longer “should I?”: it’s “how exactly?” Showing them more motivational copy is wasting their attention on a problem they’ve already solved. The Intender’s correct surface is Action Planning and Coping Planning, when, where, how, and what to do when it fails. A well-designed Intender flow is closer to a high-end concierge intake than a feel-good pep talk.

Actors are doing the behavior. Their cognitive task is maintenance under fatigue, recovery after lapses, and progression toward more demanding versions of the behavior. Showing them Preintender content — fear appeals about not doing the thing they’re already doing, is at best wasted and at worst counterproductive. The Actor’s correct surface is feedback that supports Maintenance and Recovery Self-Efficacy, plus subtle progression that prevents staleness.

The design move is simple to state and hard to execute: classify your user into one of these three states, ideally on first session and continuously thereafter, and gate content by state. A health app that asks two screening questions on signup. “have you done X in the last month?” and “are you planning to do X this week?”, can route Preintenders, Intenders, and Actors into different flows with three SQL conditions. Most apps don’t, and they pay for it in activation and retention.

What Schwarzer Got Right

Schwarzer’s most important contribution is structural, not empirical. The empirical bricks — self-efficacy, implementation intentions, outcome expectancies: he borrowed from Bandura, Gollwitzer, and the Theory of Reasoned Action tradition. What he built that nobody else had was the explicit phase architecture that says these constructs don’t all do the same work at the same moment. Some build intentions. Some translate intentions into behavior. The same construct, like self-efficacy, performs different functions on different sides of the Rubicon.

This phase architecture is what makes HAPA useful for product design. The Theory of Planned Behavior tells you intention predicts behavior and stops; if your users have strong intentions and aren’t acting, TPB has nothing to say. HAPA has plenty to say, it tells you exactly which Volitional-phase construct is failing and what intervention targets it. The model doesn’t just describe behavior change; it diagnoses where in the process a particular product or person is stuck.

Schwarzer also got the empirical layering right. Most behavior-change models in the 1990s were trying to be parsimonious. Three constructs, four constructs, the smallest model that still predicts the outcome. HAPA went the other direction. It accepted that behavior change is a multi-stage process and added the constructs the data demanded, including the messy late-stage ones like Recovery Self-Efficacy that purer theorists tried to ignore. The model is more complicated than the Theory of Planned Behavior, and that complication is the point. The behavior is complicated. A model that pretends otherwise misleads.

Finally, Schwarzer and his collaborators were unusually disciplined about clinical translation. The model wasn’t published as a pure theory and then handed off to applied researchers. Schwarzer’s lab in Berlin, and parallel programs in Asia and Europe, ran HAPA-based interventions across dozens of health behaviors — physical activity, dietary change, smoking cessation, dental hygiene, breast self-examination, condom use, sun protection, medication adherence, and published the results, including the failures. The model survived contact with the real world better than most behavior-change theories of its generation precisely because it was tested in clinical and applied contexts from the beginning rather than as an afterthought.

Where HAPA Falls Apart

It Localizes Failure Inside the Person

HAPA is a model of intra-individual cognition. It assumes the bottleneck on behavior change is the person’s beliefs, plans, and self-efficacy. That assumption is correct enough of the time to be useful, but it understates how much behavior change is determined by structural and environmental conditions that no amount of planning can fix.

A low-income parent working two jobs in a food desert has perfectly reasonable Action Self-Efficacy, perfectly reasonable Outcome Expectancies, and well-formed Action and Coping Plans for healthier eating. What they don’t have is access to a grocery store with fresh produce within transit range or the time to cook a meal from scratch. Telling them to write better implementation intentions is not just useless. It’s a moral failure dressed up as behavioral science. HAPA, as a model, has no slot for “the environment doesn’t permit this behavior.” Researchers using HAPA know this; product designers using HAPA often don’t.

The applied fix is to run an external-barrier inventory before any Coping Planning surface fires. If the user’s main obstacle is access, cost, schedule, social context, or infrastructure, the right move is to reduce the structural barrier, not to ask the user to plan around it. Apps that skip this step and route every user through a generic Coping Planning flow can produce worse outcomes than no intervention at all, because the user concludes that even the app’s behavioral expert thinks the obstacle is their fault.

The Three-Stage Categorization Is Too Crisp

Preintenders, Intenders, and Actors look clean on a slide. In reality, users move between these states multiple times a week, and the boundaries are fuzzier than the model admits. A user can be an Actor on Monday, a Preintender on Tuesday after a bad weigh-in, and an Intender on Wednesday. The stage they’re “in” is partially a function of which question you just asked them.

This matters because the design move that follows from HAPA: gate content by stage, can produce thrash if the stage classification is too unstable. The applied adaptation is to use stage classification as a slow-moving filter rather than a session-by-session switch. Update it weekly or monthly, not on every login. And design the surfaces so that mis-classification is recoverable: a Preintender accidentally routed into Volitional content shouldn’t feel patronized, and an Actor accidentally routed into Motivational content shouldn’t feel demoted. The stages are useful; rigid implementations of them aren’t.

Social Variables Are Under-Specified

HAPA’s treatment of social context is thin. Social Cognitive Theory, from which Bandura’s self-efficacy concept comes, has rich theoretical machinery around modeling, social persuasion, and collective efficacy. HAPA collapses most of this into the Action Self-Efficacy construct and leaves the social environment as a vague background variable. The Theory of Planned Behavior at least carved out “subjective norms” as a distinct construct.

The product implication is that HAPA, used alone, will under-recruit Core Drive 5 (Social Influence & Relatedness) in the Octalysis sense. Teams that import HAPA without supplementing it with explicit social-design moves will ship behavior-change products that work for self-directed individuals and underperform for users whose behavior is socially entangled. The fix is to layer social mechanics — accountability partners, shared progress, group challenges, identity-relevant communities, on top of HAPA rather than expecting HAPA to surface them. Schwarzer wrote a theory of individual cognition. Healthy behavior happens in groups.

What’s Really Happening Inside the Brain

HAPA was written in the language of social-cognitive psychology, but it lines up cleanly with what cognitive neuroscience has since learned about goal pursuit. Three brain systems do most of the work the model describes.

The Motivational phase recruits the ventromedial prefrontal cortex and the orbitofrontal cortex — the regions that integrate predicted outcomes with subjective value. When a user evaluates Outcome Expectancies, this is the circuit doing the math. Risk Perception engages the same regions plus a posterior cingulate contribution that codes self-relevance: is this risk about me, or is it about people in general? The “unrealistic optimism” failure mode of Risk Perception interventions appears to be partially a failure of the self-relevance code to activate, the user processes the risk as abstract rather than personal.

Action Self-Efficacy and the other self-efficacy variants engage a different circuit centered on the dorsolateral prefrontal cortex and the parietal action-planning regions. Self-efficacy is, in a real sense, a forward simulation of capability — the brain runs a quick model of “could I actually do this?” and reports back. Mastery experiences strengthen this forward simulation because they update the prior on capability with direct evidence. Vicarious experiences update it with social evidence. Generic motivational copy doesn’t update it at all, which is why generic motivational copy is the weakest of the three Bandura-derived sources of self-efficacy.

The Volitional phase, especially the Action Planning and Coping Planning constructs, looks neuroscientifically like a delegation move. Implementation intentions appear to shift behavioral control from deliberative prefrontal circuits to more automatic posterior-parietal and basal-ganglia circuits. The famous Gollwitzer result: that if-then planning produces effects beyond intention strength, is most parsimoniously explained as the brain handing off the “fire on cue X” job to a more automatic system. The cognitive load of remembering and deciding drops; the situational cue becomes a sufficient trigger. This is why implementation intentions feel almost like a cheat code: they let conscious goal pursuit borrow the reliability of habit-based action without waiting for the habit to form through repetition.

The implication for product designers is that Action and Coping Plans aren’t just “writing things down.” They are deliberate delegations of behavioral control from a system that’s expensive and inconsistent to a system that’s cheap and reliable. Anything that interferes with the cue — vague timing, ambiguous location, missing if-then structure — disrupts the delegation. This is why a half-formed plan (“I’ll exercise more”) performs roughly the same as no plan at all and a fully-formed plan (“on weekdays at 7:00 AM I will walk for twenty minutes around the block before checking email”) performs dramatically better.

HAPA vs Other Behavior-Change Theories

HAPA vs the Theory of Planned Behavior

The Theory of Planned Behavior, formulated by Icek Ajzen, says intention predicts behavior, and intention is itself predicted by attitudes, subjective norms, and perceived behavioral control. It’s a clean, parsimonious model that has produced enormous amounts of research. The trouble is that TPB stops at intention. If your users have strong intentions and aren’t acting, TPB has nothing actionable to say.

HAPA is in many ways the answer to that limitation. It accepts that TPB-style constructs predict intention and then adds the Volitional phase to explain why intention doesn’t reliably predict behavior. A team that runs both models on the same data will typically find that TPB explains intention well, HAPA explains behavior well, and the gap between them is the intention-behavior gap. For commercial product work, HAPA is almost always the more useful of the two because the commercially interesting question is rarely “do users intend to engage?”, it’s “do they actually engage and keep engaging?”

HAPA vs the Transtheoretical Model (Stages of Change)

James Prochaska’s Transtheoretical Model breaks behavior change into five stages. Precontemplation, Contemplation, Preparation, Action, Maintenance: and prescribes different interventions at each stage. It’s the model most clinicians of a certain generation learned, and it’s the model still embedded in many addiction-recovery programs.

HAPA’s three-stage Preintender / Intender / Actor scheme is structurally similar but mechanistically tighter. The Transtheoretical Model’s stages are defined by behavioral intentions and recency, and the boundaries between them have been criticized as poorly operationalized. HAPA’s stages are defined by relationship to the Rubicon, have you crossed it, are you planning the crossing, are you already on the other side — which is conceptually cleaner. In product contexts, HAPA stages tend to be easier to operationalize from in-product signals: a user who has logged the target behavior at least once in the last seven days is an Actor; a user who has set a goal but not yet logged the behavior is an Intender; everyone else is a Preintender. The Transtheoretical Model’s five stages map less cleanly to product telemetry.

HAPA vs the Fogg Behavior Model

BJ Fogg’s Behavior Model says B = MAP, Behavior happens when Motivation, Ability, and a Prompt converge above an action line. It’s an elegant heuristic and a brilliant teaching tool. It is not, however, a theory of how motivation forms, how ability gets built, or how prompts get internalized over time. Fogg’s model is a snapshot of the moment behavior fires. HAPA is a film of the months before and after.

The two models are complementary rather than competitive. Fogg gives you the right vocabulary for designing the moment of action. Make the behavior easier, make the motivation higher, make the prompt unmissable. HAPA gives you the right vocabulary for everything around that moment, how the intention gets built before, how the plan gets formed, how the maintenance gets sustained, how the lapsed user gets recovered. A behavior-change product that uses Fogg without HAPA tends to over-engineer the moment of action and under-engineer everything around it. The reverse failure mode — HAPA without Fogg: produces beautifully theorized products that miss the practical mechanics of making the prompt fire at the right moment.

HAPA vs Implementation Intentions Alone

Implementation intentions, in Gollwitzer’s pure form, are the if-then planning construct that lives inside HAPA’s Action Planning slot. Some researchers and product teams use implementation intentions standalone, without the surrounding HAPA scaffolding. This works for users who are already firmly Intenders, they’ve decided, and the only missing piece is the plan. It works less well for the bigger commercial population, which is mostly Preintenders, because implementation intentions don’t tell you how to build the intention in the first place.

HAPA’s value over standalone implementation intentions is that it tells you what to do before someone is ready to plan and what to do after the plan starts breaking. For most products, the audience is too cognitively diverse for a single-construct intervention to cover. HAPA’s phase architecture is, in effect, a routing layer that decides which construct to deploy on which user at which moment.

HAPA in the Real World

Health and Fitness Apps

The cleanest commercial deployments of HAPA are in health and fitness, partly because that’s the domain Schwarzer’s research was based on. Noom, the weight-management app, runs an explicit two-phase architecture that maps closely onto HAPA. The onboarding focuses on Outcome Expectancies and Action Self-Efficacy. “here’s what people like you achieved, here’s a small first lesson you can complete now.” The in-product loops focus on Action Planning (meal logging windows, exercise scheduling), Coping Planning (the “what to do when you’re at a restaurant” content), and Recovery Self-Efficacy (the famous “if you ate the pizza, here’s how to think about it” messaging). The app’s higher-than-industry retention is, in my read, mostly a function of how well it staffs the Volitional phase, not a function of any particular feature.

MyFitnessPal, by contrast, has historically been an Action Planning tool — log your food, log your exercise, without much of the surrounding scaffolding. It’s enormously successful with Actor-stage users who are already committed, and it has a much harder retention story with Preintenders and Intenders, which is the population a freemium app most needs to convert. The fix, in HAPA terms, is to add Motivational-phase content and Coping/Recovery scaffolding rather than more Action Planning features.

Financial Behavior Apps

Financial wellness products have started reaching for HAPA explicitly in the last several years. Apps like Monarch Money and YNAB do parts of the volitional layer well. They make you author Action Plans for savings contributions, debt paydown schedules, and category budgets — but they tend to under-engineer the Recovery Self-Efficacy layer for users who blow a budget category. The user who overspends in a category and opens the app needs a Recovery flow, not a red bar and a shame notification. The few financial apps that have tried explicit Recovery surfaces, frame the overspend as data, surface the Coping Plan for next month, ask one question that resets the user as an Actor rather than a failure — show measurably better lapsed-user re-engagement.

Learning Apps

Duolingo has run something that looks like HAPA-shaped design for years without explicitly citing the model. The streak counter is, charitably, an Action Plan with a strong cue. The mid-streak repair feature (“if you missed yesterday, here’s a quick recovery”) is Recovery Self-Efficacy in product form. The leagues are a clumsy CD5 layer that probably under-performs what a pure Maintenance Self-Efficacy intervention would. The notable failure mode in Duolingo’s design is the lack of Coping Planning, the app doesn’t help users anticipate predictable failure modes (“you have a busy week, here’s a 90-second daily floor”) and instead penalizes the failure when it happens.

Calm and Headspace have similar profiles. Strong Motivational-phase content (the long-form essays on the benefits of meditation, the proximal-outcome framing of “five minutes for less stress today”). Strong Action Planning surfaces (the daily meditation widget, the scheduling reminders). Weak Coping Planning. Weak Recovery Self-Efficacy. The lapsed-user welcome flow on these apps is, across the board, a place where 15 minutes of HAPA-informed design would dramatically outperform the current state.

Public Health Campaigns

Outside of commercial apps, HAPA has informed dozens of public-health interventions across smoking cessation, dietary change, breast self-examination, sun-protection behavior, and dental hygiene. The Berlin lab’s most-cited applied paper, on dental flossing among adolescents, is a textbook example of phase-specific intervention design. Preintenders received content focused on Outcome Expectancies. Intenders received Action Planning prompts. Actors received Coping Planning content. The phase-tailored version outperformed a one-size-fits-all version by a meaningful margin, replicating across the studies that have used the same design.

The Elephant in the Room: The Intention-Behavior Gap

Across the behavior-change literature, one number keeps showing up. The correlation between intention and behavior, across meta-analyses by Sheeran and Webb in 2016 covering hundreds of studies, sits around r ≈ 0.5. Half the variance, give or take. Intention is by far the strongest single predictor of behavior, and it still leaves enormous room for non-action. People who say they will exercise often don’t. People who intend to take their medication often don’t. People who plan to floss often don’t. This gap. The gap between what people intend and what they do, is the elephant every behavior-change product is implicitly trying to solve.

HAPA’s claim is that this gap exists because intention formation and intention execution are different cognitive tasks that recruit different mental machinery. A product that addresses only the first task — that helps users build strong intentions: will plateau at the intention-behavior correlation ceiling. A product that addresses both will move users past that ceiling by activating the specific Volitional-phase machinery the brain uses to convert intention into action.

This is the elephant because it has a financial implication that most growth teams underweight. The marginal user who churns is rarely a user who never wanted to engage. They are, in HAPA terms, an Intender who was never given the right Volitional-phase scaffolding to become an Actor, or an Actor who was never given the right Maintenance and Recovery scaffolding to stay one. The marketing dollar that gets a new install is often producing a Preintender or a fragile Intender, not a paying Actor. The product dollar that activates Action Planning, Coping Planning, and Recovery Self-Efficacy is what converts that install into a long-term user.

The single biggest mental shift a product team can make from reading HAPA seriously is to stop confusing intention metrics with behavior metrics. Goal-setting completion rates, plan-creation rates, onboarding-finish rates. These are intention metrics. They tell you the user has crossed the Rubicon. They do not tell you the user will keep crossing it next Tuesday at 6 AM. The metrics that matter live downstream in the Volitional phase, and they’re the ones a HAPA-informed dashboard would put front and center.

How to Apply HAPA with the Octalysis Framework

The Octalysis Framework identifies the eight Core Drives that motivate every human behavior. HAPA gives you the cognitive architecture; Octalysis gives you the motivational palette to populate each cognitive slot. The two models compose unusually well because Schwarzer’s constructs map onto Core Drives almost one-to-one once you know what you’re looking at.

The Core-Drive Mapping

Risk Perception is a Core Drive 8 (CD8): Loss & Avoidance diagnostic. The user is computing the expected cost of not acting. CD8 is the right Core Drive to activate here, but it is the wrong Core Drive to lean on as a load-bearing wall. Use CD8 once, briefly, at the risk-articulation step, then route engagement through White-Hat Core Drives. Products that try to sustain motivation through ongoing CD8 — daily streaks framed as “don’t lose your progress,” shame notifications, fear-appeal nudges. Produce short-term compliance and long-term churn. HAPA’s empirical finding that Risk Perception is the weakest of the three Motivational-phase predictors is, in Octalysis terms, the same insight as “CD8 is a diagnostic Core Drive, not an engagement engine.”

Outcome Expectancies are a Core Drive 1 (CD1): Epic Meaning & Calling plus Core Drive 2 (CD2): Development & Accomplishment cocktail. Positive Outcome Expectancies, framed at the identity level (“you will become the kind of person who…”), recruit CD1. Framed at the achievement level (“you will hit the metric, finish the program, reach the milestone”), they recruit CD2. The best Outcome Expectancy framings deliberately blend the two. The Game Techniques that surface this are Calling #67 for CD1 identity anchoring, Narrative #10 for CD1 story anchoring, and Goal Setting #15 for CD2 achievement anchoring. Time-box the Outcome Expectancy step deliberately: the brain over-rewards extended fantasy and produces an Indulging failure mode that depletes rather than energizes motivation.

Action Self-Efficacy is a Core Drive 4 (CD4): Ownership & Possession plus Core Drive 3 (CD3): Empowerment of Creativity & Feedback construct. The user is asking “can I own this behavior?” (CD4) and “can I act competently on it?” (CD3). The Game Techniques are Avatars #1 for CD4 identification, Achievement Symbols #2 for CD4 progress representation, Real-Time Feedback #57 for CD3 capability evidence, and Step-by-Step Tutorial #13 for CD3 scaffolded mastery. The mastery experience that builds Action Self-Efficacy is, in Octalysis terms, a CD3 Real-Time Feedback intervention that converts external doubt into internal evidence.

Action Planning is a Core Drive 4 (CD4): Ownership & Possession surface, full stop. The user is authoring the plan; they own both halves of the if-then sentence. The Game Techniques are Plant Picker #44 for autonomy-supportive customization of the plan, and the tree-structured Step-by-Step Tutorial pattern for letting users design their own branching plan. Products that ship default plans rather than user-authored ones lose the CD4 reservoir and produce weaker downstream commitment.

Coping Planning is a Core Drive 4 (CD4) plus Core Drive 8 (CD8): Loss & Avoidance hybrid. The user is owning the plan (CD4) for what to do when failure threatens (CD8 deployed in its diagnostic position). The Game Techniques are the same Plant Picker pattern plus a Last Stand mechanic, a pre-committed move the user authors in advance for the moment things go wrong. Coping Planning is the cleanest single Octalysis intervention available to a behavior-change product because it activates two Core Drives in their respective right-place roles: CD8 for honest failure-acknowledgment, CD4 for ownership of the response.

Maintenance Self-Efficacy is a Core Drive 5 (CD5): Social Influence & Relatedness plus Core Drive 1 (CD1) surface. The user maintaining the behavior under fatigue is leaning on identity (CD1: I am the kind of person who does this) and social belonging (CD5: my people do this too). The Game Techniques are Mentor #74 for social-modeling support, Group Quests #22 for cooperative maintenance structures, and Narrative #10 for identity-continuity framing. The product surface that builds Maintenance Self-Efficacy is rarely a notification; it’s a community membrane and an identity mirror.

Recovery Self-Efficacy is the Core Drive 4 (CD4) lapsed-user lifeline. The user has fallen off; they need to re-own the behavior without first having to process shame. The Game Techniques are Last Stand recovery surfaces — pre-authored re-entry plans the user wrote during a strong moment, and Free Lunch #24 framing of the return: no penalty for the gap, just a clean re-entry. Recovery Self-Efficacy is the place where most product teams accidentally deploy CD8 as a load-bearing wall (broken streaks, guilt-trip notifications) and pay for it in churn. The Octalysis-correct move is to deploy CD4 ownership and CD1 identity continuity, with CD8 left out of the recovery surface entirely.

The Game-Technique Stack for a HAPA-Informed Product

The compact stack, ordered by phase:

• Motivational phase: Calling #67 (CD1), Narrative #10 (CD1), Goal Setting #15 (CD2), Real-Time Feedback #57 (CD3), Step-by-Step Tutorial #13 (CD3), Avatars #1 (CD4).
• Volitional phase, Action Planning: Plant Picker #44 (CD3 + CD4), Step-by-Step Tutorial #13 trees with user-chosen pathways (CD4).
• Volitional phase, Coping Planning: Plant Picker #44 (CD4), Last Stand pre-commitment (CD4 + CD8 diagnostic).
• Volitional phase, Maintenance: Mentor #74 (CD5), Group Quests #22 (CD5), Narrative #10 (CD1).
• Volitional phase, Recovery: Last Stand re-entry (CD4), Free Lunch #24 return framing (CD4 + CD7), explicit absence of CD8 surfaces.

The cocktail effect to watch for: CD8 deployed in any role other than the diagnostic position will undercut a HAPA-informed product. Risk Perception in onboarding, lapsed-streak guilt, and any “you might lose this” framing in maintenance will produce short-term compliance and long-term attrition. HAPA’s empirical finding that Risk Perception is the weakest of the three predictors and Coping/Recovery are the strongest is the same insight Octalysis encodes as the diagnostic-versus-engine distinction. Once you see it, you can audit any behavior-change product in 15 minutes against this stack and know exactly where the CD8 is being misused.

Seven Practical Steps to Run HAPA Inside Your Product

1. Classify your users into Preintenders, Intenders, and Actors on first session. Two screening questions (“have you done X in the last 30 days?” and “are you planning to do X this week?”) get you there. Update the classification weekly, not per session. Gate content on the classification so each user gets the right phase-specific surface.
2. For Preintenders, lead with Action Self-Efficacy, not Risk Perception. A 60-second mastery experience that lets the user successfully perform a tiny version of the target behavior beats any fear appeal. Risk Perception belongs in the model, not on the homepage.
3. Force a user-authored Action Plan with a specific situational cue and a specific response. “I will exercise more” is not a plan. “On weekdays at 7:00 AM I will walk twenty minutes around the block before checking email” is a plan. Parse the input for cue and response specificity at save time; reject under-specified plans politely.
4. Always pair Action Planning with Coping Planning. Always. The 30-second question “what’s going to break this plan, and what’s your move when it does?” is the single highest-leverage intervention in the model. Build the UI for it. Make it the second step after Action Plan creation, not an optional power-user feature buried three screens deep.
5. Engineer the lapsed-user welcome surface as a Recovery Self-Efficacy intervention. When a user returns after a 3-30 day gap, do not show them their broken streak, their missed days, or their lapsed-cohort cohort. Show them a clean re-entry calibrated to their last 30 days, their pre-authored Coping Plan, and a single small action that re-establishes them as an Actor. This is the highest-ROI surface most habit apps don’t ship.
6. Run the external-barrier inventory before any Coping Planning surface fires. Ask which obstacles are environmental, which are cognitive. Reduce the environmental ones via product design. Run Coping Planning only on the residual cognitive obstacles. Skipping this step is the political failure mode of behavior-change products deployed at scale.
7. Surface the user’s own if-then plan at the moment the cue fires. If the user wrote “if I feel the urge to skip the walk, I will put on my shoes anyway,” the product surfaces that exact sentence at the moment the cue is most likely to be relevant. The delegation from deliberative to automatic control is what produces Gollwitzer’s d ≈ 0.65 effect. The product is the cue.

HAPA Was the Beginning, Not the End

Schwarzer published HAPA in its first form in 1992. Three decades later, the model has been refined, extended, and embedded in dozens of clinical and applied interventions. The current frontier is in two directions.

The first is adaptive Action Planning. The original implementation-intention construct treats the if-then plan as fixed. Recent work. Bélanger-Gravel and colleagues, plus the broader “habit replacement” literature, explores plans that update when the original cue stops firing. The product implication is that a HAPA-informed system shouldn’t lock the user into the if-then sentence they wrote in week one; it should detect when the cue stops triggering the response and prompt for an updated cue-and-response pair. This is closer to how habits actually decay and re-form in real life, and it’s the next generation of what most product teams currently ship as static goal-setting.

The second frontier is in machine-personalized phase classification. The Preintender / Intender / Actor scheme works, but the boundaries are fuzzy enough that human-authored heuristics produce mis-classifications. Several research groups are now training models on in-product telemetry to classify phase state continuously and update intervention selection accordingly. The behavioral-design risk is obvious: optimizing too aggressively for short-term engagement metrics will produce CD8-heavy interventions that the user can’t articulate why they hate. The behavioral-design opportunity is to use the same telemetry to deploy Recovery Self-Efficacy interventions earlier, more accurately, and with less product-team labor than is currently possible.

HAPA is not, and was never meant to be, a final theory of behavior change. It is a load-bearing wall in the broader architecture of how products can responsibly help people change behavior, and it earns that load-bearing role because it treats the Volitional phase with the seriousness most other models reserve for the Motivational phase. The product implication is that any team designing for behavior change should be able to point at the place in their product where Action Planning happens, the place where Coping Planning happens, and the place where Recovery Self-Efficacy is supported. If they can’t point at those three places, they are shipping half a behavior-change product.

Frequently Asked Questions

What does HAPA stand for?

HAPA stands for Health Action Process Approach. It was developed by Ralf Schwarzer, then at the Freie Universität Berlin, with the first published formulation in 1992 and substantial refinement through the early 2000s. The “health” in the name reflects its origin in health-behavior research, but the model has since been applied to financial behavior, learning, environmental behavior, and any context that involves bridging an intention to a sustained action.

How is HAPA different from the Theory of Planned Behavior?

The Theory of Planned Behavior (TPB), formulated by Icek Ajzen, predicts behavior from intention and stops there. HAPA accepts TPB’s account of how intentions form and adds an explicit Volitional phase that explains why intentions don’t reliably predict behavior. The two models overlap on the Motivational side; HAPA extends meaningfully on the post-intention side, which is the side most behavior-change products actually need.

What is the intention-behavior gap and how does HAPA address it?

The intention-behavior gap is the discrepancy between what people intend to do and what they actually do. Meta-analyses by Sheeran and Webb find the gap consistently — intention and behavior correlate at roughly r ≈ 0.5, leaving substantial unexplained variance. HAPA addresses the gap by identifying the specific Volitional-phase constructs (Action Planning, Coping Planning, Maintenance Self-Efficacy, Recovery Self-Efficacy) that translate intention into action and then maintain it.

Which HAPA construct has the largest effect on long-term behavior?

Across multiple meta-analyses, Coping Planning emerges as one of the strongest predictors of long-term behavioral maintenance, often outperforming Action Planning alone. Coping Planning specifies what the user will do when the original plan breaks: and because plans always break, the product that supports Coping Planning systematically outperforms the product that only supports Action Planning. Recovery Self-Efficacy is the complementary high-leverage construct for already-lapsed users.

What is the Rubicon in HAPA, and why does it matter?

The Rubicon is HAPA’s name for the cognitive transition from forming an intention to acting on one. The term comes from Heinz Heckhausen and Peter Gollwitzer’s Rubicon Model of action phases, which in turn borrows from Caesar’s famous river-crossing. The Rubicon matters because it marks a real shift in the cognitive task: pre-Rubicon, the user is deciding; post-Rubicon, the user is executing. Different constructs are operative on each side, which is why HAPA insists on the two-phase architecture.

How do Preintenders, Intenders, and Actors differ in product design?

Preintenders haven’t decided to act; they respond to Outcome Expectancies content, Action Self-Efficacy mastery experiences, and small demonstrations. Intenders have decided but haven’t acted; they respond to Action Planning and Coping Planning surfaces. Actors are performing the behavior; they respond to Maintenance and Recovery Self-Efficacy support. A product that ships one onboarding for all three states is producing reactance in the Preintenders, redundancy for the Intenders, and irrelevance for the Actors.

Can HAPA be used outside of health behavior?

Yes. The model was developed in health contexts but applies cleanly to any behavior that requires sustained action against competing demands. Financial-wellness, learning, environmental-behavior, and workplace-behavior products have all used HAPA-shaped designs. The constructs, risk perception, outcome expectancies, self-efficacy, action planning, coping planning. Translate across domains with minimal modification. The “health” in the name reflects origin, not scope.

How does HAPA relate to implementation intentions?

Implementation intentions, in Peter Gollwitzer’s formulation, are the if-then plans that live inside HAPA’s Action Planning construct. Gollwitzer and Sheeran’s 2006 meta-analysis across 94 studies found a medium-to-large effect (d ≈ 0.65) of implementation intentions on goal achievement. HAPA incorporates implementation intentions as one of its Volitional-phase mechanics and extends the surrounding architecture, what happens before the plan is formed (Motivational phase), what happens when the plan breaks (Coping Planning), and what happens after the user falls off (Recovery Self-Efficacy).

What’s the most common product mistake when applying HAPA?

Designing only for the Motivational phase. Most behavior-change products invest heavily in onboarding — strong Outcome Expectancies framing, peer success stories, fear-appeal copy — and then ship a thin Volitional phase consisting of a goal-setting screen and notifications. The result is a product that produces strong intentions and weak behavior, and the analytics show up as great activation curves and bad retention curves. The fix is to invest at least as much design effort in Action Planning, Coping Planning, Maintenance Self-Efficacy, and Recovery Self-Efficacy as goes into the Motivational-phase onboarding.

How does HAPA interact with the Octalysis Framework?

The two models compose cleanly. HAPA gives you the cognitive architecture: which mental task is operative at which phase, while Octalysis gives you the motivational palette to populate each cognitive slot with the right Core Drive activation. Risk Perception maps to CD8 in its diagnostic role; Outcome Expectancies map to CD1 + CD2; Action Self-Efficacy maps to CD3 + CD4; the planning constructs map to CD4 ownership surfaces; Maintenance and Recovery Self-Efficacy map to CD5 + CD1 and CD4 + CD1 respectively. The Octalysis layer answers “which Core Drive should this surface activate?” while HAPA answers “what cognitive task is the user actually trying to complete here?”

References

1. Schwarzer, R. (1992). Self-efficacy in the adoption and maintenance of health behaviors: Theoretical approaches and a new model. In R. Schwarzer (Ed.), Self-efficacy: Thought control of action (pp. 217–243). Hemisphere.
2. Schwarzer, R. (2008). Modeling health behavior change: How to predict and modify the adoption and maintenance of health behaviors. Applied Psychology: An International Review, 57(1), 1–29.
3. Schwarzer, R., Lippke, S., & Luszczynska, A. (2011). Mechanisms of health behavior change in persons with chronic illness or disability: The Health Action Process Approach (HAPA). Rehabilitation Psychology, 56(3), 161–170.
4. Schwarzer, R., & Luszczynska, A. (2008). How to overcome health-compromising behaviors: The Health Action Process Approach. European Psychologist, 13(2), 141–151.
5. Sniehotta, F. F., Schwarzer, R., Scholz, U., & Schüz, B. (2005). Action planning and coping planning for long-term lifestyle change: Theory and assessment. European Journal of Social Psychology, 35(4), 565–576.
6. Sniehotta, F. F., Scholz, U., & Schwarzer, R. (2005). Bridging the intention–behaviour gap: Planning, self-efficacy, and action control in the adoption and maintenance of physical exercise. Psychology & Health, 20(2), 143–160.
7. Luszczynska, A., & Schwarzer, R. (2003). Planning and self-efficacy in the adoption and maintenance of breast self-examination: A longitudinal study on self-regulatory cognitions. Psychology & Health, 18(1), 93–108.
8. Zhang, C. Q., Zhang, R., Schwarzer, R., & Hagger, M. S. (2019). A meta-analysis of the Health Action Process Approach. Health Psychology, 38(7), 623–637.
9. Hagger, M. S., & Luszczynska, A. (2014). Implementation intention and action planning interventions in health contexts: State of the research and proposals for the way forward. Applied Psychology: Health and Well-Being, 6(1), 1–47.
10. Gollwitzer, P. M. (1999). Implementation intentions: Strong effects of simple plans. American Psychologist, 54(7), 493–503.
11. Gollwitzer, P. M., & Sheeran, P. (2006). Implementation intentions and goal achievement: A meta-analysis of effects and processes. Advances in Experimental Social Psychology, 38, 69–119.
12. Sheeran, P., & Webb, T. L. (2016). The intention–behavior gap. Social and Personality Psychology Compass, 10(9), 503–518.
13. Bandura, A. (1997). Self-efficacy: The exercise of control. W. H. Freeman.
14. Heckhausen, H., & Gollwitzer, P. M. (1987). Thought contents and cognitive functioning in motivational versus volitional states of mind. Motivation and Emotion, 11(2), 101–120.
15. Ajzen, I. (1991). The theory of planned behavior. Organizational Behavior and Human Decision Processes, 50(2), 179–211.

Related Reading

• WOOP / Mental Contrasting (Oettingen): An S-Tier Behavioral Designer’s Guide
• The Self-Concordance Model (Sheldon & Elliot): An S-Tier Behavioral Designer’s Guide
• Hope Theory (Snyder): An S-Tier Behavioral Designer’s Guide
• Self-Determination Theory: The Complete Guide to Ryan and Deci’s SDT Framework
• The Behavioral Framework Library

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