Skip to main content
Designhashgraph-online

exposure-onboarding

Use the exposure effect deliberately in onboarding and habit formation — getting users to repeated, low-friction encounters with the product so familiarity builds and preference forms. Use when designing onboarding flows, planning feature introductions, building user habits, or evaluating why users churn after first use. The exposure effect operates over time; products that get users to come back early benefit from accumulated familiarity that single-session products don''t.

Stars
336
Source
hashgraph-online/awesome-codex-plugins
Updated
2026-05-27
Slug
hashgraph-online--awesome-codex-plugins--exposure-onboarding
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/hashgraph-online/awesome-codex-plugins/HEAD/plugins/HDeibler/universal-design-principles/plugins/aesthetics-and-emotion-principles/skills/exposure-onboarding/SKILL.md -o .claude/skills/exposure-onboarding.md

Drops the SKILL.md into .claude/skills/exposure-onboarding.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

Exposure Effect — onboarding and habit

The exposure effect operates through repetition. A user who encounters your product once is at the start of the curve; a user who encounters it daily for a week is much further along. Designing onboarding to maximize early exposure — getting users back into the product repeatedly with low friction — builds the familiarity that supports long-term retention.

The first-week imperative

Most product churn happens in the first week. Users who don't return within a week typically don't return at all. The mechanism is exposure: users who don't return haven't built enough familiarity for the exposure effect to operate. Their initial impression doesn't have time to consolidate.

Products that successfully retain users almost always achieve high first-week return frequency. Whether this is by:

  • Genuinely useful daily-use cases (calendar, email, messaging).
  • Notification-driven re-engagement (within reasonable limits).
  • Ritual integration (a morning reading habit, a daily check-in).
  • Deliberate first-week onboarding that brings users back.

The retention pattern is consistent: repeated exposure in the first week predicts long-term retention.

Designing for early exposure

Reduce friction to return. The lowest-friction return is no friction at all — push notifications, email reminders, or other prompts. The next-lowest is one-tap return (an icon on the home screen, a saved tab). Anything that requires effort to return reduces return frequency.

Give users a reason to return. New content, updated information, social interaction, scheduled events, recommendations. Each return has to deliver something; otherwise the exposure cost outweighs the benefit.

Make first sessions complete enough to return for. A user who completes a meaningful task on first session has a positive memory to return to. A user who didn't complete anything has no positive baseline.

Build in natural use cycles. Daily check-in, weekly review, morning catch-up — habits that align with users' existing routines.

Leverage notifications carefully. Notifications can drive return but can also build resentment. The right level of notification varies by product and user; over-notification is the most common failure mode.

What "low friction" means

Friction in this context is anything that costs the user time or attention to return to the product:

  • High friction: open a browser, type a URL, log in, navigate to the relevant section.
  • Medium friction: open a saved tab or bookmarked link, then navigate.
  • Low friction: open the app from the home screen.
  • Very low friction: tap a notification that takes you directly to the relevant content.
  • Negative friction: the relevant content surfaces ambient (a watch face, a widget, a daily email).

Each step down the friction ladder dramatically increases the return rate. The exposure effect needs return; whatever friction you can eliminate from return makes the effect work harder for you.

Worked examples

A meditation app's first-week design

A meditation app onboards users with:

  • Day 1: 5-minute introductory session; immediate value.
  • Day 2: notification reminder; another 5-minute session.
  • Day 3: notification with a curated session matching the user's first-day choice.
  • Day 4: a celebration of "3 days in a row" with a slightly longer session.
  • Day 5–7: continued reminders and varied content.

By day 7, the user has had 5–7 exposures, has formed a small habit, and has experienced the product's value repeatedly. The exposure effect has operated; the user now likes the app more than they would after a single session.

This pattern (reminders + valuable content + habit cues) is common across successful habit-forming apps.

A productivity tool that fails to onboard for return

A productivity tool gets users to sign up. They complete onboarding. They use the tool for an hour, find some value. Then they don't return for 3 weeks; when they do, they've forgotten how it works. They get frustrated and stop using it.

The failure: no mechanism to bring users back in the first week. Without repeated early exposure, the familiarity didn't consolidate; the next session felt like starting over; the product never became part of the user's routine.

The fix: notification campaigns in the first week reminding users of the value; weekly digest emails; integration with calendar / email so the product surfaces in existing workflows.

A reading app with daily content

A reading app delivers a curated article to users daily. Users open the app each morning to read the day's article. The content delivery is the return mechanism; the exposure effect operates through the daily ritual.

Over weeks and months, users develop strong preference for the app. Even if a competitor launched with technically better features, the daily-habit familiarity would keep users with the original.

Notifications that backfire

A new social app sends 5–10 notifications per day to new users to drive engagement. Initial engagement is high. After a week, users are exhausted; many uninstall the app or disable notifications.

The mechanism: too much exposure, the wrong kind. The notifications became an annoyance rather than a positive prompt. The exposure effect requires positive or neutral experiences; pestering users creates negative association.

The fix: calibrate notification frequency. Send fewer notifications; make each one more valuable. Let users control the cadence.

A B2B SaaS with weekly value

A B2B analytics tool delivers a weekly summary email of insights from the user's data. Users open it once a week to see what's interesting. The email has a one-click path back to the full product.

This pattern works for tools that don't need daily use but benefit from weekly check-ins. The weekly cadence is enough to maintain familiarity; the weekly email is the return mechanism.

Anti-patterns

Onboarding without ongoing engagement. A great onboarding experience that ends after day 1. The user has been introduced to the product but isn't being brought back.

Over-notification. Too many or too irrelevant notifications. Builds resentment rather than habit. The most common failure mode in product growth.

Friction at the return path. A login required every time; an app that takes 10 seconds to load; a path to relevant content that takes 5 navigation steps. Each friction reduces return rate.

Generic re-engagement. Notifications that don't show the user that the product has paid attention. "Come back to the app!" without specifics is less effective than "Your weekly summary is ready" or "John commented on your post."

Assuming users will come back on their own. Most users won't. Without active re-engagement, the early-week exposure won't happen.

Deferring monetization until familiarity exists, but then not building familiarity. Strategy of "we'll monetize later" only works if you actually build the user base; without exposure-driven retention, there's nothing to monetize later.

Heuristic checklist

When designing for early exposure, ask: What's the first-week return frequency we're targeting? Be specific. What's the mechanism for return? Notifications, email, habit, ritual. Is the friction to return low enough? Each step costs return rate. Does each return deliver something specific? Generic "come back" isn't enough. Are we calibrated to avoid annoyance? Over-notification is the most common failure.

Related sub-skills

  • exposure-effect — parent principle on the mere-exposure phenomenon.
  • exposure-redesign-risk — sibling skill on managing accumulated familiarity during redesigns.
  • feedback-loop — early feedback supports the value that brings users back.
  • mental-model — the mental model is built through exposure.
  • hierarchy — first sessions should foreground the value; bury complexity.

See also

  • references/onboarding-cadences.md — patterns for first-week onboarding cadences.