feature-onboarding

5 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Feature onboarding design principles

When designing feature onboarding, onboarding elements should be close to where the feature will live in perpetuity. Consider the primary task on a page before disrupting the user with a feature callout. Keep onboarding UI proportional to the functional hierarchy of the feature on the page. Make it clear how users can dismiss the message and return to their original task quickly. Maintain context if a call-to-action links to a new page by opening links in a new tab or window to avoid losing a user's work.

Feature onboarding campaign parameters

Create a new feature release timeline with clear parameters and ramp down plan. Define system triggers (e.g., a new feature released) and user triggers (e.g., a user visits a specific repository for the first time). For system triggers, a user should not need to dismiss the same announcement each time they visit a different repository. For user triggers, if recurring, a user should feel added value each time they see the message. Timebox coordinated campaigns to a maximum number of days across all targeted users. Specify a maximum number of impressions a user should see an in-product message and respect when a user dismisses a message. Consider how triggers may be tallied for users who belong to multiple repositories and organizations.

Feature onboarding alert collision limits

Avoid showing too many alerts at the same time. No more than 2 alerts should appear at once, as collisions are awkward and undesirable. Consider what other alerts, teaching bubbles, or banners may be active on the page when crafting an onboarding experience.

Feature onboarding sequence structure

Sequence tasks in a logical way to increase onboarding success. Treat feature onboarding as a story or journey with a beginning, middle, and end. Beginning: draw attention to the feature using teaching bubbles, alert banners, feature preview tray or announcement modals. Middle: guide users through their task using forms, checklists, or other components. End: celebrate the finish by clearly defining when a user successfully completes the onboarding flow and using a banner or other messages to confirm completion. Messages should be short and concise.

Feature onboarding best practices

Think creatively utilizing different ways to onboard users, including patterns not explicitly mentioned in the documentation. Create a well-rounded feature release campaign that may leverage both on and off-product avenues. Do not leave feature announcement campaigns running forever.

Give your agent this brain